User Feedback Triage
Purpose: Batch user feedback, surface blockers, and decide what needs attention now.
When to use: During pilots, launches, and any period where real users are testing a capability in their workflow.
Duration: 15 minutes max
Inputs Required
- Feedback from in-app widget, form, or shared channel
- Direct user messages (Slack, email, etc.)
- Any bugs or issues you noticed
Format
What feedback came in? (5 min)
Quick rundown. Don't discuss solutions yet—just surface what's there.
Any blockers for users? (5 min)
Is anyone stuck? Can't do their job? This is highest priority.
Quick decisions on small fixes (5 min)
Anything we can fix in under 30 minutes? Do it today. Anything bigger goes to weekly build planning.
Outputs
- Immediate fixes identified
- Blockers surfaced
- Items queued for weekly build planning
Tips
- 15 minutes means 15 minutes. Set a timer. End on time.
- If discussion goes long, take it offline. This is triage, not problem-solving.
- No feedback today? Good. Meeting's over in 2 minutes.
- If you're getting the same feedback repeatedly, it's not "noted"—it's urgent.
- User blockers > new features. Always.
Why Daily?
Users are trying to use the capability for real work. If something blocks the workflow, they need it fixed quickly or they will work around it.
Daily feedback sessions let you stay responsive without constant interruption. Batch the feedback, triage quickly, fix what matters.
Once the capability stabilizes, drop to 2-3 times per week or fold it into the normal operating rhythm.
See also: Weekly Build Planning