How to run effective one-on-one meetings as a product manager: protect the time as sacred, own an agenda focused on the person not status updates, ask questions that surface what you would never hear in a group setting, and close each meeting with one action item you own — not them.
Most PMs run one-on-ones wrong. They ask "what are you working on?" — a status question. They listen to the update, say "sounds good," and end the meeting. This is not a one-on-one; it's a lightweight standup with extra steps.
Effective one-on-ones are relationship infrastructure. They are the primary channel through which you learn what's actually broken, what your team members are worried about, and what would accelerate or block their best work.
The Core One-on-One Principles
It's their meeting, not yours: The one-on-one exists to serve the team member's needs — their blockers, their growth, their concerns. Your agenda comes second. If they walk away feeling heard, the meeting succeeded.
Never use it for status: Status belongs in Linear, Jira, or a standup. If you use 1:1 time for "what's the update on X," you waste the only private, high-trust context you have.
Consistency over intensity: A 30-minute weekly 1:1 consistently kept is more valuable than a 90-minute quarterly deep-dive. Frequency builds the trust that makes honesty possible.
You own the action items: If you walk out of a 1:1 with your team member holding all the action items, you've added to their load, not helped them. You should be taking on support actions — removing blockers, making introductions, clearing ambiguity on priorities.
The One-on-One Agenda Framework
H3: The Four-Block Agenda
A 30-minute 1:1 structured in four blocks:
Block 1 — Personal Check-in (5 min) Not "how are you" (which gets "fine"). Ask something specific:
- "What's been the most energizing thing this week?"
- "What's taking more mental space than it should?"
- "Is there anything outside work affecting how you're showing up?"
You don't need to solve anything here. You need to know whether to adjust.
Block 2 — Blockers and Support (10 min) "What's slowing you down that I could help remove?" This is the highest-value question a PM can ask a team member. Engineers have opinions about what they could build faster if product or process friction were removed. Designers know where they're blocked on decisions. Listen and take notes.
Block 3 — Career and Growth (10 min) Not every week, but at least twice a month. Questions that open this space:
- "What skill do you want to build in the next 6 months?"
- "What kind of work are you hoping to do more of?"
- "Is there a project on the horizon that would accelerate your growth?"
Block 4 — Feedback Exchange (5 min) Close every 1:1 with feedback in both directions. "One thing I think you're doing well right now is X. One thing I'd like to see more of is Y. What's one thing I'm doing or not doing that would help you more?"
H3: Questions That Surface What Group Settings Never Will
According to Shreyas Doshi on Lenny's Podcast, the most valuable question a PM manager can ask in a 1:1 is: "If you were me, what's the one thing you'd change about how this team operates?" This question invites the team member to take your perspective — which often reveals the systemic issues that politeness prevents surfacing in group settings.
Other high-signal questions:
- "What's something the team believes that you think is wrong?"
- "What decision have we made recently that you privately disagreed with but didn't push back on?"
- "What do you wish I understood better about your work?"
- "If you were going to leave this company in the next 6 months, what would the reason be?"
Running 1:1s With Stakeholders
One-on-ones are not only for direct reports. PMs should run monthly 1:1s with:
- Engineering managers they partner with
- Designers they work closely with
- Sales or customer success leads who interact with the product
- Senior stakeholders who influence roadmap decisions
H3: The Stakeholder 1:1 Agenda
Stakeholder 1:1s are different in tone — they are peer relationships, not manager-report relationships — but the same core principles apply: no status updates, questions that surface tension, and at least one action item from you.
Template for a stakeholder 1:1:
- "What's most on your mind about the product right now?"
- "Is there a customer problem you're seeing that you don't think the product team fully understands?"
- "Is there anything I'm doing or not doing that's making your job harder?"
According to Gibson Biddle on Lenny's Podcast, the PMs who were most effective cross-functionally at Netflix ran regular 1:1s with sales and marketing counterparts — not to manage them, but to stay current on what customers were saying in contexts the product team never saw. "The sales team hears product objections before the PM does. If you're not talking to them regularly, you're flying blind on part of the feedback loop."
Common One-on-One Failure Modes
| Failure Mode | Symptom | Fix | |-------------|---------|-----| | Status meeting | Every 1:1 starts with "what are you working on" | Ban status questions; move updates to async | | Cancellation habit | 1:1s are the first thing rescheduled when busy | Block calendar; treat 1:1s as unbreakable | | Manager-only agenda | PM talks 70%+ of the time | Prepare questions; listen more | | No follow-through | Actions from last 1:1 not reviewed | Start every 1:1 by reviewing last meeting's actions | | Shallow feedback | "You're doing great" every week | Prepare specific, behavioral feedback before each meeting |
H3: The Follow-Up Protocol
According to Lenny Rachitsky's writing on management, the single biggest credibility destroyer in 1:1s is promising to do something and not doing it. "Team members remember every commitment you made and forgot. Every dropped action item is a small withdrawal from the trust account."
After every 1:1:
- Send a one-paragraph summary of what was discussed and what you committed to
- Track your commitments in a shared doc or note visible to both of you
- Open the next 1:1 by reviewing what you said you'd do
FAQ
Q: How do you run effective one-on-one meetings as a product manager? A: Protect the time as sacred, use a four-block agenda covering check-in, blockers, career growth, and feedback, ask questions that surface what group settings never will, and close by taking on action items yourself.
Q: What should a product manager discuss in one-on-one meetings? A: Personal wellbeing check-in, blockers the PM can remove, career and skill growth aspirations, and bidirectional feedback. Never use 1:1 time for status updates that belong in async tools.
Q: How often should a product manager run one-on-ones with team members? A: Weekly for direct reports and key engineering or design partners. Monthly for stakeholders including sales, marketing, and customer success counterparts.
Q: What questions should a PM ask in a one-on-one meeting? A: What's slowing you down that I could remove? If you were me, what's the one thing you'd change about how this team operates? What decision have we made recently that you privately disagreed with? What would make you leave this company in the next six months?
Q: How do you make one-on-one meetings more effective? A: Start with last meeting's action items, use questions that invite honesty rather than politeness, take action items yourself instead of adding to the team member's list, and send a follow-up note with your commitments after every meeting.
HowTo: Run Effective One-on-One Meetings as a Product Manager
- Protect 1:1 time as unbreakable and establish a consistent cadence — weekly for direct partners, monthly for stakeholders — treating cancellation as a trust withdrawal
- Open every 1:1 by reviewing action items you committed to at the previous meeting before adding anything new to the agenda
- Use the four-block agenda: personal check-in (5 min), blockers and support (10 min), career and growth (10 min), feedback exchange (5 min)
- Ask questions designed to surface what group settings never will — including what team members privately disagreed with and what they would change about how the team operates
- Close by identifying action items that you will own, not the team member — your job is to remove friction from their path, not add to their task list
- Send a one-paragraph follow-up summary with your specific commitments after every meeting