borghei/Claude-Skills / project-management/career/pm-1on1s
pm-1on1s
VerifiedBuilds 1:1 agendas and kickoff scripts for a PM's manager, EM, designer, reports and cross-functional partners. Use when starting a new 1:1, a 1:1 has turned into status updates, or you need to give a partner hard feedback.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.6 KB |
| assets/1on1_notes_template.md | markdown | 2.0 KB |
| assets/kickoff_template.md | markdown | 3.3 KB |
| assets/manager_1on1_agenda.md | markdown | 3.0 KB |
| examples/sr-pm-first-month-with-em-partner.md | markdown | 12.4 KB |
| references/1on1-playbook.md | markdown | 7.9 KB |
| references/one-on-one-templates.md | markdown | 10.2 KB |
| references/red-flags.md | markdown | 12.1 KB |
references/1on1-playbook.md
View on GitHub# 1:1 Playbook for PMs
A deep dive on cadence, structure, and the partner-type specifics that make PM 1:1s work.
---
## 1. Cadence by partner type
| Partner | Default cadence | Length | Format |
|---------|-----------------|--------|--------|
| Manager | Weekly | 30-45 min | Live; written prep |
| Skip-level | Quarterly | 30 min | Live |
| Engineering manager partner | Weekly | 30 min | Live |
| Design lead partner | Weekly to bi-weekly | 30 min | Live |
| Direct report (PM) | Weekly | 45-60 min | Live |
| Adjacent PM peer | Bi-weekly to monthly | 30 min | Live or async |
| Sales / GTM lead | Monthly | 30 min | Live |
| Customer Success lead | Monthly | 30 min | Live |
| Support lead | Monthly | 30 min | Live (or async during quiet periods) |
| Data / analytics partner | Bi-weekly | 30 min | Live |
| Marketing partner | Monthly | 30 min | Live |
| Legal / privacy partner | Quarterly | 30 min | Live (more during compliance events) |
The cadence is the floor, not the ceiling. During launches, incidents, or org changes, double the cadence temporarily.
---
## 2. The three failure modes
Across PM 1:1s, three failure modes dominate:
### Failure mode 1: The status meeting
The 1:1 becomes "what's happening on project X". The PM reads off the status update. The other person nods.
**Why it fails:** Status can be written. The 1:1 wastes scarce live time.
**Fix:** Move status to a written async update. Use the 1:1 for what cannot be written: trust, judgment, feedback, growth.
### Failure mode 2: Ruinous empathy
The PM cares deeply about the relationship but never delivers hard feedback. Issues accumulate. By the time the PM does say something, it lands as a surprise.
**Why it fails:** Feedback delayed is feedback compounded. Late feedback feels disproportionate even when it isn't.
**Fix:** Give the feedback in the next 1:1 after the moment. Use situation-behavior-impact framing.
### Failure mode 3: Solving instead of coaching
The PM (especially with direct reports) jumps to "here's what I'd do". The report's judgment doesn't grow.
**Why it fails:** Coaching is the multiplier; solving is the additive. A PM who coaches well develops 5x their own capacity.
**Fix:** Use GROW. Ask three questions before giving any answer.
---
## 3. Structuring the manager 1:1
The manager 1:1 is the most important 1:1 you run. Treat it with discipline.
### Pre-meeting (15 min, day of)
- Review your running 1:1 notes doc
- List 3 things you want from this 1:1
- Identify 1 piece of feedback you have for your manager (if relevant)
- Identify 1 growth question
- Send the agenda to your manager 30+ min before
### During the meeting
| Block | Content |
|-------|---------|
| Opening | "What's top of mind for you?" (Let them go first) |
| Your topics | The 3 things from prep |
| Feedback | One specific moment, situation-behavior-impact |
| Growth | One question that opens a longer conversation |
| Close | Confirm 2-3 action items, owner of each |
### After the meeting (5 min)
- Update the running notes doc
- Add action items to your task system
- If feedback was shared, send a written follow-up summarizing what you heard
---
## 4. Structuring the direct-report 1:1
If you manage PMs, this is the highest-leverage 1:1 you run.
### Default rules
1. **Their agenda first.** Even if you have a hot topic, ask "What's on your mind?" before your topic.
2. **Coach, don't solve.** Use GROW unless the question is purely factual.
3. **Make space for feedback both ways.** Always end with "What feedback do you have for me?"
4. **Track growth across cycles.** Bring up their growth plan monthly.
### Monthly growth conversation (replaces one weekly 1:1)
A deeper 60-minute conversation, with the growth plan as the agenda:
| Block | Time | Content |
|-------|------|---------|
| Check-in on the cycle theme | 5 min | "What's your read on how this month went against your cycle theme?" |
| Evidence and behaviors | 15 min | Walk through each focus area; capture new evidence |
| Calibration sense-check | 10 min | "Where do you think you'd be scored today? Where do I see you?" |
| Manager observation | 15 min | Manager-driven feedback on what's working and what's not |
| Adjustments | 10 min | Update experiments, evidence targets |
| Close | 5 min | Confirm next month's experiments |
### Quarterly rubric calibration
Use `pm-career-ladder/assets/gap_analysis.md` to score together.
### Annual career conversation
Use a separate planning session, not a 1:1 block. 60-90 minutes, calendar-blocked weeks in advance.
---
## 5. Structuring the EM partner 1:1
This is the relationship that most determines team velocity. Invest in it.
### Five questions to ask the EM partner monthly
1. "What am I doing that makes your team's life harder?"
2. "Where are we mis-aligned on priorities right now?"
3. "What's an opinion you have about the roadmap you haven't shared yet?"
4. "Where are you over-extended?"
5. "What's a piece of feedback for me you've been sitting on?"
### Partnership health quarterly review (60 min)
Once a quarter, run a longer 60-minute reset:
- What's working in our partnership?
- What's not working?
- Where are our decision rights ambiguous?
- What process should we change?
- What's our shared bar for the next quarter?
---
## 6. Structuring the design partner 1:1
Design 1:1s often slip toward project review. Resist.
### Three categories to rotate weekly
1. **Craft conversation** -- A design pattern, a competitor's UX, a quality bar discussion
2. **User research** -- What we've learned, what we should run next
3. **Project review** -- Current designs in flight (default fallback)
The strongest design partnerships spend 60%+ of 1:1 time on categories 1 and 2.
---
## 7. Async 1:1s
Sometimes a live 1:1 isn't possible. Async 1:1s can work for partner-of-partner relationships (adjacent PM peers, monthly cross-functional partners).
### Async 1:1 structure
Each person writes (in a shared doc) before a deadline:
- Top 2-3 things on my mind
- Anything I need from you
- Anything I want you to know
The other person responds inline within 24 hours. If a response sparks a longer thread, schedule a live 1:1.
### When async 1:1s fail
- Trust-building (impossible async)
- Coaching conversations (GROW needs live back-and-forth)
- Feedback delivery (always live, never async)
- High-stakes alignment (always live)
---
## 8. The "what to do when nothing's wrong" problem
Sometimes the 1:1 has no urgent topics. Three good defaults:
1. **Reflection question.** "What's one thing you've changed your mind about this quarter?"
2. **Trust-building.** Share something about your week that's not work.
3. **Strategic conversation.** "If we had no constraints, what would we build in this area?"
A 1:1 with no urgent agenda is an opportunity for the long-term work that gets crowded out otherwise.
---
## 9. Ending the 1:1
Strong closes have three elements:
1. **Recap the 2-3 action items.** Owner of each. Don't leave action items implicit.
2. **Confirm the next 1:1.** "Same time next week? Anything different we should plan for?"
3. **Closing exchange.** "Anything I can do for you in the next two weeks?"
The closing exchange signals partnership and reciprocity. It is the single most under-used 1:1 ritual.
---
## 10. Reviewing your 1:1s quarterly
Once a quarter, audit:
| Question | Action if "no" |
|----------|----------------|
| Are my 1:1s producing decisions and growth, or just status? | Adopt the partner-type templates |
| Am I giving regular hard feedback? | Schedule one feedback conversation per Tier-1 partner this month |
| Are my cancellation rates <10%? | Re-cadence; if you cancel 30%, the cadence is wrong |
| Do my direct reports leave 1:1s with a clearer next step (not a solved problem)? | Shift from solving to coaching with GROW |
| Do I get feedback from my reports / partners in 1:1s? | Ask explicitly; demonstrate non-defensiveness when they share once |
The 1:1 system that works for a PM at year 3 of the job will not work at year 6. Re-audit annually.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |