Designing the 1:1: Turning 30 Minutes Into Leverage
Topic: One-on-One Meetings·4 Principles
"As a manager, the single most important thing you do is hold one-on-ones." — Andy Grove
This week's premise: A 1:1 is not a status update, not a project check-in, and not a polite "how are things." It is the highest-leverage 30 minutes you'll spend on this person this week. Andy Grove did the math in High Output Management: a well-prepared 1:1 can lift the quality of your report's work for two weeks afterward. The question isn't whether to hold them — it's how to hold them so you're not wasting two people's time. The four principles this week cover: the physical design of cadence and agenda, the trust-building 1:1 for the first 90 days, the questions that get past "I'm fine," and how to spot and repair a 1:1 that has decayed into a status meeting.
PRINCIPLE 01
The Physical Design of 30 Minutes: They Own the Agenda
Their Agenda, Your Calendar
CadenceAgendaOwnership
One-line principle
The 1:1 is your report's meeting, not yours. Weekly, 30 minutes, agenda written by them, fixed location, never canceled (and if it must move, move it in advance — not the day of).
In the author's own words
"The one-on-one is, in fact, the subordinate's meeting, with its agenda and tone set by him. The supervisor's role is one of consultant—and of asking questions."— Andy Grove, High Output Management, Ch. 4
Scene
Setup: You have a 1:1 with a senior engineer Monday. You open your calendar and there's no agenda doc.
✗ The default move
Ten minutes before, you scribble three talking points: last week's sprint progress, the upcoming feature ship, this month's OKR check-in. The meeting becomes you pushing the agenda and them answering passively. At the end they say "yeah, good" — and you have no idea what they're actually thinking.
✓ The repair
Build the mechanism: Share a Google Doc / Notion page titled "BigCat <> XX 1:1." Before each meeting they write 3–5 bullets at the top: whatever they want to talk about. You add one or two of yours underneath. The meeting follows their list; you only get the last 5–10 minutes for yours.
When you launch the practice, say it plainly: "This meeting is yours. I want you to drop three things in the doc 24 hours before we meet — anything: blockers, people stuff, career, feedback for me, questions about the company. If the doc is empty, I'll cancel the meeting."
Prep checklist (5 minutes before)
Did they write their agenda? If it's empty, did I nudge them?
Did I follow up on action items from last week? (They may not raise it, but they're watching whether you did.)
What observation about them — good or bad — do I have to deliver face-to-face this week?
What open-ended question am I going to ask? (Not a yes/no question.)
What's my own emotional state right now? Distracted or rushed will tank this meeting.
Common pitfalls
Canceling first when you're busy. The 1:1 is the first thing to go. Your report remembers every cancellation.
Using 1:1 as a project review. Status belongs in Slack, standup, and Jira. This time is too expensive for that.
Talking for 30 minutes without writing anything down. Three weeks later you forget what you promised. They don't.
Reducing frequency as people get more senior. Wrong. Senior people need different topics (strategy, career) — not fewer meetings.
Key references
Andy Grove, High Output Management (Ch. 4 "Meetings — The Medium of Managerial Work") — the founding articulation of "the agenda belongs to the report." Julie Zhuo, The Making of a Manager (Ch. 4) — modern, operational template for "they own the meeting."
Language to steal
Phrases worth keeping verbatim
"Your direct report owns the agenda." — Not "controls." Owns. Ownership language.
"This is your time, not a status check." — Say this, word for word, in the first 1:1.
"What's on your mind?" — The plainest opener, and the best. Beats "How are things?" every time.
PRINCIPLE 02
The 90-Day Trust 1:1: The Window for Psychological Safety
Onboarding 1:1s — The 90-Day Trust Window
OnboardingTrust buildingFirst 90 days
One-line principle
The 1:1s in a new hire's first 90 days are not about projects. They are about establishing a contract: "telling the truth here will not be punished." Once that window closes, reopening it costs ten times as much.
In the author's own words
"Psychological safety is a belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes."— Amy Edmondson, The Fearless Organization
90-day 1:1 agenda template
Scene
Setup: A newly hired senior PM, Day 7, their first 1:1 with you.
✓ Lara Hogan "New Manager Assimilation" style
"For the next six weeks I'm going to use the same set of questions in our 1:1s. The goal is for me to learn, fast, how to work well with you. First one: think of the best manager you've ever had — what did they do right?"
(After the answer:) "Now the worst. I don't need names. I want to know what behaviors you'd rather not see again."
"How do you want me to recognize your work? Public shout-out? Quiet Slack message? Email cc'ing my manager?"
"What would make you feel I've let you down? You don't have to answer today — next week is fine."
The five user-manual questions for the first 30 days
What did the best manager you ever had do right? The worst, do wrong? (Behaviors, not people.)
How do you prefer to receive feedback? Right away vs. written first then discussed? Verbal vs. Slack?
How do you absorb information? Sync meetings vs. async docs? Long-form vs. bullets?
What would feel like unfair treatment to you? What are your hard lines?
Outside of work, what rhythms should I know about? (School pickup, chronic illness, religious holidays.)
Common pitfalls
Talking about projects in the very first 1:1. Projects can be discussed anytime. The contract-building window happens once.
Rushing to "prove you're a good boss." What you say doesn't matter — they watch what you do. Promise less, deliver on time.
Asking the user-manual questions but not writing the answers down. They say "I like async feedback," and three weeks later you critique them in standup. Window broken.
Skipping the Day-60 "what surprised you" question. That's the last time they'll feel safe to surface friction.
Women's perspective
Female Leader's Note
Research consistently shows that during onboarding, reports — especially male reports — are more likely to interpret a woman manager's "gentle questioning" as "she hasn't made up her mind yet." Counter-move: open the first 1:1 with explicit ownership language — "I'm your manager. I'll ask a lot of questions, but the decisions land with me" — and then move into the user-manual section. That sentence isn't bravado; it sets the frame that lets the open questions land as curiosity, not indecision.
Key references
Lara Hogan, Resilient Management — the "User Manual" and "New Manager Assimilation" chapters. Michael Watkins, The First 90 Days — written for the person being onboarded, but read in reverse it's a map for onboarding others.
Language to steal
Phrases worth keeping verbatim
"Tell me about your user manual — how do you like to be managed?" — Lara Hogan made this metaphor famous.
"What would make you feel I've let you down?" — "Let down" is more concrete than "disappoint."
"I'm here to learn how to work with you, not the other way around." — A disarming opener.
PRINCIPLE 03
Questions That Surface the Truth: From "I'm Fine" to "Actually…"
Questions That Surface The Truth
QuestionsCoachingPsychological safety
One-line principle
"How's it going?" is dead. Replace it with concrete, low-risk, directional questions — and then be prepared to sit in silence for eight seconds.
In the author's own words
"To make Radical Candor work, you have to solicit it before you can dish it out. If they tell you they are 'fine,' you have to push harder."— Kim Scott, Radical Candor
Scene: rebuild your question library
Setup: Every 1:1 your report says "yeah, things are fine, nothing special." You have no idea whether they actually are.
✗ Dead questions (too much noise, too little signal)
"How are things?" → "Good."
"Anything I should know?" → "Not really."
"Any blockers?" → "Nope, all good."
"How can I help?" → "I'm fine, thanks."
✓ Replace them (specific + time anchor + direction)
· "What moment last week was the most frustrating?" (emotion + time anchor)
· "If you were me, what would you prioritize this week that I'm not doing?" (role swap)
· "Who have you worked with recently who drains your energy?" (specific behavior)
· "If you were leaving next week, what would you warn your replacement about?" (Kim Scott classic)
· "What's one thing I've done that you wanted to push back on but didn't?" (invite criticism)
· "Imagine this project fails six months from now — what's the most likely reason?" (pre-mortem)
Silence is a tool — the 8-second rule
After a real question, count to eight. Most people will start to add something at the 4-second mark — but the real insight surfaces at second 5–8. If you rush to fill the silence, you only get the surface answer.
✓ The physical move
Use your coffee. Ask the question, pick up the cup, take a slow sip, set it down. Eight seconds have passed, and you still haven't spoken. They'll start to say the real thing.
Prep checklist: the "real question" for this 1:1
How many of my prepared questions are yes/no? Cut them.
Is there at least one question with a time anchor ("last week," "this sprint")?
Is there at least one question that invites criticism of me?
How will I respond to the criticism? ("Thank you, I'll sit with that." Not immediate defense.)
How many seconds of silence can I actually tolerate before I break?
Common pitfalls
Asking a question and answering it yourself. "How was last week? Sprint felt rough, right? I felt it too…" — you just stole their answer.
Treating "I'm fine" as a closing. It isn't. It's an invitation to push once more.
Asking for criticism, then defending. Once is all it takes — next time, they won't tell the truth.
Using the same question set for everyone. Senior people need strategy and career; new hires need onboarding signal.
Women's perspective
Female Leader's Note
When a woman manager invites criticism ("What would you push back on?"), some male reports read it as weakness or as an invitation to challenge authority — the classic competence/likability double bind. One counter (a variant Sheryl Sandberg uses in Lean In): frame the question around the team, not yourself. "What's the one thing I should change to make the team run more smoothly?" The focus shifts from your vulnerability to the team's output, while you still get the signal.
Key references
Kim Scott, Radical Candor (Ch. 6 "Get/Give/Encourage Guidance") — origin of "What could I do or stop doing that would make it easier to work with me?" Michael Bungay Stanier, The Coaching Habit — seven questions that change your 1:1s.
Language to steal
Phrases worth keeping verbatim
"What could I do or stop doing that would make it easier to work with me?" — "Stop doing" pulls more feedback than "do better."
"Tell me more." — When they give you a surface answer, two words is enough.
"What else?" — Michael Bungay Stanier's "most powerful question." Ask. Get an answer. Ask again. The gold is on the third pass.
PRINCIPLE 04
Diagnose When a 1:1 Has Decayed Into a Status Meeting — and Repair It
Diagnose & Repair The Status-Update Trap
DiagnosisRepairAgenda reset
One-line principle
If your entire 1:1 is project status, you've wasted 90% of the leverage. Status belongs in Slack, standup, and Jira. The 1:1 is for the things that don't fit in a document: emotion, relationships, growth, trust.
In the author's own words
"If your 1:1s feel like status updates, you're doing them wrong. Status belongs in writing. The 1:1 is for what you can't put in a doc."— Camille Fournier, The Manager's Path
Diagnosis: has your 1:1 turned into a status meeting?
The repair script: how to restart a decayed 1:1
Setup: For six weeks straight, your 1:1 with this report has been pure status. You need to reset.
✓ Reset script (say this at the top of the next meeting)
"I want to change how we run these. For the last few weeks we've basically been doing project status — and honestly, that's all already in standup and Jira. We've been wasting the value of this meeting."
"Starting next week, three changes: One — I'll read Jira on my own; I won't ask for status here. Two — drop three bullets in the doc 24 hours before we meet. Anything goes; the less it sounds like a status update, the better. Three — once a month, we'll use a whole 1:1 just for career conversation, no current-project talk allowed."
"This change is to give you more room. If your doc is empty for the week, that's fine — it means there's nothing pressing, and I'll cancel rather than force the meeting."
Three flavors of 1:1, on a rotation (adapted from Camille Fournier)
Tactical (weekly): Unblock, align on this week's decisions, work through interpersonal friction. 30 minutes.
Career (quarterly): Promotion path, skill growth, long-term motivation. 60 minutes — bonus if you change locations (coffee shop, walking 1:1).
Color-code them on the calendar. When your report sees "Career 1:1 next week," they'll prepare.
Common pitfalls
Refusing to reset; powering through. If even you don't see the value, your report has stopped respecting all 1:1s by now.
Blaming the report when you reset. "You never write an agenda" — that's on you, not them. Own it during the reset.
Doing career 1:1s only right before perf review. That's not a career conversation — that's review prep.
Fearing "no agenda = cancel." Canceling is a healthy signal, not a failure signal.
Women's perspective
Female Leader's Note
Women managers are often expected to absorb extra emotional labor — reports treat the 1:1 as a venting session. That isn't bad on its own, but it has a cost: if a particular report uses every 1:1 to vent without moving toward action, within a few weeks you'll be drained. One way to set the boundary: "I hear you — this has been a hard stretch. Let's spend ten minutes on it, and then I want us to decide one thing you can put down this week. Otherwise we'll be having the same conversation next week." Empathy plus a push toward action — not endless containment.
Key references
Camille Fournier, The Manager's Path (Ch. 3 "Managing People") — origin of the three-tier 1:1 cadence. Will Larson, An Elegant Puzzle — "Sizing engineering teams" and "Career planning" discuss the cadence and output of career 1:1s.
Language to steal
Phrases worth keeping verbatim
"Let's reset how we do these." — "Reset" is more neutral than "change"; it doesn't assign blame.
"Status belongs in writing; this time is for what's not in the doc." — One sentence, clean boundary.
"Skip-level 1:1" — Once a quarter, meet 1:1 with your report's reports. Camille Fournier's recommended blind-spot scanner.
This Week's Practice · Your Day 1 Action
One concrete action this week — not reflection, not reading:
Pick one report (the one whose 1:1 you're least sure is producing value), and run the 8-second silence experiment from Card 3. Prep one real question ("What moment last week was most frustrating?"), ask it, pick up your cup, take a sip, count to eight, then speak.
Afterward, write two lines in the 1:1 doc: (1) at what second they started talking; (2) was the content what you expected?
If they said "I'm fine" within three seconds, push once more: "Give me a concrete example."