design-critique
Design Critique
Better critique structure. Better design output.
How to use
/design-critiqueApply design critique constraints to feedback in this conversation.
Constraints
Critique Format
- MUST use: Observation > Principle > Question for every piece of feedback
- MUST start with intent: "What were you optimizing for?" before evaluating
- MUST name tradeoffs, not flaws: "You chose density, which gives power users fast access but makes first-time experience overwhelming"
- MUST separate craft feedback (alignment, consistency) from taste feedback (should this exist at all?)
- NEVER give feedback as commands ("make the button blue"). Give direction ("the CTA needs more visual separation").
Running a Critique Session
- 5 minutes: everyone silently writes 3 specific observations. No vague words.
- 10 minutes: go around the room. Each person shares one observation. No repeats.
- 10 minutes: discuss disagreements. Where two people see different things, learning happens.
- 5 minutes: name the principle. One-sentence lesson from this review.
For Receiving Feedback
- SHOULD ask "why" before reacting (genuinely, not defensively)
- MUST distinguish between preference feedback and principle feedback
- SHOULD write down feedback you disagree with. Review it a day later.
Anti-Patterns
- Vague positives ("looks great!") that teach nothing
- Prescriptive commands instead of directional questions
- Mixing critique of concept with critique of execution in the same breath
- The most senior person speaking first (anchors the room)
More from dragoon0x/taste-skills
visual-audit
The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.
19motion-design
Animation as communication. Feedback, orientation, emphasis, delight. If motion doesn't serve one of these four purposes, it shouldn't exist. Use when evaluating animation quality, designing transitions, or deciding whether motion adds or subtracts.
15taste-as-strategy
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
15teaching-taste
Help other designers develop judgment without imposing your style. Use when mentoring designers, running design education, or building team-wide quality standards.
15tradeoff-assessment
Name what was prioritized, what was sacrificed, and whether the tradeoff was right. Every design decision trades something. Use when evaluating design decisions, defending choices, or helping teams understand what they're giving up.
14field-notes
Structured taste breakdowns of real products. The format for making taste observations legible and shareable. Use when analyzing products, writing case studies, documenting design observations, or teaching through example.
14