Recurrence and Displacement Dashboard¶
Dashboard — instantiates Workaround Governance
A monitoring view that tracks whether a workaround recurs, mutates, relocates, or shifts its burden onto other groups after a disposition is applied.
A disposition is a hypothesis: we redesigned the source, so the deviation should stop. A Recurrence and Displacement Dashboard is the instrument that tests that hypothesis over time. Its defining focus is not compliance counts but movement — whether the workaround comes back, changes shape, reappears in an adjacent team, or spawns a new hidden route — and, crucially, whether its cost has been displaced onto a different group rather than removed. The dashboard is built to resist the trap of celebrating a falling number: a drop in recorded deviations means nothing if reporting trust fell at the same time, or if the burden simply moved to newcomers. It is the archetype's closure sensor and its early-warning system, watching the aggregate pattern long after the individual case is "resolved."
Example¶
A software company's customer-support org has been governing a fleet of unofficial macros and a private team knowledge base that agents used to answer tickets faster than the sanctioned help center allowed. The disposition redesigned the official knowledge base and retired the private one. Six weeks later, the Recurrence and Displacement Dashboard shows the story the case file alone would miss. Recurrence: use of unsanctioned macros has dropped 80% on the original team — good. But displacement lights up two panels: a new private doc has appeared on the enterprise-support team (the route relocated), and average handle time for tickets from non-English-speaking customers rose, because the redesigned base dropped the informal translations the old macros carried. The equity panel makes visible that the "fix" quietly shifted burden onto a customer segment nobody was watching. The dashboard does not decide what to do; it reopens the case with evidence that the disposition is incomplete — the function was preserved for the median customer but not for everyone.
How it works¶
- Track movement, not just level. Panels watch recurrence (does it come back), mutation (does it change form), relocation (does it appear elsewhere), and new-route emergence — the ways a suppressed workaround survives.
- Watch burden transfer explicitly. A dedicated view compares outcomes across affected groups over time, so a cost that moved rather than vanished is visible rather than netted away.
- Pair every count with a trust signal. Recorded-deviation counts are read alongside reporting-trust indicators, so a fall in cases is never mistaken for success when it is really a fall in disclosure.
- Trigger review on signal, not schedule. Threshold crossings (recurrence rebound, a displacement spike) raise a review flag, feeding the case back into disposition rather than waiting for the next calendar cycle.
- Aggregate across cases. The dashboard reads the portfolio, spotting patterns (a whole class of workarounds relocating the same way) that no single case record reveals.
Tuning parameters¶
- Displacement sensitivity — how aggressively relocation and burden-shift are flagged. High sensitivity catches quiet exports of cost but raises false alarms; low sensitivity misses slow migration.
- Trust-signal weight — how much reporting-trust indicators temper raw counts. Weighting them heavily guards against gaming but complicates the headline number.
- Group granularity — how finely outcomes are split across affected populations. Finer splits surface inequities but thin the data per group and risk re-identifying individuals.
- Review-trigger threshold — how large a movement reopens a case. A tight threshold catches rebounds early but floods reviewers; a loose one lets drift accumulate.
- Lookback window — how far back trends are compared. Longer windows reveal slow displacement; shorter ones react faster to acute rebound.
When it helps, and when it misleads¶
Its strength is that it closes the loop honestly — it distinguishes a workaround that was genuinely resolved from one that merely moved, and its equity panel catches the common failure where a fix helps the visible majority while exporting cost to a group no one was monitoring. It keeps "case closed" from meaning "problem relocated."
Its central failure mode is becoming the very metric that gets gamed. If a falling deviation count is treated as the goal, people will make the count fall — by underreporting, not by adapting — and the dashboard will show triumph while the dangerous workarounds go dark. This is Goodhart's law[n1] operating on the governance process itself: the moment the measure becomes the target, it stops measuring reality. The classic misuse is rewarding teams for "fewer workarounds," which optimizes disclosure downward. The guarding discipline is to instrument reporting trust and detection quality alongside the counts, to read a drop in cases with a drop in trust as a warning rather than a win, and never to attach individual incentives to the deviation count.
How it implements the components¶
This dashboard fills the ongoing-observation side of governance — the part that runs after disposition:
recurrence_and_displacement_monitor— it is the monitor: tracking recurrence, mutation, relocation, and new hidden routes over time, and flagging when a suppressed workaround has merely moved rather than resolved.equity_and_access_impact_check— its burden-transfer panel checks continuously whether the disposition shifted cost or degraded outcomes for a group not at the decision table, catching exported inequity the case file would miss.
It does not explain *why a recurrence happened (causal_demand_diagnosis — that is Practitioner Counterfactual Walkthrough), nor hold the per-case record system it aggregates from (workaround_case_record — that is Structured Workaround Registry); it surfaces aggregate signals, not the underlying records.*
Related¶
- Instantiates: Workaround Governance — this dashboard implements the "monitor recurrence and displacement until reconciled" invariant.
- Consumes: Structured Workaround Registry — supplies the per-case data the dashboard aggregates.
- Sibling mechanisms: Structured Workaround Registry · Practitioner Counterfactual Walkthrough · Multi-Path Disposition Matrix · Nonpunitive Workaround Review · Temporary Deviation Permit · Linked Root-Cause Repair Ticket · Benefit-Preserving Transition Plan · Workaround Failure-Mode and Effects Review · Sunset and Reauthorization Review
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: Recurrence and Displacement Dashboard operates as ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response because it a monitoring view that tracks whether a workaround recurs, mutates, relocates, or shifts its burden onto other groups after a disposition is applied.
Independent corroboration: The frozen evidence defines Recurrence and Displacement Dashboard as 'A monitoring view that tracks whether a workaround recurs, mutates, relocates, or shifts its burden onto other groups after a disposition is applied', so its operative form is Monitoring, Sensing & Alerting.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Tracking whether a workaround returns, mutates, or moves burden is organizational process governance and continuous review; analytics and program evaluation provide measurement techniques.
Related originating lineages:
- Data Science & Analytics — Longitudinal event tracking and mutation detection materially supply the dashboard.
- Public Administration & Policy — The public_administration_policy lineage materially shaped Recurrence And Displacement Dashboard through program evaluation, public authority, and implementation.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of organizational_management: Tracking whether a workaround returns, mutates, or moves burden is organizational process governance and continuous review; analytics and program evaluation provide measurement techniques. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Goodhart's law — "when a measure becomes a target, it ceases to be a good measure." Applied here: if the count of recorded workarounds becomes the objective, people drive it down by reporting less rather than deviating less, so the dashboard must watch reporting trust and detection quality, not the raw count alone. ↩