UX Feedback Generator
Synthesize UX findings into clear, actionable feedback for stakeholders.
Feedback Formats
Choose format based on audience:
| Audience | Format | Focus |
|---|---|---|
| Designers | Detailed with examples | Specific fixes, rationale |
| Developers | Issue-focused | What to fix, acceptance criteria |
| Stakeholders | Summary | Impact, priority, effort |
| Design System team | Pattern-focused | Reusable solutions |
Report Structure
Executive Summary
- •2-3 sentence overview
- •Key metrics (usability score, critical issues)
- •Top priority recommendation
Strengths (What's Working)
Always start with positives to maintain constructive tone.
Issues by Priority
Group issues by urgency:
- •Critical: Prevents task completion
- •Major: Significant friction
- •Minor: Polish opportunities
Recommendations
Actionable, specific fixes with rationale.
Next Steps
Clear action items with owners/timeline if known.
Writing Guidelines
Be Specific, Not Vague
code
❌ "The navigation is confusing"
✅ "Users must navigate 5 levels deep to access API policies.
Consider: Add 'Quick Actions' section to API detail page."
Lead with Impact
code
❌ "The button color is inconsistent"
✅ "Inconsistent button styling (blue vs teal) creates uncertainty
about which actions are primary. Users may hesitate before clicking."
Provide Rationale
code
❌ "Add a search function"
✅ "Add a search function to reduce navigation depth. Currently,
users with 50+ APIs cannot quickly locate specific items,
leading to abandonment or reliance on browser bookmarks."
Suggest Solutions, Not Just Problems
code
❌ "The error message is unclear"
✅ "Replace 'Invalid input' with 'Email must include @ symbol
(e.g., you@example.com)'. This follows the pattern:
What's wrong → How to fix → Example."
Output Templates
Quick Feedback (Slack/Email)
code
**[Feature/Flow] UX Review** ✅ **Working well:** - [Strength 1] - [Strength 2] ⚠️ **Top issues:** 1. [Issue] → [Fix] 2. [Issue] → [Fix] 📋 **Recommended next step:** [Single clear action]
Standard Report
code
# UX Review: [Product/Feature Name] **Date:** [Date] | **Reviewer:** [Name] | **Version:** [Version/Iteration] ## Executive Summary [2-3 sentences: What was reviewed, overall assessment, top recommendation] **Usability Score:** X/10 **Critical Issues:** X | **Major:** X | **Minor:** X ## What's Working Well - **[Strength 1]:** [Brief explanation of why this is effective] - **[Strength 2]:** [Brief explanation] ## Issues Found ### Critical (Must Fix) #### Issue 1: [Title] - **Location:** [Screen/component] - **Impact:** [User impact] - **Evidence:** [Screenshot reference or description] - **Recommendation:** [Specific fix] - **Rationale:** [Why this fix works] ### Major (Should Fix) #### Issue 2: [Title] [Same structure] ### Minor (Nice to Fix) #### Issue 3: [Title] [Same structure] ## Recommendations Summary | Priority | Issue | Fix | Effort | |----------|-------|-----|--------| | 🔴 Critical | [Issue] | [Fix] | [S/M/L] | | 🟡 Major | [Issue] | [Fix] | [S/M/L] | | 🟢 Minor | [Issue] | [Fix] | [S/M/L] | ## Next Steps 1. [ ] [Action item with owner if known] 2. [ ] [Action item] 3. [ ] [Action item] ## Appendix - Screenshots analyzed: [List] - Evaluation criteria used: [List relevant frameworks]
Detailed Design Doc
code
# Comprehensive UX Evaluation: [Product Name] ## Evaluation Scope - **Flows analyzed:** [List] - **Frameworks used:** Nielsen Heuristics, WCAG 2.1 AA - **Analysis date:** [Date] - **Evaluated by:** [Name/Team] ## Methodology [Brief description of how evaluation was conducted] ## Findings ### Flow Analysis [Results from ux-flow-analyzer skill] ### Heuristic Evaluation [Results from ux-heuristic-evaluator skill] ### Consistency Audit [Results from ux-consistency-checker skill] ### Accessibility Review [Results from ux-accessibility-reviewer skill] ## Synthesized Recommendations ### Immediate Actions (This Sprint) [High-impact, low-effort fixes] ### Short-term (Next 2-4 Weeks) [Major improvements] ### Long-term (Roadmap) [Structural changes] ## Metrics to Track - [Metric 1]: Current [X] → Target [Y] - [Metric 2]: Current [X] → Target [Y]
Tone Guidelines
| Do | Don't |
|---|---|
| "Consider adding..." | "You should add..." |
| "Users may struggle to..." | "This is confusing" |
| "This creates an opportunity to..." | "This is wrong" |
| "To improve clarity, try..." | "Obviously you need to..." |
| "Based on heuristic X..." | "In my opinion..." |
References
For feedback templates and examples: See references/feedback-templates.md