Summary: Product Manager and Product Designer collaboration is essential for building successful digital products. When PMs and PDs use different terminology, processes, or mental models, communication gaps can slow down decision-making and weaken product outcomes. This article explains how shared language, mutual respect, clear roles, and stronger collaboration between Product Management and Product Design can improve workflows, reduce friction, and create more user-centered products.
Collaboration between Product Managers (PMs) and Product Designers (PDs) is essential for building successful products. However, communication challenges often arise due to differences in terminology, mindset, and approach.
Understanding the Communication Gap
PMs and PDs often work toward the same goals but express their ideas using different frameworks and terminologies. This is similar to telling the same story from different perspectives, using distinct linguistic styles. While many principles overlap across training programs in both fields, the variation in terminology can sometimes create confusion.
This challenge is especially noticeable in structured learning environments. Some training programs present concepts in a complex and theoretical manner, making it difficult to compare them across disciplines. While this does not pose an issue during the learning process itself, it can become problematic in a fast-paced product environment where clear and efficient communication is crucial.
Before diving deeper, it’s important to establish that the framework presented here applies only in environments where both PMs and PDs are committed to the product, their professional growth, and effective collaboration. This discussion does not address situations where companies face fundamental skill gaps or attitude issues on either side. However, it does highlight why selecting the right candidates for PM and PD roles is critical for smooth collaboration.
Principles in Product Development
Regardless of methodologies, company size, or processes, there are principles in product development that remain constant. These include:
- Business Needs & User Needs
- Strategic Fit & Constraints
- Problem Definition & Solution Development
- Iterative Process & Refinement
Anyone working in product development must be familiar with these core concepts, irrespective of how they were taught or how they are labeled. The key is to grasp the mindset behind these principles so that, even when different terms are used, the underlying intent is understood. For example, whether we refer to it as a “Business Need” or a “Business Objective,” the core idea remains the same. This ability to align on concepts despite terminological differences is the foundation of effective cross-functional collaboration.
High-Level vs. Deep Understanding: Primary and Secondary Skills
Both Product Management and Product Design are multidisciplinary fields with no rigid boundaries. PMs need a broad skill set to fulfill their responsibilities effectively, which includes both Primary Skills and Secondary Skills:
- Primary Skills: Core competencies that a PM must master to carry out their primary responsibilities.
- Secondary Skills: Complementary knowledge that enables PMs to fill gaps when needed, even if they are not specialists in those areas.
The Role of Secondary Skills
There are two main reasons why PMs (and PDs) need secondary skills:
- Bridging Gaps: Sometimes, a missing team member or a temporary need requires someone to step in with a working knowledge of another discipline. While the execution may not be perfect, it ensures progress.
- Facilitating Understanding: A foundational grasp of adjacent domains allows PMs and PDs to better understand each other’s perspectives, reducing friction in decision-making and collaboration.
For example, consider general practitioners in medicine. They have broad knowledge across multiple areas, allowing them to diagnose and treat common conditions. However, when a specialized issue arises, they refer patients to experts. Similarly, PMs may need a basic understanding of UX principles, just as PDs should be familiar with business strategy.
This dynamic also applies within design teams. A generalist designer may have expertise across multiple design disciplines, including UX research, but once a specialized UX researcher joins the team, that becomes their primary responsibility. Similarly, when a Product Strategist is introduced, their role in strategic decision-making takes precedence, even though PMs and PDs continue to contribute.
Establishing a Common Language
To foster effective collaboration, PMs and PDs must embrace three fundamental principles:
- Confidence – Respect for Primary Skills in High-Level Understanding
- Empathy – Respect for Others’ Primary Skills Over Your Own Secondary Skills
- Humility – Prioritizing the Main Goal Over Individual Expertise
1. Confidence
Effective collaboration starts with deep expertise in one’s own domain. Confidence in your knowledge and skills allows you to:
- Perform effectively within your field.
- Present information clearly and concisely.
- Share relevant insights without overwhelming the conversation.
- Establish credibility within the team.
A lack of confidence can lead to communication breakdowns in two key areas:
- When others expect expertise in your primary skill, but gaps in knowledge prevent you from leading effectively.
- When collaboration requires navigating overlapping responsibilities, and uncertainty leads to conflicts instead of alignment.
Beyond expertise, soft skills such as communication, collaboration, and adaptability are crucial for ensuring that knowledge is shared effectively.
2. Empathy
PMs and PDs must recognize that their secondary skills do not replace the primary expertise of others. Empathy plays a critical role in understanding when to contribute and when to defer to a specialist.
For example:
- If there is no designer on a team, a PM may take on certain UX responsibilities.
- If a designer has research skills, they may cover research tasks until a dedicated researcher is available.
- If a Product Strategist joins the team, they take ownership of strategic considerations, even though PMs and PDs remain involved in decision-making.
Recognizing these dynamics helps teams build trust and allocate responsibilities effectively.
3. Humility
When multiple primary skills intersect, conflicts may arise in determining the best course of action. Sometimes, no single solution satisfies all perspectives, and leadership must make a final decision based on broader company objectives, stakeholder needs, or long-term product vision.
Humility means accepting that:
- Decision-making is a shared effort, not a competition.
- The best outcome serves the product and company goals, not individual preferences.
- Understanding and aligning on priorities leads to better collaboration.
By adopting this mindset, PMs and PDs can engage in constructive discussions rather than territorial disputes.
Understanding the Team: The Key to Selecting the Right Process
To define the most effective process, the first and foremost task is to understand the team itself. Both Product Management and Design exist in an ever-evolving landscape. Team members often have preferred processes shaped by their past experiences, while new techniques continuously reshape process methodologies.
It is important to highlight a fundamental distinction: knowledge is not the same as experience. Gained experience without a solid theoretical foundation can never transition from a secondary skill to a primary skill. A common mistake is treating past experiences as knowledge. This frequently occurs when someone takes on a task outside their expertise simply because no dedicated professional is available within the company.
Another aspect of assessing knowledge is understanding the capabilities of team members, including PMs, PDs, and engineers. While I do not intend to analyze PMs in this regard due to my own domain expertise, I can outline the key considerations from a design perspective.
Imagine stepping into an organization mid-process with the responsibility of defining the optimal workflow given the available resources. The most challenging scenario arises when designers are only involved in visual implementation—let’s call this execution.
The Role of Execution Designers: Designers who primarily focus on UI implementation may not always engage in strategic decision-making. However, this does not mean they lack expertise in execution—many UI designers deeply understand usability, cognitive psychology, and visual perception. The challenge arises when their role is limited to pixel-perfect execution without contributing to broader design strategy.
Returning to the core topic, designers focused solely on execution are often not engaged in the earlier stages of product development. However, for a successful product, it is critical to involve an experienced designer from the outset. Designers have the deepest understanding of users, and while PMs recognize the importance of user needs, the challenge arises when they assume they already know what users want without proper validation.
Aligning Product and Design Processes
A critical question arises: how do we integrate a Product Process with a Design Process, especially when the former is often dictated by PMs? This is where a fundamental misunderstanding begins, and both sides bear responsibility for resolving it.
Designers possess knowledge of various design processes, ranging from Double Diamond and Lean UX to UCD and Design Thinking. However, both PM and PD training programs often overlook a crucial factor: collaboration. Training materials tend to define roles and responsibilities in isolation, without emphasizing how to work together effectively.
The reality is that just because a step belongs to a defined process does not mean that only one discipline should be involved. For instance, ideation sessions yield the best results when PMs and PDs collaborate rather than designers working in isolation. Both sides need to develop a better understanding of each other’s roles.
What PMs Need to Understand
A PD’s role extends beyond the Design Phase in the Product Lifecycle. Before a feature or product reaches the design execution phase, designers must gain a deep understanding of users. This requires access to essential data such as target market insights, localized behaviors, demographic details, and other critical factors. The less information designers have, the higher the likelihood that they rely on best practices and personal experience, which—without user input—can no longer be considered true User Experience design.
What PDs Need to Understand
The Design Process is not simply an isolated step within the Product Lifecycle. The Design Process should be seen as a parallel workflow rather than a separate, siloed step. For example, in the Double Diamond model, the Discovery phase includes extensive research and problem definition. While user research is a fundamental part of this process, the broader product Discovery phase also involves market research, which is often the responsibility of PMs, Business Analysts, Sales, or Marketing teams.
The Power of Collaboration
The importance of collaboration in product development cannot be overstated. Building a successful product is so complex that no single individual can be an expert in every domain. Responsibilities must be distributed, ensuring that each phase of development involves professionals with primary skills in the relevant areas. When gaps exist, secondary-skilled individuals can contribute, but it is crucial to recognize that everyone is working towards a shared goal—not against each other.
By fostering a culture of mutual understanding and teamwork, organizations can create seamless workflows that align Product and Design processes, ultimately leading to better, more user-centric outcomes.
Conclusion
Collaboration is the foundation of any successful product development process. PMs and PDs must recognize that they are not working in isolation but as part of a larger, interconnected system. By appreciating each other’s expertise, fostering open communication, and involving the right stakeholders at every stage, teams can bridge the gap between Product and Design—ensuring not only a more efficient process but also a more impactful end product. The key to success lies in acknowledging that we are all working toward the same goal: delivering the best possible experience for users.
