Before we get into the how, I need to clear three things out of the way. Three reasons designers use to not engage with this topic at all. I've heard all of them. None of them hold.

"We work remotely. There's no table."

You're right. There's no table.

There's just a Slack thread where three people decided what your next six weeks look like. There's a Google Doc that became a roadmap before you knew it existed. There's a recurring call between the CPO, the engineering head, and a business lead, forty-five minutes, every two weeks, that you have never been invited to and nobody told you about.

The table isn't furniture. It's wherever the decisions happen without you. Call it whatever you want. The outcome is the same: you find out about the direction after it's been set, and then you execute it.

"Our organisation doesn't really do strategy. We move too fast for that."

Moving fast is a strategy. Deciding not to decide is a strategy. Piling feature on top of feature without asking whether the thing you're building is still the right thing, that is absolutely a strategy. It just happens to be a bad one. And at some point, someone will have to clean it up. Usually design.

"Product strategy isn't really my area, is it?"

This is the one I want to spend time on. Because it's the most common, and it does the most damage. Yes. It is your area. Here's why.

What the Table Actually Is, and Why Products That Skip It Die

The product strategy table is where decisions about a product's direction get made. Not the design decisions. Not the feature decisions. The direction decisions: what problem are we solving, for whom, and why does solving it matter to the business?

Nobody calls it the product strategy table. It happens inside quarterly planning meetings, annual OKR sessions, board reviews, investor updates, leadership offsites. The agenda is usually framed around growth, market position, or technology. Design is almost never on it by default.

Here is why this matters to you specifically.

Customer expectations change. Technology changes. The cultural context that made your product relevant shifts. What worked three years ago, the interaction model, the user mental model, the navigation architecture, is now friction. Not because the design got worse. Because the world moved and the product didn't.

What doesn't evolve, stops surviving.

Every product that has ever died at the height of its apparent success died because the people running it believed they had built something so good it no longer needed to change.

Now: who is deciding what the product evolves into? Someone is making those calls. In most organisations, it's product management and engineering leadership. In some, it's the CEO. In others, the ones where design has been historically undervalued, it's whoever can get the most time in the right rooms.

The question is not whether you care about product strategy. The question is whether you're in the room where it's being decided. Because if you're not, the decisions get made without you, and then handed to you to execute. And you already know what that feels like.

Here's the scale of the problem. McKinsey's Business Value of Design research, across more than 300 publicly listed companies, found that fewer than 5% of organisations had senior leaders who could make objective design decisions. Over 40% of companies weren't even talking to their end users during development. Design was present. It was just not in the room where direction was set.

The same McKinsey research found that top-quartile design companies generated 32% more revenue and 56% more in total returns to shareholders than industry peers over five years. The business case for design at the strategy table is not philosophical. It is financial.

If you're a senior designer experiencing this right now, the execution-only dynamic, this is the same culture problem we covered here: Senior Designer Still Treated Like a Delivery Person.

What It Actually Took: A Story From Inside a Fintech Organisation

When I joined a fintech organisation at around eight to nine years of experience, I had a role and I had a team. Neither of those things opened the door.

The culture I walked into had been shaped by the designers and leaders who came before me. Design's job, in that organisation's understanding, was to receive a brief from product, give it visual shape, and deliver it. The relationship between design and product strategy was the same as the relationship between a printer and an author. You don't ask the printer what the book should say.

I understood the logic from their side. Design had never demonstrated anything beyond that capability. So why would the conversation include us?

There were two ways I could have responded. The first was to argue for design's value, to make the case in theory, using case studies from other companies, talking about the strategic role design plays at Apple or Airbnb. This is the approach most designers take. It almost never works. Because the organisation has no reason to believe the argument applies to them, to their team, to this specific situation.

The second was to make the argument in the only language that actually lands: proof.

You cannot argue your way to the product strategy table. You earn your way in. And the currency is evidence, not persuasion.

This isn't just my experience. Doug Powell, a design leader at IBM who spoke at the IXDA international conference, described what it takes to communicate design to business leadership: they are data-driven, opinionated, competitive, and have a finely-tuned no-bullshit meter. They will not respond to warm-and-fuzzy stories. They respond to clear evidence and quantifiable data. The framing matters more than most designers want to admit.

And then I delivered. On one project, we doubled the conversion percentage. Not in six months. In the shortest timeline the team had seen for an initiative of that scope. That result, specific, measurable, undeniable, was the thing that opened the first door.

After that, I was included in the annual planning. Then the half-yearly planning. Then the quarterly. The OKRs, which had always sat under product and technology, began to shift. Design started being upstream, talking directly to business about what kind of experience needed to be generated, and then delivering to that. Technology came after.

I want to be honest about where this story ends, because most people who write about this topic skip the hard part.

