Feedback: The Other F-Word
Summary
In this case study, we’ll share how one large design org began reshaping its feedback culture by focusing not just on what gets reviewed, but how we talk about work. The turning point wasn’t a new tool—it was unlearning long-held assumptions: that critique is a milestone, that it’s only for finished work, or that feedback is something senior people give and juniors receive. We’ll walk through how we introduced lightweight feedback rituals, role-based archetypes, and a simple starter kit to help designers ask for the feedback they actually need—earlier, more confidently, and with more clarity. Along the way, we’ll share the bumps, lessons, and shifts in mindset it took to make critique feel like a creative tool, not a performance review. You’ll leave with practical ideas to build a culture of feedback—and a deeper appreciation for the messy, human side of improving our craft together.
Key Insights
-
•
Feedback is a system that requires choreography, timing, and targeting to truly move design work forward.
-
•
Poorly framed feedback with conflicting comments and no clear ask causes confusion and stalls progress.
-
•
Amazon Devices built a feedback engine with defined rituals at different maturity stages to scale quality feedback for 500 designers.
-
•
Strong feedback is anchored in a clear intent, specific observations, actionable guidance, and ends with a next step and owner.
-
•
Feedback is subjective by nature and should sharpen, not flatten, the intent behind creative work.
-
•
Negative feedback archetypes — like the monopolizer or the fog — erode trust and add churn in design processes.
-
•
Positive archetypes such as the clarifier, connector, and synthesizer help set examples for effective feedback contribution.
-
•
Feedback loops must be agile and adaptive; rigid linear processes do not fit fast-changing projects.
-
•
Late or contradictory feedback can often be mitigated by frequent, early crits and cross-team alignment.
-
•
Psychological safety and balancing candor with care are essential to making feedback a growth-focused investment.
Notable Quotes
"The hidden hero or villain of craft is really feedback, the quality of feedback that we give."
"Feedback is a system. It's not just a pile of comments. It needs to be choreographed, timed, sequenced, and aimed to move the work."
"Strong teams don't serve weak feedback."
"What's weak feedback? Vague, off target, or late stuff like make it pop or opinions with no owner or next step."
"Feedback is a lot like holding up a mirror. You're reflecting what's already working and like using a flashlight to hide in the corners."
"Giving feedback is a skill, just like design. It takes practice and care."
"We approached feedback loops like a system equal parts structure and skill. They have to reinforce one another."
"You can't do one without the other. Design the system, set rituals in the quality bar. They reinforce each other."
"Match the moment. Calibrate the altitude and the type of feedback to the context."
"Feedback is more like an investment and a contribution into not just the person's work, but also to their growth."
Or choose a question:
More Videos
"Research repositories aren’t single sources of truth anymore; data and insights live in hundreds of different apps across companies."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
"If you’re the best front-end designer in West River Idaho with a good internet connection, we want to talk to you."
Russ UngerGetting Out from Under Everyone: How to Escape the Paralysis of Getting Started
June 8, 2016
"We put heavy trust in our stakeholders and co-created the curriculum with them."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"We’re going to laugh, learn, listen, and maybe take some sketch notes."
Victor UdoewaTheme One Intro
March 27, 2023
"If your topic is already tackled exceptionally by a prior book, go deeper or wait until the market shifts."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"People will talk to customers whether you want them to or not. The question is how to make it a better experience."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"Designers need better training to work with off-the-shelf enterprise software like Sitecore, Salesforce, and SharePoint."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"It’s not about the diagram, it’s about the dialogue."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
"Space matters, but don’t start with the space; start by changing people, processes, and mindsets."
Sam YenDriving Organizational Change Through Design? Do more of this and less of that
June 9, 2017
Latest Books All books
Dig deeper with the Rosenbot
What recent standards are improving interoperability between legacy EHR systems and startups?
What role should AI play in user research tools, and how do you manage associated risks and accountability?
Why is design education’s emphasis on critical making important, and how does it interrelate with critique and theory?