What it is
A prioritization technique (borrowed from London’s no-stopping “red routes”) that identifies the critical tasks many users perform frequently and importantly, so design effort concentrates where it matters most.
When to use it
During Synthesize, when deciding which tasks deserve the most design and optimization attention.
Why (value)
Prevents spreading effort thinly across every feature by focusing on the tasks that carry the most user value and volume.
How to run it
- List the tasks users perform with the product.
- Score each by frequency and importance across user groups.
- Identify the high-frequency, high-importance “red routes.”
- Ensure those tasks are frictionless and protected in design.
- Deprioritize rare, low-importance tasks.
Inputs and outputs
- Inputs: Task inventory, usage data or estimates, importance judgments.
- Outputs: A prioritized set of critical “red route” tasks.
Time and effort
Low. A focused analysis session.
Evidence and limitations
Strongest when frequency and importance draw on real usage data; estimates make it a prioritization hypothesis rather than measured fact. See Evidence and limitations.
Tips and pitfalls
- Use real usage data for frequency where possible.
- Weight importance, not just raw volume.
- Protect red routes from feature-driven clutter.
Variations
Task frequency-importance grids, critical-task analysis.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Task analysis — Break a goal into the concrete steps, sub-tasks, and decisions people perform to accomplish it.
- Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
- Severity ratings — Rate usability problems by impact so teams fix the most damaging issues first.
