One-on-Ones

The 1:1 is the single highest-leverage meeting a manager runs. It is the one recurring slot dedicated entirely to one person's work, growth, and friction — and it is the place where almost every other part of performance management either starts or gets caught. A manager who runs 1:1s well rarely gets surprised by attrition, missed deadlines, or a review that goes sideways. A manager who skips them, or turns them into status updates, finds out about problems when they are already expensive.

The core idea: the 1:1 belongs to the report, not to you. It is their time to use. Your job is to show up, listen, unblock, and steer — not to extract a status report you could have read in a ticket.

Why It Exists

A 1:1 does several things that no other meeting does:

• Surfaces what won't come up in a group. People will not say "I'm lost," "I'm bored," or "I'm thinking of leaving" in standup. They will sometimes say it across a desk when nobody else is listening.
• Builds the trust that makes feedback land. Hard feedback delivered by someone who has invested in you for months lands very differently from feedback delivered by a stranger.
• Catches small problems early. A frustration caught at week two is a conversation. The same frustration caught at month three is a resignation.
• Gives growth a regular home. Career and skill development need a recurring slot or they get crowded out by delivery forever.

Cadence

A few rules that hold regardless of cadence:

• Default to weekly. It is easier to end early than to wish you had met sooner. Thirty good minutes beats sixty padded ones.
• Protect the slot. Cancelling a 1:1 to take "a more important meeting" tells the person exactly where they rank. Reschedule, don't cancel.
• Same time, same place. Predictability lets people save things up for it instead of interrupting you all week.

If you find yourself routinely cancelling 1:1s "because there's nothing to discuss," that is itself the signal — either the relationship is too transactional or you are framing the meeting as status, which it should not be.

Agenda Ownership

The most common failure mode is the manager owning the agenda and using it to collect status. Flip it.

• The report drives. Ask them to bring topics. A shared running doc where they add bullets during the week works well — by meeting time the agenda has written itself.
• You hold a parking lot. Keep your own short list of things to raise — feedback, context they're missing, a nudge on growth — but let theirs go first.
• Empty agenda is information, not a problem. If they have nothing, don't fill it with status. Use it to go up a level: "How are you finding the work lately? What would you change about the team if you could?"

A simple shared structure that works:

## <Date>
### Their topics
- ...
### My topics
- ...
### Actions from last time
- [ ] ...

What To Talk About

A useful frame is three buckets, and a healthy 1:1 over time touches all of them:

1. Status / blockers — the thinnest slice. What's stuck, what they need from you. Keep this short; if it eats the whole 1:1, your async updates are broken.
2. Growth / career — what they're learning, where they want to go, what the next level looks like. Easy to defer forever; protect it.
3. The relationship and the team — how they're feeling, team dynamics, things bothering them they wouldn't put in writing.

A practical rhythm: most weeks lean on status and growth; roughly monthly, deliberately zoom out to career; whenever you sense something is off, prioritize the relationship bucket over everything.

Career vs status: keep them distinct

Status answers "what is happening this week." Career answers "where is this person going over the next year or two." They run at completely different cadences and the second loses every time if you don't defend it.

• Reserve one 1:1 a month (or a dedicated quarterly conversation) explicitly for career. Say "let's not do status today — I want to talk about where you're headed."
• Status that bleeds into every slot is a smell that your written/async updates aren't carrying the load they should.

Question Banks

When the conversation stalls, having questions ready is the difference between a real 1:1 and an awkward five minutes. Rotate these; don't ask all of them.

Opening / temperature check

• How are you doing — honestly, not the standup version?
• On a scale of "actively looking" to "couldn't be happier," where are you this month?
• What's the highlight and the lowlight of your week?

Work and blockers

• What's slowing you down that I could remove?
• What are you working on that you're not sure is the right thing?
• Where are you spending time that doesn't feel valuable?

Growth

• What did you learn recently that surprised you?
• What's a skill you want to be visibly better at in six months?
• What part of someone else's job looks interesting to you?

Feedback (both directions)

• What's one thing I could do differently to support you better?
• Is there feedback you've been sitting on for me?
• Who on the team deserves more recognition than they're getting?

Stepping back

• If you were running the team, what's the first thing you'd change?
• What would make you leave? What would make you stay?

The two-direction feedback questions matter most and get asked least. Asking "what could I do differently?" repeatedly, and then visibly acting on an answer once, does more for trust than any other single move.

Note-Taking

Memory is not a system. Notes are what make 1:1s compound over a year.

• Keep a running doc per person. One document, newest entry on top, spanning the whole tenure. This is your single best defense against recency bias at review time.
• A shared section and a private section. The shared doc holds the agenda and actions. Keep a separate private note for sensitive observations, feedback you've given, and patterns you're tracking.
• Capture specifics, dated. "Drove the cache migration design solo, caught the rollback gap (Mar 4)" is gold six months later. "Doing well" is worthless.
• Track actions both ways. What you committed to, and what they did. Following through on what you said you'd do in a 1:1 is most of how you earn credibility.

When the annual review comes, a manager with a year of dated notes writes a fair, specific, surprise-free review in an hour. A manager relying on memory writes a recency-biased guess in three.

Skip-Levels

A skip-level is a 1:1 between you and someone who reports to one of your reports. It is a deliberate, occasional tool — not a replacement for the manager in between.

Why run them

• Calibrate your managers. How the team describes the work and the manager tells you whether your managers are landing.
• Catch what's filtered out. Information degrades as it passes up the chain. Skip-levels give you an unfiltered sample.
• Show the team they're seen. People value being known by their manager's manager.

How to run them without undermining the manager

• Be explicit about purpose. "This isn't about going around your manager — I do these with everyone, and I want to hear how things look from where you sit."
• Don't take action items that belong to the manager. If something surfaces, route it back through the manager unless it's a safety/integrity issue. Acting directly cuts your manager off at the knees.
• Tell the manager you're doing them, not the contents. The cadence is transparent; the specifics stay confidential or the channel dries up.
• Ask team and system questions, not "rate your boss." "What's working well on the team? What's frustrating? What should I know?" gets honest answers; "is your manager good?" gets nothing useful.

Cadence is light — quarterly per person, or rolling through the org so everyone gets one a few times a year.

Anti-Patterns

• The status standup. The 1:1 becomes a verbal ticket update. Move status to async; reclaim the slot for things that need a human.
• The manager monologue. You talk 80% of the time. The ratio should be closer to inverted — you ask and listen, they talk.
• The skip-when-busy. The first meeting cut when the week gets full. This trains people that they matter least.
• The no-notes 1:1. Warm, useless conversations that evaporate. Without notes there's no follow-through and no review trail.
• The therapy-only 1:1. All rapport, never any substance, feedback, or direction. Pleasant and developmentally empty.
• The agenda hijack. You bring a packed list every week and the report never gets to drive. It stops being their meeting.

A Simple Operating Standard

If you want one bar to hold yourself to:

Every report has a protected, regularly-occurring 1:1 that they drive, where status is the smallest part, growth has a guaranteed slot, and you leave with notes and at least one action you owe them.

Get that running reliably before you worry about anything else in this section — feedback, reviews, and career conversations all attach to it.