Skip to content
Design Academy My progress

Stage 10 · Lesson 6 of 12

Design critiques and stakeholder feedback

Running critiques and handling feedback.

  • Intermediate
  • 30 min
  • 3 check questions
  • Exercise: 45 min

By the end of this lesson you can

  • Run and take part in productive design critiques.
  • Give feedback that is specific, kind and useful.
  • Handle stakeholder feedback without losing the design's purpose.

The idea

A design critique is a structured conversation to improve work against its goals. It is not approval and not a place for personal taste.

Running a critique

  1. The presenter states the goal, context, constraints and what kind of feedback they want.
  2. Participants review quietly first, then discuss.
  3. Feedback refers to goals and users: "Will people notice the delivery cost before checkout?"
  4. The presenter listens, asks clarifying questions and notes points, without defending each one.
  5. End by summarising actions.

Giving feedback

  • Be specific: point to the exact element.
  • Link to goals: why does it matter for users or the business?
  • Ask questions: "What led you to put filters on the right?"
  • Separate observation from suggestion.
  • Mention what works, too.

Stakeholder feedback

Stakeholders often give solutions ("Make the button bigger"). Ask what problem they are trying to solve. Respond to the underlying concern, which may need a different solution.

Why it matters in real projects

Regular critique improves work faster than working alone and spreads knowledge across the team. Knowing how to give and receive feedback well builds trust and reduces conflict. Handling stakeholder feedback skilfully protects good design decisions while respecting their concerns.

A realistic example

A stakeholder says, "The logo needs to be bigger on the home page." Instead of arguing, the designer asks, "What are you hoping a bigger logo will achieve?" The stakeholder explains that partners have said they did not realise the site belonged to the organisation.

The designer proposes clearer branding in the header and an "About us" summary near the top. Partners' feedback improves, and the home page layout stays focused on user tasks.

Step by step

  1. Prepare context

    Write goal, users, constraints and feedback wanted.

  2. Present briefly

    Spend no more than five minutes presenting.

  3. Allow quiet review

    Give people a few minutes to look first.

  4. Guide discussion

    Keep feedback linked to goals.

  5. Listen and note

    Thank people and write points down.

  6. Summarise actions

    Agree what you will change and follow up.

Common mistakes

  • Mistake Defending every point.

    Instead Listen, clarify and decide later.

  • Mistake Feedback based on taste.

    Instead Tie feedback to goals and users.

  • Mistake Accepting stakeholder solutions literally.

    Instead Ask about the underlying problem.

Check your understanding

Choose an answer, then check it. There is an explanation either way.

Question 1 of 3What should the presenter share first?
Show answer

Goals, context, constraints and the feedback wanted. Context focuses feedback.

Question 2 of 3Which feedback is most useful?
Show answer

Will people notice delivery costs before checkout?. It is specific and linked to goals.

Question 3 of 3A stakeholder asks for a bigger logo. What should you do?
Show answer

Ask what problem they want to solve. Find the underlying concern.

Practice exercise

Exercise · about 45 min

Run a critique

Run a critique of one of your designs.

Steps

  1. Prepare a context slide.
  2. Run a 30-minute critique with two or three peers.
  3. Take notes without defending.
  4. Summarise actions and update the design.

Deliverable

Context slide, critique notes and the updated design.

Self-assessment

Tick each item when it is true of your exercise. Be honest; this is for you.

4 items

Summary

  • Critiques improve work against goals.
  • Give specific, goal-linked feedback.
  • Listen, note and decide later.
  • Respond to stakeholders' underlying concerns.

Further reading

Third-party sources, chosen for reliability. They open in a new tab.

Your notes

Marking complete updates your course and roadmap progress.

Back to Product thinking and collaboration Roadmap