One-on-Ones That Aren't Just Status Updates
How to turn a weekly check-in into a meeting people want, drawing on Andy Grove's High Output Management, Kim Scott's Radical Candor, and Amy Edmondson's psychological safety.
Look at the last five one-on-ones you ran. If each one opened with "so, where are we on the launch?", you have a status meeting with a nicer title. The person left with the same obstacles they arrived with, and you left knowing the dates.
Why do one-on-ones decay into updates?
Status is easy. It has a clear shape, a clear answer, and it makes the manager feel informed. Everything else is harder to ask for and harder to hear.
Ask an assistant to "give me a one-on-one template" and you get a tidy list: wins, blockers, priorities, feedback. Used as written, it recreates the status meeting in four headings. A template cannot supply the conditions that make people say the real thing.
Three documented ideas address those conditions: whose meeting it is, what belongs on the agenda, and what makes honesty safe.
Whose meeting is it?
Andy Grove's High Output Management (1983) is direct about it: the one-on-one belongs to the person who reports to you. It is a forum for mutual teaching and exchange of information, and the report sets the agenda. The manager's role is to listen, ask, and teach.
His reasoning is that the manager's output is the output of their team, and a regular, well-used conversation is among the highest-leverage ways to raise it. Grove also ties frequency to task-relevant maturity: how much experience someone has with the particular task. A newer report may need closer contact, an experienced one a lighter touch.
Applied: Ask the person to send two or three topics before the meeting, and start with theirs. Move status to a written update. If they arrive with nothing, ask what is taking up the most of their attention this week.
"I manage [role] who has been in the job for [time] and is [newer/experienced] at [key task]. Draft a short note asking them to bring two or three topics to our one-on-ones, a few prompts they can use if they are unsure what to bring, and a plan for moving status updates into a written format so we can use our time on other things."
Why it works: moving the agenda to the report changes what the meeting is for before it starts.
What belongs on the agenda?
Kim Scott's Radical Candor (2017) builds on a pairing: care personally and challenge directly. She describes keeping a shared document for each one-on-one, where both people add topics, and holding regular career conversations beyond immediate tasks. Her suggested prompts include asking about someone's life story, their dreams, and a plan for the next eighteen months.
She also recommends asking for criticism first, with a question like what you could do or stop doing to make working with you easier. Receiving feedback well is the fastest way to make giving it normal.
Applied: Rotate the agenda: some weeks obstacles, some weeks growth, some weeks feedback in both directions. A manager who only ever asks about deadlines is training the person to talk about deadlines.
"Design a six-week rotation of one-on-one themes for [role], balancing current obstacles, career direction, feedback to me, feedback from me, and what they would like to learn. For each week, give three questions I could ask that cannot be answered with a single word."
Why it works: a rotation gives growth and feedback a standing place, so they are not crowded out by whatever is urgent.
What makes people say the real thing?
Amy Edmondson's The Fearless Organization (2019) defines psychological safety as a shared belief that it is safe to take interpersonal risks. She describes three leader tasks: set the stage by framing the work as a learning problem, invite participation by asking questions and showing curiosity, and respond productively when someone speaks up, with appreciation rather than blame.
A one-on-one is where a single person tests that safety. If the first piece of bad news earns a flinch, the next one will not arrive.
Applied: When someone raises a problem, thank them before you start fixing it. Say what you heard back. Ask what they have already tried. Resist the urge to solve it in the first minute.
"In a one-on-one, my report told me [difficult thing]. Help me draft how I could respond in the moment: a sentence of appreciation, a question to understand more, and a next step that does not take the problem out of their hands. Suggest two things I should avoid saying."
Why it works: the first reaction to bad news sets whether you hear the next one, so it is worth rehearsing.
How do the three compare?
| Approach | From | When it fits | Watch out for |
|---|---|---|---|
| Report-owned agenda | Andy Grove, High Output Management | Your meetings drift into updates and the report waits to be asked | Report-owned does not mean manager-silent; you still coach |
| Shared document and career talks | Kim Scott, Radical Candor | You want growth and feedback to have a regular place | Candor without care can read as criticism; care without candor goes soft |
| Psychological safety | Amy Edmondson, The Fearless Organization | People say "fine" and later you learn it was not | Safety is built through repeated reactions, not one announcement |
What won't a better format fix?
A format cannot repair a relationship where trust is already low, or where the manager is overloaded with too many reports to give each meeting real attention. If a team is stretched past what one-on-ones can cover, the structure of the team is the problem. Nor can a framework tell you what a particular person needs. It can only make it easier to find out.
Andy Grove sits in the Operator & Systems category, and Kim Scott and Amy Edmondson sit in the People & Culture category. For the originals, read High Output Management, Radical Candor, and The Fearless Organization. If a one-on-one has to include a conversation you have been avoiding, Difficult Feedback is a $49 tool built to structure it.
All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.
Frequently asked questions
If status updates are the problem, where should project status go instead?
Into whatever already carries it: a tracker, a shared document, a short written update before the meeting. Grove's logic is that the one-on-one exists for what only a conversation can do. Anything that fits in a ticket or a message is better handled there, so the hour is free for coaching, obstacles, and the things people have not yet written down. Short written updates before the meeting, even three bullet points, keep the hour for conversation instead of reporting.
How often should one-on-ones happen?
Grove ties frequency to what he calls task-relevant maturity: how much experience a person has with the specific task. Newer reports may need more frequent contact, experienced ones less. The more reliable rule is consistency. A meeting that is regularly cancelled tells the person where they rank, whatever the calendar invite says. If you must shorten the meeting, keep the slot and use a shorter agenda rather than skipping, since regularity is part of the message.
What do I do when the person just says everything is fine?
Treat it as a signal about safety rather than a fact about their week. Edmondson's guidance is to invite participation through questions that make candor easy to give, and to respond to what you hear with appreciation. Asking what could be better, instead of whether anything is wrong, gives people a way in. Try a specific question, such as what is one thing you would change about how we work, and give them time to think before answering.
Is it appropriate to give critical feedback in a one-on-one?
Yes, and Kim Scott's Radical Candor argues it is a natural place for it, provided it comes from genuine care for the person. Her framework pairs challenging directly with caring personally. Feedback that arrives only in the annual review is too late to be useful, and feedback delivered without care tends to produce defensiveness. Whatever you say, follow up on at least one point from the last meeting, since remembering is how people learn candor is worth the risk.
Should I take notes during one-on-ones?
Many managers using these frameworks keep a shared running document so both people can add topics and track commitments. Scott describes a shared agenda for exactly this reason. Agree on what gets written down, particularly if the conversation touches on performance or personal matters. Be clear with your report that notes exist and who can see them, since that shapes what they feel safe saying.
Can AI help me prepare for one-on-ones?
It can help draft questions, spot patterns in your notes, and suggest ways to open difficult topics. It cannot read the person across the table or know what has changed in their life. Use it to prepare and reflect, and use the meeting to listen. Ask it to critique your last agenda and find questions that could only be answered with a one-word reply, then rewrite those.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Apologizing to a Customer When You Got It Wrong
How to write an apology a customer believes, using the Trust Triangle from Frances Frei and Anne Morriss, the Trust Equation from Maister, Green and Galford, and Robert Cialdini's commitment principle used ethically.
Asking for a Raise Without Turning It Into a Standoff
How to run a pay conversation as a problem you and your manager solve together, using three documented negotiation approaches from Fisher and Ury, Chris Voss, and Deepak Malhotra.
Running a Post-Mortem Without Blame That Still Changes Something
How to run a review after a failure that finds real causes without scapegoating anyone or letting accountability disappear, using Amy Edmondson, W. Edwards Deming, and Gene Kranz.