Develop the writing discipline of PM: Amazon's working-backwards PR/FAQ, the Shape Up pitch format, and the lightweight spec that survives contact with implementation. By the end you can write a press-release-first narrative for a launch, a pitch for a cycle, and — most importantly — you've absorbed that PM writing is writing first, and the format is downstream of the prose being good. The PR/FAQ is test-first development: writing the press release before the product commits you to the observable outcome before the implementation pathway, reveals the cases you hadn't considered, feels slow upfront, and saves multiples downstream. If you accept TDD as a discipline, you accept the PR/FAQ on the same grounds. The fat-marker sketch is the good architecture diagram — deliberately incomplete, showing load-bearing components and omitting details, because diagrams that specify everything are read by no one. The lightweight spec is commit-message discipline at feature scale. And Zinsser's "every word must earn its place" is code review for prose: you don't approve a PR with unused imports and dead code paths; same standard, different artifact.
This course unlocks once you've finished its prerequisite. Open prerequisite →
This is the most underrated module in the curriculum and probably the one with the highest return on time invested. The reason it's underrated: the topic looks small. Specs. Templ…
PM craft is partly writing craft, and this is rarely said because the audience either thinks it can already write or thinks writing is separate from "real" PM work. Both are wrong…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Applied to a surviving product from M4 — ideally the same one as M5.
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.