A Three-Part Framework for UX Strategy That Actually Gets Used
UX teams often end up executing someone else's vision. Stakeholders who don't understand the full scope of UX assign tactical work — wireframes, tests, interface tweaks — while the strategic decisions happen elsewhere. A UX strategy framework flips that dynamic, giving the team a way to identify opportunities, educate decision-makers, and build credibility through measurable outcomes.
The approach here borrows from the book Strategy and the Fat Smoker, which breaks strategy into three parts: a diagnosis of the current state, guiding policies for decision-making, and an action plan for delivery.
Diagnosis: Assess Where You Are
A strategy needs a starting point. The diagnosis phase answers where the organization stands and where UX can have the most impact.
Name What Isn't Working
Begin by listing failures. The organization may lack a UX team, fund it poorly, or see slipping satisfaction scores. Frame issues in business language: a slow sign-up flow might cost 20 percent of registrations monthly, or complicated navigation could hurt retention. Tying each failure to a business metric gives the case for change weight.
Map the Desired Experience
Create two simple journey maps: one for the current experience, another for an ideal path. Highlight stages like discovery, sign-up, onboarding, and support, then ask how the improved journey serves business goals — faster onboarding may cut support costs; a streamlined checkout could lift order value.
A real example comes from the Samaritans, a UK mental health charity. Their telephone support worked well, but email, text, and social media channels were neglected because volunteers struggled to manage multiple systems. An aspirational map showed a unified interface where all communications could be handled in one place — a target state that improved things for both users seeking help and volunteers.
Audit Resources and Influence
Inventory the UX team's skills and any budget for tools or software. Identify where the team already has influence — perhaps with product or marketing groups — and which policy owners, process leads, or executives need to be brought on board. Knowing allies and gaps early makes the strategy realistic.
Accept Constraints
List technical, budget, or policy limitations such as a headcount freeze or rigid IT systems. Accepting them as givens forces creativity and builds credibility — the strategy promises value within boundaries, not impossible changes.
Guiding Policies: Set the Course
Policies act as guardrails for deciding what to chase and what to decline.
Pick a Tactical or Strategic Model
- Tactical: UX people embed on projects and run tests and designs directly. This requires a larger team — roughly one UX professional for every two developers.
- Strategic: Act as a center of excellence, advising other teams through guidelines, workshops, and tools. This needs fewer hands but broader influence.
The right choice depends on resources and goals. Moving fast on many projects favors tactical; shifting mindsets argues for strategic.
Define a Prioritization Method
A digital triage scores requests on impact, effort, and risk, enabling the team to tackle higher-scoring work first. A repeatable, fair process makes saying yes or no easier.
Build a Playbook
A playbook stores design principles, standard operating procedures, and templates. It might include a UI design system, accessibility or research standards, writing guides, and interview templates. As a shared reference, it lets others repeat the team's process and preserves know-how as the team grows.
Plan Communication
A RACI chart clarifies who is Responsible, Accountable, Consulted, and Informed. From there, decide update frequency, channels (email, Slack, demos), and who leads each conversation. Regular communication surfaces concerns early.
The Action Plan: Execute and Adapt
Actions turn policy into delivery through concrete projects, support, and risk management.
Scope Deliverable Projects
Run a discovery phase for a new product, build a design system for marketing, or conduct user testing on a main flow. For each project, record what will be delivered and when. Prioritize with triage scores and keep scopes small enough to finish in a few sprints, proving value quickly.
Provide Training and Tools
A strategic approach requires enabling others. Plan workshops, record testing-orientation videos, and create reference guides along with a curated tool list — prototyping apps, research platforms, analytics dashboards — all easily accessible in the playbook.
Secure an Executive Sponsor
A senior sponsor can remove roadblocks; specify what they need to do, such as championing a budget line or approving hires. Also assign collaborators on the product side for scoping features and on IT for research tooling. Clear roles prevent drift.
Identify Risks Early
List major risks and mitigations: a hiring freeze stalls tactical hires, stakeholder interest wanes, or technical debt slows releases. Solutions might include shifting entirely to a strategic approach or sending a weekly one-page update to sponsors. A fallback plan keeps the strategy viable when circumstances change.
Sustaining UX Within the Organization
A strategy only works when it becomes part of the culture. Sustained visibility and ritual make that happen:
- Build awareness: Run lunch-and-learn sessions, host an annual UX day, and create a monthly salon for sharing challenges and wins.
- Make UX tangible: Put personas and journey maps in offices, print design principles on everyday items, and share success metrics company-wide.
- Embed into processes: Establish UX policies and review outdated procedures, and create friendly competition between teams using UX metrics.
Embedding UX takes time, but visible and repeated efforts shift mindsets beyond the UX team itself.
The gap between documenting a strategy and following it is where most efforts fail — the title Strategy and the Fat Smoker makes the point. As Winston Churchill said:
“Success is going from failure to failure with no loss of enthusiasm.”
Persistence through setbacks, not the strategy document itself, determines whether the organization realizes the business value.
