Start-With-Why One-Pager
The PM's core artifact: define the thing by nailing the problem and why-now before anything else.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 90%
Crowley frames the one-pager/PRD/spec as the PM's signature artifact, the equivalent of designs for designers and code for engineers. Its most important section is the opening background-and-context that answers what the problem is, why it matters, and why it matters now. Get those right and the rest is easy; the doc then becomes the running home base for decisions made along the way.
Origin
Maggie Crowley's articulation of a widely-used PRD practice, emphasizing the 'why now' element she says most people omit; she connects the 'why now / side quest vs main quest' idea to Linear founder Karri Kuoppala's framing shared on the same podcast.
Core principles
- 01The one-pager is the PM's artifact and their chance to start with why
- 02Center the team on the problem before any solution
- 03'Why now' is perishable: some opportunities exist only in a window
- 04The doc is a living decision log, not a one-time spec
How to run it
- 1
Write background and context
Open with the background and context: what is the problem, why does it matter, and why does it matter now. Keep it plain, literally answer those three questions.
Pro tip Literally write 'why this problem matters' and 'why this problem matters now' as prompts and answer them; don't make it complicated.
Watch out Don't forget why it's worth solving right now versus every other problem you could solve; most people skip the 'why now.'
- 2
Take it to the team and get it shredded
Before going any further, bring the doc to your squad (product, design, engineering) and use it to have a conversation, inviting smart people to poke holes.
Pro tip Go to your engineering counterpart first and ask them to tear it down; that's how it gets better.
Watch out Don't be precious about your work; you need people to poke holes in it.
- 3
Keep a running decision log
As the project proceeds, record dated decisions ('on this day we decided X,' or 'we decided to solve only this part of the problem'), and link off to research and artifacts, making the doc the home base.
In the wild
Crowley observes that 'why now' shows up constantly when investing in startups but rarely in product building, even though certain opportunities are perishable and disappear if not pursued now.
→ Answering 'why now' pre-empts the question a stakeholder will inevitably ask and forces genuine focus on perishable opportunities.
Common mistakes
Skipping discovery and the one-pager entirely
On a doomed rewrite, Crowley's team skipped discovery, didn't really write a one-pager, and didn't do technical/design research into the actual requirements, and it spiraled from a promised 6 months to 2.5 years.
Is it for you?
Best for
PMs kicking off a defined product/feature with a design-engineering squad who need to align everyone on the problem before building.
Not ideal for
Exploratory strategy-level questions, which call for the fuller landscape-first strategy doc instead.
From the transcript
“the most important section in my opinion in the document is is this this first part which is like what is the background and context…”
“I would literally write why this problem matters and why this problem matters now”
“it can become the home base of the decisions that you make along the way”
“the first person I go to was typically speaking my engineering counterpart and I say like shred this like go through it rip it apart”
From the episode
Mastering product strategy and growing as a PM
Maggie Crowley (Toast, Drift, Tripadvisor)