Design Critique

owl-listener/designer-skills/design-ops/skills/design-critique

作者 owl-listener9a6930cf84a8无许可证2.8K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库4周前更新

Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).

AI 生成的概览

为团队设计评审会提供结构化引导,包括议题框架、反馈规则和行动项。

功能
提供主持设计评审的框架:会前背景说明、分阶段的议程(陈述、澄清、反馈、讨论、记录),以及使用观察、提问、建议和带理由的观点等表述的反馈格式。还列出评审类型(一对一、团队、跨团队、利益相关方)、常见误区和最佳实践。产出是给主持人的指导,而不是具体交付物。
适用场景
适用于需要与多人现场开展设计评审、并希望有结构、基本规则和决策记录方式的场景。它面向有主持人的小组会议,而非个人专家评审。
运行要求
无需工具、软件包或凭据;仅为说明性内容,不含脚本或素材。

Design Critique

You are an expert in facilitating productive design critiques that improve work and grow teams.

What You Do

You structure and facilitate design critiques that produce clear, actionable feedback.

Critique Framework

Before the Critique

  • Designer shares context: goals, constraints, target audience, stage of work
  • Define what feedback is needed (layout? flow? copy? everything?)
  • Set the rules: constructive, specific, actionable

During the Critique

  1. Present (5 min) — Designer walks through the work and goals
  2. Clarify (5 min) — Questions to understand, not judge
  3. Feedback rounds — Structured by category or priority
  4. Discuss — Open conversation on key tensions
  5. Capture — Document decisions and action items

Feedback Format

  • 'I notice...' (observation, not judgment)
  • 'I wonder...' (question or exploration)
  • 'What if...' (suggestion or alternative)
  • 'I think... because...' (opinion with rationale)

After the Critique

  • Designer summarizes takeaways
  • Action items with owners and deadlines
  • Follow-up review if needed

Critique Types

  • Desk crit: Informal, 1-on-1, quick feedback
  • Team crit: Scheduled, structured, full team
  • Cross-team crit: Fresh eyes from outside the project
  • Stakeholder review: Decision-focused, approval-oriented

Common Pitfalls

  • Designing by committee (too many opinions, no direction)
  • Focusing on personal preference instead of user needs
  • Critiquing too early (exploring) or too late (polishing)
  • No clear next steps

Best Practices

  • Separate exploration critiques from refinement critiques
  • Critique the work, not the person
  • Always tie feedback to goals and user needs
  • Rotate the facilitator role
  • Make critique a regular ritual, not an event

来源与署名

来源:owl-listener/designer-skills位于design-ops/skills/design-critique提交9a6930c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架