design-critique

Topics in the source

• Product Design Critique
• When to use
• When not to use
• Pre-critique context
• The pass (in order)
• Output format
• Anti-patterns

A structured critique pass for a screen, flow, or component. The output is a prioritized list of changes a designer or engineer can act on — not adjectives. Critique is not redesign; recommend, do not rebuild. A designer or engineer asks for feedback on a screen, mock, or live UI. A feature is shipping and someone wants a final UX read. A flow is suspected of causing user drop-off and you want a pre-research read before instrumentation. The user wants a redesign. That is a design project, not a critique. The work is so early that no concrete artifact exists. Sketch with them instead of critiquing air. You have no context on the user job. Ask for it first; design critique without user context devolves into taste. Before opening a screen, get: Who is the user. Specific role and competence, not "users". What job they are doing on this screen. One sentence. What success looks like. What the user can do after this screen that they could not before. Where this screen sits in the larger flow. What precedes and follows. If any of these is missing, ask. Critique without these is opinion. 1. Clarity of the user job. Within 3 seconds of opening, is it obvious what this screen is for? Does the

This is an excerpt. Refer to the complete source and its current requirements.