Working with Designers and Executives

Working well with designers and executives is essential for a product manager. The actual job is not just to coordinate but to create trust, influence decisions, and ensure that user needs and business goals align through design and leadership.

The trap many new PMs fall into is treating designers as task executors or executives as unquestioned authority. Instead, you must understand where your roles start and end, how to collaborate on shared responsibilities, and how to push back with evidence when necessary.

The division of ownership between Product Managers and Designers

Product managers are accountable for the overall success of the product. This means owning prioritization, business modeling, metrics, stakeholder input, project management, and scope planning.

Designers own the success of the product’s design. Their exclusive responsibilities include information architecture, site maps, responsiveness, interaction design, and visual design.

Between these two sets of responsibilities lie shared domains: user research, wireframes, user flows, user stories, personas, identifying needs, validating features, MVPs, experiments, and understanding customer problems.

Laying down clear role boundaries upfront builds trust and prevents confusion. You might do user research sometimes; the designer might do it other times. You collaborate on user stories and personas. But you own the “what” and “why” — prioritization, business goals — while designers own the “how” in the interface.

This clear division ensures that both PMs and designers feel ownership without stepping on each other’s toes. It also improves the quality of collaboration and decision-making.

How to work effectively with designers

Designers care deeply about the emotional and experiential aspects of the product. They are not just UI decorators; they are problem solvers who translate user needs into intuitive interfaces.

Here are five guidelines for working well with designers:

• Rule 1: Diminish barriers between “Product” and Design
  You are not above designers. Team up with them as equals. Respect their expertise and input.

• Rule 2: Pay attention and care about details
  Designers sweat the small stuff because that’s where user delight happens. Show that you care about details too.

• Rule 3: Speak the language of designers, not just analytics
  Designers prioritize emotional impact and usability. Frame your discussions in terms of user feelings and flows, not just metrics.

• Rule 4: View designs as hypotheses
  Treat wireframes and mockups as experiments to test assumptions, not final answers. Encourage iteration.

• Rule 5: Have a flexible schedule
  Designers sometimes need long stretches of focused work. Respect their flow by scheduling meetings thoughtfully.

The PM’s role is influence, not authority

You do not have direct authority over designers or engineers. Your power is influence, built on respect, empathy, and clear communication.

You must be thorough in your approach — understand user needs, market context, and technical constraints — to earn the trust of your collaborators.

Working with Executives: How to communicate value and priorities clearly

Executives look at the product through a business lens. Their concerns are return on investment, resource allocation, and timelines.

Your job is to validate every idea, no matter how senior the source, before committing resources.

• Rule 1: Validate every executive idea rigorously
  Don’t implement ideas just because they come from the top. Do the necessary research. Know your users and the problem you are solving. Prioritize features and themes with clear reasons.

• Rule 2: Prove the worth of investment with strong business cases
  Create business cases that show the return on investment for each product iteration or feature. Executives want to see the impact versus the effort matrix.

• Rule 3: Use timeline-based roadmaps to communicate plans
  A roadmap with clear time frames for current, near-term, and long-term development shows that work is planned and controlled. This builds executive confidence and helps them plan resources.

The honest reality about stakeholder management

Stakeholder alignment is never perfect. Executives have agendas, designers have principles, engineers have constraints. Your job is to listen, translate, and reconcile these perspectives into a coherent product direction.

This requires patience, empathy, and firm prioritization.

Field exercise: Clarify roles and build collaboration

Time: 15 minutes

1. List your current product team members, including designers and executives you regularly interact with.

2. For each, write down what you believe are their primary responsibilities and concerns.

3. Schedule a meeting with your lead designer and one executive. Share your understanding of roles and ask for their feedback.

4. Identify at least two areas where responsibilities overlap and discuss how you will collaborate.

5. Commit to a shared communication cadence and agree on how you will handle disagreements or priority conflicts.

Test yourself: The roadmap pushback

From the field: Talvinder on collaboration

Where to go next

• If you want to improve your influence with engineering teams: Working with Engineers
• If you want to master stakeholder negotiation: Negotiation Skills for PMs
• If you want to deepen your user research skills: User Research Methods
• If you want to build strong product roadmaps: Roadmap Planning and Communication

PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, Amazon, and dozens of other companies.