After two years of this, we still weren't fully there. Design was in the room. But OKRs still weren't owned by design. The perception that design can own strategic outcomes, not just contribute to them, is a harder cultural shift than getting invited to the meeting. I was getting a seat. I was not yet running the table.

Getting a seat at the strategy table is not a destination. It's a position you have to hold, re-earn, and defend. Sometimes in the same organisation. Sometimes indefinitely.

Anyone who tells you otherwise has not actually done it.

The Werewolf: Why Most Designers Fail at This Even When They Get In the Room

I want to give you a mental model for the kind of designer who survives, and thrives, in product strategy conversations. I call it the werewolf.

Not because it's dramatic. Because it's accurate.

A werewolf knows exactly when to fight. When the conversation is going somewhere that would damage the product or the user, and you have the evidence to say so clearly, you fight. You don't politely suggest. You make the case, you hold the ground, you are willing to be uncomfortable.

A werewolf knows when to retreat. When the decision has been made and the political cost of continuing to push outweighs the benefit, you let it go. You note your objection, you make it legible, and then you support the direction that was chosen. Because being the person who can't stop relitigating lost decisions is the fastest way to lose the seat you just earned.

A werewolf knows when to show confidence. Not performance confidence, the kind that sounds impressive in a meeting and evaporates under questioning. Real confidence, which is built from knowing your domain deeply and being able to defend your thinking at multiple altitudes simultaneously: the thirty-thousand-foot view of where the product needs to go, and the ground-level specifics of how you'd get there.

And a werewolf makes friends. Not networking. Not relationship-building as a career strategy. Genuine understanding of the other people in the room: what they are responsible for, what constraints they operate under, what they're afraid of, what they need. Because the strategy table is not a design critique. It is a negotiation between people with different mandates, and you cannot negotiate with people you haven't taken the time to understand.

The designer who gets a permanent seat at the strategy table is not the smartest in the room. They are the most useful. They know when to push, when to yield, and when to simply make everyone else's job easier. That combination is rarer than intelligence.

The designers who fail at this, and I have watched many fail at it, almost always do so in one of two ways. The first: they push too hard, too consistently, on too many things. They fight every battle. They make design feel like resistance rather than contribution. The room starts working around them. The second: they yield too much, too quickly. They attend the meetings but don't change anything. They are present but not useful. The room stops including them because their presence makes no difference.

The werewolf does neither.

Eight Things That Actually Get You In and Keep You There

1. Get involved before the brief exists

The single most important move is also the least glamorous. Find out where priorities are being formed, before they become tasks, before they become tickets, before they land in your queue as a brief to execute. That might be a monthly leadership sync you're not currently in. A product-business conversation that happens over a call you've never been invited to. A document that gets written before the planning cycle officially starts.

Get close to that moment. Not by forcing your way in, but by making yourself useful to the people who are already in it. Ask questions. Contribute early thinking. Offer a perspective on what the user needs that nobody else in that conversation can offer. If you can't get in early, get close to someone who is. Know what is being prioritised. Know why. Know what assumptions are being made before they become decisions. That knowledge is how you show up informed, not reactive.

2. Speak business first, design second

This is not a suggestion to stop being a designer. It is a suggestion to wear the right hat at the right moment.

At the strategy table, the conversation is about growth, margin, market position, risk, and capability. If you enter that conversation talking about user journeys, affordance, or information architecture, you will be heard as a specialist with a narrow view. You will be listened to politely and then the conversation will move on without you.

The same thinking, reframed: "This feature is introducing friction in an already-complex onboarding flow, and we're seeing dropout at the exact point where activation matters most. Here's what that costs us in monthly revenue." That lands. That contributes to the conversation that's already happening.

Design thinking is a capability. Business language is how you make that capability legible to the room. You need both. Most designers only bring one. This is exactly the kind of reframing we explored in building a business-driven UX portfolio.

3. Be predictive, not just reactive

A designer who shows up with solutions is useful. A designer who shows up with a view of what's coming, before anyone else has named it, is irreplaceable.

Being predictive means reading the signals that others in the room are too close to their own responsibilities to see. Customer behaviour shifting. A technology change that will affect the interaction model in two product cycles. A competitive move that your current product architecture isn't equipped to respond to.

It also means being honest about risk. Not performing confidence about a direction when you have genuine doubts. The people at the strategy table are making bets. They need to know the odds. A designer who can say "here is what this hypothesis gets right, here is where it could fail, and here is the signal we'd watch for" is contributing to the quality of the bet, not just executing on it.

4. Know the other people's constraints, not just their positions

The product manager is not trying to undermine design. They are under pressure to ship. The engineering lead is not being obstructive. They are managing debt and realistic timelines. The finance partner is not anti-user. They are accountable for a number that the organisation has committed to.

