Every designer deals with stakeholders. The product manager who writes briefs. The engineering lead who builds your designs. The executive who approves budgets. The marketing director who wants different priorities. The customer support team who deals with what you ship. Each has different goals, different pressures, different ways of measuring success.

Managing this complex web of stakeholders is one of the hardest parts of design leadership. You need buy-in from people who don’t report to you, who have competing priorities, who measure success differently than you do. You need to navigate conflicts without authority to resolve them. You need to influence people who might resist you.

This chapter shows you how to understand stakeholder dynamics and manage them strategically. How to map stakeholder incentives, manage competing interests, turn resistant stakeholders into advocates, and handle conflict productively.

Example: The Impossible Stakeholder

At a retail company, a product designer named Sofia was assigned to redesign the mobile checkout flow. The brief was clear: reduce cart abandonment by simplifying the checkout process. User research showed exactly what needed to change. The current flow had seven steps. Users wanted three. The design solution was straightforward.

But there was one problem: the Head of Marketing, David, wouldn’t approve anything that removed promotional opportunities from checkout. The current seven-step flow included two screens for cross-sells, upsells, and promotional offers. David’s bonus was tied to promotional revenue. Removing those screens would impact his metrics.

Sofia presented her research. Users abandoned because checkout felt too long. Every additional step decreased completion by 25%. The promotional screens generated minimal revenue (less than 2% of users clicked them) but caused massive abandonment. Removing them would increase overall revenue by improving completion rates.

David dismissed the research. ‘Users say they want simple, but they respond to promotions. The data shows promotional screens drive revenue. We can’t remove them.’ He had his own data showing that promotional screens generated £50,000 monthly. Never mind that improved checkout completion could generate £200,000 monthly. He was optimising for what he was measured on.

Sofia could have gone to leadership and asked them to overrule David. This would have created an enemy and damaged her credibility with other stakeholders who would see her as unwilling to work collaboratively. Instead, she tried to understand David’s position.

She asked for a coffee chat. Not to pitch her design. Just to understand his world. What was he trying to achieve? What was his boss measuring him on? What would success look like for him? What was he worried about?

She learnt that David’s team was under pressure to increase average order value. His boss had given him a target: increase AOV by 8% this quarter. The promotional screens in checkout were his main lever. If he lost them, he didn’t know how else to hit his target. He wasn’t being obstinate. He was protecting his ability to do his job.

Sofia also learnt that David was frustrated with the promotional screens. They were generic. Every user saw the same promotions regardless of their cart contents or purchase history. The conversion rate was terrible. He knew they could be better, but his team didn’t have the technical capacity to personalise them.

Armed with this understanding, Sofia reframed her proposal. Instead of ‘remove promotional screens,’ she proposed ‘replace ineffective promotional screens with personalised recommendations integrated into the checkout flow.’

She worked with the engineering team to prototype personalised recommendations. Instead of generic promotions on separate screens, they’d show relevant add-ons inline with cart items. ‘Customers who bought this running shoe also bought these socks’ appeared right next to the shoes in the cart. One screen instead of two separate promotional screens. Relevant suggestions instead of generic promotions.

She ran a test with 1,000 users. The new approach had three times higher conversion on recommendations (6% vs 2%) whilst reducing checkout abandonment by 30%. Total revenue increased 18%. Average order value increased 12%. David’s metric improved more than her approach than with his current screens.

She presented this to David privately first, before any formal review. ‘I think I found a way to hit your AOV target whilst solving the checkout abandonment problem. The test results show personalised inline recommendations convert 3x better than current promotional screens. You’d get better performance on your metrics and users get a simpler checkout.’

David approved immediately. In the formal review meeting, he championed the new design. He presented it as his team collaborating with design to improve promotional effectiveness. Sofia didn’t care who got credit. The work was getting done. Users were getting a better experience. Revenue was increasing. That’s what mattered.

Six months later, David became one of Sofia’s strongest advocates. When she proposed other projects, he supported them. He’d learnt that collaborating with her made him more successful at his own goals. This is how you turn resistant stakeholders into allies.

Understanding Stakeholder Incentives

The key to Sofia’s success was understanding David’s incentives. He wasn’t being difficult for the sake of it. He was protecting his ability to hit his targets. Once she understood that, she could propose a solution that served both their goals.

Most stakeholder resistance comes from misaligned incentives. Here’s how to decode them:

Follow the Metrics

People are measured on specific things. Those metrics drive behaviour more than stated values or company goals. If a product manager is measured on feature velocity, they’ll resist anything that slows down shipping. If an engineering lead is measured on system stability, they’ll resist risky changes. If a sales director is measured on deal volume, they’ll resist anything that complicates the sales process.

Find out what each stakeholder is measured on. Ask directly: ‘What does success look like for you this quarter?’ or ‘What is your boss evaluating you on?’ Once you know their metrics, you can frame your proposals in ways that help them succeed on those metrics.

Identify Hidden Constraints

Sometimes stakeholders resist because they’re operating under constraints they haven’t shared. Budget limits. Political pressure. Technical debt. Commitments to other teams. These hidden constraints make seemingly reasonable requests feel impossible to them.

David’s hidden constraint was that he didn’t have technical resources to personalise promotions. Sofia’s solution worked because it included the technical implementation, removing his constraint. If she’d just said ‘make promotions better,’ he couldn’t have acted on it.

Recognise Risk Aversion

Change creates risk. If something goes wrong, stakeholders get blamed. The status quo feels safer than innovation, even when the status quo isn’t working well. This makes stakeholders resist change that seems perfectly sensible.

Address risk directly. Run small tests. Provide data. Offer to own the risk yourself. Make it safe for stakeholders to say yes by reducing the downside of failure.

