Working with Designers and Executives

Working with designers and executives is a core part of your job as a product manager. The actual job is not just coordinating tasks — it is owning the product’s success by influencing multiple stakeholders with different perspectives, priorities, and incentives. That requires clarity on who owns what, rigorous validation of ideas, and the skill to lead without hierarchical power.

The trap is to assume that design is just a delivery step and executives are just decision-makers you must obey. That mindset leads to frustration, broken trust, and missed opportunities. Instead, you must build a partnership with designers and a respectful but evidence-driven relationship with executives.

Define roles clearly to build trust with designers

Designers and product managers share many responsibilities, but each also owns distinct areas. You cannot succeed without explicitly laying out the land.

Product managers own prioritization, business modeling, metrics, stakeholder input, project management, scope planning — the full accountability for the product’s success. Designers own the look, feel, and interaction — information architecture, site maps, responsiveness, interaction design, and more.

The overlap is in user research, wireframing, user flows, personas, identifying needs, MVP definition, and experiments. In these zones, the work must be collaborative. Sometimes the designer leads user research, sometimes you do. Sometimes you co-own user stories and flows.

Set expectations upfront: who will lead research for this feature? Who drafts the initial wireframe? Who owns the final user story? This clarity alleviates friction and builds trust.

Let me be direct about this: you cannot assume that “design” is a black box your team hands off to. You must engage deeply with the design process, not just for handoff but to shape the problem space and solution options.

Validate every executive idea rigorously before prioritizing

Executives are important stakeholders — they bring business context, customer relationships, and strategic vision. But their ideas are not sacred. The actual job is to validate every idea, no matter how senior the source, before committing engineering time.

What I tell PMs is this: know your users and the problem well enough to evaluate the urgency, priority, and impact of executive requests. Don’t just accept feature demands at face value.

Validation means user research, data analysis, and understanding the competitive landscape. It means translating vague requests into user stories with clear acceptance criteria and measurable outcomes.

The trap is to treat executives as infallible and prioritize their ideas without question. This leads to bloated roadmaps, technical debt, and stakeholder disappointment.

Instead, apply a consistent framework:

• What user problem does this idea solve?
• How urgent and widespread is the problem?
• What is the expected impact on key metrics (revenue, retention, engagement)?
• What are the trade-offs with other priorities?

If you cannot answer these, you are not ready to commit.

Influence without authority is your critical leadership skill

Most product managers do not have direct authority over designers, engineers, or executives. Your actual job is to influence these teams to execute your product vision.

This requires empathy, communication, and negotiation skills. You must understand each stakeholder’s goals and constraints, then frame your requests in terms that matter to them.

For designers, this means respecting their craft and process while advocating for user needs and business goals. For executives, this means translating data and user insights into clear, concise recommendations that align with company objectives.

The trap is to try to “command and control” or to be overly deferential. Neither works.

Instead:

• Build relationships based on trust and evidence.
• Use data and user stories to make your case.
• Be transparent about trade-offs and risks.
• Invite collaboration rather than dictate solutions.

This is what week one looks like for most new PMs — realizing that your job is not to tell people what to do, but to convince them why to do it.

Collaborating with designers: A typical conversation

Here is a common pattern I see in product teams:

You want to push a feature idea. The designer pushes back because the user research is incomplete or the UX flow is not validated. You feel pressure from executives to ship fast. The designer worries about quality and consistency.

The solution is to hold a joint session to clarify roles and expectations. Agree on who leads the next round of user research. Define what “done” looks like for the wireframes. Set a realistic timeline that balances speed and quality.

This kind of collaboration requires ongoing communication. Don’t let email or Slack threads become battlegrounds. Schedule regular syncs, demo progress, and surface blockers early.

Managing executives: The validation checklist

When an executive requests a feature or change, run it through your validation checklist before saying yes:

• Have you talked to users to confirm the problem?
• Do you have data supporting the scope and urgency?
• Have you assessed the impact on other roadmap items?
• Can you quantify the expected business outcome?
• Have you considered alternative solutions?

If not, schedule a follow-up with research or analysis. If yes, communicate clearly what you will deliver and when.

This builds credibility with executives — they see you as a trusted partner, not a gatekeeper.

The iterative nature of product and design collaboration

Design is an iterative process. Your meetings with designers must respect their concentration and flow. Frequent interruptions derail their ability to solve complex problems.

What I tell PMs is this: schedule focused design reviews instead of ad hoc questions. Give designers ample time to work between sessions.

Chris Butler’s video on PM-designer collaboration is an excellent resource. He emphasizes the importance of shared ownership, mutual respect, and iterative feedback loops.

The power of shared language and artifacts

Use shared artifacts to align:

• User personas
• User journey maps
• Wireframes and prototypes
• User stories with acceptance criteria
• Metrics dashboards

These create a common language across product, design, and executives. They reduce misunderstandings and help focus discussions on facts, not opinions.

Test yourself: The executive feature request dilemma

Where to go next

• If you want to master cross-functional collaboration: Influence Without Authority
• If you want to sharpen your user research skills: User Research Methods
• If you want to improve stakeholder management: Stakeholder Management Strategies
• If you want to learn about product prioritization frameworks: Prioritization Techniques

PL alumni now work at Flipkart, Google, Razorpay, PhonePe, Swiggy, Amazon, Microsoft, and 30+ other companies.