UX thinking
The ability to design human experience: understand the journey, reduce cognitive load, test solutions with users and improve interfaces and processes.
Definition
BT360 v2.0.0The ability to design human experience: understand the journey, reduce cognitive load, test solutions with users and improve interfaces and processes.
What is it made up of?
3 INDICATORS- 01Understanding the user and their journey
- 02Reducing complexity and cognitive load
- 03Testing solutions with users
Behavior levels 0–5
MANAGER'S GOAL - 3| Lv. | Label | Descriptor |
|---|---|---|
| 0 | Absent | Designs for themselves; does not think about the user journey; does not notice complexity; there are no tests; people make mistakes and give up. |
| 1 | Poorly developed | Considers obvious needs; the interface or process is overloaded; validates only against colleagues' opinions; problems surface after launch. |
| 2 | Underdeveloped | Builds a simple journey; notices obvious barriers; runs isolated checks; does not test complex scenarios; improvements are isolated. |
| 3 | Normally developed leader's goal | Understands the user and the journey; reduces the load; tests the prototype with users; improves based on the results; accounts for edge cases. |
| 4 | Highly developed | Designs the experience as a system; finds non-obvious barriers; uses research and metrics; teaches the team; connects UX to business value. |
| 5 | Overdeveloped | UX turns into perfectionism: endless research and iterations, launch is postponed; beauty matters more than usefulness; the team cannot keep up. |
How is it measured?
coating BSJT - BT360 situational test: provides a hypothesis about judgments in work situations and does not replace observation, 360 and interviews.
TEIQue is indirectly related to empathy, but does not measure UX skill. The level is confirmed by practical testing and improvement.
Development Actions
5 CATEGORIESPractical task: run a UX review of a process or interface and propose improvements.
Course 'UX thinking': journey, barriers, prototypes, tests, accessibility.
Run five user tests and improve two barriers.
Review with a designer or researcher: where you designed for yourself.
Introduce the rule in the team to test a solution with users before launch.