126 lines
4.1 KiB
Markdown
126 lines
4.1 KiB
Markdown
# Journey-Driven PRD Template
|
|
|
|
## 🎯 Vision Statement
|
|
*"We believe that [user type] should be able to [achieve outcome] without [current pain point]. When this happens, [positive impact]."*
|
|
|
|
## 🎭 Character Profiles
|
|
### Primary Protagonist: [User Persona Name]
|
|
- **Background Story**: [Brief user story and context]
|
|
- **Motivation**: [What drives this user]
|
|
- **Current Struggle**: [Specific pain points they face]
|
|
- **Desired Transformation**: [How they want to change]
|
|
|
|
### Supporting Characters
|
|
- **Antagonist**: [Main obstacle or competing solution]
|
|
- **Mentor**: [How your product guides the user]
|
|
- **Allies**: [Other users or systems that help]
|
|
|
|
## 📖 The Hero's Journey
|
|
### Act 1: The Ordinary World
|
|
- **Current State**: [What users do now]
|
|
- **Inciting Incident**: [What triggers the need for change]
|
|
- **Refusal of the Call**: [Why users resist change]
|
|
|
|
### Act 2: The Special World
|
|
- **Crossing the Threshold**: [How users discover your solution]
|
|
- **Tests & Allies**: [Key features and integrations]
|
|
- **Approach to the Inmost Cave**: [Core user experience]
|
|
- **The Ordeal**: [Critical decision points or challenges]
|
|
- **Reward**: [Value users receive]
|
|
|
|
### Act 3: Return with the Elixir
|
|
- **The Road Back**: [How users return to their workflow]
|
|
- **Resurrection**: [Transformation achieved]
|
|
- **Return with the Elixir**: [Ongoing value and sharing]
|
|
|
|
## 🎪 Key Scenes (Features)
|
|
### Scene 1: [Feature Name]
|
|
- **Setting**: [Where/when this happens]
|
|
- **Characters**: [Who's involved]
|
|
- **Action**: [What happens]
|
|
- **Dialogue**: [User interactions]
|
|
- **Outcome**: [Result for the user]
|
|
|
|
### Scene 2: [Feature Name]
|
|
- **Setting**: [Where/when this happens]
|
|
- **Characters**: [Who's involved]
|
|
- **Action**: [What happens]
|
|
- **Dialogue**: [User interactions]
|
|
- **Outcome**: [Result for the user]
|
|
|
|
## 🎬 Technical Production
|
|
### Props & Sets (Technical Requirements)
|
|
- **Core Infrastructure**: [Backend systems needed]
|
|
- **User Interface**: [Frontend components]
|
|
- **Data Management**: [Storage and processing]
|
|
- **Integration Points**: [APIs and third-party services]
|
|
|
|
### Special Effects (Advanced Features)
|
|
- **AI/ML Capabilities**: [Intelligent features]
|
|
- **Real-time Processing**: [Dynamic functionality]
|
|
- **Personalization**: [User-specific experiences]
|
|
|
|
## 📊 Success Metrics (Box Office Numbers)
|
|
### Leading Indicators
|
|
- **User Engagement**: [Daily/weekly active users]
|
|
- **Feature Adoption**: [Usage of key features]
|
|
- **Time to Value**: [How quickly users see benefits]
|
|
|
|
### Lagging Indicators
|
|
- **User Retention**: [Long-term engagement]
|
|
- **Business Impact**: [Revenue, efficiency gains]
|
|
- **User Satisfaction**: [NPS, reviews, testimonials]
|
|
|
|
## 🎭 User Journey Map
|
|
```
|
|
[User's Current State]
|
|
↓ (Pain Point)
|
|
[Discovery of Solution]
|
|
↓ (Onboarding)
|
|
[First Value Realization]
|
|
↓ (Adoption)
|
|
[Regular Usage Pattern]
|
|
↓ (Advanced Features)
|
|
[Power User Status]
|
|
↓ (Advocacy)
|
|
[Referral & Sharing]
|
|
```
|
|
|
|
## 🎪 Go-to-Market Strategy
|
|
### Opening Night (Launch)
|
|
- **Target Audience**: [Initial user segment]
|
|
- **Marketing Channels**: [How to reach users]
|
|
- **Success Criteria**: [Launch metrics]
|
|
|
|
### Word of Mouth (Growth)
|
|
- **Viral Mechanisms**: [How users share]
|
|
- **Referral Programs**: [Incentives for sharing]
|
|
- **Community Building**: [User engagement]
|
|
|
|
## 🎬 Risk Assessment
|
|
### Plot Twists (Potential Issues)
|
|
- **Technical Risks**: [System failures, performance]
|
|
- **User Adoption Risks**: [Resistance to change]
|
|
- **Market Risks**: [Competition, market changes]
|
|
|
|
### Contingency Plans
|
|
- **Plan B Scenarios**: [Alternative approaches]
|
|
- **Rollback Strategies**: [How to recover]
|
|
- **User Communication**: [How to handle issues]
|
|
|
|
## 📝 Success Criteria
|
|
### Minimum Viable Product (MVP)
|
|
- [ ] Core user journey complete
|
|
- [ ] Basic functionality working
|
|
- [ ] Initial user feedback positive
|
|
|
|
### Full Release
|
|
- [ ] All key scenes implemented
|
|
- [ ] Performance targets met
|
|
- [ ] User satisfaction high
|
|
- [ ] Business metrics achieved
|
|
|
|
---
|
|
|
|
*This template transforms product development into a storytelling experience, making it easier to understand user needs and create compelling solutions.*
|