pm 1:1 meeting template

Most PMs waste their 1:1s. They walk in without an agenda, give a project update their manager could have read in Jira, and walk out having used 30 minutes to accomplish nothing that an async message could not have handled.

A 1:1 is your protected time for the conversations that do not happen naturally: strategic questions, career feedback, difficult alignment issues, decisions that need a face rather than a thread. The rule is simple: the person who is NOT the manager owns the agenda. You drive the 1:1 with your manager. You drive the 1:1 with your engineering lead. You show up with a document, not an open-ended “anything to discuss?”

Below are three templates. Pick the one that matches your meeting, copy it, and fill it in before the meeting starts.

Template 1: PM and Engineering Lead (weekly, 30 min)

This is your most operational 1:1. The goal is alignment on what is happening this week and what is coming next week, so neither of you gets surprised.

# 1:1: [Your Name] ↔ [Eng Lead Name] · [Date]

## This week's priorities (5 min)
- What I am focused on:
- What you are focused on:
- Are we pointed at the same thing? [yes/no — if no, resolve now]

## Blockers and decisions (10 min)
- Decisions I need from you:
- Decisions you need from me:
- Blocked items (who owns unblocking, by when):

## Technical debt and quality (5 min)
- Anything degrading that we should address this sprint?
- Anything I am asking for that is harder than I think it is?

## Next sprint preview (5 min)
- What is likely coming in the next sprint:
- Capacity concerns (PTO, oncall, other commitments):

## One thing unsaid (5 min)
- Is there anything about how we are working together that is not working?

Why “one thing unsaid” matters: Engineering leads will not volunteer frustration about unclear specs, shifting priorities, or being pulled into meetings. You have to ask directly, every week, until they trust that the question is real.

Template 2: PM and Manager (weekly, 30 min)

This is your growth and decision-support meeting. Do not bring your manager a status update — bring them a question, a trade-off, or a request.

# 1:1: [Your Name] ↔ [Manager Name] · [Date]

## What I need from you this week (10 min)
- Decision I need help with:
- Context: [the trade-off, not just the question]
- My recommendation: [always bring one]

## Strategic question (10 min)
- Something I am thinking about but do not have clarity on:
  [Could be about product direction, org dynamics,
  a stakeholder conflict, or a bet you are unsure about]

## Feedback (5 min)
- Feedback I want on something specific I did this week:
- Feedback I have for you: [yes, upward feedback — say it]

## Career and growth (5 min)
- Skill I am working on this month:
- What I need to get to the next level:
- Anything I should be doing differently?

The “my recommendation” rule: Never bring your manager a naked question. “Should we build X or Y?” is a delegation of your job. “I recommend X because of Z, but Y has this trade-off — what am I missing?” is a decision support request. Your manager’s job is to pressure-test your thinking, not to think for you.

Template 3: PM and Stakeholder (biweekly, 30 min)

This is your alignment meeting. Stakeholders — sales leads, marketing, ops, finance — do not need your sprint details. They need to know what is coming, what is not coming, and where you need their input.

Use the ROAD format: Results, Outlook, Ask, Decisions.

# 1:1: [Your Name] ↔ [Stakeholder Name] · [Date]

## Results since last meeting (5 min)
- What shipped:
- Key metric movement:
- Customer feedback signal:

## Outlook for next 2-4 weeks (10 min)
- What is coming next:
- What got deprioritised and why:
- Timeline risks:

## My ask (10 min)
- What I need from your team:
- By when:
- What happens if I do not get it:

## Decisions to align on (5 min)
- Open decision that affects both of us:
- My recommendation:
- Your input needed by [date]:

Why biweekly, not weekly: Weekly stakeholder 1:1s decay into status meetings within a month. Biweekly gives you enough time between meetings to have something real to report and something real to ask for. If a stakeholder insists on weekly, counter with: “Let me send you a weekly async update and we meet biweekly for the conversations that need a room.”

How to make these stick

Prepare before the meeting, not during it. Fill in your template 15 minutes before the 1:1. If you cannot fill it in, that tells you something — either nothing important happened this week (unlikely) or you are not paying attention to the right things.

Share the doc before the meeting. Send it 30 minutes ahead. This lets the other person read, react, and come prepared to discuss rather than absorb. The meeting becomes a conversation, not a presentation.

Rotate the “one thing unsaid” question. People stop answering honestly if the question becomes routine. Vary it: “What is the most annoying thing about working with me right now?” or “If you could change one thing about how our team operates, what would it be?”

Related pages

• Stakeholder Management — how to identify which stakeholders need a recurring 1:1 and which need an async update
• Working with Engineering — the full picture of PM-engineering collaboration, not just the weekly sync
• IC to Senior PM — how the quality of your 1:1s changes as you move from execution to strategy