UX Strategy: How Teams Stop Building the Wrong Thing
You’ve probably watched this happen. A team ships exactly what was asked for, on time, and it still misses. Not because the design was bad. Because no one agreed on what good meant before the work started.
That’s the problem UX strategy solves.
I’m Jay Sethi. I’ve spent close to two decades doing UX strategy, research, and design across medtech, fintech, and ecommerce. Here is how I explain it to teams, without the jargon.
What UX strategy actually is
UX strategy is a plan that says where the experience is headed, and why. It connects three things that usually live in separate decks: what users need, what the business needs, and what technology can actually do.
When it’s working, everyone building the thing can answer the same questions the same way:
- What’s the value to the user, in plain language?
- How does this map to where the business is going?
- Why are we building this now, from a business perspective?
- How will we know if it worked?
- How does this hold up across channels and touchpoints?
- What matters most, and what can wait?
- What’s the rough timing?
If your team gives five different answers to those, you don’t have a design problem yet. You have a strategy problem. And no amount of wireframes will fix it.
Why you need it
Here’s the mechanism. Distributed teams make hundreds of small decisions a week. Without a shared direction, each decision is a guess. The guesses compound. You end up with an experience that feels stitched together, because it was.
A clear strategy does three things. It makes the vision accessible to everyone doing the work, not just the people who were in the kickoff meeting. It gives executives something concrete to react to and align with, which is how UX work actually gets funded. And it ties design decisions to business outcomes, so “is this good design?” becomes “did this move the number we agreed on?”
In my experience, teams with a written strategy don’t just build better things, they waste less. Less rework, fewer late stage pivots, fewer meetings re-litigating decisions that should have been settled in week one.
One caveat. This matters most when more than a handful of people are touching the experience. If it’s you and a founder in a room, you can hold the strategy in your head. Past twenty people, write it down.
How to actually practice it
Forget the textbook version. Here is the sequence that works in the real world.
1. Set strategy goals tied to business goals
Not “improve UX.” Something like “cut support calls about onboarding by 30% this year.” If you can’t tie it to a business outcome, it’s not a strategy goal. It’s a wish.
2. Validate with people, not assumptions
Talk to stakeholders. Talk to customers. Read the voice of customer data you already have. Add competitive analysis or clickstream review only if the interviews leave a gap. Most teams skip this and pay for it later. The mistake I see most is treating stakeholder opinions as validated goals. They’re a starting point, not evidence.
3. Synthesize into a concept, then test the concept
Take what you learned and sketch where the experience should go. Rough, conceptual, not polished. Then put it in front of stakeholders and customers. You’re checking one thing: are we aimed at the right future? Polishing the wrong direction is the most expensive mistake in UX.
4. Turn it into a roadmap with milestones
Map the goals to milestones over time. Expect to revise it. A roadmap that never changes was either perfect or ignored. Usually it’s the second one.
5. Get honest about people and cost
What skills do you need, what do you have, and what’s the rough price of the gap? High level estimates are fine here. The point isn’t precision. It’s surfacing the resourcing conversation before you’re mid build and short a researcher.
The part nobody talks about
A UX strategy document that sits in a drive folder is theater. The test is simple. Can a designer, three months in, make a tradeoff decision using the strategy without booking a meeting? If yes, it worked. If no, it was a deck.
So here’s my opinion, plainly. Most teams don’t need a longer strategy process. They need a shorter one they actually use.
Where’s this breaking down on your team right now: the goals, the validation, or the part where the strategy meets the roadmap? Tell me in the comments. I read every one.
And if you’re leading a team that’s building without that shared direction, this is the work I do with product and UX teams. Getting the strategy sharp enough that the design decisions get easy. I take on a small number of these at a time. You know where to find me.
Jay Sethi, UX Strategist, Researcher and Designer