Back to Details

design-critique

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Design Critique

设计评审

Better critique structure. Better design output.
更优质的评审结构，更出色的设计产出。

How to use

使用方法

  • /design-critique
    Apply design critique constraints to feedback in this conversation.
  • /design-critique
    在当前对话中应用设计评审的反馈约束规则。

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").
  • 必须遵循：每条反馈都采用「观察>原则>问题」的结构
  • 在评估前必须先询问意图：“你本次优化的目标是什么？”
  • 必须指出权衡取舍而非直接判定缺陷：“你选择了高密度布局，这能让资深用户快速获取信息，但会让首次使用的用户感到不知所措”
  • 必须将工艺反馈（对齐、一致性）与审美反馈（是否有必要存在？）分开
  • 绝对不能以命令式语气给出反馈（比如“把按钮改成蓝色”），而应给出方向指引（比如“CTA按钮需要更清晰的视觉区分”）

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.
  • 5分钟：所有人安静写下3条具体的观察结果，禁止使用模糊表述。
  • 10分钟：轮流发言，每人分享一条观察结果，不得重复。
  • 10分钟：讨论分歧点。当两人有不同看法时，正是学习的契机。
  • 5分钟：提炼原则。总结出本次评审的一句话核心经验。

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)
  • 无实质内容的空洞赞美（比如“看起来很棒！”），无法带来任何启发
  • 用指令式命令替代方向性问题
  • 将对设计概念的批评与对执行细节的批评混为一谈
  • 资历最深的人先发言（会主导整个会场的判断）