Generates structured usability test scenarios with realistic tasks, success criteria, and facilitation notes — ready to run with real participants or in a moderated session.

2026-06-111.9k

interfaces-that-feel

Owl-Listener/designer-skills

Apply an emotional resonance lens to any UI. Use when a design is technically correct but flat — to identify what's missing and prescribe specific changes at the copy, motion, and interaction layer.

2026-06-111.9k

business-design

Owl-Listener/designer-skills

A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.

2026-06-111.9k

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

Present (5 min) — Designer walks through the work and goals
Clarify (5 min) — Questions to understand, not judge
Feedback rounds — Structured by category or priority
Discuss — Open conversation on key tensions
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