110 lines
2.4 KiB
Markdown
110 lines
2.4 KiB
Markdown
---
|
|
name: V6 Idea Submission
|
|
about: Suggest an idea for v6
|
|
title: ''
|
|
labels: ''
|
|
assignees: ''
|
|
---
|
|
|
|
# Idea: [Replace with a clear, actionable title]
|
|
|
|
### PASS Framework
|
|
|
|
**P**roblem:
|
|
|
|
> What's broken or missing? What pain point are we addressing? (1-2 sentences)
|
|
>
|
|
> [Your answer here]
|
|
|
|
**A**udience:
|
|
|
|
> Who's affected by this problem and how severely? (1-2 sentences)
|
|
>
|
|
> [Your answer here]
|
|
|
|
**S**olution:
|
|
|
|
> What will we build or change? How will we measure success? (1-2 sentences with at least 1 measurable outcome)
|
|
>
|
|
> [Your answer here]
|
|
>
|
|
> [Your Acceptance Criteria for measuring success here]
|
|
|
|
**S**ize:
|
|
|
|
> How much effort do you estimate this will take?
|
|
>
|
|
> - [ ] **XS** - A few hours
|
|
> - [ ] **S** - 1-2 days
|
|
> - [ ] **M** - 3-5 days
|
|
> - [ ] **L** - 1-2 weeks
|
|
> - [ ] **XL** - More than 2 weeks
|
|
|
|
---
|
|
|
|
### Metadata
|
|
|
|
**Submitted by:** [Your name]
|
|
**Date:** [Today's date]
|
|
**Priority:** [Leave blank - will be assigned during team review]
|
|
|
|
---
|
|
|
|
## Examples
|
|
|
|
<details>
|
|
<summary>Click to see a GOOD example</summary>
|
|
|
|
### Idea: Add search functionality to customer dashboard
|
|
|
|
**P**roblem:
|
|
Customers can't find their past orders quickly. They have to scroll through pages of orders to find what they're looking for, leading to 15+ support tickets per week.
|
|
|
|
**A**udience:
|
|
All 5,000+ active customers are affected. Support team spends ~10 hours/week helping customers find orders.
|
|
|
|
**S**olution:
|
|
Add a search bar that filters by order number, date range, and product name. Success = 50% reduction in order-finding support tickets within 2 weeks of launch.
|
|
|
|
**S**ize:
|
|
|
|
- [x] **M** - 3-5 days
|
|
|
|
</details>
|
|
|
|
<details>
|
|
<summary>Click to see a POOR example</summary>
|
|
|
|
### Idea: Make the app better
|
|
|
|
**P**roblem:
|
|
The app needs improvements and updates.
|
|
|
|
**A**udience:
|
|
Users
|
|
|
|
**S**olution:
|
|
Fix issues and add features.
|
|
|
|
**S**ize:
|
|
|
|
- [ ] Unknown
|
|
|
|
_Why this is poor: Too vague, no specific problem identified, no measurable success criteria, unclear scope_
|
|
|
|
</details>****
|
|
|
|
---
|
|
|
|
## Tips for Success
|
|
|
|
1. **Be specific** - Vague problems lead to vague solutions
|
|
2. **Quantify when possible** - Numbers help us prioritize (e.g., "20 customers asked for this" vs "customers want this")
|
|
3. **One idea per submission** - If you have multiple ideas, submit multiple templates
|
|
4. **Success metrics matter** - How will we know this worked?
|
|
5. **Honest sizing** - Better to overestimate than underestimate
|
|
|
|
## Questions?
|
|
|
|
Reach out to @OverlordBaconPants if you need help completing this template.
|