The 20-minute critique: a format that survives real teams

Every design team says it values critique. Very few actually run it, and the reason is rarely laziness. It's that most critique formats are designed for design school — ninety unhurried minutes, work pinned to a wall, everyone present and prepared. Real teams have twenty-five minutes between standup and a client call, one person on another continent, and a deep collective instinct to be nice to each other.

So formats collapse. Critique becomes "any feedback?" at the end of a share-out, which produces either silence or vague encouragement, and six months later someone writes a doc proposing the team should really do critique properly. Repeat forever.

The format below has survived hundreds of sessions across our cohorts and inside teams our alumni run. It survives because it's built around the real constraints: twenty minutes, no preparation from anyone except the presenter, and structural defenses against politeness.

The format

Minute 0–3: the presenter frames — and names the question. The presenter shows the work and answers exactly three things: what problem this solves, what stage it's at, and what specific question they want answered. Not "thoughts?" — a question. "Does the hierarchy on this pricing page make the middle tier feel default?" The question is the whole trick. It converts the room from judges into consultants, and it makes off-topic feedback visibly off-topic.

Minute 3–6: silent looking. Three timed, genuinely silent minutes while everyone examines the work and writes notes. This step gets cut first and must not be. Without it, the first spoken opinion anchors the room and everything after is a reaction to it. Silent notes mean every participant forms an independent read — which is the entire informational value of having multiple people present.

Minute 6–16: structured response. Go around the room; each person gets two minutes, uninterrupted. The structure for each response is fixed: one thing that's working and why, then responses to the presenter's question, then anything else — flagged honestly as outside the brief. The "why" clause is non-negotiable in both directions. "I like the type" teaches nothing; "the type is working because it's doing the hierarchy's job, which frees the color to do emphasis" teaches the whole room.

The presenter's job during this: silence, except for clarifying questions. No defending, no explaining what they meant. The urge to defend is enormous and resisting it is a skill — but a defended critique produces no information, only a negotiation.

Minute 16–20: the presenter closes. The presenter states what they heard and what they'll act on — out loud, in a sentence or two. Not everything mentioned; what they'll act on. This closes the loop, filters the feedback through the person accountable for the work, and quietly establishes the most important norm in the room: feedback is input, and the designer still owns the decision.

Why it survives

Notice what the structure is doing. The named question defends against vagueness. Silent looking defends against anchoring. Fixed turns defend against the loudest voice owning the room. The mandatory "why" defends against empty praise. And the presenter's closing defends against critique-as-theater, where feedback is performed and then evaporates.

None of these defenses require courage from any individual, which is exactly the point. Formats that rely on people being brave fail, because on a normal Tuesday nobody is. Formats that make honesty structurally cheaper than politeness survive.

Two operational notes. Keep it to five people or fewer — beyond that, the math stops fitting in twenty minutes and the added perspectives are redundant anyway. And run it on a fixed cadence with rotating presenters, so critique is something the team does weekly rather than an event someone must summon the confidence to request.

Twenty minutes, once a week. It's the highest-return meeting a design team can hold, and it fits between standup and the client call.