Triage means sorting incoming feedback into "do now", "later" and "no", on a schedule instead of whenever a message arrives. One fixed slot per week keeps feedback from either piling up or taking over your days. The 45 minutes below are a starting point, not a rule; shrink or grow them to fit.
Before the session
Collect everything into one list during the week: email, in-app messages, tester reports, store reviews. See feedback channels. For each item note: source, app version, type.
Agenda (45 minutes)
1. Sweep (10 min). Read each new item once. Tag it: bug, idea, question, praise, noise. Merge duplicates and write a count next to the original.
2. Urgent check (5 min). Anything that loses data, blocks sign-in or payment, or crashes on launch jumps the queue. Decide the fix date now.
3. Patterns (10 min). Look at tags and counts. What came up from more than one person? Beware of one loud author: see feedback bias.
4. Decide (10 min). For each pattern pick one: do this week, schedule, park with a reason, decline. Use impact against effort as in how to prioritize app feedback. Longer-term decisions belong on the roadmap: turn app reviews into a roadmap.
5. Reply (10 min). Answer questions, thank people whose feedback you will use, tell decliners why in one sentence. Templates: close the loop.
Rules that make it stick
- Same day and time each week; put it in the calendar.
- Stop at the timer. Unfinished items roll over.
- Do not fix during triage; only decide.
- Keep a "parked" list and re-read it monthly.
- Limit "do this week" to what fits your week.
Example outcome (Example)
Twelve items: five bugs (two duplicates), four ideas, two questions, one praise. One crash goes to Tuesday, one idea is scheduled, two are declined with a reply.
No feedback this week? Request some. AppReviewX gives private, structured feedback from other developers; one feedback you write earns one credit. Get started.
Hub: app feedback guide.