Most people who come to me want a new website or application. Or change an existing one.
They think their problem is visual. It almost never is.
The question "what's the difference between UX design and UX strategy?" sounds like a technical one. Designers will give you a Venn diagram. Agencies will send you a PDF. But the honest answer is simpler and harder at the same time.
One builds things. The other decides what's worth building and why.
The Question Nobody Asks Before They Start
A client came to me not long ago — a company called Crimson Atlas. They needed a new website, not on WordPress. That was the brief. But in the first conversation, it became clear the website wasn't the problem.
They couldn't tell me clearly what they sold. They couldn't explain why a client would choose them over a competitor. They had years of experience and genuine expertise, but none of it was articulated in a way that worked for someone who didn't already know them.
That's not a design problem. That's a strategy problem.
We never opened a design tool in those early weeks. We worked on language. On positioning. On the gap between what they believed they offered and what their clients actually needed to hear. By the time we got to the website, every decision had a reason behind it. The client's own words back to me later: "We didn't just get a website. We got language."
That's the difference.
What UX Design Actually Is
UX design is the execution layer. It's the work that turns decisions into something real — screens, flows, interactions, page structures. A good UX designer asks: how does this work? How does a user move from point A to point B without friction? What does this button say, and where does it live?
This work matters. It matters a lot. But it only works when the decisions upstream are correct.
Most clients confuse UX design with UI design — the visual layer they see in the browser. That confusion is understandable. What you see is what you remember. But UX design includes the research, the architecture, the logic of how an experience holds together. The visual design is a byproduct of decisions made earlier.
And even UX design, done well, is still execution. It's still downstream of strategy.
What UX Strategy Actually Is
UX Strategy is the work before the work.
It answers the questions that design cannot answer on its own. Who is this for, exactly? Why would they choose you over someone else? What do you need them to understand in the first ten seconds? What does success actually look like, and how will you measure it?
That last one is the question I ask every client who tells me they already know their business. And they do — they know it from the inside. But when I ask "how will you know if the new site is working?" most of them go quiet.
That silence is where strategy lives.
In every project, I run a UX Strategy Mapping exercise with my clients. We work through five things together: who their competition is, why a client would buy from them and not a competitor, where their efforts should go to close the gap between where they are and where they want to be, what specific activities will get them there, and how we will measure progress. This isn't a workshop you do and file away. It becomes the blueprint that guides every design decision that follows. You can see how I structure this work in my UX Strategy and Product Design services.
Without it, you're guessing. And guessing is expensive.
What Happens When You Skip Strategy
I've seen this pattern more times than I can count. A founder or a team decides they know what they need. They want to move fast, keep the budget low, get something live. They skip the strategic work. They hire someone to execute.
Six months later, the site doesn't perform. The messaging doesn't convert. The team isn't happy with it. So they go back to market. Another designer. Another brief. Another round.
I've had clients come back to me after going through four different designers, having spent money four separate times, still without a result they believed in. And every time, the conversation starts the same way: "You told us from the beginning."
The real price of skipping strategy isn't the cost of one bad design. It's the cost of doing it four times. It's two years of slow or no results. It's hundreds of hours of work invested in the wrong direction. A budget-friendly fast lane to market that leads nowhere is not actually fast.
I don't work with clients who refuse to look at strategy. Not because I'm difficult, but because I can't guarantee results without it. I don't patch existing solutions. I build solutions that work.
So Which One Do You Need?
Here's what I tell every client who asks me this question: stop thinking about whether you need UX design or UX strategy. That's the wrong frame.
Ask yourself whether you have clarity.
Clarity means you know what you sell and can say it in one sentence. It means you know who your client is and why they choose you. It means every decision — visual, structural, textual — has a reason behind it that connects back to your business goals. It means you're not building something because it looks good to you, but because it serves the people you're trying to reach.
What you prefer visually and what your clients need to see are often two different things. Strategy closes that gap. Design makes it visible.
If you have clarity, you're ready to design. If you don't, design will only make your confusion more expensive.
Clarity is the alibi you reach for when you don't know what to choose. When you have it, design becomes straightforward. When you don't, no amount of good design will save you.
What This Means in Practice
The work I do with clients starts with clarity — always. The design, the language, the structure of pages, the tone, the calls to action — all of it flows from the strategic work we do together at the start.
That's not how most agencies operate. Most agencies take a brief, build to the brief, and hand you screens. If the brief was wrong, the screens will be wrong. And most briefs are wrong, not because clients don't care, but because they haven't had the right conversations yet.
The right conversations are hard. They require asking questions you've been avoiding. They require choosing who you're for and accepting that means you're not for everyone. They require measuring what you're doing instead of guessing that it's working.
That's what UX strategy is. Not a fancy term. Not a premium line item on an invoice. It's the difference between building something that works and building something that looks like it should work.
If you're building a website, a product, or a service experience and you're not sure whether you need design or strategy — start here. Let's find out where your clarity breaks down before we build anything.