Before/After Trace Monitoring¶

Monitor — instantiates Revealed-Use Path Alignment

Measure the intensity of the old workaround trace before and after a path change to test whether the redesign absorbed the deviation — or merely moved it.

Before/After Trace Monitoring measures the intensity of a deviation trace at two or more points — before a path change and after it — to verify that the official update actually did its job. A successful alignment has to show three things at once: the old workaround fades, the new official route carries the load, and no worse trace has appeared elsewhere. What makes it this mechanism is that it closes the loop: it is the only one here that judges whether alignment worked, on evidence, by re-measuring the same trace across the change. Everything else in the set diagnoses before the fix; this one verifies after it.

Example¶

Employees used to bypass the benefits portal by emailing HR directly, so the workaround trace is the volume of "how do I change my benefits" emails. HR redesigns the portal's landing page to surface the top three self-service actions. Monitoring baselines the direct-email volume and portal completion rate for the month before launch, then tracks both for two months after. The direct-email trace falls by roughly 60% (illustrative) and self-service completions rise — but the monitor also catches a new trace: a bump in IT help-desk tickets about portal login errors. The redesign absorbed the original deviation and pushed a smaller one downstream. The output is a verdict — alignment largely worked — plus a flag: a fresh friction point to feed back into the loop.

How it works¶

Fix and baseline the metric first. Choose the trace measure and size it before the change — you cannot detect a fade you never measured.
Re-measure on a comparable window. Same metric, same length and seasonality of window, after the change.
Watch for displacement, not just decline. The decisive check is whether a new desire path has formed at the next friction point — celebrating the fall of the old trace alone is how a moved problem passes for a solved one.
Report fade, adoption, and displacement together. A verdict, not a single flattering number.

Tuning parameters¶

Baseline window — how long you measure before the change. Too short and ordinary variation masquerades as effect; longer baselines cost calendar time.
Displacement scope — how far afield you look for new traces. Narrow scope declares premature victory; wide scope catches spillover but adds monitoring cost.
Attribution guardrail — how hard you rule out confounds such as a seasonal dip or a concurrent launch. Loose attribution credits the redesign for luck.
Sustain horizon — how long after launch you keep watching. Stop too early and a trace that re-forms once the novelty fades goes unseen.

When it helps, and when it misleads¶

Its strength is that it stops the redesign from being open-loop: it converts "we paved it, surely it worked" into checked evidence, and its displacement watch is precisely what keeps a team from cheering a problem that merely relocated. Its failure mode is Goodhart's law — once "reduce the old trace" becomes the target, the trace can be suppressed (block the shortcut) while the underlying friction, and the need behind it, persist and surface elsewhere; a falling metric is not the same as a solved problem.^[1] Confounds can also masquerade as success. The classic misuse is measuring only the metric that improved and declaring victory. The discipline is to pair the fade of the old trace with adoption of the new route and an explicit displacement search, and to hold attribution honestly against the confounds.

How it implements the components¶

use_trace_capture — it re-captures the same deviation trace after the change, on comparable terms, so the two readings can be set against each other.
post_alignment_monitor — its core: it checks whether the old path fades, the new route is genuinely used, and no worse trace appears at the next friction point.

It does NOT diagnose the original deviation (that's Desire Path Walkthrough and Clickstream Deviation Scan) or make the change it evaluates (Informal Route Legalization Patch or Route Closure with Alternative); it judges the result, it does not produce it.

Instantiates: Revealed-Use Path Alignment — it supplies the loop's closing evidence, the test of whether the official update actually re-aligned use.
Consumes: Informal Route Legalization Patch or Route Closure with Alternative — it monitors the effect of whatever change those mechanisms shipped.
Sibling mechanisms: Trace Decay Review · Informal Route Legalization Patch · Desire Path Walkthrough · Clickstream Deviation Scan · Friction Mapping Session · Frontline Go-Along Interview · Use-Trace Heatmap · Workaround Inventory · Safety and Accessibility Review · Route Closure with Alternative · Temporary Paving Pilot

Notes¶

It is close to Trace Decay Review but not the same: this is a paired pre/post measurement bracketing a specific intervention, asking "did our change work?" Trace Decay Review asks whether a trace is fading on its own and sets the cadence for re-inspection. Use this one when you have a change to evaluate; use that one to watch an unchanged system over time.

References¶

[1] Goodhart's law — when a measure becomes a target, it ceases to be a good measure. If the goal collapses into "make the old trace go away," the trace can be forced down without the friction being fixed, so the monitor pairs trace-fade with genuine adoption of the new route. ↩