- Home
- Templates
- Product Requirements Document (PRD)
- Marty Cagan's Inspired/Empowered PRD
Marty Cagan's Inspired/Empowered PRD
Based on Marty Cagan's approach from Inspired and Empowered. Focuses on empowered product teams with clear problem definition, constraints, and success criteria rather than prescriptive solutions.
PRD: Marty Cagan "Inspired & Empowered" Variant
This variant follows Marty Cagan's product discovery philosophy: opportunity-focused, problem-first, team empowerment, and dual-track discovery (parallel design/engineering). Emphasis on understanding the customer's job-to-be-done and validating assumptions before full implementation.
Document Metadata
- Template Variant: Marty Cagan "Inspired & Empowered"
- Philosophy: Opportunity discovery, customer empowerment, design/engineering collaboration
- Best For: Innovative features, unclear customer needs, high-risk/high-reward bets
- Author: [PM Name]
- Date: [YYYY-MM-DD]
- Status: [DRAFT | VALIDATING | APPROVED | ACTIVE]
The Opportunity (Not the Solution)
The biggest mistake PMs make is jumping to solutions before fully understanding the opportunity. Start here.
Problem Discovery
What problem are we trying to solve? Ground this in customer research, not your intuition.
Customer Job-to-be-Done:
[Reference Oster's Jobs-to-be-Done framework. What is the customer trying to accomplish?]
Discovered Through:
- Direct customer interviews (count: ___)
- Customer observation/shadowing (count: ___)
- Market research (source: ___)
- User behavior data (metric: ___)
Why Now? (Timing)
Opportunities have windows. Why is this the right time?
- Market Signal: [What changed in the market?]
- Competitive Threat: [What are competitors doing?]
- Technology Enablement: [What new capability enables this?]
- Customer Urgency: [How desperate are customers for this?]
Showing 40 of 330 lines
Enter your email below to unlock the full template
Unlock Full Template
Enter your email to access the complete template
Frequently Asked Questions
How does Marty Cagan's PRD differ from traditional PRDs?
Cagan's approach focuses on defining the problem, constraints, and success criteria rather than prescribing solutions. The engineering team is empowered to find the best solution. The PRD defines 'what' and 'why', not 'how'.
Other Product Requirements Document (PRD) Variants
Lenny Rachitsky's PRD Template
Lenny Rachitsky's practical PRD format that balances comprehensiveness with usability. Includes structured sections for problem, solution, user stories, and launch planning.
Kevin Yien's Stripe/Square PRD
Kevin Yien's PRD format refined at Stripe and Square. Emphasizes clear problem definition, user-centric design, and measurable outcomes with minimal overhead.
Related Templates
Fill This Template With AI
PM33 turns these templates into living documents. AI-powered suggestions, auto-populated metrics, and team collaboration built in.
Join the Waitlist