Framework · Strategy & vision · 3 min read
UX value model
A simple calculation that expresses internal-tool UX in operational terms (time saved × users × frequency, plus errors, training and support load), so stakeholders see what a design change is worth.
Seconds saved per task, from a test or benchmark. Be conservative.
e.g. 20 secondsHow many people do the task. Use your organisation's real number.
e.g. 1,200 usersHow often each user does it per day.
e.g. 15 times a dayErrors, training time, support tickets, workarounds replaced, employee experience.
e.g. fewer rework casesHours saved = Time saved × Users × Frequency (+ errors, training, support)
Use it when
- A stakeholder asks "why invest in UX for an internal tool? Users have no choice."
- You need to compare two UX improvements and want a business reason to pick one.
- You present a UX strategy or roadmap and want one concrete number tied to a business outcome.
How to use it
- Pick one frequent task. Choose a task many users do many times a day, such as creating a booking. Frequency is what turns small savings into big numbers. Output: one task name.
- Collect the real numbers. Find the number of users, how often each does the task, and how long it takes today. Ask analytics, operations managers or support. Where you have no data, say which number you still need. Output: users, frequency and current time, each with its source.
- Estimate the saving conservatively. Use a time saving you can defend from a test or a benchmark, and round down. Output: one time-saved figure with its evidence.
- Do the calculation. Multiply time saved × users × frequency to get hours per day, then per year. Convert to cost only if you have the real loaded cost of employee time. Output: hours saved per day and per year.
- Add the other value drivers. Note errors (rework, claims, compliance risk), training time to proficiency, support tickets, Excel workarounds replaced, and employee experience. Keep them as words if you have no numbers. Output: a short list of further benefits.
- Present the method. Show the formula, every number and its source, and say what you would measure after the change. Output: one slide or paragraph for a stakeholder meeting.
Worked example
The value model from the module, for a fictional booking tool. The numbers are illustrative.
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
| Value driver | What the lead added |
|---|---|
| Time | 100 hours per day, from the calculation above. |
| Errors | Fewer wrong entries in the booking form means less rework. No number yet; the lead asked support for data. |
| Training | New staff learn one form instead of two screens. Time to proficiency to be measured. |
| Support | Tickets tagged "booking form" as a baseline for after the change. |
In the meeting, the lead showed the formula first and said which numbers came from analytics and which still needed confirming.
Watch out for
- Invented numbers. Never make up users, frequency or time saved in front of stakeholders. If you don't have them, show the method and ask for the data.
- Optimistic savings. A big time-saved figure invites challenge. Be conservative and say where it comes from.
- Only the result. "22,000 hours" with no method looks like marketing. Show each number and its source.
- Time as the only value. Errors, training, support load and workarounds often matter more to operations leaders. Name them too.
Template
Copy this into your notes or a slide.
Task:
Users: Source:
Frequency (per user/day): Source:
Time today: Source:
Time saved (conservative):Evidence:
Hours/day = users × frequency × time saved ÷ 3600 =
Hours/year = hours/day × working days =
Other value
Errors:
Training / time to proficiency:
Support tickets:
Workarounds replaced:
Employee experience:
Numbers still needed:
What we will measure after the change: