Executives sometimes hear “UX” and picture prettier screens, usability testing or a particularly nice button. Those things can matter, but a UX strategy is more fundamental: a plan for improving the experience in a way that helps customers and the business succeed.
A handsome button is lovely. It is not, on its own, a strategy. Neither is calling the backlog a roadmap and adding a gradient.
For SaaS products, that means connecting research, product direction and delivery decisions to outcomes such as activation, retention, efficiency and sustainable growth. It is not decoration on top of strategy. It is part of strategy.
UX is more than UI polish
Visual quality affects trust and comprehension, but it is only one layer. A strategy should clarify who the product serves, the job they are trying to do, the frictions worth solving and the evidence that will show whether the work helped. In my Prudential PruWorks case study, journey mapping and user testing came before visual design because the team first needed to understand the work actuaries were actually doing.
This is where UX leaders earn their keep: triangulating customer evidence, product data, market realities and business constraints. A beautiful answer to the wrong problem is still the wrong answer—just harder to argue with in a review meeting.
The three parts of a useful UX strategy
Vision: a concise picture of the experience and value you are trying to create.
Goals and measures: outcomes that connect customer needs to business priorities.
Plan: a prioritised set of initiatives, research and delivery decisions that can move those measures.
At ShipServ, I mapped user pain points to strategic objectives so teams could see why each initiative mattered. The ShipServ UX strategy work is a good example of turning a broad ambition into decisions about what to tackle, what to measure and what to leave alone.
Make the business case without magic numbers
There are plenty of dramatic UX ROI statistics in circulation. Some are useful conversation starters; many get repeated long after their original context has vanished. I find it more convincing to build the case from the product in front of us:
What does a failed task cost in support effort, lost time or churn risk?
Where do users abandon an important workflow, and what do interviews reveal about why?
Which operational measure should improve if we remove a known friction?
What is the cost of building the wrong thing versus testing the assumption first?
When a UX strategy can answer those questions, it becomes much easier to discuss investment in the same language as product and finance: risk, opportunity, efficiency and customer value.
What changes in day-to-day delivery
A clear strategy gives teams a filter. It makes roadmaps sharper because people can ask, “Does this move the outcome we agreed?” It makes research more purposeful because the learning questions are explicit. It makes iteration faster because success criteria were not invented after the build.
On Oxford University’s environmental-impact assessment tool, workshops and interviews helped establish which needs and features mattered most before the team moved into solutions. You can see that approach in my Oxford University RIOT case study.
How to prove progress
Start with a baseline. Know the current task success, time, adoption, support demand or retention signal.
Pair quantitative and qualitative evidence. Metrics tell you what changed; research helps explain why.
Share a simple impact narrative. State the customer problem, the intervention, the evidence and what you will do next.
Keep ownership shared. Product outcomes are rarely “owned by design” alone.
A strong UX strategy does not promise that every redesign will transform revenue overnight. It gives a team a disciplined way to make better bets, learn earlier and align around the experience customers actually need. That is much less flashy than a slogan—and considerably more useful.
