You can be brilliant at your craft, understand the business deeply, and drive significant impact, but if you’re not positioned strategically, your influence will be limited. Positioning is about how others see you, what they think you’re capable of, and what opportunities come your way.

Good positioning means you’re seen as indispensable rather than replaceable, strategic rather than tactical, a leader rather than an executor. It means opportunities find you instead of you having to chase them. It means your career advances whilst you drive meaningful impact.

This chapter shows you how to position yourself for maximum influence and impact. How to become indispensable, build your narrative, choose battles wisely, and advance your career strategically.

Example: The Designer Who Became Indispensable

When Nina joined a fast-growing startup as their second designer, she was hired to execute. Create interfaces for features the product team defined. Support the senior designer on complex projects. Ship work quickly to keep pace with growth. Standard IC designer role.

But Nina understood that her position in the company would determine her influence and career trajectory. She needed to become indispensable, not just competent. She needed to position herself as someone the company couldn’t succeed without.

She identified three strategic gaps in the organisation. First, nobody owned the end-to-end user experience across products. The company had four different products, each designed by different people at different times. The experience felt fragmented. Users complained about inconsistency.

Second, nobody was systematically gathering and synthesising user feedback. Customer support collected complaints. Product managers heard feature requests in sales calls. But nobody was turning this scattered feedback into strategic insights about what users actually needed.

Third, nobody was thinking about design at a platform level. Each product team solved problems in isolation. They were rebuilding similar components repeatedly. There was no shared design system, no common patterns, no institutional knowledge about what worked.

These weren’t gaps in her job description. They were strategic gaps in how the company operated. Nina decided to fill them, not by asking permission, but by simply doing the work.

She started creating a weekly synthesis of user feedback from all sources. She read customer support tickets, joined sales calls, analysed app store reviews, and synthesised patterns. Every Friday, she sent a concise email to product leadership: ‘This week’s user insights.’ Three key themes. Supporting evidence. Implications for product decisions. It took her two hours weekly.

Product leaders started relying on this email. It became required reading. They’d reference it in meetings. ‘As Nina’s synthesis showed last week…’ She became the go-to source for understanding users across the company. Not because it was her job, but because she made herself invaluable at it.

She started documenting design patterns across products. When she noticed three products using three different approaches to form validation, she created a document comparing them, analyzing which worked best, and recommending a standard approach. She shared it with product and engineering leads.

They loved it. It saved them from debating the same decisions repeatedly. Nina started doing this for common patterns: navigation, error handling, onboarding, settings. Within six months, she’d created an informal design system through documentation. Teams started asking her opinion on pattern decisions. She became the expert on design consistency.

She also started running monthly cross-product design reviews. She invited all designers, product managers, and interested engineers. Each session, one team presented their work. The group provided feedback. This created shared knowledge, prevented duplicate work, and built design community.

These reviews became highly attended. Product managers found them valuable for understanding what other teams were doing. Engineers appreciated seeing design rationale. Nina positioned herself as the hub of design knowledge in the company.

Within a year, Nina had made herself indispensable. When the company decided to hire a Head of Design, they offered her the role. She’d filled the leadership gap before the title existed. When she asked for a substantial salary increase, they approved immediately. They couldn’t imagine the company without her contributions.

Nina’s strategic positioning turned an execution role into a leadership role. She identified gaps, filled them without being asked, and became the person the company depended on. This is strategic positioning at work.

Becoming Indispensable

Indispensable doesn’t mean irreplaceable. Everyone is replaceable eventually. It means you create so much value that replacing you would be painful and expensive. It means you own things that matter and do them better than anyone else could.

Here’s how to position yourself as indispensable:

Own Something Important

Identify something critical to the organisation that nobody owns well. It might be a process, a knowledge domain, a relationship, or a capability. Then own it so thoroughly that you become the obvious person for anything related to it.

Nina owned user insight synthesis, cross-product consistency, and design knowledge sharing. These weren’t in her job description. They were gaps she filled. Once she owned them, removing her would create immediate problems.

Create Systems, Not Just Outputs

Outputs are tasks completed. Systems are improvements that keep delivering value. If you only create outputs, you’re replaceable by anyone who can do the tasks. If you create systems, you’ve built infrastructure the organisation depends on.

Nina’s weekly synthesis was a system. Her design pattern documentation was a system. Her monthly reviews were a system. These kept delivering value even when she wasn’t actively working on them. They multiplied her impact.

Make Others Successful

Indispensability isn’t about hoarding knowledge or making yourself the bottleneck. It’s about making everyone around you more effective. When you help others succeed, they depend on you not because they have to, but because they want to.

Nina’s systems helped product managers make better decisions, helped designers learn from each other, and helped engineers understand design rationale. She made everyone better at their jobs. They valued her because she multiplied their effectiveness.

Building Your Narrative

How people perceive you matters more than you might think. Two designers with identical skills can have vastly different influence based on how they’re perceived. Building your narrative means actively shaping how others see your work, your capabilities, and your value.

Know Your Story

What’s the arc of your career? What problems do you solve? What makes you different? What value do you create? Most people haven’t thought about this clearly, so when asked ‘what do you do?’, they give generic answers. ‘I’m a product designer’ tells people nothing distinctive.

Nina’s narrative was clear: ‘I help companies create consistent user experiences across products by building design systems and synthesising user feedback into strategic insights.’ This positioned her specifically. Not just a designer. A designer who solves particular problems in particular ways.

Demonstrate Progression

Your narrative should show growth over time. From execution to strategy. From individual contributor to multiplier. From solving assigned problems to identifying and solving systemic issues. This progression shows you’re not static. You’re developing, taking on more responsibility, increasing impact.

