Marcus Andrey Study
Ler em português Library

Framework · Strategy & vision · 3 min read

UX vision statement

A short, repeatable statement of where UX is going and why, made concrete with 2–3 future-state scenarios and co-created with the people who must believe it.

1Users

Who the vision is for, and their need or context.

e.g. operators in daily work
2Outcome

The experience our internal applications will give them.

e.g. quick, confident, few errors
3Business

What the organisation gains when that is true.

e.g. less rework and support
4Pain today

What is wrong now, in words users would recognise.

e.g. every tool works differently
5Key shift

The change you will make to get there.

e.g. consistent, evidence-based experiences
6Scenarios

Two or three short future-state stories that make it concrete.

e.g. a clerk, three years from now

For [users] who [context], our tools will [outcome], so that [business outcome]

The parts of a UX vision statement, made concrete with future-state scenarios.

Use it when

  • Someone asks you for "the UX vision" and you only have a list of goals.
  • Teams work hard but in different directions, and you need one picture of where you are going.
  • You have a strategy kernel and need a short, memorable way to communicate the direction.

How to use it

  1. Listen first. Interview designers and key stakeholders in your first 30 days (see Stakeholder interview). Collect what they want to be true and what hurts today. Output: interview notes and recurring themes.
  2. Run a co-creation workshop. Ask the group: "What should be true about UX here in three years?" Cluster the answers with affinity mapping. Output: 3–5 themes the group agrees on.
  3. Draft with the 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]. Output: a draft vision statement.
  4. Make it concrete with scenarios. Write 2–3 short "future state" scenarios ("A customs clerk on a Monday morning, three years from now…"). A North-Star prototype or storyboard is even stronger. Output: a one-page vision narrative with scenarios.
  5. Test and refine. Read it to a product manager and ask them to repeat it. Try it on a real decision. Run feedback rounds until you reach v1. Output: vision v1.
  6. Revisit it yearly. Check whether the vision still fits the business and the evidence, and update it with the group. Output: a yearly review date in the calendar.

Worked example

The vision from the module, for a fictional internal operations platform.

Formula part Filled in
For [users] Operators
who [need/context] do their daily work in our internal tools, many times a day
our internal applications will [experience outcome] let them complete that work quickly, confidently and with few errors
so that [business outcome] operations run with less rework, training and support load
Unlike today, where [current pain] every tool works differently and decisions rely on opinion
we will [key shift] offer consistent, evidence-based experiences

Short version used in meetings: "Every operator can complete their daily work in our internal tools quickly, confidently and with few errors, through consistent, evidence-based experiences."

Scenario: "A booking operator starts her Monday three years from now. The tool shows only the orders that need her attention, the same filter works in every app she uses, and she corrects a customs code in one step."

Watch out for

  • Written alone, presented as finished. People don't commit to a vision they had no part in. Co-create it, even if it takes longer.
  • Too vague to decide anything. "World-class experiences" can't help a team choose. Name users, the outcome and the shift.
  • Only words. A statement without scenarios stays abstract. Show a day in the life of a real user role.
  • Never revisited. Context changes. Review the vision yearly with the people who use it.

Template

Copy this to draft your vision.

For [users]
who [need / context],
our internal applications will [experience outcome],
so that [business outcome].
Unlike today, where [current pain],
we will [key shift].

Short version (one sentence):

Future-state scenario 1 (role, moment, three years from now):
Future-state scenario 2:

Test: Can a PM repeat it after one hearing?  Yes / No
      Did it help decide something? Which decision?
Next review:
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close