Product managers have to be true leaders to be successful. You lead people via your subject matter expertise, clarity of vision, and influence — not through authority.
Working with designers and executives is a core part of your job as a product manager. The actual job is to ensure alignment without authority — you own the product’s success but you do not directly manage the people who build or design it.
This means you must be clear about who owns what, create trust through clarity, and validate every idea before making prioritization calls. Without this, you risk confusion, frustration, and wasted effort.
Clarify ownership between you and designers to build trust
Designers and product managers share some responsibilities but also have distinct domains. If you don’t clarify this early, you will waste time in conflicts or duplicated work.
Product managers own prioritization, business modeling, metrics, stakeholder inputs, project management, and scope planning. You are accountable for the overall product success.
Designers own information architecture, interaction design, visual design, responsiveness, and site maps. They also deeply engage in user flows, wireframes, and personas.
Shared responsibilities include user research, user stories, identifying customer needs, and defining MVPs and experiments.
Set clear boundaries upfront with your designers. Agree on who owns which parts of user research, who drafts wireframes, and how you collaborate on user stories and personas.
This clarity improves trust. When designers know what you own and you know what they own, you avoid stepping on each other’s toes and collaborate more smoothly.
Influence without authority is the core leadership skill
No developer, designer, or other stakeholder reports to you. This is by design. If they did, they wouldn’t be fully honest with you.
Your actual job is to lead via influence — your expertise, clarity, and vision must earn respect. You must convince others why your prioritization and solutions make sense.
This is not easy. It requires being thorough, logical, and empathetic in your approach.
Think of your role as closer to a CEO than a manager — but without the authority. You set the direction, but the team owns the how and the execution.
Sprint planning at a SaaS startup
You (PM): “Here’s the customer problem we need to solve: onboarding drop-off at 40%. Priya, what design ideas can address this?”
Priya (Designer): “We could simplify the signup flow and add progress indicators.”
You (PM): “That aligns with the data. Let’s prioritize that for the next sprint and measure impact.”
Rahul (Engineer): “I’ll break down the tasks once we finalize the wireframes.”
Aligning cross-functional teams without direct authority
To succeed:
- Empower your team with context and clear goals. Define the “what” and “why” but let engineers and designers decide “how.”
- Remove blockers proactively. Chase down resources, clarify requirements, and shield the team from distractions.
- Celebrate wins and amplify credit to your team. When stakeholders praise progress, redirect it to the individuals who delivered.
- Communicate clearly and listen actively. Tailor your language to different stakeholders: executives want business impact, designers want user clarity, engineers want technical feasibility.
Validate executive ideas before prioritizing
Executives often bring ideas with urgency and authority. Your job is to validate every idea before accepting it into the roadmap.
No matter how senior the source, you must do the necessary research:
- Understand the user problem behind the idea.
- Assess the urgency and priority relative to other work.
- Check whether the idea aligns with your product vision and data.
- Test assumptions through user research or data analysis.
This is not about being obstructive. It is about ensuring your product decisions are evidence-based and user-centered.
Roles and responsibilities in product teams: who owns what?
| Role | Responsibilities | Notes |
|---|---|---|
| Product Manager | Prioritization, business modeling, metrics, stakeholder input, project management, scope planning, product success accountability | Owns the problem space, defines what to build |
| Product Designer | Information architecture, interaction design, visual design, responsiveness, wireframes, prototypes, user experience | Owns the solution space, defines how it looks and feels |
| Product Owner | Backlog management, sprint planning, requirement gathering, running sprints | Internal role focused on sprint execution |
| Engineering | Technical implementation, architecture, quality, release | Owns how and when to build |
| Executives | Strategy, business goals, funding, market positioning | Provide direction and constraints |
Understanding these boundaries helps you collaborate effectively and avoid role confusion.
A day in the life: balancing context switching and deep work
Your day will be fragmented by meetings with designers, engineers, executives, and customers. Managing your time without breaking the flow for your team is critical.
Schedule meetings to minimize disruption to design and engineering’s deep problem-solving time.
Be intentional about when you ask for reviews and feedback so it doesn’t interrupt creative flow.
Field exercise: Clarify roles with your design team (15 min)
- List all shared responsibilities between you and your designers (user research, user stories, personas, etc.).
- List all responsibilities exclusive to designers (information architecture, interaction design, visual design).
- List all responsibilities exclusive to you as PM (prioritization, metrics, stakeholder input).
- Write a short email or Slack message to your designer(s) clarifying these roles for your current project.
- Schedule a quick sync meeting to align and adjust as needed.
Doing this upfront will save weeks of confusion.
Test yourself: Prioritizing executive requests
You are PM at a Series B fintech startup in Bangalore. The CFO wants a new dashboard for compliance reporting in 2 weeks. The CEO demands SSO integration by next quarter due to a large customer request. The engineering lead says the team is at capacity with the current roadmap.
The call: How do you prioritize these requests and communicate your decision to executives and engineering?
Your reasoning:
You are PM at a Series B fintech startup in Bangalore. The CFO wants a new dashboard for compliance reporting in 2 weeks. The CEO demands SSO integration by next quarter due to a large customer request. The engineering lead says the team is at capacity with the current roadmap.
Your task: How do you prioritize these requests and communicate your decision to executives and engineering?
your reasoning:
Where to go next
- Master cross-functional collaboration: Working with Engineers
- Build stakeholder influence skills: Leadership Skills for PMs
- Learn user research fundamentals: User Research Methods
- Develop product prioritization frameworks: Prioritization Techniques