Everything we’ve discussed in this book comes down to one practical challenge: how do you actually build influence when you have no formal power? How do you go from being the designer who takes notes in meetings to the designer whose perspective shapes strategic decisions?

This chapter provides a concrete playbook for building influence as a designer without authority.

The Credibility Ladder

Influence without authority is built through credibility. But credibility isn’t binary. You don’t just have it or not have it. Credibility is a ladder you climb incrementally, one rung at a time. Each level unlocks new possibilities for influence.

Rung 1: Craft Excellence

Everything starts with the quality of your work. If your designs are mediocre, if your research is sloppy, if your deliverables are inconsistent, nothing else matters. You’ll never get the credibility needed for strategic influence. This is the price of admission.

Craft excellence means your interfaces are intuitive and polished. Your research is rigorous and insightful. Your documentation is clear and thorough. Your work consistently meets or exceeds professional standards. People look at your output and think, ‘This person knows what they’re doing.’

But craft excellence alone is insufficient. Many brilliant designers remain stuck at this rung because they assume their work speaks for itself. It doesn’t. Craft excellence creates an opening for influence, but it doesn’t guarantee it. You need to climb higher.

Rung 2: Business Understanding

The next level is demonstrating that you understand the business, not just design. You know how the company makes money. You understand key metrics. You can connect design decisions to business outcomes. You speak the language of product managers and executives.

This means asking questions like ‘What’s the business goal for this project?’ and ‘How will we measure success?’ It means understanding conversion funnels, retention metrics, customer acquisition costs, and lifetime value. It means being able to say, ‘This design change should increase conversion by X%, which translates to £Y in additional revenue.’

When you demonstrate business understanding, you stop being seen as ‘the designer who makes things pretty’ and start being seen as someone who understands what the company is trying to achieve.

Rung 3: Strategic Thinking

The third level is demonstrating that you can think strategically. You can see patterns across projects. You can identify problems before they become crises. You can propose solutions that address root causes rather than symptoms. You think beyond individual features to platform and product strategy.

This might look like noticing that three different features are all trying to solve variants of the same underlying user need, and proposing a unified solution. Or identifying that the company’s growth problems aren’t about acquisition but about activation, and redirecting focus accordingly. Or spotting that technical debt in the design system is slowing down every team, and building a business case for addressing it.

Strategic thinking shows you can contribute at a higher level than execution. You’re not just doing the work. You’re helping decide what work should be done.

Rung 4: Proactive Problem-Solving

The fourth level is consistently solving problems you weren’t asked to solve. You identify gaps, propose solutions, and drive them to completion without waiting for permission or assignment. You take ownership of outcomes, not just outputs.

This is the Marcus creating a design system example from Chapter 1. He saw a problem, built a solution, demonstrated value, and earned influence through action. This level shows you’re not just strategic in thinking. You’re strategic in doing.

Rung 5: Multiplying Others

The highest level is when you make everyone around you more effective. You mentor other designers. You help product managers think more clearly. You enable engineers to ship better work. You create frameworks and tools that benefit entire teams. Your impact extends beyond your own output.

When you multiply others, you become indispensable. Leadership starts asking, ‘How do we clone this person?’ You’ve built influence that extends across the organisation.

Example: From Pixel Pusher to Strategic Partner

Luke joined a healthcare technology company as a product designer. For the first six months, he focused exclusively on execution. Take briefs from product managers. Create interfaces. Iterate based on feedback. Ship designs. Move to the next project. His work was excellent. Nobody complained. Stakeholders were happy.

But Luke wasn’t being included in strategic discussions. When product managers talked about roadmap priorities, he wasn’t in the room. When executives debated company direction, design wasn’t represented. James was seen as someone who executes well, not someone who contributes to strategy.

He asked his manager why. The answer was honest but uncomfortable: ‘You’re great at execution, but you haven’t shown you can think strategically about the business. You deliver what you’re asked for, but you don’t challenge the brief or propose alternatives. You focus on design quality, but you don’t connect it to business outcomes.’

Luke realised he was stuck on Rung 1 of the credibility ladder. His craft was excellent, but he needed to climb higher. He made a conscious decision to change his approach.

Step one: demonstrate business understanding. In his next project kickoff, instead of just asking ‘What should this look like?’, he asked business questions. ‘Why are we building this now? What metric are we trying to move? What happens if we don’t build it? How does this fit with our Q3 goals?’ Product managers noticed. He wasn’t just taking orders. He was trying to understand context.

He started attending company all-hands meetings and asking questions about business metrics. He read quarterly business reviews. He talked to the sales team to understand why deals were won or lost. He studied competitors to understand market positioning. Within two months, he could speak fluently about the company’s business model, growth challenges, and strategic priorities.

Step two: demonstrate strategic thinking. He started sharing not just designs, but the reasoning behind them. ‘I explored three approaches. Option A optimises for new user acquisition with a simple onboarding flow. Option B optimises for existing user retention with powerful features upfront. Option C balances both but takes longer to build. Based on our Q3 goal of increasing revenue from existing customers, I recommend Option B because it increases feature adoption, which correlates with retention.’

He started documenting patterns he noticed across projects. After working on five different features in three months, he wrote a memo: ‘I’ve noticed all these features struggle with the same problem. We don’t have clear user segments, so we design for everyone and delight no one. What if we created distinct user personas and optimised features for specific segments?’

