PM 1:1
Template Pack.
Three formats: PM ↔ Manager, PM ↔ Engineering Manager, PM ↔ Designer. Replace the awkward silence.
Cadence: ______
Doc owner: ______
Why most PM 1:1s waste time
Most PM 1:1s default to status updates that should be in the tracker. The PM walks through what they shipped, the manager nods, and 30 minutes evaporate. 1:1 time is for the things that don’t fit anywhere else — ambiguity, friction, growth, decisions you can’t make alone, signals you don’t want to put in a public Slack channel. If your last 1:1 could have been an async update, you used the slot wrong. Reclaim it with structure.
The universal 4-block structure
All three formats below use the same four blocks. The blocks shift in proportion depending on who you’re meeting with, but the bones are constant.
Doc rule: a shared rolling doc, owned by the PM, with action items captured at the bottom. If it isn’t written down, it didn’t happen.
Format 1 — PM ↔ Manager (weekly, 30 min)
- Top of mind — PM names the single most-important unresolved thing.5 min
- Where I need a decision — not advice; an actual call.8 min
- Signals from the team — what the manager won’t hear elsewhere (eng frustration, design tension, exec pressure).5 min
- Career & growth — quarterly thread; touch monthly minimum.5 min
- Two-way feedback — one specific item each direction.5 min
- Action items — written into the rolling doc with owners.2 min
- What did I deliver this week vs. what I committed to?
- What context do I have that you’re missing?
- Where am I being blocked — and what would unblock me?
- What’s the one decision you’d make differently if you were me right now?
- What’s my growth focus this quarter, and what’s the next visible signal of progress?
- What feedback have you heard about me from someone else this week?
- Where am I underweighting the bigger picture and overweighting the work in front of me?
- What’s the next stretch assignment you’d trust me with?
- How can I help you this week — specifically?
- What’s a meeting I’m in that I shouldn’t be?
- What signal am I sending that I don’t intend to send?
- What’s one thing I should stop doing?
Once a quarter, replace the agenda with: where am I now, where do I want to be in 12 months, what are the three things I need to demonstrate to move? Document the three things. Refer back at the next quarterly. Promotions become defendable when the artifact predates them.
When something belongs above your manager, say so explicitly: "I think this needs your manager involved — here’s why." Don’t go around them; bring them with you. The trust you build by being explicit pays back when you actually need air cover.
Format 2 — PM ↔ Engineering Manager (bi-weekly, 30 min)
- Are we still aligned on the why? — the most underrated check. Surface drift early.5 min
- Delivery health — what’s on track, at risk, slipping. Surface dependencies that aren’t visible in the tracker.8 min
- Quality / debt conversation — explicit slot. What’s eroding velocity? What’s a safe place to invest?6 min
- People signals — engineer frustrations the EM is hearing, scope tensions, attrition risk.5 min
- Cross-team dependencies — named owners and named risks.4 min
- Action items + alignment doc update.2 min
- If we shipped exactly what we’re building today, what would disappoint you in three months?
- What’s a scope cut you’d propose if I made it safe to propose?
- Where am I creating ambiguity that’s slowing the team down?
- What dependency are we underestimating right now?
- Which engineer is at risk of burnout or boredom — and what would help?
- What technical debt is silently capping our velocity this quarter?
- Where would more PM context unblock an engineer’s decision?
- What’s a hire we should be making that we’re not?
- If we paused all new work for a week, what’s the most valuable thing the team could do?
- How are we doing on the “why are we building this?” alignment — honest answer?
Drift between PM and EM on intent — not delivery — is the silent killer of every initiative that “shipped but didn’t land.” Every other 1:1, ask: "if you had to explain why we’re building this in one sentence to your most senior engineer, what would you say?" If their answer differs from yours, that’s the most valuable signal in the meeting.
Format 3 — PM ↔ Designer (weekly, 20 min)
- Discovery alignment — what we’re investigating, what we’re assuming, what we’d need to disprove.6 min
- Research debrief — what came out of recent customer conversations or usability sessions.5 min
- Design-debt surfacing — the patterns that are silently breaking down at scale.4 min
- One open question we’ll bring to engineering together.3 min
- Action items.2 min
- What’s the customer behavior we’re trying to change, in their words?
- What pattern in the product is silently degrading right now?
- Which assumption in this spec do you least believe?
- What’s a piece of design debt that would cost us a quarter if we don’t fix it soon?
- What did the last 3 customer conversations make you want to redesign?
- Where am I over-specifying and crowding out your discovery?
- What would you ship if I gave you a week with no PM input?
- What’s a UI choice we made — and accept — that you actually disagree with?
Escalation patterns
Escalation is not failure — it’s the system working. The trick is doing it before the relationship costs more to repair than the issue costs to surface. Four explicit triggers:
Skip-level 1:1s
Twice a year, request a 25-minute skip-level. The goal is signal, not gossip. Three questions, no fourth:
- What’s working in our team that you’d want other teams to copy?
- What’s blocked for you because of how our team operates?
- What would you change about my role or scope if you were me?
Send the questions a day in advance so they think before the meeting. Take notes. Share the relevant signals back to your manager — same week, written, not in passing.
The 1:1 anti-patterns
- Status updates as the agenda. Anything that could be written async should be. 1:1 is for what doesn’t fit anywhere else.
- No documented action items. If you can’t list the actions from your last 1:1, you didn’t have a 1:1 — you had a chat.
- Canceling without rescheduling. Cancel happens. Cancel-without-reschedule signals: "you don’t matter." Reschedule the same week or own the cost.
- All-tactical, no-strategic. If 6 weeks pass without a single career or strategy conversation, you’re stuck in a status loop. Force one in deliberately.
- Manager doing all the talking. The PM owns the agenda. The PM drives. If you’re a manager doing 70% of the talking, you’re solving the wrong problem.
Async 1:1 template
When sync isn’t possible — travel, illness, scheduling collision — don’t skip. Run the async version: a 15-minute structured doc + a 5-minute sync.
- PM writes (10 min, the day before): what shipped, what’s burning, where I’m stuck, one growth note, one feedback item up.
- Manager reads + comments (10 min, async): answers each section in writing, with named decisions and one feedback item down.
- 5-minute sync call (or 5-minute Loom): only the items that need spoken nuance — tone, complex decisions, anything sensitive.
Done well, async 1:1s produce more documented signal than sync ones. Don’t treat them as a downgrade.