No Status Updates, How I Do One-on-Ones
summary
Manager role focuses on people not tasks, removing blockers and building trust; one-on-ones stop being status reports and become coaching sessions that surface highlights, blockers, and specific asks, record commitments, and follow up. Status is easier to fetch automatically or from GitHub/GitLab/Jira, so meetings run on an every-other-week 30-minute cadence (extendable to 1 hour), include shared agendas, concrete feedback questions, confidentiality agreements, and documented follow‑ups so promises get kept.
AI-written summary · about
chapters (16)
- 0:00One-on-ones without status updates
- 2:53Status updates unnecessary
- 6:42Core goals of one-on-ones
- 8:48One-on-ones for employees
- 10:57Preparing one-on-one meetings
- 13:52Giving and receiving constructive feedback
- 17:00Active listening importance
- 18:42Discussing news openly
- 20:50Handling meeting cancellations
- 22:58Key takeaways
- 24:22Q&A: No discussion topics
- 26:10Q&A: Engaging reserved members
- 27:34Q&A: Confidentiality
- 29:40Q&A: Duration and non-work topics
- 31:28Q&A: Career growth for managers
- 32:31Q&A: Sharing accomplishments
related talks
34mHow to do one-on-one meetings the right way
19mOops I'm a Manager - On More Effective 1-on-1 Meetings
37mOne-on-One: the benefit you should look for
11mCrafting effective 1:1s for distributed teams
41mDesigning your 1:1 - The most important meeting in your career
07m"Are you a good or bad manager?"
46mCracking the cadence of your software engineering 1:1s
31mManaging Meetings Without Succumbing to Zoom Fatigue