His product manager read the memo and brought it to the leadership team. They approved a research project to create user segments. James led it. He interviewed 40 customers, created five personas with distinct needs, and presented a segmentation framework. Product started using it to make roadmap decisions. James had identified a strategic gap and filled it.

Step three: proactive problem-solving. Luke noticed that the design team (three designers) didn’t have consistent quality standards. Each designer had their own approach. Work from different designers looked and felt different. This was creating brand inconsistency and confusing users.

He didn’t wait for leadership to notice this problem. He spent two weeks creating a lightweight design system with the most common patterns. Just buttons, forms, typography, and colours. He shared it with the other designers. They started using it. Quality became more consistent. Stakeholders noticed. The Head of Product asked Luke to present the design system at the company all-hands.

Six months after starting his credibility climb, Luke was in strategic planning meetings. Product managers explicitly asked for his input on roadmap priorities. Executives invited him to weigh in on company direction. His title hadn’t changed, but his influence had grown dramatically.

A year later, when the company hired a Head of Design, they offered Luke the role. But the promotion came after the influence, not before. James was already leading. The title just recognised it.

The Three Types of Strategic Relationships

Influence is built through relationships. But not all relationships are equal. You need three types of strategic relationships to build comprehensive influence.

1. Peer Relationships: Your Coalition

These are the product managers, engineers, researchers, and other designers you work with directly. They’re your coalition. When you need support for an idea, these are the people who’ll back you up. When you’re stuck, they’ll help you navigate. When opportunities arise, they’ll recommend you.

Build peer relationships by making other people’s work easier. When an engineer is stuck on an interaction pattern, help them figure it out. When a product manager needs user insights, share your research. When another designer asks for feedback, give it generously and thoughtfully. When someone is overwhelmed, offer to help.

This isn’t about keeping score or expecting immediate reciprocity. It’s about accumulating social capital by being genuinely helpful. Over time, people remember who helped them when they needed it. They return the favour when you need support.

2. Upward Relationships: Your Sponsors

These are the managers, directors, and executives above you in the hierarchy. They control resources, make strategic decisions, and have authority you lack. You need some of them to be advocates for your work and your ideas.

Build upward relationships by solving problems these people care about. Find out what keeps your manager’s manager up at night. What are they being measured on? What would make their job easier? Then find ways to help with those challenges.

This might mean proactively sharing insights from your work that inform their decisions. Or offering to help with a project they’re struggling with. Or creating visibility into work happening in your area that they should know about. The key is providing value without being asked.

3. Cross-Functional Relationships: Your Network

These are people in other departments you don’t work with directly. Sales, marketing, customer support, operations, finance. They have perspectives and information you need. They also have influence in parts of the organisation you can’t access directly.

Build cross-functional relationships by being genuinely curious about what other departments do. Have coffee with someone from sales to understand how customers buy. Talk to customer support to learn what users struggle with. Ask finance how they think about ROI. These conversations make you smarter and create bridges across the organisation.

When you need to influence a decision that involves multiple departments, these relationships become crucial. You can understand different perspectives, identify potential resistance, and build coalition across functions.

Example: The Cross-Functional Alliance

At a media company, designer Maya wanted to improve the site’s accessibility. The business case was clear. Twenty per cent of the UK population has some form of disability. The current site was unusable with screen readers. Keyboard navigation didn’t work properly. Colour contrast failed accessibility standards. This limited the site’s potential audience and created legal risk.

But accessibility improvements rarely got prioritised. Engineering said they didn’t have capacity. Product said users weren’t asking for it. Leadership said it wasn’t a revenue driver. Maya had been trying to get accessibility on the roadmap for eight months. Every attempt failed.

She realised she needed a different approach. Instead of trying to convince product and engineering alone, she needed a broader coalition. She started having conversations across the company, not to pitch accessibility but to understand everyone’s challenges and goals.

She talked to the Head of Customer Support. She learnt that they received dozens of complaints monthly from users who couldn’t navigate the site. These complaints took time to handle and frustrated users who couldn’t be helped because the problems were product issues, not user error. Customer Support would love to reduce this complaint volume.

She talked to the Head of Legal. She learnt that they were worried about potential lawsuits under disability discrimination laws. The company was exposed. Legal would love to reduce this risk.

She talked to the VP of Engineering. She learnt that he wanted to improve the team’s reputation for quality and technical excellence. The engineering team was seen as fast but sometimes sloppy. Engineering would love to ship something that demonstrated careful, thoughtful work.

Maya stopped talking about accessibility as a design initiative. She made it a company initiative with clear benefits for multiple departments. She wrote a proposal framing accessibility improvements as solving several problems simultaneously: reducing support burden for Customer Support, mitigating legal risk for Legal, demonstrating technical quality for Engineering, and expanding potential audience for Product.

She didn’t propose this alone. She got buy-in from Customer Support, Legal, and Engineering first. When she presented to leadership, she had three departments backing her. The Head of Customer Support talked about complaint reduction. Legal talked about risk mitigation. Engineering talked about quality improvement. Maya talked about user impact.

The proposal passed in one meeting. Within three months, the site met WCAG AA standards. Customer Support complaints about accessibility dropped 89%. Legal moved the company off their risk watchlist. Engineering got praised in an all-hands for the quality of the implementation. Product saw a 6% increase in engagement from users with accessibility needs.

Maya’s cross-functional relationships transformed an idea that kept getting rejected into an initiative that had organisational support. This is the power of coalition-building.