Product and UX
PM × Design: How to Work Together
How Product and Design work together: sharing responsibility, discovery, decision criticism, handoff and shared quality criteria.
The strong link between Product and Design is built around a common problem, not brief transmission and layout verification. PM brings a strategic and business context, the designer leads the exploration of interaction and form of solution; both are responsible for proving value and making clear tradeoffs.
PM and Design: Who is in charge of what?
Product Manager (PM) and its objectives
Product Manager defines what problem the product solves, who it’s for, and how the team will handle it. PM is responsible for understanding the market, users, and business goals. Regular tasks are prioritizing features, hypotheses, aligning goals with the business.
**Example: ** If you need to increase your subscription by 15%, PM will specify who the key audience is, what prevents them from paying, what problem should be addressed.
Product Designer (UX/UI) and its Zone
The designer is responsible for how the product looks and feels, and the goal is to make sure that the user is painlessly able to achieve their goals, and that includes prototyping, testing, feedback, and continuous interface improvements.
Example: The user takes too long to search for a checkout button.The designer explores interaction patterns, suggests a new layout, and tests on real customers.
Product success on the market is possible only when real user problems are identified and an original, simple solution is found. Julie Zhuo, former Facebook Design Director, The Making of a Manager
Quick principles for effective work
Joint formulation of objectives
PM and Designer discuss how a product should work from a business and user perspective.The discussion begins with a common CJM (Customer Journey Map) map and hypotheses for improving the experience.
Example: Launching a new onboarding page. PM brings in data about the first entry into the product, the designer suggests new steps based on UX patterns. Together, conduct a usability test, see how new users go.
General rituals and documentation
Optimal collaboration is built on regular meetings: grooming ideas, collaborative design reviews, prototyping test solutions, and it’s important to have a Notion, Confluence, structured task so that there’s no dispute at the last stage.
Example: At a workshop, the team negotiates on the main user personas and uses one CJM template.
Mistakes and anti-patterns
Ignore the Designer’s Opinion When Planning a Feature
When PM sets priorities without consulting a designer, raw scripts and weak user flow appear.
Signal: After launching a feature that is markedly different from the usual product patterns, support receives more questions about navigation.The team checks session records and topics: the reason may be in visual inconsistency, a new term or a changed logic, rather than the fact of novelty itself.
A formal approach to UX research
The designer only passes on PM research to check the box, not to make a real difference, and the result is that the product is no better, and the project is stalled.
Example: After the A/B test, the form was simplified, but the user actions were not affected - key insights from the research are not included in the Roadmap.
Joint artifacts and communication channels
CJM, user stories, design systems
The key is to have a transparent tool stack. PM monitors user stories and shaves backlog, the designer develops the design system and prototypes, and it’s important to negotiate rules: where to watch the final layouts, who appruits what, how to record experiments.
**Example: * Miro co-assembles a user path map, negotiates bottlenecks, Figma the final prototype, and guesses don’t leave, only after the test.
Quick syncs and revue
Running is more important than long-term approvals, and regular short calls allow you to solve problems on the go, rather than waiting for weekly meetings.
The more often the team compares the vision and refines the details on the move, the more stable the pace and less conflicts. Jared Spool, CEO User Interface Engineering, uie.com
How to avoid losing a user between a manager and a designer
Transparent research and feedback
All insights and user pains are discussed openly, both sides comment on the findings of the research, and check that the solutions are not only functional, but also pleasant to the user.
**Example: * prioritize together – even a simple tech feature can change NPS, so quick tests and validated solutions are needed.
Metrics through the UX prism
It is important to track not only business metrics (like LTV or MAU), but also UX metrics: time to first value, number of errors per step, NPS, CSAT. The main benchmarks and numbers depend on the industry. See, for example, in Lean Analytics and NNG UX KPIs.
FAQ
**What if PM and designer disagree on the solution? Go through prototypes and tests. The real user will show you what’s best.
When to engage a designer – before or after Roadmap? The designer should be involved in hypotheses and prioritization from the start, not just in the rendering stage.
What documents are important to keep together? CJM, personas, hypothesis backlog, test documentation, key findings on UX results.
How to evaluate the quality of interaction between PM and Design? The speed of decision-making, the number of conflicts on layouts, % of hypotheses with real user value.
What is the purpose of UX metrics? Time to first value, NPS, CSAT, conversion to key actions, percent errors/failures.
Where to find examples and guides on PM and Design rituals? Good cases and approaches are NN Group on Rituals in UX and Product Design at Scale.