Skip to content

Workaround Inventory

Register — instantiates Revealed-Use Path Alignment

A structured catalog of the informal routes, side systems, and unofficial handoffs a system has accumulated — each entry logged with its context and a first-pass reading of why it exists.

Shadow work is invisible precisely because it is scattered — a spreadsheet here, a side channel there, a "just ask Priya" there. Workaround Inventory makes it countable. It is a living register that enumerates the discrete workarounds a system has grown, one row each, and attaches to every entry the context a later step needs: which official path it bypasses, who uses it, how often, and a first-pass hypothesis of why. Its distinguishing move is turning a diffuse, tacit mass of shortcuts into an itemized, interpretable list — where a heatmap shows a bright smear, the inventory names the individual shortcuts inside it and stages each as a testable claim. It captures and hypothesizes; it does not visualize concentration, and it does not itself pass judgment.

Example

A mid-size manufacturer's finance team runs its month-end close on the official ERP — officially. In practice a controller notices the close actually rides on roughly a dozen unsanctioned Excel workbooks. The inventory logs each one: "FX-revaluation macro — bypasses the ERP's currency module — used by three analysts — because the standard report can't handle a mid-month rate change." "Manual intercompany tie-out sheet — bypasses the consolidation step — because two subsidiaries book in different calendars." Once the twelve are laid side by side with their hypothesized causes, a pattern nobody could see while the workbooks lived on separate laptops jumps out: eight of the twelve trace to a single missing ERP capability. That clustering reframes the story from "our analysts keep going rogue" into "the system has one gap that eight people are independently routing around," and hands a concrete, prioritized target to the interpretation and decision steps.

How it works

What distinguishes the inventory from the other capture tools is that it is discrete, attributed, and provisionally interpreted:

  • Enumerate to completeness. The goal is to find all of them, including the workarounds nobody volunteers, so the register reflects real shadow practice rather than the sanctioned story.
  • Attribute each entry. Every row carries the bypassed official path, the population, the frequency, and — the load-bearing field — a hypothesized cause.
  • Cluster and stage. With causes attached, entries group by root, converting a pile of shortcuts into a small set of testable hypotheses for the next step.

Tuning parameters

  • Scope boundary — which teams and systems get canvassed. Narrow is fast but misses the cross-team side channels, which are often the riskiest.
  • Entry granularity — one row per workaround or per variant. Finer captures nuance; coarser stays usable.
  • Attribute set — how many fields each entry carries (owner, frequency, bypassed path, hypothesized cause, rough risk). More fields give richer triage but heavier upkeep.
  • Elicitation stance — self-reported versus directly observed. Self-report is cheap but systematically under-reports the embarrassing workarounds, which tend to be the ones that matter.
  • Refresh cadence — one-shot audit or standing register. Workarounds regenerate, so a stale inventory quietly misleads.

When it helps, and when it misleads

Its strength is that it makes invisible shadow work visible, countable, and clustered — giving every downstream step a concrete unit to reason about, and often revealing that a dozen "rogue" behaviors are one unmet need wearing twelve disguises.

Its failure modes start with candor: the register depends on people admitting to workarounds they may prefer unseen, so a punitive inventory returns empty. A subtler trap is that a catalogued workaround has usually become normal — its accumulated risk no longer felt — so the act of listing can launder deviance as routine rather than flag it.[1] And its classic misuse is as a hit-list: treating the inventory as a roster of offenders to discipline, which guarantees the shadow work simply goes deeper and darker. The discipline is to read every entry as a symptom to interpret, protect the informants, and route verdicts to a separate filter rather than judging inside the catalog.

How it implements the components

Workaround Inventory realizes the capture-and-first-interpretation side of the archetype's machinery:

  • use_trace_capture — the register is the captured trace in enumerated form: each informal route logged as a discrete, attributed entry.
  • trace_interpretation_rule — every entry carries a first-pass hypothesis of why it exists, keeping the trace tied to its context and turning a shortcut into a testable claim rather than a reified fact.

It does not visualize where behavior concentrates — that aggregate picture is Use-Trace Heatmap — and it neither judges whether a workaround may be legitimized (Safety and Accessibility Review) nor enacts any change (Informal Route Legalization Patch, Route Closure with Alternative).

Notes

The per-entry hypothesis is deliberately a first pass — broad, not deep. Recovering the real lived reason behind a given workaround (why this person, at this moment) is the job of narration in Frontline Go-Along Interview. Keeping the two separate is what lets the inventory stay wide and the interview stay deep, instead of the register collapsing into a handful of well-understood cases while the long tail goes unlogged.

References

[1] Normalization of deviance — Diane Vaughan's term for how a repeatedly-tolerated departure from the official standard gradually comes to be treated as normal, so its risk stops being noticed. An inventory that merely lists long-standing workarounds can reinforce that normalization unless each entry is explicitly re-examined rather than assumed benign. ↩