design-critique

Category: Development & Coding | Uploader: Owl-Listener | Downloads: 0 | Version: v1.0（Latest）

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

Changelog: Source: GitHub https://github.com/Owl-Listener/designer-skills

Directory Structure

Current level: design-ops/skills/design-critique/

📄 SKILL.md 1.9 KB

SKILL.md

---
name: design-critique
description: Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.
---
# 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

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

design-critique

Directory Structure

SKILL.md

Report

Notice