Friday, March 6, 2026
Creative, Arts & Skills

Design Crits that Teach: Ask for the Right Feedback

goodman 136 Views ,  ,  , 

Design Critique: Get the Right Feedback (That Teaches)

🧭 What & Why

What is a design crit?
A structured, time-boxed conversation where a designer presents work and invites targeted feedback aligned to user goals and project outcomes. Effective crits sharpen judgment, accelerate iteration, and build shared standards.

Why it matters:

  • Well-structured feedback is one of the most powerful drivers of learning and performance when it answers three questions: Where am I going? How am I going? Where to next? conselhopedagogico.tecnico.ulisboa.pt

  • Many teams ask, “Thoughts?” and get vague reactions. Instead, ask for specific feedback that teaches: evidence, trade-offs, and next steps—so the team learns how to reason, not just what to change.

  • Use the right type of feedback for the moment—appreciation (what to keep), coaching (how to improve), or evaluation (how it stacks up vs. a bar). Naming the type reduces confusion and defensiveness. Harvard Business Review+1

✅ Quick Start (Do This Today)

Before the session (15–30 min prep)

  1. Write a 1-page brief: objective, target user, top jobs/pain points, constraints, success metric.

  2. Pick your feedback type(s): appreciation / coaching / evaluation—state this up front. Harvard Business Review

  3. Make a question list (3–5 max):

    • “Does this flow remove the top friction for X user?”

    • “Which variant best supports goal Y and why?”

    • “Where does copy misalign with tone/brand guidelines?”

  4. Choose attendees intentionally: decision owner, 1–2 peers, 1 cross-functional partner, and (optionally) an outside eye. Keep the core group to ~3–7 people. Scott Berkun

  5. Circulate materials (link to prototype + brief) at least 2–24 hours ahead to avoid reactive “first-impression theatre.” Nielsen Norman Group

During the session (30–45 min)

  • 2 min: Host sets purpose, feedback types, and ground rules (kind, specific, about the work).

  • 5 min: Designer tells the story—users, constraints, prior learnings; states the 3–5 questions. Nielsen Norman Group

  • 20–30 min critique:

    • Start with what’s working and why (teach the bar).

    • Move to coaching: evidence-based suggestions tied to the goals.

    • Park off-topic items in a backlog.

    • Facilitator enforces turn-taking and time boxes. GV Library

  • 5–8 min wrap: Designer reflects back: “I’m keeping A, exploring B vs C for Y reason, and I’ll prototype D.”

After (10 min)

  • Send a one-pager: decisions, open questions, owners, due dates; attach recording or notes.

🛠️ 30-60-90 Habit Plan

Days 1–30: Start the ritual

  • Stand up a weekly crit (45 min), rotating facilitator.

  • Adopt a crit template (brief + goals + 3–5 questions).

  • Teach the three feedback types; print a one-line definition on the agenda. Harvard Business Review

  • Measure two things: session helpfulness (1–5) and clarity of next steps (Yes/No).

Days 31–60: Raise the bar

  • Introduce guidelines: comment on how work meets user goals, brand, content clarity, and visual design—avoid solutioning unless asked. Nielsen Norman Group

  • Pilot role cards: Presenter, Facilitator, Scribe, Timekeeper, Decision Owner.

  • Track iteration velocity: # of decisions closed per crit; average time from crit → new prototype.

Days 61–90: Make it teach

  • Add micro-lessons (5 min): show “why this worked” examples.

  • Invite a guest outsider quarterly to avoid groupthink.

  • Review metrics; refine cadence and attendee mix.

  • Celebrate 3 “kept decisions” per month to reinforce appreciation, not just critique.

🧠 Techniques & Frameworks That Work

1) The 3 Feedback Questions (Hattie & Timperley)

  • Where are we going? (goals/criteria)

  • How are we going? (current performance vs. criteria)

  • Where to next? (specific next steps) — Use these to structure every comment. conselhopedagogico.tecnico.ulisboa.pt

2) Name the Feedback Type (Stone & Heen)

  • Appreciation: what to keep and why it works.

  • Coaching: specific guidance to improve.

  • Evaluation: judgment vs. a standard.
    Use one at a time, or clearly label transitions. Harvard Business Review+1

3) Benevolent Critique (d.school)
Adopt a stance of helpful rigor: be candid about the work, generous about the person; ground comments in user evidence. Stanford d.school

4) Formalize the Ritual (GV & NN/g)
Schedule crits, set rules, begin with goals, and ask for targeted input to avoid derailment. GV Library+2Nielsen Norman Group+2

5) Build Feedback-Seeking Muscles
Choosing constructive critique (vs. praise only) improves learning attitudes over time; normalize it. AAALab

