Value Leakage assessment - prove you can produce and defend an honest recovery number
Objective. Test mastery of Value Leakage for the certification gate. The learner must size a finding correctly with quantity x unit-cost x confidence, keep recovered capacity and cash recovered separate, distinguish detected/Open from Verified, catch overlap, and name the validations and escalations. Tied to the gate: practical score >=80, no critical error, manager review.
This assessment puts the learner in two realistic situations - a sales demo moment and a CSM validation moment - and scores whether they produce a defensible number and defend it honestly. The pass bar is not fluency; it is honesty discipline. Presenting a projection or a sized figure as a recovered result, or blending capacity and cash, is an automatic fail regardless of the rest. self_check holds the actual assessment questions with model answers.
See it in the demo
Scenario 1 - the sales demo challenge (buyer pushes back)
A revenue-cycle buyer in a live demo says: 'Your Overview shows Process around 1.12 crore. That is our number, right? And if I add the capacity line to it, that is our total savings.' You have the demo open.
The learner must: (1) correct the misread that a seeded magnitude is the customer's number, and explain how the real number is built from measured quantity and finance-agreed rates; (2) refuse the capacity-plus-cash sum and explain why; (3) pick one finding and break it into quantity x unit-cost x confidence out loud; (4) state the one explicit limitation; (5) propose the honest next step (build one finding on the customer's own data). A correct response is calm and uses the honesty as the pitch, not as an apology.
Scenario 2 - the CSM validation challenge (figure under dispute)
A customer's operations lead emails: 'Your tool says we recovered a large amount in capacity and quality this quarter. Finance does not believe it and neither do I.' You open Recovery and Attribution and find: two high-value findings that appear to describe the same idle hours; a large value sitting at Open being reported as recovered; and a capacity line and a cash line that someone has summed in the customer's own deck.
The learner must: (1) separate capacity from cash and explain the rule; (2) identify the overlap and explain that overlapping findings cannot be summed; (3) identify that the Open value is a sized opportunity, not recovered money, and that only Verified-with-evidence counts; (4) list the five input validations (time basis, rates, recoverable share, overlap, owner); (5) say what escalates to the customer's finance (rate and recoverable-share questions) versus to product (detection method and evidence standard). A correct response rebuilds trust by showing the inputs, not by defending the total.
Scored checklist - what a correct answer contains
Score out of 100; pass is >=80 with no critical error and manager review.
- Writes value = quantity x unit-cost x confidence and explains what each term protects against (20)
- Keeps recovered capacity and cash recovered as separate lines and refuses to sum them (20, and summing them is a critical error - see below)
- Distinguishes detected / Open (sized opportunity) from Verified-with-evidence (recovered) (15)
- Catches overlap and explains that overlapping findings cannot be summed (10)
- Names the five CSM input validations - time basis, rates, recoverable share, overlap, owner (15)
- Treats seeded demo magnitudes as illustrative, not as a customer figure (10)
- Routes escalations correctly - rate/recoverable-share to finance, detection/evidence to product (10)
Critical errors that fail the assessment
Any one of these fails the assessment regardless of the score elsewhere, because each is exactly the inflation the app exists to prevent:
- Summing recovered capacity and cash recovered into one total, or stating that freed capacity is cash saved without the customer redeploying or removing it.
- Presenting a projection, a detected finding, or an Open value as a recovered result - treating sized opportunity as money won.
- Quoting a seeded demo magnitude (for example Capacity ~78 lakh or Process ~1.12 crore) as the customer's actual opportunity or result.
- Summing overlapping findings that describe the same underlying hours into an aggregate.
- Asserting a rate, recoverable share, detection accuracy, security or compliance specific as fact instead of 'confirm with product / finance.'
These are not deducted gradually; they are the line between a defensible number and the dishonest total the app is built to resist.
Interpretation check
Passing means producing a defensible number and defending it honestly: the value formula explained, capacity and cash kept separate, detected/Open distinguished from Verified, overlap caught, validations and escalations named. Blending capacity and cash, or presenting a projection or Open value as recovered, is an automatic fail.
In the field
KnackGlobal (RCM, ~6,000 seats): the assessment mirrors the real stakes - a single blended or overstated recovery figure on a flagship account under incumbent attack is what finance writes down, so the certification deliberately fails exactly the behaviours that would lose the account on ROI.
Practical task
Complete both scenarios in writing and have a manager review them against the scored checklist. For Scenario 1, produce the spoken demo response including one finding broken into quantity x unit-cost x confidence and the stated limitation. For Scenario 2, produce the validation packet: the corrected capacity and cash lines, the overlap finding, the Open-vs-Verified correction, the five validations run, and the escalation routing. You pass at >=80 with no critical error and manager sign-off.
Self-check
ASSESSMENT Q1: A buyer says the demo's ~1.12 crore Process tile is their number and wants it added to the capacity line for a total. Give the full correct response.
First, the ~1.12 crore is a seeded demo magnitude that proves the model sizes and ranks leaks - their real number is built from their measured quantity and finance-agreed rates, which we confirm together. Second, I will not add the capacity line to it: recovered capacity and cash recovered are never summed, because freed capacity only becomes cash if you redeploy or remove it. Let me instead take one finding, break it into quantity x unit-cost x confidence, show its owner and recovery state, and we build your real number on your own data. Critical errors avoided: quoting the seeded figure as theirs, and blending capacity with cash.
ASSESSMENT Q2: On Recovery you find a large value at Open being reported as recovered. Is it recovered, and what do you say?
No. Open means sized but not acted on - an opportunity, not money won. Only a finding at Verified, with evidence, counts as recovered, and even then capacity and cash stay on separate lines. I would reclassify it as a sized opportunity, note what evidence would move it to Verified, and correct any report that counted it as recovered.
ASSESSMENT Q3: Two high-value findings appear to describe the same idle hours and have been summed. What is the error and the correct handling?
Overlap / double-counting. Overlapping findings that share the same underlying hours cannot be summed, or the aggregate overstates recovery. I validate whether they share a quantity basis, de-duplicate or net them, and only then report an aggregate - keeping capacity and cash separate throughout.
ASSESSMENT Q4: List the five inputs a CSM validates before trusting a leak number and why each matters.
Time basis (is quantity measured or estimated - estimated is discounted by confidence), rates (unit-costs agreed with finance, not assumed), recoverable share (realistic, not theoretical maximum), overlap (no double-counting of the same hours), and owner (a real accountable person, or the finding is just a statistic). The number is only as honest as these.
ASSESSMENT Q5: Which questions do you escalate rather than answer, and to whom?
Rate and recoverable-share questions go to the customer's finance; detection method, coverage, evidence standard and any security or compliance specific go to product. Anything uncertain is stated as a seeded demo example with 'confirm with product / finance' - asserting it as fact is a critical error.
Verified vs demo. The scenarios use seeded demo magnitudes (for example Capacity ~78 lakh, Process ~1.12 crore) that prove the model, not customer results. A correct answer explicitly treats them as illustrative and builds any real number from the customer's measured quantity and finance-agreed rates, with detection method, recoverable share and verification evidence confirmed with product and the customer's finance.