One-on-one

There was a long stretch where a manager and a team member had no standing place to talk alone. Every conversation happened in front of other people. Status went around the table at the weekly meeting, and once every six months there was a review conversation. Between those two, the two of them never sat down together.

The trouble is that a lot of what matters can't be said in a room full of colleagues. That the current assignment is a bad fit. That the same person on another team keeps blocking things. That six months from now the plan is to be somewhere else. None of that makes it onto a weekly agenda, so it piles up with nowhere to go and comes out all at once.

The scene usually looks like this. Someone resigns, and the manager asks why they didn't say something sooner. They had been unhappy for four months, and there was never a thirty-minute slot on the calendar where that sentence would have fit.

Performance management typically runs on a half-year or quarterly cycle. Goals get agreed at the start, conversations accumulate during the period, and at the end everything that accumulated is written up as a performance review. The one-on-one is the instrument built for that middle stretch. Split into thirty minutes every two weeks instead of one long session twice a year, nothing in the final write-up arrives as news.

The team member writes the agenda, the meeting opens with whatever was agreed last time, and the rest of the time goes to what's stuck. A thirty-minute slot breaks into five pieces.

1. A day or two beforehand, the team member adds agenda items. A line or two in a shared document is enough. When the manager fills this in instead, the character of the meeting changes entirely.
2. Start with what was agreed last time. "You were going to ask the infrastructure team about those permissions" — one line each. Skip this and the same topic gets reintroduced from scratch every session.
3. Work through the items the team member brought. This usually takes more than half the time. Decisions that need making, problems that can't be solved alone, questions with no obvious owner.
4. The manager passes on what they have. Praise and corrections, decisions made outside the team, directions likely to shift next quarter. Softening the message so far that the other person never registers there was a problem defeats the purpose, which is why radical candor — caring personally while saying the hard thing directly — is the assumption underneath this piece.
5. Write two or three lines about who does what before the next session. Those lines become step 2 next time.

Notes go into one running document rather than a fresh file each session. Six months of history in one place means nobody has to reconstruct anything from memory at review time — what was discussed, and when, is already written down with dates.

Two people, the manager and one team member, on a fixed interval blocked out across the whole team in advance. Thirty minutes every two weeks is the most common setting; some teams run thirty minutes weekly or an hour biweekly. A manager with eight reports spends two hours a week on biweekly thirty-minute sessions.

The interval tightens when circumstances call for it. Someone who just joined, someone whose scope just changed, someone whose results are falling short and who therefore has more to talk about — all of them go weekly for a while and shift back to biweekly once things settle. Someone three years into the same steady work can move to monthly with no real cost.

Sessions can move, but they don't get skipped. If Thursday doesn't work, do it Friday; if that fails, Monday. Two cancellations in a row and the team member concludes the slot is gone, and nobody writes agenda items for a slot they believe is gone.

Who does the cancelling is a signal too. It's almost always the manager. For the team member that half hour is the only one of its kind that week; for the manager it's one of eight, so it's the first thing to yield when the calendar gets crowded. Teams that protect the practice tend to adopt one rule: book one-on-ones before other meetings, and when they move, move them within the same week.

"Let's not do this here — bring it to our one-on-one."

This isn't a topic for a room with other people in it; raise it when it's just the two of us.

"I put it on the agenda for this week's one-on-one."

It's already written in the shared doc, so read it before you walk in.

"If you haven't had a one-on-one in two months, it wasn't postponed — it's gone."

Repeated cancellation isn't an interval change, it's the practice quietly ending.

At Pagedeck, Grace holds thirty minutes with Mia every other Tuesday afternoon. Last session's note said they would look at the draft roadmap for next quarter, so that comes first, and then they move to Mia's items. This time the list includes requirements that flipped twice between engineering and design. Raised in the weekly meeting, that turns into an argument about whose fault it was. Raised between two people, it turns into a decision about what gets locked down first next time.

Grace uses the last five minutes for what she brought. The way Mia organized the investor meeting materials last month worked well, and there's a chance the team splits in two next quarter. Both are too early for a company-wide announcement and too late to hold until the half-year review.

The most common mistake is treating the one-on-one as a status report. Meeting the manager alone makes it feel like an account of progress is owed, and the first few sessions usually go that way. But progress is already visible in the tracking tool and the weekly meeting. Spending thirty minutes repeating it leaves no room for the things that can't go in a tracking tool. Three months of that and both sides start to resent the slot, and whoever tires of it first begins cancelling.

The other mistake is assuming a quiet week means the session can be dropped. Nothing urgent is happening, so saving thirty minutes looks like a reasonable call. But the value of this slot comes from already being open when something does happen. Skip it routinely and then schedule one on the day a problem appears, and the meeting request itself puts the other person on edge. On a team that keeps the half hour even on uneventful weeks, that half hour carries no signal at all.