179 lines
4.0 KiB
Markdown
179 lines
4.0 KiB
Markdown
# Vision Document Template
|
|
|
|
Use this template when creating a vision issue in GitHub Projects. Copy the structure below into the issue description, then fill in each section based on the discovery process.
|
|
|
|
---
|
|
|
|
## Product Vision: [Product Name]
|
|
|
|
### Problem Statement
|
|
|
|
**What problem exists?**
|
|
|
|
[Describe the core problem being addressed. Be specific about the pain points, challenges, or inefficiencies that currently exist.]
|
|
|
|
**Why does this problem matter?**
|
|
|
|
[Explain the impact of this problem—costs, frustration, missed opportunities, risks, etc. Quantify when possible.]
|
|
|
|
**Current State:**
|
|
|
|
[How do people currently address this problem? What workarounds, competitors, or manual processes exist? Why are these insufficient?]
|
|
|
|
---
|
|
|
|
### Target Users
|
|
|
|
**Primary Users:**
|
|
|
|
- **Who:** [Role, title, context]
|
|
- **Characteristics:** [Expertise level, environment, constraints]
|
|
- **Goals:** [What they're trying to achieve]
|
|
- **Pain Points:** [Specific frustrations or challenges they face]
|
|
|
|
**Secondary Users (if applicable):**
|
|
|
|
- **Who:** [Other stakeholders, admins, support staff]
|
|
- **Relationship:** [How they interact with primary users or the product]
|
|
|
|
**User Personas:**
|
|
|
|
[Optional: Create 1-2 concrete personas with names, backgrounds, and specific scenarios]
|
|
|
|
---
|
|
|
|
### Solution Overview
|
|
|
|
**In one sentence:**
|
|
|
|
[Elevator pitch: What this product does and who it's for]
|
|
|
|
**Core Capabilities:**
|
|
|
|
1. [First major capability]
|
|
2. [Second major capability]
|
|
3. [Third major capability]
|
|
|
|
[Describe the 2-3 essential things this product must do to deliver value]
|
|
|
|
**Unique Value Proposition:**
|
|
|
|
[What makes this solution different from or better than alternatives? Why would users choose this?]
|
|
|
|
---
|
|
|
|
### Core Value Proposition
|
|
|
|
**For Users:**
|
|
|
|
[How does this solution make users' lives better? What specific benefits do they gain?]
|
|
|
|
**Key Benefits:**
|
|
|
|
- [Benefit 1: e.g., Save 10 hours/week on manual reporting]
|
|
- [Benefit 2: e.g., Increase decision confidence with real-time data]
|
|
- [Benefit 3: e.g., Reduce errors from manual data entry]
|
|
|
|
**Differentiation:**
|
|
|
|
[Why is this better than current alternatives? What's the compelling reason to switch/adopt?]
|
|
|
|
---
|
|
|
|
### Success Metrics
|
|
|
|
**How we'll measure success:**
|
|
|
|
| Metric | Target | Timeframe |
|
|
|--------|--------|-----------|
|
|
| [Metric 1: e.g., Active Users] | [e.g., 10,000] | [e.g., 12 months] |
|
|
| [Metric 2: e.g., Weekly Retention] | [e.g., 70%] | [e.g., 6 months] |
|
|
| [Metric 3: e.g., Time Saved per User] | [e.g., 10 hrs/week] | [e.g., 3 months] |
|
|
|
|
**User Success Indicators:**
|
|
|
|
[What user behaviors or outcomes indicate the product is delivering value?]
|
|
|
|
- [Indicator 1]
|
|
- [Indicator 2]
|
|
- [Indicator 3]
|
|
|
|
---
|
|
|
|
### Scope & Boundaries
|
|
|
|
**In Scope:**
|
|
|
|
[What IS included in this vision]
|
|
|
|
- [Capability 1]
|
|
- [Capability 2]
|
|
- [Capability 3]
|
|
|
|
**Out of Scope:**
|
|
|
|
[What is explicitly NOT included—define boundaries to prevent scope creep]
|
|
|
|
- [Not doing 1]
|
|
- [Not doing 2]
|
|
- [Not doing 3]
|
|
|
|
**Future Considerations:**
|
|
|
|
[Things that might be considered later but aren't part of the initial vision]
|
|
|
|
- [Future item 1]
|
|
- [Future item 2]
|
|
|
|
---
|
|
|
|
### Strategic Alignment
|
|
|
|
**Business Goals:**
|
|
|
|
[How does this vision align with broader organizational or business objectives?]
|
|
|
|
**Market Opportunity:**
|
|
|
|
[What market need or opportunity does this address? Size, growth, trends?]
|
|
|
|
**Competitive Landscape:**
|
|
|
|
[Who else is in this space? How do we compare or differentiate?]
|
|
|
|
---
|
|
|
|
### Risks & Assumptions
|
|
|
|
**Key Assumptions:**
|
|
|
|
[What are we assuming to be true that could impact success?]
|
|
|
|
1. [Assumption 1]
|
|
2. [Assumption 2]
|
|
3. [Assumption 3]
|
|
|
|
**Known Risks:**
|
|
|
|
[What could go wrong or prevent success?]
|
|
|
|
- [Risk 1 + mitigation strategy]
|
|
- [Risk 2 + mitigation strategy]
|
|
|
|
---
|
|
|
|
## Notes
|
|
|
|
[Any additional context, background, or considerations]
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
After finalizing this vision:
|
|
|
|
1. Share with stakeholders for feedback and alignment
|
|
2. Identify epics that will deliver on this vision
|
|
3. Reference this vision when prioritizing and making product decisions
|
|
4. Review and update quarterly or when significant learnings emerge
|