Route Recovery Pattern¶
Workflow — instantiates Predictive-Cue Wayfinding Design
A defined procedure an agent follows after a wrong turn — backtrack, regain context, compare alternatives, and report the bad scent — turning a dead end into a recoverable step.
When a cue misleads and an agent lands somewhere wrong, what happens next decides whether they recover or abandon. The Route Recovery Pattern is the procedure for that moment: a defined sequence — detect the wrong turn, backtrack to the last good point, restore enough context to re-choose, present the alternative routes, and capture a report of the bad scent that caused the detour. The defining idea is that recovery is an invoked workflow triggered by a realized error, not an always-on layer: it activates when the agent is already off-track and walks them back to a productive choice. It is the sequence of steps, not the standing signage those steps lean on.
Example¶
A caller reaches a bank's voice phone system to dispute a charge. From the top menu they choose "Account services" — a reasonable-sounding cue — and find themselves three levels deep in balance-and-statement options with no dispute path. The recovery pattern kicks in the moment they press the "go back" key. First it backtracks one level rather than dumping them at the root, so they do not lose all progress. Then it restores context: "You were in Account Services. To dispute a charge, most callers need Card Services instead." It presents alternatives: "Say 'disputes,' 'fraud,' or 'go to main menu.'" And when the caller reaches the right place, it quietly logs the misroute — "Account services → attempted dispute" — as a false-scent report the design team can mine.
The wrong turn that used to end in a frustrated hang-up now ends in a resolved dispute, and the system has captured evidence that "Account services" is emitting scent it should not. The recovery workflow did not prevent the wrong turn; it made the wrong turn survivable and informative.
How it works¶
The distinguishing element is the ordered, error-triggered sequence:
- Detect and re-enter. Recovery begins when a wrong turn is signaled (an explicit "back," a bounce, a "this isn't it") rather than running continuously.
- Backtrack to a good point. It returns the agent to the last place their choice was sound — not all the way to the start — preserving progress.
- Restore context and re-orient. It re-states where the agent is and why the previous choice failed, so the next choice is better-informed.
- Offer alternatives. It surfaces the sibling routes the agent should have among, converting a dead end into a live decision.
- Capture the report. It records the false-scent encounter so the misleading cue can be fixed at the source.
Tuning parameters¶
- Backtrack granularity — one step back versus a jump to the start. Fine steps preserve progress but can trap an agent near the bad cue; a full reset is clean but costly.
- Context-restoration richness — a terse "you are here" versus a full re-explanation. More context aids recovery but slows the fast re-router.
- Alternatives offered — how many sibling routes to present. Too few strands the agent; too many recreates the original overload.
- Report friction — how easy it is for the agent to flag bad scent. Frictionless capture yields more signal; any friction and most agents skip it.
- Trigger mode — automatic (the system infers a wrong turn) versus manual (the agent asks). Automatic recovery helps the passive but risks intervening when nothing is wrong.
When it helps, and when it misleads¶
Recovery is essential wherever wrong turns are inevitable and their cost is nontrivial — deep menus, high-stakes flows, unfamiliar spaces. By making exploration safe, it also encourages agents to try uncertain paths at all, and its report step turns each recovery into evidence that feeds the whole pattern. It is the applied form of the usability principle that systems should help users recognize, diagnose, and recover from errors.[n1]
Its failure mode is recovery that costs more than the wrong turn: if backtracking is heavy, context-restoration long, or the report path clumsy, agents abandon rather than recover, and the workflow becomes a second obstacle. A subtler failure is capturing false-scent reports that nobody ever acts on — recovery without a feedback loop treats the symptom forever. The guarding discipline is to make backtracking cheap and context restoration proportionate, and to actually route the exception reports back into cue fixes rather than letting them pool unread.
How it implements the components¶
orientation_recovery_path— the workflow is the recovery path: the ordered steps that return a lost agent to a productive choice.route_alternative_set— mid-recovery it presents the sibling routes the agent should choose among, turning a dead end into a live decision.false_scent_exception_log— its final step captures the misleading-cue encounter the agent just hit, feeding it back for repair.
It executes recovery but does not maintain the standing landmark-and-breadcrumb layer that recovery leans on (landmark_and_breadcrumb_system) — that persistent orientation infrastructure is Breadcrumb and Landmark Trail, which this workflow consumes.
Related¶
- Instantiates: Predictive-Cue Wayfinding Design — supplies the procedure that makes a wrong turn recoverable and informative.
- Consumes: Breadcrumb and Landmark Trail — the always-on landmarks and trail this workflow backtracks along and re-orients against.
- Sibling mechanisms: Breadcrumb and Landmark Trail · Cue-Destination Alignment Matrix · Destination Preview Card · Link-Label Scent Audit · Misleading-Cue Red Team · Progressive Disclosure Preview · Scent Clickthrough Trace Dashboard · Task-Based Wayfinding Test
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Route Recovery Pattern operates as a repeatable ordered procedure or handoff sequence that coordinates action because it a defined procedure an agent follows after a wrong turn — backtrack, regain context, compare alternatives, and report the bad scent — turning a dead end into a recoverable step.
Independent corroboration: The frozen evidence defines Route Recovery Pattern as 'A defined procedure an agent follows after a wrong turn — backtrack, regain context, compare alternatives, and report the bad scent — turning a dead end into a recoverable step', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Recovering from wrong navigation through backtracking, context recovery, and alternative comparison is an interaction-design pattern.
Related originating lineages:
- Cognitive Science — Wayfinding and information-scent theory materially explain route error and context reconstruction.
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: a defined procedure an agent follows after a wrong turn — backtrack, regain context, compare alternatives, and report the bad scent — turning a dead end into a recoverable step.
Review resolution: Both blind reviewers agree that human_computer_interaction is the primary historical origin. Explicit reconciliation of alternate_origin_disagreement, origin_mode_disagreement starts from reviewer_a's mechanism-specific evidence: Recovering from wrong navigation through backtracking, context recovery, and alternative comparison is an interaction-design pattern. Reviewer A proposed alternates=cognitive_science, computer_science, origin_mode=cross_disciplinary_synthesis, domain_reach=universal, and encyclopedia_synthesis=true; reviewer B proposed alternates=computer_science, origin_mode=convergent, domain_reach=universal, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (cognitive_science, computer_science) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and records domain_reach=universal and encyclopedia_synthesis=true. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The false-scent report captured here differs from the one the Misleading-Cue Red Team produces: recovery logs reactive, user-encountered bad scent (a real agent hit it in the wild), whereas the red team logs proactive, hunted bad scent (found before any user was harmed). Both write to the same exception log from opposite directions.
[n1] "Help users recognize, diagnose, and recover from errors" is one of Jakob Nielsen's ten usability heuristics: error states should be expressed in plain language, name the problem, and offer a constructive way out. Route recovery is that heuristic applied to wayfinding, where the "error" is a wrong turn induced by a cue. ↩