Working with Designers and Executives

Working effectively with designers and executives is essential to your success as a product manager. The actual job is less about dictating tasks and more about aligning diverse perspectives into a shared understanding of the problem and the solution.

Misunderstandings about roles and unchecked executive demands are common traps that slow down product delivery and erode team trust. You will learn how to set clear boundaries with designers and how to validate executive input before committing engineering resources.

The roles and responsibilities between PMs and designers are overlapping but distinct

Product managers and designers both contribute to defining and delivering user value — but their core responsibilities differ.

Product managers own prioritization, business modeling, metrics, stakeholder input, project management, scope planning, and ultimately the product’s success. Designers own interaction design, information architecture, site maps, responsiveness, and the user interface.

Shared responsibilities include user research, wireframing, user flows, user stories, personas, defining MVPs, and experimenting with solutions. This overlap requires you to coordinate closely and clarify ownership early.

You will often find cases where the designer leads user research while you focus on business context, or vice versa. Sometimes you co-own persona development or MVP definition. The key is to explicitly agree on who owns what for each deliverable.

This clarity alleviates confusion and builds trust, enabling the designer to focus on solving complex problems without constant interruptions. It also ensures you get timely input on business priorities and user needs.

The trap of breaking the designer’s flow

Design is a highly iterative and concentrated process. Interrupting designers with too many meetings or shifting priorities mid-sprint breaks their flow and reduces quality.

You must balance the need for collaboration with giving designers ample uninterrupted time to solve complex problems. Frequent check-ins are important, but they should not fragment the designer’s focus.

Chris Butler’s video on how PMs should work with designers is a must-watch — it covers many practical challenges and solutions for this relationship.

How to validate and prioritize executive ideas

Executives often have ideas about features or product directions that come with urgency and authority. Your job is to validate every idea, no matter how senior the source, before committing to implementation.

Start by understanding the user problem behind the executive’s request. Know your users deeply — their pain points, workflows, and priorities. Evaluate the urgency and business impact of the proposed feature.

You should always have a prioritization strategy grounded in user research, data, and business goals. This enables you to push back respectfully or negotiate scope instead of blindly accepting every executive demand.

This discipline prevents the product roadmap from being hijacked by internal politics or outdated assumptions. It ensures engineering effort is focused on what truly moves the needle.

Influence without authority is your daily reality

As a PM, you rarely have direct authority over designers, engineers, or executives. Your power comes from influence — from building trust, clear communication, and shared understanding.

You must consistently articulate the “why” behind product decisions, translating business goals and user needs into actionable plans. When disagreements arise, your role is to facilitate discussion, surface evidence, and guide the team towards consensus.

The ability to influence without authority is a skill you develop by listening, empathizing, and demonstrating domain expertise. It is not about commanding but persuading.

What the product manager owns in this collaboration

• Prioritization: Deciding which features or fixes deliver the most value within constraints.
• Business modeling: Understanding revenue, cost, and metrics that define success.
• Scope planning: Defining what is in and out of the current work.
• Stakeholder management: Aligning executives, sales, marketing, design, and engineering.
• User research collaboration: Partnering with designers to uncover true user needs.
• Experimentation: Running MVPs, prototypes, and tests with users.
• Project management: Coordinating timelines and dependencies without micromanaging.

What the designer owns

• Interaction design: How users engage with the product.
• Information architecture: Organizing content and flows.
• Visual design: Look and feel, branding alignment.
• Responsiveness: Ensuring usability across devices.
• User testing: Validating design hypotheses with users.
• Wireframing and prototyping: Creating artifacts for exploration and communication.

A real Slack conversation example

Three guidelines for working with executives

1. Validate every idea before implementation. Ask for user evidence and business impact.
2. Know the problem you are solving. Don’t just take feature requests at face value.
3. Be transparent about prioritization. Share your rationale clearly and early.

These guidelines prevent the roadmap from becoming a wish list and keep everyone aligned on business goals.

How to deal with conflicting inputs

Executives, designers, engineers, and sales all have different priorities. Your job is to synthesize these inputs into a coherent plan.

Use data and user feedback as your north star. When conflicts arise, bring stakeholders together to review evidence. Facilitate trade-off discussions with empathy and clarity.

Remember: the actual job is to make a call no one else can make — not to please everyone.

Field reflection: from a Pragmatic Leaders AMA

"I always tell PMs: if you cannot clearly explain who owns what between you and the designers, you are setting yourself up for months of rework and frustration. Clear roles build trust faster than any process." — Talvinder Singh

Field exercise: clarify roles with your design partner (10 min)

1. Write down the key deliverables in your current sprint (user research, wireframes, user stories, prototypes).
2. For each deliverable, note who is the primary owner and who supports.
3. Schedule a 15-minute sync with your lead designer to confirm this ownership.
4. Agree on a communication cadence that respects design flow (e.g., weekly check-ins, asynchronous updates).
5. Reflect on any overlaps or gaps and plan how to address them.

Test yourself: Prioritizing executive demands and design flow

Where to go next

• If you want to master stakeholder management: Stakeholder Management Fundamentals
• If you want to improve your user research skills: User Research Methods
• If you want to build strong product roadmaps: Roadmapping and Prioritization
• If you want to learn about agile collaboration: Agile Product Development
• If you want to prepare for leadership roles: Product Leadership Essentials