One-on-one meetings for small teams — the standing agenda, the two questions, and the notes ledger

A one-on-one is the most expensive recurring meeting in a small team — two people, every week, all year — and the most commonly wasted, because it gets run as a status report the manager asks for instead of a meeting the employee owns. Status already lives in your standup notes and your project board; a meeting that repeats it is two salaries spent reading aloud. This page is the alternative: a standing five-item agenda that fits thirty minutes, the two questions that actually produce the truth, the notes ledger that makes promises survive the meeting, and the four variants (weekly, monthly deep-dive, skip-level, exit) that cover the cases the weekly can't. When the person you're meeting is new, start from the employee onboarding checklist — the first 1:1 is the last item on it.

1. The rule: it's their meeting — which means the agenda lives with them

The single change that fixes most 1:1s: the employee owns the agenda document, the manager keeps the questions. You are not there to collect updates — you are there to remove obstacles, hear things before they become resignations, and make decisions the person can't make alone. If the manager is talking for more than half the meeting, it isn't a 1:1; it's a slow staff meeting. Three consequences of the rule:

• The agenda file is shared and pre-filled. Both of you can add items all week — the night before a hard conversation is when people actually write things down. A 1:1 that starts from a blank page starts with five minutes of “so… what's new?”
• Cancellation goes one way. The manager can move it, but not skip it without a note that says why and when it resumes. A skipped 1:1 with no explanation reads as “you're not worth the half hour” — and it's the note the person quotes when they leave.
• Small talk opens, work closes. Two minutes of human first, then the agenda. The reverse — work first, then “anyway… how's everything?” — is how important things stay unsaid.

2. The standing agenda: five items, thirty minutes, every week

Same five items every week, in this order. The order matters: blockers before career, career before housekeeping — because the last ten minutes get squeezed and the items at the end are the ones that quietly never get discussed.

1. What's blocking you? (10 min) The obstacles only they can name and only you can move: the approval that takes a week, the person who never replies, the tool that needs a licence. 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.
2. What's in flight? (5 min) Two minutes per project only — name, state, next milestone. This is the 1:1's version of a header, not its body. Detail belongs in the project channel, where everyone can see it.
3. Feedback, both directions (5 min) One specific thing each way: something to keep doing, something to change. The manager's half is easy and therefore skipped; the employee's half only happens if you ask and then hold still while they answer.
4. Career and capacity (5 min) What they want more of, what they want less of, what they'd like to learn. In small teams this is where retention is won — the person who's been doing invoices for nine months doesn't leave over money, they leave over invoices.
5. Housekeeping and logistics (5 min) Holidays, expenses, tools, the form nobody can find. Last because it's the safest place to run over.

Thirty minutes, not sixty. A standing hour invites filling; a standing half-hour forces the agenda to earn its items.

3. The two questions that do the work

If the meeting ran out of agenda, these two questions fill it — and if the meeting has an agenda, these two questions are what it was protecting:

• “What's slowing you down that you haven't told me?” The unsaid blocker is the expensive one. Ask it directly, then survive the silence: the first answer is a deflection, the second is a fact, and the pause between them is the meeting. Ask it monthly even when everything looks fine — especially then.
• “What do you want here that you haven't asked for?” More scope, a title, remote days, a course, off one project. People don't volunteer wants to the person who pays them; asking once a quarter makes it normal. Write down what they say and bring it back next quarter — a request remembered is retention; a request forgotten is the exit interview.

4. The notes ledger: one file per person, every promise dated

The 1:1 that changes nothing is the one whose decisions evaporate in the hallway. Keep one shared note per person — running doc, newest on top — with three lists per entry:

• Decided — what was agreed, one line each, with the date. (“2026-09-08: Priya takes on the changelog; Marcus stops being paged for it.”)
• Owed by me — what the manager promised, with the date it's due. This is the list that builds trust: 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, with dates. No dangling “look into it” — either a date or it leaves the list.

Read the last meeting's lists first each week — 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 promotions, raises, and the quarterly business review all cite it.

5. The four kinds of 1:1 — the weekly is not the only one