Nina’s progression was visible. Started as execution designer. Began synthesising insights. Created design patterns. Built systems. Established community. Each step showed increased scope and impact.

Connect Your Work to Business Outcomes

Always connect your work to outcomes that matter to the business. Revenue. Retention. Efficiency. Customer satisfaction. Market position. If you can’t articulate how your work contributes to business success, others won’t see the connection either.

Nina didn’t just say she created design systems. She said her work improved consistency, which reduced development time, which allowed teams to ship faster, which improved competitive position. She connected design work to business value.

Example: Reframing ‘Just a Designer’

Tom was a talented designer at an enterprise software company, but he was frustrated. In leadership meetings, his perspective was often dismissed. ‘That’s a design concern’ meant ‘not strategic.’ He was seen as someone who made things look good, not someone who contributed to business strategy.

He decided to reframe how leadership saw him. Instead of presenting design solutions, he started presenting business solutions that happened to involve design. Instead of ‘we should redesign the dashboard,’ he said ‘we could increase feature adoption by 40% by making the dashboard more task-oriented. Here’s the design approach that achieves that.’

Instead of ‘this design is better for users,’ he said ‘this design reduces customer support costs by 30% because users don’t get confused about key workflows. Here’s the data from our test.’

He stopped using design jargon in leadership meetings. No ‘affordances’ or ‘information architecture’ or ‘user flows.’ He talked about conversion, retention, efficiency, and revenue. He translated design thinking into business language.

He also started proactively identifying business problems and proposing solutions. He noticed customer churn was high among new enterprise clients. He did research, identified that complex setup was the issue, and proposed a redesigned onboarding experience. He presented it as ‘reducing enterprise churn by 35%’ not as ‘improving onboarding UX.’

Within six months, leadership perception shifted. They started inviting him to strategic planning sessions. They asked his opinion on business decisions beyond design. They saw him as a strategic thinker who used design as a tool, not as ‘the design person’ who needed to be consulted on aesthetic decisions.

Tom’s reframing changed his career trajectory. Same skills, different positioning, completely different influence.

Choosing Your Battles

You can’t fight every fight. You have finite energy, finite political capital, finite credibility to spend. Strategic positioning means choosing which battles matter and which to let go.

High-Impact vs. Low-Impact

Some issues have massive impact if solved. Others have minimal impact even if solved perfectly. Focus your energy on high-impact battles. Let low-impact issues go, even if you’re right about them.

If a minor UI inconsistency bothers you but users don’t notice it, let it go. If a strategic product decision is about to go wrong and you have evidence, fight that battle. Save your credibility for issues that matter.

Winnable vs. Unwinnable

Some battles are unwinnable right now. The organisation isn’t ready. The stakeholders won’t budge. The timing is wrong. Fighting unwinnable battles wastes credibility and energy. Sometimes the strategic move is to plant seeds and wait.

If you’ve tried three times to get buy-in for an idea and failed each time, step back. Maybe the organisation needs to experience the problem more acutely before they’ll accept your solution. Maybe you need to build more credibility first. Maybe you need different stakeholder support. Don’t keep fighting the same battle the same way.

Hills to Die On

There are rare issues worth spending all your credibility on. Issues of ethics, safety, user harm, or fundamental principle. These are hills to die on. But they should be rare. If everything is a hill to die on, nothing is.

Be selective. Most issues aren’t worth maximum escalation. But when something truly matters, when users could be harmed or ethics are at stake, fight that battle with everything you have.

Strategic Visibility

Your work needs to be seen to create influence. But visibility without substance is just noise. Strategic visibility means making your impact known without self-promotion, creating visibility for work that matters, and helping others see the value you create.

Document Your Impact

Keep track of outcomes you’ve influenced. Features that improved metrics after your redesign. Problems you identified that were later validated. Systems you built that others now depend on. Decisions you influenced that led to better outcomes.

This isn’t for ego. It’s so you can articulate your value when it matters. In performance reviews. In promotion discussions. When new opportunities arise. Having concrete examples makes your impact undeniable.

Share Knowledge Publicly

Write about what you’re learning. Give talks about approaches you’ve developed. Create documentation others can use. Publish insights from your work. This creates visibility whilst providing value to others.

Nina’s weekly synthesis email created visibility for her user insight work. Her design pattern documentation showcased her systems thinking. Her monthly reviews demonstrated her leadership. She wasn’t self-promoting. She was sharing valuable work that happened to showcase her capabilities.

Let Others Tell Your Story

The most powerful visibility comes from others praising your work. When stakeholders cite your research. When colleagues reference your frameworks. When leadership mentions your contributions. This is more credible than self-promotion.

Create opportunities for this by making others successful. When your work helps them achieve their goals, they’ll naturally mention it. Nina’s synthesis helped product managers make decisions. They mentioned her work because it was genuinely useful.

Career Positioning

Strategic positioning isn’t just about influence. It’s about advancing your career whilst driving impact. The two should reinforce each other.

Build Towards Where You Want to Go

If you want to be a design leader, start doing design leadership work before the title. If you want to be a strategist, start contributing strategic thinking. If you want to be a specialist, build deep expertise. Your current work should prepare you for your next role.

Nina wanted to lead design. So she started doing leadership work: synthesising insights, establishing systems, building community. When the leadership role opened, she was the obvious choice because she was already doing the work.

Make Yourself Promotable

Promotions happen when you’re already operating at the next level and the organisation recognises it. You get promoted to Senior when you’re already doing Senior work. You become a Lead when you’re already leading. You advance by demonstrating capability, not by asking for advancement.

This means seeking opportunities to stretch beyond your current role. Take on projects slightly above your level. Solve problems your manager would normally solve. Contribute in forums above your pay grade. Show you can handle the next level before requesting it.