One-on-Ones
You are a manager with 5-8 direct reports, and you are spending 3-4 hours a week in one-on-ones that feel like status updates. Your reports leave feeling like they just gave a progress report. You leave feeling like you learned nothing you could not have gotten from a Slack message. The problem is not the meeting — it is what you are doing with it. The best managers treat the 1:1 as their highest-leverage 30 minutes of the week. Here is how.
The Status Update Trap
The default 1:1 follows a predictable pattern: the report shares what they worked on last week, what they are working on this week, and any blockers. The manager nods, offers a suggestion or two, and they both move on.
Kim Scott, author of Radical Candor — the single most referenced book on Lenny’s Podcast — identifies the deeper failure: most managers default to status updates because it feels productive, but they are avoiding the harder conversations. As she puts it, “90% of us make 90% of our mistakes in that ruinous empathy bucket.” The 1:1 is where ruinous empathy does the most damage, because the synchronous, private setting is precisely where critical feedback should happen — and where managers most often let it slide.
The litmus test: if everything discussed in your 1:1 could have been an async update in your project management tool, you are wasting the synchronous time.
Cadence and Structure
How Often
| Report Type | Recommended Cadence | Reasoning |
|---|---|---|
| New hire (first 90 days) | Weekly, 45-60 min | Building trust, accelerating onboarding, catching misalignment early |
| Experienced IC | Weekly, 30 min | Consistent enough to catch problems before they escalate |
| Senior IC / tech lead | Weekly or biweekly, 30 min | Biweekly only if the relationship is strong and communication is frequent async |
| Skip-level report | Monthly, 30 min | Maintains visibility and gives the report access to senior leadership |
Scott is emphatic about why these conversations must happen synchronously and regularly: “You want to have these conversations synchronously. Slack is just a feedback train wreck waiting to happen. I once coached someone who kept giving feedback over Slack and I finally just quit coaching him.” The cost of a weekly 30-minute meeting is trivially small compared to losing a high performer because you missed the signal that only surfaces in live conversation.
The Three-Part Structure
Petra Wille, product leadership coach and author of Strong Product People, uses a structure that most guests converge on:
Part 1: Their agenda (15 minutes). The report owns this. They bring what is on their mind — a problem they are stuck on, a decision they need input on, something that is frustrating them. If the report consistently has nothing to bring, that is itself a signal: either they do not trust you enough to be candid, or you have not set the expectation that this time is theirs.
Part 2: Your observations (10 minutes). Feedback, coaching, context they might be missing. This is where the manager adds value beyond what the report could get from a peer. Share what you are seeing that they might not see — patterns in their work, how they are perceived by stakeholders, blind spots.
Part 3: Development (5 minutes). Not every week, but regularly: career goals, skill gaps, stretch opportunities. Wille recommends a specific practice: “Block yourself an hour in your calendar once a quarter, write down the names of your direct reports, and then think about what would be the next bigger challenge for each of them. It’s not always the case that this comes around the corner the next day. Sometimes it takes a quarter or two, but if you wrote it down, you will see this opportunity.” The 1:1 is where you share that vision and check on progress.
Questions That Actually Work
Generic questions produce generic answers. The best 1:1 questions are specific enough that the report cannot answer with “everything is fine.”
For Uncovering Problems
| Question | Why It Works |
|---|---|
| ”What is the hardest part of your work right now?” | More specific than “how are things going” — forces identification of a concrete challenge |
| ”If you could change one thing about how we work together, what would it be?” | Gives explicit permission to critique the relationship |
| ”What is something you are worried about that you have not brought up yet?” | Signals that you want the hard stuff, not the polished update |
| ”On a scale of 1-10, how happy are you at work right now? What would make it a [N+1]?” | The number anchors the conversation; the follow-up is where the insight lives. |
For Coaching
| Question | Why It Works |
|---|---|
| ”What would you do if you were in my position on this decision?” | Develops their judgment by forcing them to think one level up |
| ”What did you learn from how that project went?” | Builds reflection habit without making it feel like a post-mortem |
| ”What is one thing you want to get better at this quarter?” | Keeps development front of mind |
The 1:1 as a Coaching Tool
The highest-leverage shift a manager can make: stop solving problems for your reports and start coaching them to solve problems themselves.
Lane Shackleton, CPO at Coda, describes how he uses 1:1s as a coaching vehicle: “I found myself giving a similar set of advice in one-on-ones. And I think anytime you find as a leader yourself repeating the same lessons, it should be a signal” — a signal to codify those lessons into principles the team can internalize rather than depend on the manager to repeat. The coaching stance means your job in a 1:1 is not to give answers but to ask questions that help them find their own answer. When you give the answer, you create dependency. When you help them find the answer, you create capability.
When a report brings a problem, follow this sequence before offering your perspective:
- Ask: “What options have you considered?”
- Ask: “What do you think is the best option and why?”
- Ask: “What would need to be true for that option to work?”
- Then share your perspective, add context they might be missing, or endorse their decision.
Melissa Tan, former head of growth at Dropbox and Webflow, adds a nuance on the balance between caring and directing. She describes giving a new team member critical feedback just two weeks in — telling them they needed to move much faster — and framing it through intent: “My intention is to set you up for success.” The report later called it one of the most valuable conversations of their career. For a new PM, you might be 60% directing, 40% coaching. For a senior PM, flip it to 20/80. The key is that coaching and directness are not opposites — they are complementary, and the best managers combine them in every 1:1.
Handling Difficult 1:1 Conversations
Three scenarios managers consistently find hardest:
1. The Report Who Says Everything Is Fine
Scott’s approach starts with soliciting feedback first — before giving it. Her recommended question: “What could I do or stop doing that would make it easier to work with me?” She warns: “Do not write down my question because if you sound like Kim Scott and not like yourself, then other people are not going to believe you want the answer. It needs to sound authentic to you.” If someone consistently says everything is fine, vulnerability from the manager is the unlock. Share something you are struggling with first. Vulnerability is reciprocal. They are not going to be honest with you if you are not honest with them.
If vulnerability does not work after several attempts, be direct: “I have noticed you do not bring problems to our 1:1s. I want to make sure this time is useful for you. What would make these meetings more valuable?“
2. Delivering Critical Feedback
Scott uses a framework she calls CORE: Context, Observation, Result, nExt step.
- Context: “In the meeting…”
- Observation: “…when you offered both sides of the argument…”
- Result: “…it earned you credibility.”
- Next step: “Do more of that.”
The same structure works for criticism: Context (“In the product review”), Observation (“you presented three options without a recommendation”), Result (“the VP had to make the decision without your informed perspective”), Next step (“come with a clear recommendation next time”). No sandwich. Scott is emphatic: “You want to be humble, you want to be helpful, you want to do it immediately, you want to praise in public and criticize in private, and you don’t want to give people either praise or criticism about their personality.”
3. The Report Who Wants a Promotion
Wille recommends radical transparency through her five-step coaching framework: define what good looks like, assess where the PM is today, share your vision for their growth, co-create a development plan, and follow up consistently. “Even if you don’t have your compass, your definition of what makes a good product manager, you usually have an idea of what they want to learn next or where they want to get better at. Start with the development plan — that’s the perfect start.”
If a promotion is not realistic in the near term, say so. Tell them exactly what the gap is between where they are and where they need to be. Write it down. Agree on it together. Then check in on it every month. The worst thing you can do is be vague about what it takes, because then they fill the ambiguity with resentment.
A Note for ICs
The 1:1 is your meeting. If your manager is turning it into a status update, redirect: “I can share project updates async. Can I use this time to get your input on a decision I am facing?” Come with 2-3 topics, including at least one that is not a status update. Hold your manager accountable for commitments they make. Most managers will be relieved when you take ownership of the agenda.
Key Takeaway
- If your 1:1 could have been a Slack message, you are doing it wrong. Reserve synchronous time for coaching, feedback, and the conversations your report cannot have anywhere else. As Scott warns, “Slack is just a feedback train wreck waiting to happen.”
- Use the 1-10 happiness question regularly. The number itself matters less than the follow-up: “What would make it one point higher?”
- Coach before you solve. Ask “what options have you considered?” before offering your answer. The goal is to build their judgment, not their dependency on yours.
Related
- Hiring PMs — The 1:1 relationship starts at the hire
- Performance Reviews — Feedback in 1:1s should mean no surprises in reviews
- OKRs — OKR progress is a standard 1:1 agenda item
- IC vs Management Track — Whether you are in 1:1s as a manager or a report shapes your career
Sources
- Kim Scott on Radical Candor — CORE feedback framework, ruinous empathy as most common failure, soliciting feedback before giving it, synchronous over async for feedback
- Lane Shackleton on what sets great teams apart — Repeating lessons as codification signal, “oh shit moments” as growth indicator, principles and rituals at Coda
- Petra Wille on coaching product people — Five-step coaching framework, next bigger challenge exercise, development plan as starting point, quarterly reflection practice
- Melissa Tan on building high-performing teams — Direct feedback with stated intent, caring deeply while challenging directly, developing talent as lifelong relationship
- Ken Norton on product leadership skills — People-pleasing PM archetype, redefining leadership style, letting go of needing to be liked, creative vs reactive operating