Design Sense and Critique

Here is the trap every PM falls into at least once. You open a design review, see a button you would have placed differently, and say "can we move that to the top-right and make it blue?" Congratulations, you just did the designer's job worse than they would have, and taught them you do not trust them. A PM's job in a design critique is to frame problems, not push pixels. That reframe is the difference between a designer who dreads your feedback and one who seeks it out.

#You don't need to be a designer. You need design sense.

Design sense is not the ability to produce good design. It is the ability to recognize it and articulate why something does or does not work for the user. The two come apart completely, and I can tell a confusing flow from a clear one and say exactly why without being able to draw either. That recognition, plus the discipline to express it as a problem rather than a solution, is the whole competency. It is the "Design Sense & Feedback" behavior of User Experience Design.

#The cardinal rule: problem framing over solution prescription

When I catch myself reaching for a solution, I run it backwards and ask: what problem is my fix trying to solve? Then I say that instead. The fix was a symptom of a problem I had not named, and naming it usually produces a better answer from the designer than I would have.

#What a PM brings instead of pixels

If not pixels, then what? Four things only the PM reliably holds:

• The problem and the user. Why this screen exists, who it is for, what job they are doing (Jobs To Be Done). Designers solve better when the problem is sharp.
• The constraints. Feasibility, scope, the trade-offs, the deadline. "It has to ship this sprint and work offline" is information only you may have.
• Consistency and simplicity. Does this fit the product's predominant patterns, or invent one users have to learn? Is it the simplest thing that solves the problem? Championing these is explicitly in the competency.
• The data and the research. What the funnel and the usability tests say. Evidence beats opinion in a critique every time.

Here is the hardest line I hold: usability is objective, and taste is the designer's domain. If a user cannot complete the task, I will escalate it. If I just prefer a different shade of green, I keep quiet, because it is not my craft and it is not my call.

#Pixel-pushing is a symptom of a deeper failure

When a PM micromanages a design, it is usually because the upstream work was thin. The problem was not framed and the requirements were vague, so the PM grabs control at the pixel level instead. The fix is not better critique technique. It is doing the specification and research work that should have set the designer up to succeed. Good critique starts long before the review does.

#How AI is changing it

PMs can now generate clickable prototypes themselves, which changes critique in a subtle way. Instead of describing a problem in prose, a PM can hand the designer a rough working artifact that says "something like this, but you make it good". That can sharpen the conversation. Used badly, it becomes pixel-pushing with extra steps, the PM imposing a generated solution. AI can also pre-screen a design against heuristics and accessibility rules, but it cannot supply taste. Judging which of many options actually serves the user is still the human bar. See AI in Prototyping and Delivery.

#Continue Reading

• User Experience Design for the competency this behavior belongs to.
• Competitive Landscape Analysis for the other half of the UX competency: reading the market.
• The Four Big Product Risks for why usability is owned by design and framed by the PM.
• Feature Specification for the upstream work that sets a designer up to succeed.
• The Product, Design, and Engineering Venn for where PM judgment ends and design craft begins.