Something shifts when you get the title. You expect things to change - the conversations you're invited into, the weight your opinion carries, the problems you're trusted with. Then Monday comes. Nothing changed.
That confusion - between what the title promised and what the work actually looks like - is the thing I want to talk about. Not because you're doing something wrong. But because nobody told you what the title actually required of you.
The title didn't change your role. You were supposed to change your role - and nobody told you that.
The Sentences That Reveal Everything
When I talk to senior designers, certain sentences come up again and again. I've started calling them diagnostic sentences - not complaints, but symptoms.
"I count screens. That's basically my KPI."
"The tech team overrides my decisions - sometimes down to colours."
"I haven't been in a single sprint planning session this quarter."
"I genuinely don't know what success looks like for this product - not according to the org."
Each of these describes the same thing: a designer who is executing other people's ideas without realising it. A mason who is very skilled, but who is not the architect.
If you recognise one of those sentences - this is for you.
If you're also not getting interview callbacks despite having the experience, you might find this useful: Why You're Not Getting UX Interview Calls
This Isn't Just Your Experience. The Data Confirms It.
In 2019, InVision surveyed 2,200 organisations across 77 countries on how design was actually used inside their companies. The finding was hard to ignore: 83% of those organisations kept design at a purely executional level - focused on screens, flows, and handoffs, not on shaping the product strategy that preceded them.
McKinsey's research reinforced this from a different angle. Across 300 publicly listed companies, they found that fewer than 5% of senior leaders could make objective design decisions - and over 40% of those companies weren't even talking to end users during development. Design was present. It just wasn't influential.
Nielsen Norman Group's maturity data - drawn from over 5,000 organisations - shows that 49% sit at what they call "Emergent" maturity: UX people in formal roles, but design not yet treated as a strategic priority. Only 4% of organisations reach a level where design is genuinely integrated into decisions.
So when you feel like a delivery person with a senior title, you are not imagining things. You are experiencing what the data describes as the norm.
The same McKinsey study found that companies where design is integrated - where it sits at the strategic level - generated 32 percentage points more revenue growth and 56 percentage points more total returns to shareholders than their peers over five years. The business case for design influence is not philosophical. It is financial.
The Org Problem Is Real. It Is Still Your Responsibility.
I want to be careful here, because I've seen this go wrong in both directions.
On one side, designers who carry all the blame themselves - who assume that if they just do better work, get sharper, produce cleaner outputs, the influence will follow. It won't. Organisational culture, leadership priorities, and power structures shape how design is used far more than the quality of any single designer's output.
On the other side, designers who understand the org problem clearly, name it accurately - and stop there. They diagnose the culture and then wait for it to change. That is equally stuck.
The honest position is in the middle. The organisation is contributing to this situation. So are you, in ways you may not yet see. And the reason to address your part - even though the org needs to change too - is simple:
You cannot control the org. You can control how you show up inside it.
The PIE Model: Position, Integrate, Evidence
At Xperience Wave, working with mid-to-senior designers across India's product ecosystem, we've observed a consistent pattern in how designers move from execution mode to genuine influence. We've formalised it into three stages: PIE.
P - Position: How are you perceived before you enter the room?
Most designers seek authority inside the org while their positioning outside the org is undefined. Positioning is not self-promotion - it is clarity about what you stand for and what problems you are equipped to solve.
A designer who is known externally as someone with a clear point of view on a domain - AI-first product design, fintech onboarding, B2B SaaS research - walks into internal conversations differently than one who is only known by their job title. Positioning creates pull. It means stakeholders come to you rather than assigning to you.
This is not about LinkedIn activity. It is about building subject-matter expertise with enough visibility that the people who matter - internally and externally - associate a specific kind of thinking with your name.
If positioning in the AI space is relevant to you, this is a useful read: AI-First Design: What Senior UX Designers Need to Know
I - Integrate: Are you speaking the language of the room?
One of the most common patterns I see: a senior designer presenting work to product and tech stakeholders using design language. Talking about hierarchy, affordance, research insights, user journeys. The room nods politely and overrides the decision anyway.
Influence does not come from having the right answer in the wrong language. It comes from learning to translate your design thinking into the terms that the business actually uses - retention, activation, conversion, development cost, time to market.
Integration also means presence in the right rooms at the right time - sprint planning, product reviews, quarterly strategy conversations. Not to represent design, but to contribute to the shared problem. That distinction matters. Representing design is advocacy. Contributing to the shared problem is influence.
E - Evidence: Can you show before you ask?
This is where "build evidence" becomes concrete. Evidence is not a portfolio. Evidence is a specific claim, linked to a specific outcome, that you made visible before asking for anything.
It sounds like: "That onboarding flow we redesigned last quarter - drop-off at step 3 went from 67% to 41%. Here's what we changed and why." Or: "User research I ran three months ago flagged this problem. Here's what happened when engineering addressed it."
Evidence changes the ask. Instead of "trust design more," you are saying "here is what happens when you do." That is a different conversation. Most designers wait until they have authority to build evidence. The designers who gain authority are the ones who build it first.
Knowing how to frame and present research findings as business evidence is its own skill. This goes deep on it: Mixed-Methods UX Research: When to Use It, How to Do It
What This Looked Like in Practice: Ashwin's Story
Ashwin was a senior designer at an AI-first product company. His tech co-founder was overriding UX decisions down to the colour of buttons. His team lead was functioning as a contributor, not a leader. Ashwin had stopped expecting the culture to change.
When we started working together, his instinct was to push for a new title - design lead, head of design, something that would give him the authority he felt he should have. We reframed the goal. Before asking for the title, build what the title is supposed to represent.
Over four months, we worked through PIE in sequence.
Position first. We built his SME positioning around AI-first product design - a specific, credible, timely domain. LinkedIn content. One conference talk. Three long-form articles published over six weeks. Nothing dramatic, but consistent enough that when his name came up, people could attach a perspective to it.
Then integration. He spent six weeks learning the cross-functional language in his org - what the product team cared about, what the business metrics were, what the tech lead's constraints actually were. He stopped presenting design as design. He started presenting it as a solution to their problems. Slowly, he was invited into conversations he had previously been excluded from.
Then evidence. He documented every design decision that had a measurable downstream effect - even small ones. He made those outcomes visible in weekly standups, in Slack, in 1:1s with his manager. He was not boasting. He was creating a record.
Four months in, Ashwin was being positioned alongside the same team lead he had previously reported to. The gates to strategic conversations had opened - not because the culture changed, but because he had changed how the culture perceived him.
An Unpopular Opinion About Where Most Designers Look
I've noticed a pattern in what senior designers spend their energy on when they feel stuck. They worry about design systems when the real gap is governance - who decides what gets built. They learn new AI tools when what they need is AI-first thinking - a point of view on what AI means for their product's users, not proficiency in the tool. They pursue a new designation when what they need is to understand what a designation requires of you before it will work for you.
There are three kinds of people who hold design leadership titles:
- The first has the title in name - it was given, not earned through influence.
- The second manages people but has no real strategic voice.
- The third shapes direction, is treated as a peer by product and engineering leadership, and is accountable to business outcomes, not just design outputs.
The title is the same. The role is entirely different.
The PIE Model is about how you move from the first kind to the third - not by waiting for the org to give you a bigger title, but by becoming someone for whom the bigger title is the only accurate description.
If you're already at senior level and your goal is to move into a Head of Design, Director, or VP role, our Tide programme is built specifically for that transition.
One Thing to Do This Week
Don't start with positioning. Don't start with integration. Start with evidence - because it requires no permission and no structural change.
Look back at the last 60 days. Find one design decision that had a downstream effect on a metric the business cares about. Write three sentences: what you changed, why you changed it, what happened. Share it in the next forum you have - a standup, a Slack channel, a 1:1.
That is it. One data point, made visible. Rome was not built in a day. But Rome was built intentionally, brick by brick, by people who had decided what they were building before anyone else had seen the blueprint.
Your influence is built the same way.
If you're a senior designer who has the title but not the influence - and you want to understand what stage of PIE you're at and what to do about it - we run a free 45-minute strategy call at Xperience Wave.
Most designers we speak to are in the right place for our Current programme (for mid-to-senior designers) or our Tide programme (for designers ready to lead teams). The strategy call tells us which, or neither.
Sources
- InVision, The New Design Frontier (2019). Survey of 2,200+ organisations across 77 countries.
- McKinsey & Company, The Business Value of Design (2018). 300 publicly listed companies, 2M+ data points.
- Nielsen Norman Group, The State of UX Maturity: Data from Our Self-Assessment Quiz (2022). n=5,371.
- Almas, CEO & Co-founder, Xperience Wave