When you understand what someone is actually constrained by, not just what position they hold, you stop experiencing conflict as personal and start engaging with it as structural. And structural conflicts are solvable. Personal conflicts are exhausting. The werewolf makes friends by understanding what the room is actually under pressure about. That understanding is what allows you to contribute to their problem, not just push your own agenda.

5. Operate at thirty thousand feet and at ground level simultaneously

One of the fastest ways to lose credibility at the strategy table is to get lost in detail at the wrong moment. One of the fastest ways to lose it permanently is to never be able to back up a strategic view with specifics.

The designers who hold the seat are the ones who can switch altitude without warning. They can articulate the product direction at the level of a board conversation, and then immediately go to: here's what that means for the next sprint, here's the specific interaction problem we'd have to solve, here's what we'd need to validate before committing. Both directions. No lag. That combination signals that you are not just a thinker or just an executor. You are someone who can hold the whole picture.

6. Speak in "we", not "I"

Nobody gets a strategy executed alone. The designers who understand this speak differently in these rooms. Not "I would approach this by..." but "here's how we'd bring this to life: the research we'd need, the engineering alignment required, the timeline that makes this viable."

That language signals that you are thinking about implementation, not just ideas. That you understand what it takes to actually move something from a strategic direction into a shipped experience. That you are not going to create more coordination problems than you solve. It is also, practically, how you start getting budget and resources allocated. You cannot resource an individual. You can resource a plan.

7. Hold your ground without making it a fight

There will be moments where the direction being taken is wrong. You know it. You have the evidence. You need to say so.

The mistake most designers make here is one of two: they say nothing, or they make it a confrontation. The first makes you irrelevant. The second makes you a problem.

The move is to name your concern specifically, attach it to a consequence the room cares about, and make it easy for the room to engage with it. "I want to flag something before we commit to this direction. The assumption here is that users understand the new flow without guidance, and our research from the last release suggests that's not a safe assumption. Here's what we saw." That is not a fight. That is a contribution. Say it once, clearly. If the room hears it and still proceeds, note your concern and move with the direction. You have done your job. You have not made an enemy. You have left a record.

8. Display leadership through what you enable, not what you produce

The closer you get to the strategy table, the less the conversation is about your own design output. It is about what you enable across a team, across a function, across the organisation.

This is the hardest shift for designers to make, because we have been trained to measure our contribution in deliverables. Case studies. Screens. Research reports. Those remain relevant. But the designer who holds a permanent seat at the strategy table is also the one who made their team better, who helped a product manager make a more informed decision, who showed a junior designer what it looks like to operate in a room that doesn't speak your language and still be heard.

Leadership is not about being the smartest in the room. It is about making the room smarter. When you can do that consistently, not just deliver well, but elevate the quality of the decisions being made around you, you stop being a contributor to the strategy and start being part of it.

The Honest Version of How This Ends

I told you the story of the fintech organisation. Two years of proof-building, culture-shifting, result-delivering. Getting into the annual plan, the half-year plan, the quarterly. Watching OKRs start to include design's perspective rather than just receive it.

And I told you it still wasn't fully there after two years.

I want to sit with that for a moment, because this is the part that most writing on this topic skips.

Getting a seat at the product strategy table is not a problem you solve once. It is a position you build, earn, lose partially, rebuild, and hold onto through a combination of consistent evidence, sustained relationships, and the kind of political fluency that nobody teaches in a design curriculum.

Some organisations will meet you halfway. Some will resist no matter what you deliver, because the culture around design's role was calcified long before you arrived and will outlast any single person's effort to change it. Knowing which situation you're in, and deciding accordingly whether to keep investing or to take what you've learned somewhere it will compound faster, is itself a strategic decision.

You are not fighting for a seat at someone else's table. You are fighting to change what the table looks like. That is a longer fight. It is also the only one worth having.

Start with one room. One conversation. One piece of evidence that you were not just a designer in that meeting, you were the person who changed the quality of the decision. That is how it begins. One room at a time.

Working on getting into the room, or trying to hold the seat you already have?

At Xperience Wave, we work 1:1 with mid-to-senior designers on exactly this: building the positioning, the language, and the evidence base to operate at the level the title requires. Book a free 45-minute strategy call.

Read Next

If you have the title but not the influence yet: Senior Designer Still Treated Like a Delivery Person
If AI is reshaping what strategy even means for design: AI Isn't Taking Your Job. But This Type of Designer Will.
If you're asking why the salary doesn't reflect the contribution: The Difference Between a ₹12L and ₹30L UX Designer (It's Not Skills)
Explore the programme built for this transition: Xperience Wave Current

Sources & References

- Murad, Co-founder & Head of Design, Xperience Wave