The 'Why Now' One-Pager
by Maggie Crowley • Vice President of Product at Toast
Maggie is currently VP of Product at Toast, with previous leadership roles at Charlie Health, Drift, BevSpot, and TripAdvisor. She holds an MBA from Harvard Business School and is a former Olympic speed skater.
🎙️ Episode Context
Maggie Crowley discusses the tangible traits that separate great product managers from the rest, emphasizing the importance of simplifying complexity and "carrying the water" (doing unglamorous work). She shares a detailed framework for writing product strategy documents that align teams, breaks down how to write effective one-pagers, and offers contrarian views on why being "data-driven" can sometimes be a red flag.
Problem It Solves
Prevents feature creep and aligns the team on the urgency and specific problem context.
Framework Overview
A simplified spec document that prioritizes the context and timing over the feature list. It centers the team around the problem rather than the solution details.
🧠 Framework Structure
Start with Context: Define the backgr...
The Two Critical Whys: Explicitly ans...
Record Decisions: Use the doc to log ...
Collaborative Shredding: Present it t...
When to Use
At the kickoff of any new feature or initiative, before design or code begins.
Common Mistakes
Skipping the 'Why Now' justification or making the document too long/complex so no one reads it.
Real World Example
Using the One-Pager to center a team's engineering and design efforts on a specific user problem, rather than just handing off a solution to build.
What is the problem, why does it matter, and why does it matter now?
— Maggie Crowley