By the end of this lesson you can
- Gather useful feedback from clients and stakeholders.
- Turn vague or conflicting feedback into clear actions.
- Push back respectfully when feedback harms users.
The idea
Clients and stakeholders often give feedback that is vague ("make it pop"), prescriptive ("make the logo bigger") or conflicting. Your job is to understand the concern behind it.
Ask for the right feedback
Present work against agreed goals and ask focused questions: "Does this flow cover all the cases your team handles?" rather than "What do you think?"
Find the underlying need
When someone asks for a specific change, ask why. "Make the logo bigger" may really mean "I'm worried people won't recognise our brand". There may be a better solution.
Handle conflicts
When stakeholders disagree, bring them together, restate the goals and use evidence (research or test results) to decide. Name a decision owner.
Push back respectfully
If feedback would hurt users, explain the risk with evidence and offer alternatives or a test: "Removing the guest checkout may reduce sales; could we A/B test it first?"
Record decisions
Write feedback and decisions down and share them, so everyone agrees what will change.
Why it matters in real projects
Managing feedback well keeps projects on track and protects the user experience. It builds trust with clients and stakeholders because they feel heard, even when you do not implement every request. It is an essential skill for both agency and in-house designers.
A realistic example
A client says: "The homepage feels empty. Can we add more products?" The designer asks what worries them. The client explains that sales of new lines are low. The designer proposes a "New this month" section instead of filling the page, and suggests measuring clicks on it. The client agrees, and the decision is recorded in a shared document.
Step by step
Restate goals
Begin reviews by reminding everyone of the goals.
Ask focused questions
Guide feedback to what you need.
Ask why
Explore the concern behind each request.
Resolve conflicts
Use goals and evidence, and name a decision owner.
Push back with evidence
Explain risks and offer alternatives or tests.
Record decisions
Share a written summary of what will change.
Common mistakes
Mistake Asking "What do you think?"
Instead Ask focused, goal-based questions.
Mistake Implementing every request literally.
Instead Find the underlying need.
Mistake Not recording decisions.
Instead Share written summaries.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 30 min
Feedback triage
Process a set of stakeholder feedback.
Steps
- List five pieces of feedback (real or invented).
- Write the likely underlying need for each.
- Propose a response or alternative.
- Write a decision summary to share.
Deliverable
A feedback triage table and decision summary.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Guide feedback with goals and focused questions.
- Look for the need behind requests.
- Resolve conflicts with evidence.
- Push back respectfully and record decisions.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
- Stakeholder interviews (opens in a new tab)Nielsen Norman Group
- A/B testing 101 (opens in a new tab)Nielsen Norman Group
Your notes
Marking complete updates your course and roadmap progress.