Example: Why the VP Kept Saying No

At a fintech company, a design team kept proposing improvements to the mobile app. Better onboarding. Improved navigation. Streamlined features. Every proposal was well-researched, well-designed, and well-argued. Every proposal got rejected by the VP of Product.

The design team was frustrated. ‘She just doesn’t value design. She only cares about features.’ But a senior designer named Alex decided to understand why before judging. He asked the VP for coffee to learn about her perspective.

He learnt that the VP had been burned by a redesign two years earlier. The design team had convinced her to approve a major app redesign. It took six months. When it launched, usage dropped 15%. Users hated the changes. It took another three months to recover. The VP had to explain the failure to the board. It nearly cost her the job.

Since then, she’d become risk-averse about design changes. She’d approve small tweaks but nothing substantial. It wasn’t that she didn’t value design. She was terrified of another catastrophic redesign. Every substantial design proposal triggered that fear.

Armed with this understanding, Alex changed the team’s approach. Instead of proposing big redesigns, they proposed small, testable improvements. Instead of ‘redesign onboarding,’ it was ‘test removing one field from step two.’ Instead of ‘improve navigation,’ it was ‘A/B test moving the menu icon to the top left.’

Each proposal included a test plan with clear success metrics, limited scope, and easy rollback. ‘We’ll test with 5% of users for one week. If metrics drop, we revert immediately. If metrics improve, we roll out gradually.’

The VP approved these proposals. They were low-risk. Each test succeeded. Small improvements accumulated. Within a year, the app had improved dramatically through dozens of small, tested changes. The VP’s trust in design increased because every change proved its value before scaling.

Alex had turned a resistant stakeholder into a supportive one by understanding and addressing her underlying fear. This is stakeholder management at work.

Managing Up, Down, and Sideways

You need to manage relationships in three directions: up (to managers and executives), down (to people you might mentor or influence), and sideways (to peers and collaborators).

Managing Up

Managing up means making your managers and executives successful. This isn’t about sucking up. It’s about understanding what they need and providing it.

Executives need different things than individual contributors. They need summaries, not details. They need to know what decisions need to be made, not every option considered. They need to understand business impact, not just user experience improvements.

When presenting to executives, lead with the decision required and the recommendation. Follow with supporting evidence. Be prepared to go deeper if asked, but don’t lead with depth. Respect their time. Make it easy for them to say yes.

Managing Sideways

Managing peers is about collaboration and mutual success. You don’t have authority over peers. You need to influence through value, relationships, and reciprocity.

The best peer relationships are built on mutual benefit. Help your peers succeed at their goals. Share information that makes their work easier. Offer to collaborate on challenges they’re facing. When you need their support, they’ll remember who helped them.

Managing Down

Even without direct reports, you influence people. Junior designers look to you for guidance. New team members need onboarding. Contractors need direction. This is managing down.

Managing down is about multiplication. Teaching others makes them more effective. Creating frameworks helps teams work better. Documenting decisions prevents repeated questions. Good managing down means your influence extends beyond your own output.

Handling Conflict Productively

Stakeholder conflicts are inevitable. Different people have different goals. Resources are finite. Priorities compete. Conflict isn’t the problem. How you handle it determines whether it’s productive or destructive.

Separate People from Problems

When conflicts arise, it’s easy to personalise them. ‘Marketing is being unreasonable’ or ‘Engineering doesn’t care about users.’ This makes resolution harder because it becomes about defending positions rather than solving problems.

Instead, separate the people from the problem. ‘Marketing needs to hit AOV targets and design needs to reduce abandonment’ is a problem to solve together, not a conflict between departments. This framing makes collaboration possible.

Seek to Understand Before Being Understood

In conflicts, everyone wants to be heard first. But listening creates more progress than talking. Before defending your position, genuinely understand theirs. Ask questions. Seek to understand their constraints, their pressures, their perspective.

Often, conflicts dissolve when both parties actually understand each other. What seemed like incompatible positions become different approaches to shared goals.

Look for Enlarging the Pie

Most conflicts are framed as zero-sum. Either your way or their way. Marketing gets promotional screens or design gets simplified checkout. But creative solutions often exist that serve both parties.

Sofia’s personalised recommendations enlarged the pie. Marketing got better promotional performance. Design got simpler checkout. Users got better experience. Looking for these solutions requires moving beyond initial positions to underlying interests.

Getting Executive Sponsorship

Some initiatives need executive sponsorship to succeed. You can’t influence them through peer relationships alone. You need someone with authority to champion them. Here’s how to get it:

Identify the Right Executive

Not every executive is the right sponsor. You need someone who cares about the problem you’re solving, has authority in the relevant area, and has credibility with other executives. Often this isn’t your direct manager. It might be a VP whose goals align with your initiative.

Make It Easy to Sponsor

Executives are busy. If sponsoring your initiative requires heavy lifting, they’ll pass. Make it easy. Do the work. Build the coalition. Gather the evidence. Present them with a complete case that just needs their endorsement and authority.

Align with Their Priorities

Executives sponsor things that help them achieve their priorities. Frame your initiative in terms of what they care about. If the CTO cares about technical excellence, frame your design system as improving code quality. If the CEO cares about revenue, frame accessibility improvements as expanding addressable market.

The Stakeholder Map

For complex initiatives, create a stakeholder map. List every person whose support you need or whose resistance could derail you. For each stakeholder, document their level of support (advocate, neutral, resistant, opposed), their influence (high, medium, low), what they care about, and what strategy you’ll use with them.

This map becomes your political strategy. You can see where you need to build support, who might block you, and how to address resistance. Update it as relationships shift. This systematic approach prevents you from missing critical stakeholders or being blindsided by resistance.