<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k" -->

---
title: Why Most Design Critiques End Up Making Products Worse
description: Design critique sessions, borrowed from art school, often damage product work rather than improve it. Key dysfunctions include seniority gradients distorting...
canonical: https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Why Most Design Critiques End Up Making Products Worse | daily.dev
og:description: Design critique sessions, borrowed from art school, often damage product work rather than improve it. Key dysfunctions include seniority gradients distorting...
og:url: https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k
og:image: https://api.daily.dev/og/posts/EeDbFfP9K.png
og:image:alt: Why Most Design Critiques End Up Making Products Worse
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Most Design Critiques End Up Making Products Worse

**[Medium](https://daily.dev/sources/medium_js)** · 14 min read · 0 upvotes · 0 comments

## Summary

Design critique sessions, borrowed from art school, often damage product work rather than improve it. Key dysfunctions include seniority gradients distorting feedback weight, opinion laundering (personal preferences stated as UX principles), and convergence pressure pushing teams toward consensus through social fatigue rather than genuine agreement. The 'aggregation problem' describes how individually reasonable notes collectively erode a design's original point of view. A better model separates divergent exploration from convergent decision-making, assigns explicit decision rights before meetings, requires feedback to name a specific problem before proposing a fix, protects load-bearing design decisions from casual override, and weights feedback by expertise proximity rather than seniority. The core argument: critique should function as specialist diagnosis, not committee democracy.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://medium.com/design-bootcamp/why-most-design-critiques-end-up-making-products-worse-f6f5a5a5c785>

## Questions this post answers

### Why do design critique sessions sometimes make a good design worse even when every comment seems reasonable?

Group dynamics, not incompetence, cause the damage. Seniority gradient makes offhand comments from senior people carry outsized weight, opinion laundering presents personal taste as settled fact, and convergence pressure pushes rooms toward agreement to avoid social friction. Combined, many individually harmless notes accumulate like sediment, an 'aggregation problem' that smooths a distinctive design into something generic and forgettable.

_Teams refining how they run feedback loops can find more structured thinking on design process via daily.dev._

### How does Apple's design process differ from typical product design critique meetings?

Based on accounts from former employee Ken Kocienda in Creative Selection, Apple's process is not an open democratic critique but a series of demos judged by a small number of people with real taste and real decision rights, iterating rapidly and privately before wider review. The goal is quality judged by accountable individuals rather than consensus reached by a large group.

_Designers weighing critique formats against decision-rights models can track these comparisons on daily.dev._

### What structural changes can make design feedback sessions produce sharper decisions instead of diluted compromises?

Separate divergent brainstorming from convergent decision-making into different meetings, assign one explicit decision-maker before the session starts, require feedback to name a specific problem before proposing a fix, protect load-bearing design choices from casual override, and weight input by relevant expertise and proximity to the problem rather than seniority or title.

_Anyone redesigning their team's feedback rituals can follow more practical process guidance on daily.dev._

## Similar posts on daily.dev

- [DOC • Critique](https://daily.dev/posts/doc-critique-eqg0trkck) · DOC · 0 upvotes · 0 comments
- [Consumerism is also a UX problem](https://daily.dev/posts/consumerism-is-also-a-ux-problem-cbym0ct5t) · Medium · 0 upvotes · 0 comments
- [Design Systems Are Products, Not Projects \| Why Yours Is Failing](https://daily.dev/posts/design-systems-are-products-not-projects-why-yours-is-failing-lfxllhcal) · ITNEXT · 0 upvotes · 0 comments
- [10 uncomfortable UX lessons from real design mistakes](https://daily.dev/posts/10-uncomfortable-ux-lessons-from-real-design-mistakes-mtnemvkwg) · LogRocket · 79 upvotes · 2 comments
- [The Design System Adoption Problem is Older Than AI](https://daily.dev/posts/the-design-system-adoption-problem-is-older-than-ai-jhrdjcaig) · Headway · 0 upvotes · 0 comments

---

Tags: [#ux](https://daily.dev/tags/ux), [#leadership](https://daily.dev/tags/leadership)

[View this post on daily.dev](https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Why Most Design Critiques End Up Making Products Worse","url":"https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k"},"datePublished":"2026-07-21T07:32:47.152Z","dateModified":"2026-09-13T21:18:19.080Z","description":"Design critique sessions, borrowed from art school, often damage product work rather than improve it. Key dysfunctions include seniority gradients distorting...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c3e13f982953f4c231ab14b9bc239f5c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c3e13f982953f4c231ab14b9bc239f5c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Medium","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Medium","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/medium","url":"https://daily.dev/sources/medium_js"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ux,leadership","timeRequired":"PT14M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Medium","item":"https://daily.dev/sources/medium_js"},{"@type":"ListItem","position":3,"name":"Why Most Design Critiques End Up Making Products Worse"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-most-design-critiques-end-up-making-products-worse-eedbffp9k#faq","mainEntity":[{"@type":"Question","name":"Why do design critique sessions sometimes make a good design worse even when every comment seems reasonable?","acceptedAnswer":{"@type":"Answer","text":"Group dynamics, not incompetence, cause the damage. Seniority gradient makes offhand comments from senior people carry outsized weight, opinion laundering presents personal taste as settled fact, and convergence pressure pushes rooms toward agreement to avoid social friction. Combined, many individually harmless notes accumulate like sediment, an 'aggregation problem' that smooths a distinctive design into something generic and forgettable. Teams refining how they run feedback loops can find more structured thinking on design process via daily.dev."}},{"@type":"Question","name":"How does Apple's design process differ from typical product design critique meetings?","acceptedAnswer":{"@type":"Answer","text":"Based on accounts from former employee Ken Kocienda in Creative Selection, Apple's process is not an open democratic critique but a series of demos judged by a small number of people with real taste and real decision rights, iterating rapidly and privately before wider review. The goal is quality judged by accountable individuals rather than consensus reached by a large group. Designers weighing critique formats against decision-rights models can track these comparisons on daily.dev."}},{"@type":"Question","name":"What structural changes can make design feedback sessions produce sharper decisions instead of diluted compromises?","acceptedAnswer":{"@type":"Answer","text":"Separate divergent brainstorming from convergent decision-making into different meetings, assign one explicit decision-maker before the session starts, require feedback to name a specific problem before proposing a fix, protect load-bearing design choices from casual override, and weight input by relevant expertise and proximity to the problem rather than seniority or title. Anyone redesigning their team's feedback rituals can follow more practical process guidance on daily.dev."}}]}
```

