Pick which feature requests to build next
4 Wochen · 4 Einheiten pro Woche, je etwa 45 Min.
Wo du am Ende stehst: You can rank your feature backlog with a scoring method weighted by revenue and fit, and explain each pick to users.
Phasen
- Gather the Evidence · Woche 1
- Learn the Frameworks · Woche 2
- Score and Decide · Wochen 2 bis 3
- Communicate and Repeat · Woche 4
Woche 1Gather the Evidence
- Tag 1Build a single request list
Copy every open feature request into one spreadsheet with columns for request, requester, date, and source. Stop at 45 minutes even if incomplete; done means every source has been scanned once.
- Tag 3Merge duplicates into problems
Group requests that describe the same underlying problem and write a one-line problem statement for each group.
- Tag 5Attach revenue and usage
Add columns for each requester's plan, monthly revenue, and activity level, then total revenue per problem.
- Tag 6Write your product direction
Write three sentences on who the product is for and what it must be great at, to judge fit later.
Woche 2Learn the Frameworks
- Tag 8Study RICE scoring
Read one RICE guide and note in two lines how Reach, Impact, Confidence, and Effort would apply to your top five problems. Done means you can explain each factor without looking.
- Tag 10Study the Kano model
Label your top ten problems as basic, performance, or delighter and note one surprise.
- Tag 12Decide your weighting rules
Write how much weight revenue, number of requesters, and strategic fit get, so loud voices count once.
- Tag 13Score the top fifteen problems
Give each of your fifteen biggest problems a RICE score plus a fit score from 1 to 3 using your weighting rules. Keep estimates rough; consistency matters more than precision.
Woche 3Score and Decide
- Tag 15Talk to two quiet customers
Message two paying users who never request features and ask what slows them down most, then note answers.
- Tag 19Rescore with new insights
Update scores using the quiet customers' answers and write down which rankings moved and why.
- Tag 20Pick the next two builds
Choose the top two, write one paragraph per pick on why it beat the third-ranked item.
Woche 4Communicate and Repeat
- Tag 22Reply to requesters
Send short, kind replies to requesters of the top five non-picked items explaining where they stand. Use one template and finish within the session.
- Tag 24Set a monthly review ritual
Write a 30-minute monthly checklist: add new requests, rescore the top fifteen, confirm next picks.
Die Tage zählen ab dem Tag, an dem du den Plan speicherst. Sobald er dir gehört, verteilt Targela die Einheiten passend zu deiner Woche und deinem Tempo, und du kannst jeden Schritt ändern.
Kostenloses Konto. Nur wer den Link zuerst speichert, bekommt den Plan.