User Experience Design
#What it is
The verbatim definition from my competency model: the ability, individually and with the design team, to define requirements and deliver UX designs that are easy to use, leverage UX best practices, and dovetail with the product's predominant UX patterns.
Notice what this competency is not. It is not "the PM does the design". I have never met a great PM who wanted to push pixels, and the ones who try usually make worse products. The phrase that matters is "individually and with the design team." The PM owns the problem and the requirements and is accountable for the experience being usable. The designer owns the craft of the solution. Confusing those two is the fastest way I know to a resentful designer and a mediocre product. In Marty Cagan's framing of The Four Big Product Risks, usability is the designer's risk to own, and the PM's job is to make sure it gets owned, not to own it instead.
#The behaviors
My model names two behaviors, and the second one surprises people in a UX competency.
Design Sense & Feedback. Advocating intuitive, user-centered design; giving clear context, feedback, and problem framing; balancing usability against feasibility and impact; championing consistency and simplicity; and iterating from feedback. The keyword is problem framing, because a PM's most valuable design contribution is a sharply framed problem and clear constraints, not a sketch of the solution. How to do this without being a designer is the whole of Design Sense and Critique.
Competitive Landscape Expertise. Monitoring competitors and trends; analyzing strengths, weaknesses, and positioning; spotting differentiation; and translating market context into product priorities and messaging. This sits inside the UX competency in my model because so much of UX is relative. Users judge your experience against every other app on their phone, and a PM who does not know the competitive bar is designing blind. The full method is in Competitive Landscape Analysis.
The cardinal sin of PM design feedback is prescribing the solution: "move this button, make it blue, add a carousel". That tells the designer what without why, strips them of the craft they are better at than you, and usually fixes a symptom rather than the cause. Useful feedback names the problem ("users aren't noticing this action") and the constraint ("and it has to work one-handed"), then trusts the designer to solve it. More in Design Sense and Critique.
#How it shows up by level
| Level | What User Experience Design looks like |
|---|---|
| APM | Writes clear requirements for one feature; gives basic, problem-framed feedback; knows the product's core patterns. |
| PM | Partners a designer through an area; champions consistency and simplicity; weighs usability vs feasibility; tracks key competitors. |
| Sr PM | Sets the experience bar for a product area; runs effective design critique; uses competitive insight to find differentiation. |
| Director/VP | Stewards design quality and pattern consistency across the org; builds the PM-design partnership as a cultural norm. |
#How to grow it
- Learn to critique, not redesign. Practice giving feedback that names the problem and leaves the solution to the designer. This is the highest-leverage UX skill a PM can build (Design Sense and Critique).
- Build a pattern vocabulary. You do not need to design, but you should be able to name the product's predominant patterns and notice when a new screen breaks them. Inconsistency is a usability tax your users pay.
- Audit competitors with your thumbs, not your eyes. Actually use three competitor products for a real task each month. Reading reviews is not the same as feeling the friction (Competitive Landscape Analysis).
- Sit in usability tests. Watching real users fail at your design rewires your instincts faster than any best-practices doc (User Research and Discovery).
#How AI is changing it
The biggest shift is that PMs can now prototype the experience themselves. Tools like v0 and Lovable turn a prompt into a working interface in minutes, so a PM can communicate intent as a clickable artifact instead of a wall of text. That raises the floor on a PM's design contribution and tightens the loop with the designer. It does not replace design sense or craft. A generated UI is a starting point that still needs a designer's judgment on hierarchy, accessibility, and fit with the product's patterns. The premium stays on taste, on knowing which of a hundred AI-generated options is actually good. See AI in Prototyping and Delivery.
#Continue Reading
- Design Sense and Critique for how a PM gives useful design feedback without being a designer.
- Competitive Landscape Analysis for the second behavior: reading the market to find differentiation.
- The Four Big Product Risks for why usability is the designer's risk and value is the PM's.
- User Personas and Journey Mapping for the research artifacts that ground design decisions.
- The Product, Design, and Engineering Venn for where the PM's role ends and the designer's begins.