There is a specific kind of frustration that shows up in organisations with genuinely good designers. The work is strong. The research is sound. The prototypes are thoughtful. And somehow the product that ships is mediocre, the roadmap is set by whoever argued hardest last quarter, and the same conversation about priorities happens every three months without ever resolving.
That is not a design problem. Adding more design capacity to it makes it worse — more good work, produced faster, arriving at the same wall.
UX strategy is the work of fixing the wall.
What is UX strategy?
UX strategy is the plan connecting user experience to business outcomes: what role UX plays in the organisation, what it's meant to achieve, how decisions get made, and how the work actually reaches users.
Where UX design produces interfaces, UX strategy determines which interfaces are worth producing, who decides, on what evidence, and how the organisation is structured to make that repeatable rather than accidental.
It typically covers four questions:
- Direction. What experience are we trying to create, for whom, and how does it support what the business needs?
- Prioritisation. How do we decide what to work on, and what does that decision rest on?
- Capability. Do we have the people, skills, and processes to deliver it?
- Influence. Does UX work reach decisions early enough to matter, or does it arrive after the decisions are made?
That last question is where most organisations actually struggle, and it's rarely the one they think they have.
The symptoms of a strategy problem
Design problems and strategy problems look similar from inside. Some reliable indicators that you're facing the second kind:
Good work doesn't ship, or ships degraded. Research findings get acknowledged and don't change the roadmap. Designs get approved and arrive in production noticeably different. The bottleneck is organisational, not creative.
The same debates recur. Every quarter the team revisits who the primary user is, or whether to prioritise acquisition or retention. Nothing is settled because nothing was ever decided on a basis that outlasts the meeting.
UX is consulted after the decision. Design gets briefed on what to build rather than participating in deciding what to build. The result is competent execution of choices nobody validated.
No shared definition of success. Different teams optimise for different metrics without noticing they conflict. Marketing wants signups; support wants fewer tickets; product wants engagement. Each is individually reasonable and collectively incoherent.
Research doesn't accumulate. Studies get run, findings get presented, and eighteen months later the same questions get researched again because nothing was retained.
Hiring hasn't helped. More designers produced more output and the same outcomes. That's the clearest signal available that capacity was never the constraint.
UX maturity: where organisations actually sit
Most organisations underestimate the gap between where they are and where they think they are. The Nielsen Norman Group's maturity model provides a useful frame — six stages, from absent to user-driven.
Absent. No UX consideration. Decisions made on assumption and internal preference.
Limited. UX happens occasionally, usually because one person cares. No process, no consistency, no budget line.
Emergent. UX work is real but inconsistent. Dependent on individuals and projects rather than embedded. Research happens when someone insists.
Structured. Processes exist and are followed. UX has a defined role, a budget, and repeatable methods — though influence over strategic decisions is still limited.
Integrated. UX participates in product decisions from the start. Research informs the roadmap. Success is measured in user outcomes, and the measurement is trusted.
User-driven. User experience drives organisational strategy. Rare, and mostly found in organisations where product quality is the primary competitive advantage.
Two things are worth knowing about this progression. First, stages can't be skipped — attempting to install integrated-stage practices in an emergent-stage organisation produces process theatre that collapses under the first deadline. Second, moving up one stage is a meaningful achievement, typically taking twelve to eighteen months. Realistic targets matter more than ambitious ones.
What UX strategy work covers
Experience vision. A specific articulation of what the product should feel like to use and what it should be better at than the alternatives. Specific enough to rule things out — a vision that excludes nothing directs nothing.
Maturity assessment. An honest read of where the organisation currently sits, what's blocking the next step, and what sequence of changes would actually move it.
Decision-making process. How product decisions get made, what evidence they rest on, and where UX enters. Usually the highest-leverage change available, and usually the least discussed.
Team structure and capability. Whether you have the right roles, in the right places, with the right remit. Frequently the answer isn't "hire more" but "position differently" — a strong team reporting into the wrong function will underperform a weaker one positioned correctly.
Metrics and measurement. Defining what good looks like in terms the business recognises, and building the measurement to support it. UX without metrics gets funded on faith, which is a weak position in every budget cycle.
Research operations. How research gets commissioned, conducted, stored, and reused. The difference between an organisation that learns and one that repeatedly re-learns.
Roadmap alignment. Connecting UX priorities to business priorities so they compete less and reinforce more.
Stakeholder alignment. Often the actual work. Not persuasion, but building the shared evidence base that makes the right decision the obvious one.
Engagement models
Strategy work doesn't fit a single shape. Four common ones:
Focused strategy engagement. A defined piece of work over several weeks — maturity assessment, experience vision, process redesign — producing specific recommendations and a sequence for acting on them. Right when there's a clear question to answer.
Fractional UX leadership. Ongoing senior involvement without a full-time hire. Setting direction, mentoring the team, representing UX in leadership conversations, raising the standard of the work. Suits organisations with designers but no design leadership — a common and costly gap.
Advisory retainer. Regular sessions with product leadership: reviewing decisions, stress-testing plans, providing outside perspective. Low commitment, high leverage where the team is capable and needs a sounding board rather than a leader.
Workshops. Concentrated sessions for specific outcomes — alignment on user segments, prioritisation, vision-setting. Effective for breaking a specific deadlock; not a substitute for ongoing capability.
The right model depends on whether you're solving a problem, filling a gap, or building capacity. We'll say which one your situation actually calls for, including when the answer is that you don't need external help.
What independence actually buys
The most valuable thing an external strategist brings usually isn't expertise. Your team likely knows the problems better than an outsider will.
It's the ability to say things internal people can't.
Internal teams are invested — in existing plans, in previous decisions, in relationships with the people who made them. A designer who has argued the same point unsuccessfully for a year cannot make it again without it sounding like grievance. A product lead cannot easily say the current strategy isn't working when they helped set it.
An outside voice has no history in the room. The same observation, made by someone with no stake, lands differently. This is uncomfortable to acknowledge and it is consistently the largest part of the value.
The corollary: an external strategist who only tells you what you want to hear is worthless. The value is entirely in candour, which means the engagement has to be able to survive disagreement.
Common mistakes
Treating strategy as a document. A strategy deck that changes no decisions and alters no process is an expensive artefact. The output is what happens differently afterwards.
Copying another organisation's model. Spotify's squad model, Google's design sprints, Amazon's working-backwards — all developed in specific contexts with specific constraints. Imported wholesale, they usually fail for reasons that have nothing to do with their merit.
Skipping maturity stages. Installing advanced practices in an organisation that lacks the foundation produces ceremony without substance, and discredits the underlying idea for years afterwards.
Strategy without leadership buy-in. UX strategy changes how decisions get made, which is inherently a leadership question. Without support at that level, the recommendations don't have anywhere to land.
Hiring instead of restructuring. Adding people to a team that lacks influence produces more work with the same impact — at higher cost.
No measurement. Strategy work is hard to evaluate, which is precisely why defining success upfront matters. Without it, the engagement gets judged on whether people enjoyed the workshops.
How we approach strategy work
We start with an honest assessment. Where the organisation actually sits, what's genuinely blocking progress, and what's realistically achievable in the next twelve months. That assessment is frequently uncomfortable, and it's the part that makes everything after it useful.
We work on decisions, not documents. The measure of strategy work is what gets decided differently afterwards. Deliverables exist to support that, not to substitute for it.
We're specific about sequence. Organisations can't change everything simultaneously. What comes first, what depends on what, and what to deliberately defer matters more than the completeness of the recommendation.
We'll tell you when you don't need us. Sometimes the problem is capacity, not strategy, and the honest answer is to hire rather than consult. Sometimes the team already knows what to do and needs support to say it. Saying so costs an engagement and is the right call.
The work draws on thirteen years across agencies, startups, and corporate teams — including organisations like Netia, Microsoft, ERGO, and ASUS — and formal certification from the Nielsen Norman Group, the institution that shaped modern UX practice, across UX leadership, information architecture, journey mapping, usability testing, and analytics.
Working across many organisational contexts is itself the relevant qualification here. Strategy advice from someone who has only seen one company work is one company's strategy, generalised.
Every engagement is run personally. No account layer between you and the person doing the work.
Frequently asked questions
What's the difference between UX strategy and product strategy?
They overlap substantially. Product strategy addresses what to build and why, in market and business terms. UX strategy addresses the experience that product should deliver and the organisational capability to deliver it. In practice they should be developed together; where they're separated, the seam is usually where problems appear.
Do we need UX strategy if we already have a UX team?
Often that's exactly when it's needed. A capable team producing good work that doesn't influence decisions is the most common strategy problem there is — and it's invisible from inside, because the work itself is fine.
How long does a strategy engagement take?
A focused engagement — maturity assessment, vision, process recommendations — typically runs four to eight weeks. Fractional leadership and advisory work are ongoing by nature, usually reviewed quarterly. Meaningful organisational change takes considerably longer than the engagement that initiates it.
What does fractional UX leadership involve?
Senior UX direction without a full-time hire: setting standards, mentoring designers, representing UX in leadership discussions, and making the judgment calls a team without design leadership otherwise makes by default. Typically a defined time commitment per week or month.
How do we measure whether it worked?
By defining success criteria at the start — which decisions should be made differently, which processes should change, which metrics should move. It's harder to measure than a redesign, which is exactly why it needs to be specified rather than assumed.
What if leadership doesn't support the recommendations?
Then the engagement has surfaced the real constraint, which is useful information even when it's unwelcome. UX strategy changes how decisions get made; without leadership support, recommendations have nowhere to land. That's worth knowing early rather than discovering after six months of effort.
Can you work alongside our existing design leadership?
Yes, and it's often the most productive arrangement. An external perspective supports internal leadership rather than replacing it — particularly on the arguments internal leaders have already made and need reinforced from outside.
Where to start
A useful diagnostic: think of the last significant product decision your organisation made. Was UX involved in making it, or in executing it?
If the honest answer is the second, that's the gap — and no amount of additional design capacity will close it.