Design Critique Template: Free Template and How to Use It
November 12, 2026 | Read Time : 3 mins
Table of Contents
Good design rarely comes from one person working alone. It comes from honest, structured feedback. But unstructured feedback often turns into vague opinions like “I don’t like the color.” A design critique template keeps the conversation focused on goals, users, and evidence.
This guide gives you a free, copy-ready template and a step-by-step method for running critiques that make designs better. It works for UI designers, UX teams, product managers, and agencies.
What Is a Design Critique?
A design critique is a structured discussion where a designer presents work and others give feedback based on shared goals. It is different from a design approval meeting. The aim is to improve the work, not to vote on it.
Critique vs. Opinion
Opinion
Critique
“I don’t like this layout.”
“The layout buries the main button, so users may miss the primary action.”
“Make it pop more.”
“The headline and body text have similar weight, which weakens the visual hierarchy.”
“It feels off.”
“The spacing is inconsistent between cards, which breaks the pattern.”
Why Use a Template
A template keeps every critique consistent and productive. It helps you:
Stay focused on the problem the design is solving
Reduce bias by tying feedback to goals and users
Save time with a repeatable agenda
Include everyone so quieter voices are heard
Track decisions so feedback becomes action
Who Should Join a Critique
Designers presenting and reviewing work
Product managers who own the goals
Developers who judge feasibility
Researchers who bring user insight
Stakeholders who need context, not final approval
Free Design Critique Template (Copy and Use)
This template has four parts: a design brief, a feedback framework, a scoring rubric, and an action log. Copy each into Figma, Notion, Google Docs, or a spreadsheet.
Part 1: Design Brief
The presenter fills this in before the session.
Field
What to Record
Project and stage
Name of the design and its maturity (early concept, mid-fidelity, final polish)
Goal
The business or user problem being solved
Target user
Who the design is for and their key needs
Constraints
Technical, brand, time, or budget limits
Feedback wanted
The specific questions you want answered
Out of scope
What not to critique at this stage
Part 2: Feedback Framework
Reviewers use this structure to keep comments clear and useful.
Step
Prompt
Example
Observe
What do I see?
“The call-to-action sits below the fold.”
Relate
How does it connect to the goal?
“Users need to start signup quickly.”
Suggest
What could improve it?
“Try moving the button above the fold.”
Question
What am I unsure about?
“Was this placement tested?”
Part 3: Scoring Rubric
Rate each area from 1 to 5, then add short notes.
Criteria
What to Check
Score (1-5)
Notes
Clarity
Is the purpose obvious in a few seconds?
Visual hierarchy
Does the eye land on what matters first?
Consistency
Do colors, type, and spacing follow the system?
Usability
Can users complete key tasks easily?
Accessibility
Contrast, text size, and keyboard and screen reader support
Brand fit
Does it match the tone and identity?
Total
/30
Part 4: Action Log
Feedback
Decision
Owner
Deadline
Accept / Explore / Decline
Accept / Explore / Decline
Accept / Explore / Decline
How to Use the Design Critique Template: Step by Step
Step 1: Set the Context
Share the brief before the meeting. Reviewers should know the goal, the user, and the questions being asked. Without context, people default to personal taste.
Step 2: Choose the Right Participants
Invite three to six people. Too few limits perspective, and too many slows the session down.
Roles to Assign
Presenter: walks through the design and listens
Facilitator: keeps time and the discussion on track
Note-taker: logs feedback in the action log
Reviewers: give structured feedback
Step 3: Present the Design
Keep the presentation short, about five minutes. Explain the problem, the user, and the key decisions. Then stop talking. The presenter’s job in a critique is mostly to listen.
Step 4: Gather Feedback Using the Framework
Ask reviewers to use the Observe, Relate, Suggest, Question structure. This turns “I don’t like it” into feedback the designer can use.
Ground Rules
Critique the work, not the person
Tie comments to goals and users
Stay within the feedback requested
Offer reasons, not just preferences
Share positives as well as problems
Step 5: Score and Compare
Use the rubric to rate the design. Scores give you a quick snapshot and make it easy to compare versions across rounds.
To back up scores with expert analysis, a professional UX audit services review can benchmark your design against usability best practices and spot issues the team missed.
Step 6: Validate With Real Users
Critique shows what the team thinks. Users show what actually works. Where feedback conflicts or assumptions are unclear, test the design with real people.
Pairing critique with UX research services such as usability tests and interviews settles debates with evidence instead of opinion.
Step 7: Turn Feedback Into Action
End the session by sorting feedback in the action log. Mark each item as accepted, worth exploring, or declined, and assign an owner. The designer keeps the final call, but each decision should be explained.
For bigger challenges, design thinking workshops help teams explore alternatives together and agree on a direction.
Design Critique Example
Example: SaaS Dashboard
A team reviews a new analytics dashboard.
Feedback
Reasoning
Decision
Key metrics are the same size as secondary charts
Weak hierarchy makes the main insight hard to find
Accept
Use a dark theme
Possible fit for power users, but untested
Explore
Add more decorative icons
Adds noise without helping tasks
Decline
Result: The designer enlarged the key metrics and simplified the layout. The next critique scored higher on clarity and hierarchy.
Common Design Critique Mistakes to Avoid
Giving solutions too early. Describe the problem first, then suggest fixes.
Critiquing without context. Feedback needs a goal and a user.
Letting the loudest voice dominate. Use the facilitator to balance the room.
Treating feedback as orders. The designer weighs input against the brief.
Ignoring accessibility. Include it in every review, not just the final one.
Skipping follow-up. Feedback without owners and deadlines gets lost.
Best Practices for Better Critiques
Keep sessions to 30 to 45 minutes so focus stays high.
Critique early and often instead of waiting for final polish.
Match feedback to the design stage. Don’t debate pixels in a rough concept.
Record decisions so the team remembers why choices were made.
Build a critique habit with a regular weekly or biweekly slot.
When to Get Expert Help
If your team lacks the time or experience to run effective reviews, an outside partner can help. A team offering UI/UX design services can review your designs, run user tests, and redesign the flows that need work.
Frequently Asked Questions
What should a design critique template include?
At minimum: a design brief, a feedback structure, a scoring rubric, and an action log with owners and deadlines.
How long should a design critique take?
Thirty to forty-five minutes works well for most designs. Break larger projects into several shorter sessions.
Who should lead a design critique?
A neutral facilitator, not the presenter. This keeps the discussion balanced and on time.
What is the difference between a design critique and a design review?
A critique focuses on improving the work through discussion. A review is often a checkpoint for approval or sign-off. Many teams use both at different stages.
Conclusion
A strong design critique template replaces vague opinions with focused, goal-driven feedback. Share the brief, use a clear feedback structure, score the work, and turn every comment into an action with an owner.
Copy the four-part template above and use it in your next review. Your designs, and your team conversations, will improve quickly.
Share
AUTHOR
Team OriginUX
OriginUX Studio is a CoE for User Experience providing UI & UX across Product, Service and Customer Experience Design. We are a cross-disciplinary design team that loves to create great experiences and make meaningful connections for businesses and their users through UI & UX.
Founded in 2016, our larger purpose is to help brands understand what they want to do and where they want to go. To do that we have to make understanding customer experience simple, effortless, and affordable for everyone.
OriginUX studio is based out of Bangalore, India.
We are a cross-disciplinary design team that loves to create great experiences and make meaningful connections for businesses and their users through UI & UX.