👥 Who This Is For (Variations)

  • Solo designers / freelancers: Record self-crits. Share a 5-min Loom with 3 questions to a small peer circle; ask for 48-hour turnaround.

  • Product teams / startups: Make the weekly crit the default decision forum for UX copy, flows, and visual changes; keep attendees lean.

  • Agencies: Run multi-stakeholder crits in two passes—internal (coaching), then client (appreciation + evaluation).

  • Students / bootcamps: Tie crits to rubrics; ask reviewers to cite a criterion with each comment; start with strengths to teach the bar.

  • Non-design disciplines (content, research, data viz): Same ritual; tune criteria to clarity, accuracy, and audience needs.

⚠️ Mistakes & Myths to Avoid

  • “Any feedback is good feedback.” No—mis-typed feedback (evaluation when you need coaching) slows learning. Label it. Harvard Business Review

  • Open mic chaos. Unguided “What do you think?” invites derailment. Start with goals + questions. GV Library

  • Pixel-pushing too soon. Anchor to user goals and success metrics first.

  • Designers defending every choice. Ask for evidence and alternatives; treat critique as a studio-class, not a debate club.

  • No ownership. End with decisions, owners, and dates—every time.

💬 Real-Life Scripts & Checklists

Presenter opening (1–2 min)

“Goal: Help first-time users complete onboarding under 3 minutes. Today I need coaching on the passwordless flow. Here are my 3 questions: (1) Does Variant B reduce cognitive load? (2) Where does copy break tone? (3) What should we test next?”

Facilitator ground rules

“Comments must connect to a goal or user evidence. We’ll start with what’s working and why, then coaching. Please avoid solutioning unless asked.”

Reviewer prompts

  • “I see X helping Y user because…”

  • “Evidence suggests users struggle at step 3; have we tried…?”

  • “Between A/B, B better supports the success metric because…”

Wrap-up (designer)

“Keeping: success banner pattern. Exploring: shorter empty-state copy. Next: prototype alt for step 2. I’ll report back Friday.”

One-page crit template (copy-paste)

  • Project / date / owner

  • Objective & success metric

  • Target user & top job

  • Constraints / known risks

  • Feedback type(s) requested

  • 3–5 questions

  • Key artifacts (links)

  • Decisions & owners

  • Next steps & due dates

🧰 Tools, Apps & Resources

  • Figma / FigJam – Live presentation + sticky notes; timer and vote plugins.

  • Loom – Asynchronous 5-minute brief & walk-through.

  • Notion / Confluence – Crit templates, decisions log, design history.

  • Miro – Affinity clustering to surface themes from comments.

  • Calendly / Google Calendar – Recurring crit slot; attach agenda and links.

  • Recording – Zoom or Meet; auto-transcribe for searchable learnings.

Pros/Cons snapshot

  • Pros: shared context, faster iteration, institutional memory.

  • Cons: takes discipline; without clear roles and questions, crits drift.

📌 Key Takeaways

  • Ask for the right kind of feedback and label it.

  • Structure beats spontaneity: brief, roles, and 3–5 questions.

  • Teach the bar: start with what works and why.

  • Tie every comment to user goals/evidence.

  • Make it a ritual: weekly crits, decisions log, and a 30-60-90 plan.

❓ FAQs

1) How many people should be in a crit?
Aim for ~3–7: small enough for depth, large enough for diverse perspective. Scott Berkun

2) Should the designer speak first or last?
First—for context and targeted questions—then last to reflect back decisions. Nielsen Norman Group

3) What if senior leaders hijack the session?
Set feedback types and questions upfront; park unrelated items; assign a facilitator with authority to time-box. GV Library

4) How do we keep feedback constructive?
Adopt benevolent critique—be candid about work, generous about people; connect comments to goals and evidence. Stanford d.school

5) How do we avoid derailment?
Publish goals, send materials in advance, and use feedback guidelines (user goals, brand, content clarity, visual design). Nielsen Norman Group

6) How do we make critique part of culture?
Create a recurring ritual, teach the three feedback types, and measure helpfulness/clarity; iterate on the format quarterly. Harvard Business Review

📚 References

  1. Hattie, J., & Timperley, H. (2007). The Power of Feedback. Review of Educational Research. Link

  2. O’Hara, C. (2015). How to Get the Feedback You Need. Harvard Business Review. Link

  3. Huston, T. (2024). The Art of Giving Feedback (Podcast). HBR IdeaCast—on appreciation, coaching, evaluation. Link

  4. Gibbons, S. (2016). Design Critiques: Encourage a Positive Culture to Improve Products. Nielsen Norman Group. Link

  5. Gibbons, S. (2021). Derailed Design Critiques: Tactics for Getting Back on Track. Nielsen Norman Group. Link

  6. Google Ventures Library. (2015). GV Guide to Design Critique. Link

  7. Stanford d.school. How to Give Feedback (Tool). Link

  8. Chin, D. B., et al. (2019). Educating and Measuring Choice: A Test of the Transfer of Curiosity. AAALab, Stanford—on embracing constructive criticism. Link

  9. Berkun, S. (2007). How to Run a Design Critique. Link

  10. CMU Eberly Center. Communicate high standards and confidence in students through feedback. Link