Every small team runs some version of the same broken meeting: the manager asks for updates, the employee recites them from the project board they both can already see, and thirty minutes later nothing has been decided and nothing unsaid has been said. It's the most expensive recurring meeting you run — two people, every week, all year — and it's usually spent reading status aloud.
Here is the reframe: the 1:1 is the employee's meeting, not yours. You are not collecting updates — you are removing obstacles, hearing things before they become resignations, and making decisions the person can't make alone. If the manager talks for more than half the meeting, it isn't a 1:1; it's a slow staff meeting.
The standing agenda: five items, thirty minutes, same order every week
The order matters because the last ten minutes get squeezed — and the items at the end are the ones that quietly never get discussed:
- What's blocking you? (10 min) — the obstacles only they can name and only you can move. Every blocker gets an owner and a date, yours. "I'll chase [X] by Thursday" said in a 1:1 is a promise with a witness.
- What's in flight? (5 min) — two minutes per project: name, state, next milestone. This is the meeting's header, not its body.
- Feedback, both directions (5 min) — one specific thing each way. The manager's half is easy and therefore skipped; the employee's half only happens if you ask and then hold still.
- Career and capacity (5 min) — more of what, less of what, what they'd like to learn. This is where retention is won in small teams.
- Housekeeping (5 min) — holidays, expenses, tools. Last because it's the safest place to run over.
The agenda file is shared and pre-filled all week — the night before a hard conversation is when people actually write things down. And cancellation goes one way: the manager can move the meeting, but not skip it without a note that says why and when it resumes.
The two questions that do the work
If the meeting has an agenda, these two questions are what the agenda was protecting:
- "What's slowing you down that you haven't told me?" — the unsaid blocker is the expensive one. The first answer is a deflection, the second is a fact, and the pause between them is the meeting.
- "What do you want here that you haven't asked for?" — more scope, a title, remote days, off one project. People don't volunteer wants to the person who pays them; asking once a quarter makes it normal. A request remembered is retention; a request forgotten is the exit interview.
The notes ledger: why the meeting compounds
The 1:1 that changes nothing is the one whose decisions evaporate in the hallway. Keep one shared note per person, three lists per meeting, every item dated:
- Decided — one line per decision with the date.
- Owed by me — what the manager promised, with the due date. You chase your items at the top of next week's meeting, unprompted. Nothing signals the meeting matters like your own blockers getting moved.
- Owed to me — what the employee took on. No dangling "look into it" — either a date or it leaves the list.
Open next week by reading last week's lists: closing last week's loops takes two minutes and is the difference between a meeting and a chat. After a quarter the ledger doubles as review evidence — the promotion case cites dates, not memories.
The weekly is not the only 1:1
- Weekly (30 min) — the default, every direct report, no exceptions.
- Monthly deep-dive (60 min) — three questions sent the day before: What went well? What was wasted? What do you want next quarter?
- Skip-level (quarterly) — ground rule said out loud: "I'll keep what you tell me private unless it's a safety or conduct issue." The middle manager always knows the meeting happened.
- The exit 1:1 (within a week of a resignation) — the exit interview gets form answers; this one gets the truth. One question: "What should have been different this year?" Written down verbatim.
A six-person studio, six weeks
Founder-run design studio: decisions made in conversations nobody else saw, tasks floating between people, and a senior designer who announced a resignation in the project meeting "because it was the only time anyone would listen." Standing 1:1s started week one with the ledger; week two the founder closed his own owed item unprompted and the designer moved her private list of stalled requests into the file; week three the two-question routine surfaced what she hadn't asked for — the client-facing work the founder was quietly keeping for himself. By week six the resignation was withdrawn, not because of a raise but because the frustration had been named and given a date. Ad-hoc interruptions dropped to near zero because they had somewhere to go, and the eighty-minute all-hands became thirty.
The scorecard
- Held rate ≥ 90% — cancelled-with-note counts as held; cancelled-last counts as missed. The calendar is telling the truth the org chart won't.
- Loop-closure ≥ 80% — your own "owed by me" items closed within a week.
- One new item per person per month — a quarter with zero new blockers or requests from someone means the meeting isn't safe yet.
The full version — the four 1:1 types in detail, the five traps, and the copy-paste one-page template — is on the ops notes page: One-on-One Meeting Template for Small Teams. If the person you're meeting is new, start with Employee Onboarding Checklist — the first 1:1 is the last item on it.
Top comments (0)