1:1s That Don't Suck: An Operating Model for Managers Who Hate Meetings
Most 1:1s degrade into status updates. A simple structure — and one tool change — turns them back into the highest-leverage hour on a manager's calendar.
The status-update failure mode
If the 1:1 has become a verbal version of Jira, you're using the wrong forum. Status belongs in async; 1:1s belong to growth, blockers, and signal.
The 3-bucket structure
Bucket 1: their agenda (10 minutes). Bucket 2: feedback both directions (15 minutes). Bucket 3: career and growth (5 minutes). Skip status entirely.
The tool change
Shared agenda doc, updated by the report in advance. If they didn't update it, the meeting is shorter, not longer. Forcing function for thoughtful 1:1s.