Skip to content

Friction Mapping Session

Method — instantiates Revealed-Use Path Alignment

Lay the official path and the workaround side by side and score each step for effort, delay, uncertainty, and social and cognitive cost, so the cost gap that drives the deviation becomes visible and rankable.

Friction Mapping Session is a structured working session that places the intended path and the observed workaround next to each other and scores each step for its real cost — steps, time, waiting, hand-offs, uncertainty, cognitive load, social and political cost. The move that distinguishes it is that it doesn't just note that people deviate (a walkthrough) or ask them why (a go-along) — it measures the cost gap, decomposed by type, converting "the shortcut is easier" into "the official path costs nine steps, two approvals, and an eleven-day wait; the workaround costs three and none." That decomposition is what tells a redesign which friction is actually load-bearing.

Example

Employees keep bypassing a company's official expense system, getting a manager to sign a paper form and reimbursing from petty cash. A friction-mapping session puts both paths on a wall. The official path scores nine steps: log into a portal, find the correct cost code, attach receipts in a required format, route to two approvers, and wait roughly eleven days — with high uncertainty ("will it bounce for the wrong code?") and real cognitive load. The workaround scores three steps, same-day cash, one signature, near-zero uncertainty. Scoring each step across dimensions exposes that the friction isn't the raw step count — it's two drags: the cost-code lookup (uncertainty) and the eleven-day wait (delay). The output is a ranked friction ledger naming those two dominant drivers, which tells the redesign exactly what to cut rather than "make the tool nicer."

How it works

  • Map both paths in parallel. The official route and the workaround, step for step, on the same surface — the comparison is the artifact.
  • Score every step across dimensions. Not just minutes: effort, waiting, uncertainty, social cost, cognitive load — because the driver is often the one that resists a stopwatch (humiliation, fear of rejection).
  • Rank the drivers. Surface the load-bearing friction so redesign targets it, not the cosmetic steps that are merely visible.
  • Size the cause, then hand off. It produces the causal magnitude and leaves the lived texture to the go-along and the go/no-go to the decision rule.

Tuning parameters

  • Cost dimensions counted — time-only versus the full set including social and cognitive cost. Narrow scoring is fast but routinely misses the friction that actually drives the deviation, which is often stigma or uncertainty rather than minutes.
  • Step granularity — coarse phases versus fine sub-steps. Fine granularity locates the exact drag but risks false precision.
  • Measured versus estimated — stopwatch data and real counts versus participants' in-the-room guesses. Measured is credible but slow; estimated is quick but skews optimistic.
  • Whose friction — map for the median user or the worst-served. Mapping the worst-served is what links the ledger to the equity check.

When it helps, and when it misleads

Its strength is that it makes the deviation's cause rankable and comparable, so a redesign spends its effort where the friction actually lives instead of on whatever looked broken. It is the design cousin of value stream mapping, which lays a process end to end to expose delay and waste rather than mere activity.[1] Its failure mode is that friction easy to quantify (steps, minutes) crowds out friction that isn't (fear, stigma, distrust), so a tidy ledger can confidently point at the wrong driver; and estimates made in a room lean optimistic. The classic misuse is mapping only the official path to "prove" it is fine, or scoring to justify a tool already chosen. The discipline is to score the non-time dimensions explicitly, sanity-check the ledger against the go-along's lived account, and map the workaround as seriously as the official route.

How it implements the components

  • intended_actual_path_comparison — the session's spine is the parallel, step-by-step scoring of the official path against the workaround.
  • trace_interpretation_rule — the ranked cost gap is the interpretation: it explains the deviation as a measured response to specific friction, stated as a testable claim ("cut the eleven-day wait and the workaround should fade").

It does NOT capture the raw trace (Use-Trace Heatmap and Clickstream Deviation Scan) or recover the spoken reasons and whom the path excludes (that's Frontline Go-Along Interview); it prices the gap, it does not find or narrate it.

  • Instantiates: Revealed-Use Path Alignment — it turns an observed deviation into a ranked account of the friction that caused it, aiming the redesign at the load-bearing cost.
  • Consumes: Desire Path Walkthrough or Use-Trace Heatmap to supply the two paths it prices — it scores a workaround already identified, it does not discover one.
  • Sibling mechanisms: Frontline Go-Along Interview · Clickstream Deviation Scan · Desire Path Walkthrough · Use-Trace Heatmap · Workaround Inventory · Before/After Trace Monitoring · Trace Decay Review · Safety and Accessibility Review · Route Closure with Alternative · Temporary Paving Pilot · Informal Route Legalization Patch

References

[1] Value stream mapping is the Lean practice of drawing every step of a process, with its wait times and hand-offs, to reveal where delay and waste accumulate rather than where activity is busiest. Friction mapping applies the same lens comparatively, to the official path and the workaround at once. ↩