Using the 30–60–90 Framework for Design Critique
For the past four years I worked in a mature design team at SEEK, who were familiar with how to give, and receive, design critique. Moving to a new organisation, where I am the first UX hire, I needed to get back to basics to get the feedback I need — what is design critique? Why do it? What is involved? How do I give you feedback? What’s this 30–60–90 thing?
What is a Design Critique?
A design critique is a means for a designer to update stakeholders, and peers, on their progress. They should explain the business and user goals and present a design intended to meet these or solve a problem, along with the rationale behind it. Design critiques are about critiquing the product, not the designer.
Why do a Design Critique?
But you’re a designer and I’m not, why do you need my feedback?
Sometimes we are too close to an idea, so we can’t see the forest for the trees. Good ideas can come from anywhere and together we make a stronger design. You can’t have great design, without great feedback. We need technical feedback to ensure our ideas are technically feasible, strategy and business folk to check our ideas are viable. Of course, we also seek outside feedback from real users to confirm .
