Module 6 of 12 · 8 min read
UX Strategy & Vision
How to turn a diagnosis of your UX practice into a strategy kernel, a vision people remember, opinionated principles, OKRs and a roadmap.
Why it matters
Sooner or later, someone will ask you for "the UX vision" or "the UX strategy". Many new leads answer with a list of goals ("be world-class", "improve consistency") or a list of everything the team does. That is not strategy. This module helps you build a real one: a diagnosis of the critical challenge, a guiding policy, coherent actions, and a way to communicate them that people remember.
Common pitfalls: writing the vision alone and presenting it as finished; writing principles nobody could disagree with; and promising outcomes without the capacity to deliver them.
1. Vocabulary: vision ≠ strategy ≠ roadmap
The examples below use a fictional setting: an internal operations platform with several product teams, including a booking tool used by expert operators.
| Concept | Answers | Horizon | Example (fictional internal operations platform) |
|---|---|---|---|
| Vision | Where are we going and why? | 2–5 years | "Every operator can complete their daily work in our internal tools quickly, confidently and with few errors, through consistent, evidence-based experiences." |
| Principles | How do we decide? | Stable | "Efficiency for experts over first-time delight" |
| Strategy | What will we focus on, and what won't we? | 1–2 years | "Consolidate a shared foundation (design system + patterns) before scaling research" |
| Objectives / OKRs | What outcome by when? | Quarter–year | "Reduce task time for the top 5 booking-tool tasks by 15%" |
| Roadmap | In what order? | Quarters | Q1 maturity baseline, Q2 critique rituals, … |
2. Good strategy (Richard Rumelt, Good Strategy / Bad Strategy)
A strategy has a kernel of three parts:
- Diagnosis. What's the critical challenge?
- Guiding policy. The overall approach to deal with it.
- Coherent actions. Concrete steps that reinforce each other.
Bad strategy = fluff, goals posing as strategy ("be world-class"), or a list of everything.
A worked example: four pillars as a strategy kernel
Below is one example of a four-pillar model for a UX practice. It is not a template to copy. Use it to see what a kernel looks like, then derive your own pillars from your own diagnosis, ideally after a listening tour of your first 30 days (see 30-60-90 plan). Your organisation may need three pillars, or five, or completely different ones.
Diagnosis (hypothesis):
UX in the internal applications grew domain by domain. Designers are isolated (often one per domain), practices and components drift, UX demand is invisible so it's allocated by urgency, and decisions rely mostly on opinion because usage data isn't systematic and is constrained by data protection.
Guiding policy:
Build one connected UX practice that shares a common foundation and evidence, while leaving product decisions close to the domains.
Coherent actions (= the pillars):
| Pillar | Actions |
|---|---|
| 1. Consistent practice | Shared principles, design-system governance, common process "minimum standard" |
| 2. Growth & learning | Cross-domain critique, mentoring pairs, career ladder, knowledge base |
| 3. Transparent capacity | Intake process, capacity map, prioritisation criteria agreed with stakeholders |
| 4. Evidence-driven UX | Maturity baseline, GDPR-safe metrics, lightweight benchmark of top tasks |
Notice how they reinforce each other: shared standards make cross-domain critique possible; capacity transparency frees time for research; evidence feeds the standards. That reinforcement is what makes it a strategy and not a list.
See the full worked example (what good looks like, signals and first moves for each pillar) and build your own in Design your UX practice.
Derive your own:
- Write your diagnosis in 3–4 sentences. Mark each claim as evidence or assumption.
- Write a guiding policy in one sentence: the approach, and what it rules out.
- Group your planned actions into 3–5 themes. Each theme becomes a pillar.
- Check coherence: for each pillar, name one way it helps another. If a pillar helps nothing else, question it.
3. Writing a UX vision that sticks
Vision statement formula
For [users] who [need/context], our internal applications will [experience outcome], so that [business outcome]. Unlike today, where [current pain], we will [key shift].
Make it concrete
- Vision artefact: a short narrative + 2–3 "future state" scenarios ("A customs clerk on a Monday morning, three years from now…"). A North-Star prototype or storyboard is even stronger.
- Test it: can a product manager repeat it after one hearing? Does it help decide something?
Co-create it
A vision imposed by the lead gets compliance. A vision co-created gets commitment.
- Interviews with designers and key stakeholders (days 1–30, see Stakeholder interview).
- Workshop: "What should be true about UX here in three years?" (affinity mapping)
- Draft → feedback rounds → v1.
- Revisit yearly.
4. Design principles
Good principles are opinionated and help choose between two good options. "Make it simple" is not a principle; anyone would agree.
Test: could a reasonable team adopt the opposite principle? If not, it's too generic.
Example principles for internal operational apps:
| Principle | Opposite (also valid elsewhere) |
|---|---|
| Speed for experts over guidance for novices. Keyboard, density, bulk actions. | Guided onboarding first |
| Show the exception, not the rule. Surface what needs attention. | Show everything, let the user filter |
| Consistent across tools, specific within domains | Each domain optimises locally |
| Prevent errors before reporting them | Validate on submit |
| Measure what we change | Ship and move on |
5. Connecting UX to the business
Internal apps don't sell; they save. Speak in operational outcomes:
- Time: task completion time × users × frequency = hours saved (→ cost).
- Errors: wrong data entry → rework, claims, compliance risk.
- Training/onboarding: time to proficiency for new staff.
- Support: tickets / help-desk load.
- Adoption: shadow tools (Excel workarounds) replaced.
- Employee experience: satisfaction, retention in operations roles.
Simple value model (use in a stakeholder meeting):
Task: create a booking in the (fictional) booking tool
Users: 1,200 Frequency: 15/day Time saved: 20s
→ 1,200 × 15 × 20s = 100 hours/day ≈ 22,000 hours/year
(The numbers above are illustrative. Use real numbers from your organisation, and never invent them in front of stakeholders. If you don't have them yet, show the method and say which numbers you need.)
6. UX roadmaps & OKRs
UX roadmap (NN/g style)
Organise by themes/problems, not features; use horizons (Now / Next / Later) rather than fixed dates; include confidence levels.
| Now (this quarter) | Next (1–2 quarters) | Later (3+) |
|---|---|---|
| Maturity baseline & listening tour | Cross-domain pattern library v2 | UX benchmark programme |
| Cross-domain critique ritual | Intake & capacity board | Career ladder & mentoring |
| Analytics event taxonomy (pilot in one app) | Roll out analytics to 2 more apps |
OKR example
Objective: Make UX demand and capacity visible across internal applications.
- KR1: 100% of UX requests from 5 domains go through one intake by end of Q2.
- KR2: Capacity map reviewed monthly with domain leads (≥ 4 of 5 attending).
- KR3: Designer-reported "workload sustainable" score ≥ 3.5/5.
Practice
Evidence to collect
Keep proof in your leadership log:
- Vision one-pager and roadmap.
- Any decision where you tied UX to a business metric.
Read / watch
Library → Strategy & vision: Rumelt's Good Strategy / Bad Strategy, NN/g's UX Strategy and UX Roadmaps, Jared Spool on UX strategy, Mapping Experiences (Kalbach).
Talking about it
- With your manager: present the kernel, not the slide deck. "Here's what I think the critical challenge is, here's the approach, and here are three actions that reinforce each other. What am I missing?" Asking for challenge early turns your manager into a co-author.
- With product managers and stakeholders: lead with the business outcome (time, errors, onboarding, support) and the value model method. Keep design vocabulary for your team.
- With senior management: one sentence of vision, one sentence of diagnosis, one ask. See Module 10: Stakeholders, Influence & Change.
- In a promotion or hiring conversation: be honest about what is diagnosis and what is assumption. "My hypothesis is X; I'd confirm it in the first 30 days by Y" sounds more senior than a confident plan built on guesses.
Check yourself
Answer out loud, then open the section to compare.
- What are the three parts of a strategy kernel? → answer
- How do vision, strategy and roadmap differ? → answer
- Write one UX OKR for a tool in your scope. → answer
- How would you derive your own pillars instead of copying someone else's? → answer
Connections
← Module 5: Enterprise & Internal Applications · UX Lead Course · Module 7: DesignOps, Team Models & Capacity →
Related
- 11 — Workshop techniques: co-create the vision in a workshop (UX Vision Co-creation)
- Module 9: UX Maturity & Measurement: metrics behind the OKRs
- Module 10: Stakeholders, Influence & Change: communicating the vision to management
- Module 7: DesignOps, Team Models & Capacity: roadmap must match capacity
- Module 5: Enterprise & Internal Applications: employee experience as business value