1. Weekly (30 min). The default. Standing agenda above. Every direct report, every week, no exceptions — the week you cancel for “nothing to discuss” is the week the thing worth discussing went unsaid.
2. Monthly deep-dive (60 min). Same person, longer horizon: career, capacity, growth, the annoying project, the thing they'd change if it were their company. Standing agenda suspended — three questions sent the day before: What went well this month? What was wasted? What do you want next quarter?
3. Skip-level (30 min, quarterly). You meet your reports' reports without the manager in the room — and the ground rule is said out loud: “I'll keep what you tell me private, unless it's a safety or conduct issue.” No promises you can't keep, no ambush of the middle manager afterwards. The value is unfiltered signal from three layers down; the risk is a manager who hears about it second-hand, so the middle manager knows the meeting happened, every time.
4. The exit 1:1 (30 min, before the exit interview). When a resignation lands, the exit interview gets the form answers; the 1:1 you hold the same week gets the truth. One question: “What should have been different this year?” Write it down verbatim and fix what's fixable — the next person on that team is watching whether it gets fixed.

6. Worked example — the six-person studio that stopped managing by interruption

A six-person design studio, founder-run. The founder held ad-hoc chats all day — a question at a desk here, a Slack thread there — and ran one all-hands project meeting weekly that went eighty minutes. Symptoms: 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.”

• Week 1: standing weekly 30-minute 1:1s booked, agenda file created per person, the founder pre-filled each one with two items to seed the format. The all-hands shrank to 30 minutes with a written agenda — the detail moved to channels, where the six could read it instead of sitting through it.
• Week 2: first ledger closes a loop in front of the team — the founder had owed a budget decision from week 1 and opened the meeting by closing it, unprompted. The senior designer, who had been keeping a private list of stalled requests, added hers to the ledger that week.
• Week 3: the two-question routine surfaced the unsaid one: the senior designer wanted the client-facing work the founder was quietly keeping for himself. “What do you want here that you haven't asked for?” answered it in eleven words.
• By week 6: the resignation was withdrawn — not because of a raise, because the frustration had been named and given a date. Ad-hoc interruptions dropped to near zero (they had somewhere to go now), and the project meeting's eighty minutes became thirty — because the 1:1s were absorbing the blockers that had been going to all-hands.
• The outcome that matters: the founder recovered about four hours a week and the studio's first promotion happened on schedule — with the case made from six months of dated ledger entries instead of a memory argument.

7. The five traps

• The status meeting in disguise. If the manager does 80% of the talking and every item is an update, it's a slow report. Status lives in channels; the 1:1 is for what channels can't hold — blockers, doubt, ambition.
• Cancelled-last is cancelled-first. The 1:1 moved “just this once” four weeks running teaches the team where it ranks. If you must move it, the note says why and the new date is in the same message.
• Solving instead of hearing. The blocker named at minute four gets solved by minute five — by you, over the top of them, before the second sentence. Ask “what have you tried?” first; the person you trained to bring problems is worth more than the problem you solved.
• No notes, no continuity. “I'll remember” is the lie every manager tells. Six people, fifty meetings a quarter — the ledger is the only version of the 1:1 that compounds.
• Skip-level as ambush. Meeting your reports' reports and acting on what you hear without the middle manager knowing converts a listening tour into a coup. The ground rules keep it a listening tour.

8. Metrics — the 1:1 scorecard

1. Held rate: ≥ 90% of scheduled 1:1s held, per month. Below that and the calendar is telling the truth the org chart won't: these meetings are optional. Count cancelled-with-note as held; cancelled-last as missed.
2. Loop-closure rate: ≥ 80% of “owed by me” items closed within a week. Your own promises are the credibility engine of the meeting; track them like you track anyone's.
3. Unsaid-to-said: ≥ 1 new blocker or request surfaced per person per month. If a quarter produces zero new items from someone, either nothing is wrong (rare) or the meeting isn't safe yet (likely) — check which.

9. Copy-paste one-page 1:1 template

One file per person, shared, newest meeting on top. Fill the brackets, keep the three lists, and open next week by reading them:

1:1 — [Name] — [Date]

Blocks and news first (2 min of human, then):
1. Blocking me: [item] — owner: [name] — by: [date]
2. In flight: [project — state — next milestone]
3. Feedback (both ways): manager → [keep: ___ / change: ___] · report → manager: [keep: ___ / change: ___]
4. Career & capacity: [more of ___ / less of ___ / want next: ___]
5. Housekeeping: [holiday, expenses, tools, ___]

Decided: [one line per decision, dated]
Owed by manager: [item — by date]
Owed by report: [item — by date]

Quarterly add-ons: deep-dive three questions sent ahead; skip-level once a quarter with the ground rule said out loud; exit 1:1 within a week of any resignation — “What should have been different this year?” verbatim, in the file.