Feature Request Triage System

J

Jordan Reyes

@jordan-reyes

·

Design systematic feature request triage processes

3 copies0 forks
Create a feature request triage system for {{product_name}}.

Request volume: {{volume}}
Current process: {{current_process}}
Team size: {{team_size}}

**Triage Framework:**

**Intake Standardization**
- Required information for each request
- Submission channels
- Auto-categorization rules

**Initial Triage Criteria:**

1. **Validity Check**
   - Is this actionable?
   - Is it within our scope?
   - Is there enough information?

2. **Quick Filters**
   - Already on roadmap?
   - Duplicate of existing request?
   - Known limitation we accept?

**Scoring Dimensions:**

| Dimension | Weight | Scoring Guide |
|-----------|--------|---------------|
| Customer Impact | 30% | How many affected? |
| Revenue Impact | 25% | Revenue at risk/opportunity |
| Strategic Fit | 20% | Alignment with strategy |
| Effort | 15% | Implementation complexity |
| Urgency | 10% | Time sensitivity |

**Disposition Categories:**
- Accept (add to roadmap)
- Consider (needs more research)
- Decline (with reason)
- Defer (future consideration)

**Communication Templates:**
- Acknowledgment
- Accepted
- Declined
- Need more info

**Process Cadence:**
- Triage frequency
- Review meetings
- Escalation paths

Details

Category

Productivity

Use Cases

Request managementBacklog groomingCustomer communication

Works Best With

gpt-4claude-3
Created Updated Shared

Create your own prompt vault and start sharing