How to Give Website Feedback That Actually Helps

Your development team has just sent over designs or a staging site for review. You stare at it, knowing something needs to change, but struggling to articulate exactly what. Sound familiar? The quality of your feedback directly impacts the quality of your final website. This guide will help you communicate in ways that lead to better outcomes for everyone.

Why Feedback Quality Matters

Vague feedback wastes everyone's time. When you say "this doesn't feel right," your team has to guess what you mean. They might change the wrong thing, leading to another round of revisions. Or they might interpret your concern correctly but solve it differently than you imagined, creating new issues.

For more insights on this topic, see our guide on Website Launch Checklist: 25 Things to Verify.

Clear, specific feedback accelerates the project. It helps your team understand exactly what concerns you and why, enabling them to address the root issue rather than symptoms. The result: fewer revision rounds, faster timelines, and a better final product.

The Anatomy of Helpful Feedback

Great feedback has four components: what you're reacting to, what specifically concerns you, why it's a problem, and (optionally) what you think might help.

What You're Reacting To

Be specific about location. Instead of "the homepage," say "the hero section on the homepage" or "the testimonials area below the fold." If you can, include a screenshot with the area highlighted.

What Concerns You

Describe the specific element or aspect that's bothering you. Is it the color? The size? The position? The wording? The quantity? Getting granular helps narrow down the issue.

Why It's a Problem

This is the most important—and most often missing—part of feedback. Explain the underlying concern. "The call-to-action button doesn't stand out enough" is better than "change the button color," because it lets the designer find the best solution. Maybe color isn't the answer; maybe size or position would be more effective.

What Might Help (Optional)

If you have an idea for a solution, share it—but frame it as a suggestion, not a directive. "Would it help to make the button larger, or maybe use a contrasting color?" invites collaboration rather than dictating the answer.

Feedback Examples: Bad vs. Good

Let's transform some common feedback from unhelpful to actionable:

Example 1: Visual Discomfort

Bad: "I don't like it."

Better: "Something about the homepage doesn't feel right to me."

Best: "The homepage feels too busy—there's so much competing for attention that I'm not sure where to look first. I'm worried visitors will be overwhelmed. Could we simplify the hero section to focus on one main message?"

Example 2: Branding Concerns

Bad: "The colors are wrong."

Better: "This doesn't match our brand."

Best: "The blue in the header is different from our brand blue (#2B4D7C)—it looks more purple on my screen. Can we verify we're using the correct brand colors from our style guide?"

Example 3: Functional Issues

Bad: "The form doesn't work."

Better: "I tried submitting the contact form and nothing happened."

Best: "On the contact page, I filled out all fields and clicked Submit on my iPhone (Safari). The button didn't respond, and I received no confirmation or error message. I've attached a screenshot showing the filled form."

Common Feedback Mistakes

Avoid these pitfalls that derail productive feedback:

Designing by Adjective

"Make it pop" or "make it more modern" sound meaningful but aren't. What makes something "pop"? Bigger? Brighter? More contrast? Different position? The designer's interpretation of "pop" may differ from yours.

Instead, describe the outcome you want: "I want this section to immediately grab attention" or "I want visitors to notice this button before anything else."

Prescribing Solutions

"Change the background to light gray" prescribes a specific solution without explaining the problem. Maybe you want gray because the current background feels too stark—but there might be better solutions you haven't considered.

Instead: "The white background feels harsh and clinical. We want to feel warmer and more welcoming. Would a subtle cream or light gray help, or is there another approach?"

Contradictory Feedback

If multiple people review the work, consolidate feedback before sending. Nothing frustrates a design team more than "make it bigger" from one stakeholder and "make it smaller" from another. Resolve internal disagreements first.

Expanding Scope

"While we're at it, can we also add..." is dangerous. Feedback should address what's been presented, not add new requirements. Scope creep buries projects in delays and cost overruns.

Forgetting the Users

Your personal preferences matter less than your users' needs. Before requesting a change, ask: does this serve our visitors, or just my taste?

How to Organize Your Feedback

Structured feedback is easier to address than scattered thoughts.

Prioritize Your Points

Not all feedback is equally important. Distinguish between:

• Must fix: Issues that absolutely must be addressed (broken functionality, incorrect information, brand violations)
• Should fix: Important improvements that would significantly enhance the result
• Nice to have: Minor preferences that you'd like but could live without

Organize by Page or Section

Group feedback logically rather than listing items in the random order you noticed them. This helps the team work systematically through the revisions.

Use Annotation Tools

Visual annotation tools let you point directly at elements and attach comments. This is far clearer than describing locations in text. Many design review platforms include annotation features, or you can use simple screenshot markup.

Feedback Timing Matters

Provide feedback within the timeframe your team requests. Delayed feedback stalls the entire project, and rushed feedback tends to be incomplete.

Also, don't drip-feed feedback over days. Review thoroughly, consolidate your thoughts, and provide everything at once. Multiple small feedback batches create confusion and duplicate work.

The Feedback Conversation

Sometimes written feedback isn't enough. Complex issues or subjective concerns often benefit from a quick call or screen share. If your written feedback isn't getting the results you want, suggest a conversation.

During these conversations, focus on dialogue rather than dictation. Ask questions: "What led you to this approach?" Understanding the rationale behind decisions often resolves concerns—or reveals legitimate issues the team hadn't considered.

Related Reading

• The Website Discovery Phase: What Happens and Why It Matters
• Website Revision Rounds: How Many Is Normal?
• How to Read a Website Development Proposal