PM Writing Skills Guide
(2026 Edition)
5 rules for great PM writing with before/after examples, 5 document types every PM writes, and how to improve your writing deliberately.
Practice PM Writing Daily — Free →5 Rules for Great PM Writing
1. Lead with the answer, not the setup
❌ Before
Over the past 3 weeks, we've been seeing some interesting patterns in our retention data that I wanted to bring up because I think there's something worth discussing as a team...
✅ After
D7 retention dropped from 28% to 22% over 3 weeks. Likely cause: the onboarding change shipped on Oct 14. Proposal: rollback by Friday.
💡 Executives and engineers skim. The first sentence should be the takeaway. Everything else is evidence for that takeaway.
2. Cut hedging words
❌ Before
I think we could potentially consider perhaps launching this next quarter, maybe in some kind of phased rollout.
✅ After
We'll launch in Q2 with a phased rollout: 10% → 50% → 100%.
💡 Hedging signals lack of conviction. Say what you mean. If you're uncertain, name the uncertainty directly: 'I'm 70% confident' beats 'I think maybe.'
3. Use numbers, not adjectives
❌ Before
A lot of users are complaining about the checkout flow, and retention seems to have gotten worse recently.
✅ After
Support tickets about checkout are up 3x (from 12/week to 38/week). D7 retention is down from 24% to 18% week-over-week.
💡 Vague adjectives ('a lot,' 'better,' 'worse') don't inform decisions. Numbers force specificity and enable judgment.
4. Name names and owners
❌ Before
Someone should probably look into this and figure out what we can do.
✅ After
@Priya will audit checkout analytics by Thursday and share findings. I'll own the decision on rollback by EOD Friday.
💡 Passive voice kills accountability. Every important action needs a name + deadline + what 'done' looks like.
5. Structure for scanning
❌ Before
One long paragraph with multiple points and no formatting that makes the reader parse everything in order just to find what they care about.
✅ After
**Context:** retention dropped. **Cause:** onboarding change. **Proposal:** rollback Friday. **Owner:** me. **Decision needed by:** Wednesday.
💡 Headings, bullets, and bold text let readers skim to the part they need. This is how busy people read.
5 Document Types Every PM Writes
PRD (Product Requirements Document)
2–3 pages ideal; 5 max🎯 Goal: Align a cross-functional team on what to build and why
📐 Structure: Overview → Problem → Goals/Non-goals → User Stories → Success Metrics → Design → Technical Considerations → Rollout → Open Questions
Weekly Exec Update
5 bullets, 60 seconds to read🎯 Goal: Keep leadership informed without taking their time
📐 Structure: 1 line summary → 3 bullets of progress → 1 blocker/risk → 1 priority for next week
Strategy Memo
4–6 pages🎯 Goal: Make a considered case for a directional change or major bet
📐 Structure: TL;DR → Context → Our thesis → Evidence → Risks and mitigations → What we're NOT doing → Asks
Post-Launch Retro
1–2 pages🎯 Goal: Capture learnings from a launch, good or bad
📐 Structure: What we shipped → What went well → What didn't → What we learned → What we'd do differently
Decision Doc
1 page🎯 Goal: Document a reversible or hard decision so the team is aligned
📐 Structure: Decision → Context → Options considered → Why this option → Who decided → When revisited
FAQ
Why is writing such an important PM skill?
Because PMs influence through clarity, not authority. Every time you align a team, persuade an executive, or set direction, you're doing it through written artefacts (PRDs, strategy docs, updates) as much as through conversation. PMs who write clearly get their ideas shipped; PMs who write fuzzily get endless meetings. At senior levels, writing quality increasingly separates strong from average PMs.
How do you improve PM writing?
Three habits compound: (1) write one long-form async update per week and get feedback from a peer, (2) read exceptional PM writing — Lenny Rachitsky, Shreyas Doshi, First Round Review, Packy McCormick — and steal structures, (3) ruthlessly edit your own drafts. Cut 20% of every first draft. The best PMs revise more than they write.
Should PM writing be formal or casual?
Direct. Neither formal nor casual — just direct. 'This feature will ship Q2' beats both 'We are pleased to announce the feature is targeted for Q2' AND 'lol gonna ship this in Q2 hopefully.' Clarity outranks tone. Match your audience — executives prefer brevity, engineers prefer specificity — but always prioritise clarity over register.
Build PM Writing Muscle Daily
Practice writing PRDs, updates, and strategy memos — with AI feedback.
Start Free Trial →