Value Leakage adoption playbook - from a sized list to a living, owned recovery ledger
Objective. Give the CSM a runnable plan to take Value Leakage from a one-time sizing exercise to a living ledger with named owners and verified recoveries. Adopted means findings are detected, validated, owned and moved from Open to Verified on a recurring cadence - with recovered capacity and cash recovered kept as separate lines that are never summed.
Most leakage work dies as a slide: an impressive total that no one owns and no one verifies. This playbook defines what adopted looks like for Value Leakage, stages the rollout from a single pilot finding to a scaled ledger, names the adoption risks specific to this app and how to counter them, and sets the success measure and review cadence from the app's own grounding. The non-negotiable through-line: value = quantity x unit-cost x confidence, six categories, and capacity never summed with cash.
The adoption goal and what adopted looks like
The goal is a living leakage ledger, not a sizing deck. Adopted means four things are true on a recurring basis: (1) findings are surfaced by workflow detection and sized by quantity x unit-cost x confidence rather than guessed; (2) every high-value finding has a named, accountable owner, not a team label; (3) findings move through states from Open to Verified with evidence, and the customer trusts the number enough to take it to finance; (4) the recovery view is read with recovered capacity and cash recovered on separate lines that are never added together.
What it is NOT: a single consultant-style total, a screen that ages untouched after kickoff, or a blended 'total savings' headline. If the customer is quoting one big number with no owner and no Verified evidence behind it, the app is installed but not adopted. The honest signal of adoption is boring and specific: a short list of owned findings, each with a status, a capacity line and a cash line that stay apart.
Staged rollout - pilot, team, scale
Stage 1 - Pilot (one finding, one owner). Open Top value leaks (https://leakage.demo.timechamp.io/#/leaks) against the customer's own early data, pick the single highest-value finding you can defend, and walk it end to end: break it into quantity x unit-cost x confidence, validate the five inputs (time basis, rates, recoverable share, overlap, owner), assign one named owner in Attribution, and set its baseline on Recovery. Milestone: one finding at a validated Open state with a real owner and an agreed definition of verification evidence.
Stage 2 - Team (a category becomes a routine). Expand to one full category - for example capacity (https://leakage.demo.timechamp.io/#/capacity) or process (https://leakage.demo.timechamp.io/#/process) - so a team and its manager review their findings on a cadence. Milestone: that category's high-value findings are all owned, and at least one finding has moved from Open toward Verified with evidence, read as a capacity line and a cash line kept separate.
Stage 3 - Scale (the ledger runs the programme). All six categories are live, Top value leaks sets the validation order, and a recurring review uses Recovery and Reports to track verified recovery, owner coverage and time to verification. Milestone: the customer runs the review themselves and can defend the aggregate to finance because every finding is confidence-discounted, checked for overlap, and labelled capacity or cash.
Top adoption risks for this app and how to counter them
Risk 1 - the inflated total. The customer blends capacity and cash into one impressive number for the board. Counter: from day one, read Recovery as two lines and refuse the blend out loud; make 'we never sum capacity and cash' a stated rule of the review.
Risk 2 - sized but un-owned. Findings get a value but no accountable person, so nothing recovers. Counter: make owner coverage a standing agenda item; no finding enters the recovery plan without a named owner from Attribution.
Risk 3 - detected read as proven. The customer treats a detected or Open finding as banked money. Counter: teach that detection produces a candidate and only Verified-with-evidence counts; keep Open and Verified visibly distinct in every review.
Risk 4 - double-counting. Two findings claim the same freed hours. Counter: validate overlap before trusting any aggregate; flag findings that share underlying hours so they are never summed.
Risk 5 - stale rates and assumptions. Unit-costs or recoverable-share figures drift from what finance will agree. Counter: agree rates with the customer's finance up front and re-confirm them at each review; anything uncertain stays 'confirm with product / finance' and is discounted by confidence.
Success metric to watch and the review cadence
Watch the measures the app's own grounding names, and keep them honest:
- Verified recovery with evidence - the headline, labelled capacity or cash, never blended. This is the one number that proves adoption.
- Owner coverage - the share of high-value findings with a named, accountable owner.
- Time to verification - how long findings take from Open to Verified.
- Unresolved high-value findings - the biggest leaks still sitting Open.
Cadence: a short weekly working review (move findings forward, close ownership gaps, validate new detections) and a monthly or quarterly business review that reports verified recovery with evidence to the customer's finance - capacity line and cash line separate. Use Reports (https://leakage.demo.timechamp.io/#/reports) for the review pack. The review that cannot show a Verified finding with evidence is reporting activity, not recovery; that is the signal to go back to Stage 1 on one finding and earn the number properly.
Interpretation check
Adopted means a living, owned ledger with Verified-with-evidence recoveries, not an impressive one-time total. Recovered capacity and cash recovered stay on separate lines and are never summed; a detected or Open finding is a sized opportunity, not money won.
In the field
KnackGlobal (RCM, ~6,000 seats): adoption here means a recovery ledger that defends the account on hard ROI against the incumbent - owners on every high-value finding, findings moved to Verified with evidence, and freed capacity kept strictly separate from cash so finance backs the number instead of writing it down.
Practical task
Pick one real customer account this month. Stage 1: open Top value leaks, select one defensible finding, break it into quantity x unit-cost x confidence, validate the five inputs (time basis, rates, recoverable share, overlap, owner), assign a named owner in Attribution, and set its baseline on Recovery with an agreed definition of verification evidence. Then draft the weekly-plus-quarterly review cadence and the four measures you will report - with capacity and cash as separate lines.
Self-check
What distinguishes an adopted Value Leakage deployment from an installed-but-unused one?
Adoption is a living ledger: findings detected and sized by quantity x unit-cost x confidence, every high-value finding owned, findings moving from Open to Verified with evidence, and recovery read as separate capacity and cash lines. Installed-but-unused is a one-time total with no owners and no Verified evidence that ages on a slide.
What is the pilot-stage milestone and why keep it to one finding?
One defensible finding at a validated Open state with a named owner and an agreed definition of verification evidence. Keeping it to one finding earns trust in the model before scale - one well-validated finding beats a long un-owned list.
A customer wants the board deck to show one combined savings number. How do you counter this as an adoption risk?
Refuse the blend: capacity and cash are separate lines that are never summed, because freed capacity is only cash if the customer redeploys or removes it. Make 'we never sum capacity and cash' a stated rule of the review - the honesty is what makes the number fundable.
Which four measures do you watch, and which is the headline?
Verified recovery with evidence (the headline, labelled capacity or cash), owner coverage, time to verification, and unresolved high-value findings. Verified recovery with evidence is the one that proves adoption, kept honest by never blending capacity and cash.
What is the signal that a review is reporting activity rather than recovery?
It cannot show a single finding at Verified with evidence. The counter is to go back to one finding, validate its five inputs, assign a real owner and earn the Verified status properly before scaling.
Verified vs demo. The category model, workflow detection, Top value leaks ranking, Attribution, the quantity x unit-cost x confidence model, and Recovery with the capacity-vs-cash separation are demo-shown on seeded data with illustrative magnitudes (for example Capacity ~78 lakh, Process ~1.12 crore). Real rate sources, detection coverage, recoverable-share assumptions, acceptable verification evidence and the customer's org/ownership model are customer-specific - confirm with product and the customer's finance.