Ruler or Reality
When a number jumps, check whether customers moved or the ruler did.
The job
Stop leaders funding, firing or announcing on the basis of a jump caused by a new tagging model, a reworded taxonomy, a newly connected source or a model upgrade rather than by customers, and put a price on each false alarm it stops.
The moment
The CFO is about to approve a $4.2M emergency billing programme because billing complaints rose 22% in August. On the boss screen the tile already carries an amber the ruler moved badge. One tap shows that the jump lands exactly on 14 August, the day the new complaint-tagging model went live. Over the two-week parallel run the old ruler reads +1%, and the relabelling grid shows 1,380 service outage complaints relabelled as billing. The spliced series is flat, the programme is paused, and the ledger ticks over: False alarms averted this year: 3, $6.9M not spent on phantom problems.
What it does
- Log a method change
- Stamp the break verdict and adjustment factor
- Record a paused decision
- Notify tile and KPI owners
- Drill relabelled items
What you see
A tape measure laid over the chart: break markers, an old-versus-new ruler overlay with a relabelling grid, a spliced series, and a running ledger of false alarms averted
What it moves
False alarms averted per year (count and dollar value of programmes paused or re-scoped), and the share of leader-screen KPI jumps checked against the change log before the meeting
Built for
- Finance
- Analysts & data
- CX leaders & VoC
- Executives & leadership
