Giving Great Feedback
Learn how to provide valuable reviews that actually help product builders improve.
Why Your Feedback Matters
Every review you write helps a builder make their product better. Quality feedback can:
- ✅ Help identify blind spots the builder missed
- ✅ Validate or challenge product assumptions
- ✅ Provide user perspective they haven't considered
- ✅ Guide product roadmap and priorities
- ✅ Build your reputation as a valuable reviewer
The Feedback Framework
1. Start with the Positive
Always begin by highlighting what works well. This helps the builder understand their strengths and what to preserve while improving.
- "The onboarding flow is incredibly smooth - I was up and running in under 2 minutes"
- "The pricing page is crystal clear. I immediately understood which plan fits my needs"
- "Love the minimal UI - it doesn't overwhelm users with options"
2. Be Specific and Detailed
Vague feedback like "it's confusing" doesn't help anyone. Point to exact issues and explain your reasoning.
"The design is weird"
"Pricing is confusing"
"Not sure what this does"
"The sidebar navigation uses 4 different icon styles which feels inconsistent"
"The $29/month tier doesn't clearly show which features I get vs the $9 tier"
"The homepage hero doesn't explain what problem this solves in the first 5 seconds"
3. Explain the Impact
Help builders understand WHY something matters by explaining the potential impact.
"The CTA button uses the same color as the background"
"This might hurt conversions because users don't immediately notice the primary action"
"The CTA button blends into the dark background, which might reduce conversions since users won't immediately see where to click. Consider using a high-contrast color like orange or green."
4. Suggest Solutions (Optional)
If you have ideas, share them! But remember - you're not the designer. Frame suggestions as options, not demands.
- "Have you considered adding a progress indicator to the multi-step form?"
- "What if you moved the pricing comparison to the homepage instead of hiding it?"
- "You might get more signups by offering a 14-day trial instead of requiring payment upfront"
5. Give a Fair Score (1-10)
Your score should reflect the product's current state, not its potential. Consider:
- 1-3: Major issues, hard to use
- 4-5: Functional but rough
- 6-7: Good with room to improve
- 8-9: Excellent, minor tweaks
- 10: Perfect, nothing to change
- • User experience
- • Value proposition clarity
- • Execution quality
- • Market potential
- • Stage (MVP vs launched)
Review Best Practices
✓ Do
- ✓ Actually try the product before reviewing
- ✓ Put yourself in the target user's shoes
- ✓ Focus on user experience, not personal taste
- ✓ Be constructive even when critical
- ✓ Explain your reasoning
- ✓ Consider the product's stage (MVP vs mature)
- ✓ Balance criticism with encouragement
- ✓ Engage if the builder asks follow-up questions
✗ Don't
- ✗ Write one-sentence reviews
- ✗ Be vague ("it's bad", "needs work")
- ✗ Be harsh without being helpful
- ✗ Compare to completely different products
- ✗ Focus only on design if it's a technical tool
- ✗ Give feedback on features you didn't test
- ✗ Expect the builder to implement all your ideas
- ✗ Review competitors negatively
Example of a Great Review
What Works: The core functionality is solid - I was able to create and export my first project in under 5 minutes. The template library is impressive with 50+ options. The real-time collaboration feature worked flawlessly when I tested it with a colleague.
Areas for Improvement:The pricing page doesn't clearly differentiate between the Pro and Team plans - I had to dig into the FAQ to understand if Team includes all Pro features. The onboarding tutorial is too long (8 steps) and made me want to skip it. Consider reducing to 3-4 essential steps.
Specific Issues:The export dialog uses technical terms like "rasterize" and "vector" which might confuse non-designer users. The mobile version has horizontal scrolling on the dashboard which feels broken. The search function didn't find my project when I searched for part of its name.
Suggestions:Consider adding a "Compare Plans" table on the pricing page. For onboarding, try progressive disclosure - show basics first, advanced features later. The search could benefit from fuzzy matching so partial names work.
Overall:This is a strong product with clear value. Fix the mobile issues and simplify the onboarding, and you'll have something really special. The collaboration feature alone sets you apart from competitors.
Earn Credits for Quality Reviews
Every detailed review you write earns you credits. The better your feedback, the more you earn:
Ready to Review?
Browse products and start giving valuable feedback to help builders improve.