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 從公開儲存庫中收錄這些內容。

檢舉或申請下架