Networking sold outSales open until 15.09 · 23:59--d --h --m --s
Product & Management Stage

Design Critique: How to Stop Crying into Your Pillow After Stakeholder Feedback

September 17, 2025 1:15 PM
Long Lecture
🇬🇧 English
Bratysława 1

About

Ever poured your heart and soul into a design, only to get feedback that makes you want to curl up in a ball under the covers? Or asked for an opinion, and all you got was a vague, ""I expected better""? We've all been there!

In this talk, you'll discover how to transform design feedback from a potential source of frustration into a powerful tool for growth. You'll learn to deliberately ask for feedback that provides valuable insights, and how to truly listen to even the toughest comments without taking them personally. I'll show you how to prompt stakeholders for concrete feedback, not just vague generalities. We'll delve into why stakeholders sometimes give negative feedback and explore various techniques for responding constructively. Plus, I'll share tips on how to organise feedback so you don't get lost in a sea of notes.

Get ready for a session packed with practical tips, real-life examples and frameworks that will help you gain actionable insights, create better designs, and ultimately, build stronger relationships with your stakeholders.

Talk by

Photo of Iga Mościchowska, UX consultant and trainer at WITFLOW & [ation] center
Iga Mościchowska
UX consultant and trainer at WITFLOW & [ation] center

Watch the full talk

Watch this WaysConf session, then continue with related talks or explore the current programme.

Explore the 2026 agendaMore WaysConf recordings
From the recording

Talk in brief

This practical talk separates the emotional experience of stakeholder feedback from the work of design critique. It explains why vague reactions appear, how designers can present the problem, constraints, reasoning, and specific questions before inviting comments, and how to evaluate suggestions after the meeting. Feedback may reveal an oversight, a valid domain concern, or a preference that should not drive the product. By classifying input, returning to user and business evidence, and responding without reflexive defense, designers can protect both the relationship and the quality of the decision.

Key takeaways

  1. 01

    Emotional reactions are normal, not decisive

    Experience does not eliminate discomfort, but recognizing the reaction creates space to examine feedback before accepting or rejecting it.

    Watch from 2:29
  2. 02

    Set the critique frame in advance

    Explain the problem, constraints, reasoning, and areas where feedback is useful so stakeholders respond to the decision rather than personal taste.

    Watch from 8:20
  3. 03

    Admit when the design is incomplete

    Stakeholders sometimes notice missing requirements or weak reasoning; productive critique requires designers to consider that possibility honestly.

    Watch from 11:59
  4. 04

    Classify suggestions before responding

    Separate clear corrections, questions needing evidence, negotiable choices, and low-priority preferences instead of treating every comment as equivalent.

    Watch from 14:59
  5. 05

    Return the discussion to consequences

    User impact, business goals, budget, and priority are stronger grounds for accepting or declining a suggestion than authority or personal conviction.

    Watch from 17:59
Read edited transcript highlights

These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.

Feedback skill includes emotional recovery

Years of practice do not guarantee that criticism stops hurting. The useful skill is not emotional immunity but the ability to notice the reaction and avoid making it the decision rule. Designers can give themselves time, identify what was actually said, and return to the purpose of the work before choosing whether a comment should change the design.

Watch from 2:29

Better critique begins before the comments

A stakeholder cannot evaluate reasoning that remains hidden. Presenting the problem, constraints, explored options, and rationale shows that the output is not a personal preference. Naming the areas where feedback is needed also narrows the conversation. Instead of inviting a general verdict, the designer creates a shared question that participants can help answer.

Watch from 8:20

Criticism may expose a genuine omission

It is tempting to assume that difficult feedback comes from someone who does not understand design. Sometimes the stakeholder knows the domain better, notices a missing state, or sees a consequence the team overlooked. A mature critique process leaves room for that possibility. Protecting craft does not require defending every artifact as if it were already complete.

Watch from 11:40

Not every suggestion has the same status

After the session, feedback can be sorted rather than obeyed in sequence. Some items are clear omissions that should be fixed. Others require user evidence, technical input, or a priority decision. A third group may be preferences with little expected effect. Classification turns an emotionally mixed conversation into a manageable set of product decisions.

Watch from 14:59

Decline through trade-offs, not dismissal

When a suggestion is weak, the response can examine its impact on customers, budget, scope, or agreed goals. Deferring an idea to the priority list may be appropriate, provided it is not used as a routine way to make people disappear. The objective is to preserve trust while making clear that attention and delivery capacity are limited resources.

Watch from 17:59
Explore WaysConf 2026

View the agenda

Get tickets