Their meeting, not your status update. The moment it becomes a progress report it stops surfacing anything useful.
10 min read · Level 3
It is their meeting, and the moment it becomes your status update it stops surfacing the things it exists to surface. The problems that damage companies are usually known by someone for weeks before they reach the founder; a regular private half hour is the cheapest mechanism for shortening that delay. Cancelling it under pressure removes the early-warning system exactly when pressure makes problems most likely.
A recurring private conversation between a manager and someone who reports to them. Typically 30 minutes, weekly or fortnightly, with the agenda owned by the person being managed.
Its purpose is to surface things that would not otherwise reach you: blockers, frustrations, ideas, and concerns people will not raise in a group.
Because the problems that damage a company are usually known by someone for weeks before they reach the founder. A regular private conversation is the cheapest mechanism for shortening that delay.
And because people leave managers rather than companies. A half hour of genuine attention every week is most of what makes someone feel their work is seen.
A bad 1:1: the manager runs through a task list, asks for status on each, gives some updates, and ends. Twenty-five minutes of information that a written update would have carried better.
A good 1:1 opens with 'What's on your mind?' and then mostly listens.
What surfaces in a good one: 'I'm not sure the activation goal is achievable with the current onboarding.' 'I found the way that feedback was given in standup difficult.' 'I think we should stop the paid channel — I've been sitting on that for two weeks.'
None of these appear in a status report. All three matter. And the third one — a real opinion held privately for a fortnight — is precisely what the meeting exists to extract.
A useful default split: they talk for twenty minutes, you talk for ten.
First-time founders often cancel 1:1s when busy. Cancelling repeatedly signals that the person is optional, and it removes the channel exactly when pressure makes problems most likely.
The second mistake: using it to give instructions. That is a different meeting. Instructions can be written; the 1:1 is for what cannot.
The third: no notes and no follow-through. If someone raises the same blocker three times and nothing changes, they stop raising things — and you have lost the mechanism entirely.
Same time weekly or fortnightly. Move it rather than cancelling it, and say why.
Ask them to bring topics. Open with 'what's on your mind?' rather than a list of yours.
Roughly two-thirds them. If you are doing most of the talking, it has become a status meeting.
'What is slowing you down?' and 'what would you change if it were your call?' both reliably surface real things.
Revisit last week's items first. Following through is what makes people keep raising things.
Career direction, what they want to be doing in a year. Not every week, but not never.
From your first employee. With two people it is informal; with five it must be scheduled.
Not a substitute for immediate feedback. If something needs saying today, say it today rather than saving it for Thursday.
"I don't think the activation goal is achievable with the current onboarding." "I found the way that feedback was given difficult." "I've thought for two weeks we should stop the paid channel." None of these appear in a status report, and the third — a real opinion held privately for a fortnight — is precisely what the meeting is for.
Open with "what's on your mind?" and then be quiet. The useful sentence usually arrives after a silence you were tempted to fill.
If someone raises the same blocker three times and nothing changes, they stop raising things — reasonably, having concluded it achieves nothing. The mechanism does not fail loudly; it just quietly stops producing information while the meeting continues.
Revisit last time's items first, every time. Follow-through is the entire reason anyone tells you anything difficult.
Create a free account to read the rest and apply it to your own startup.