Budget review. Your CFO pushes back: "We already own three dashboards that show OEE and downtime. Why fund another analytics tool?"
Q1 What's the sponsor's answer?
A
We're not buying another dashboard — we're funding the loop that turns a finding into an acted, verified, audited dollar. That gap is where the current tools stop. Detection is table stakes; the existing dashboards prove it. The thesis is closing the gap between a finding and a number Finance will sign.
B
It consolidates the three dashboards into one, saving license fees. Consolidation is an IT argument, not an investment thesis. The return comes from verified savings, not from fewer dashboards.
C
This platform's detection is more accurate than the dashboards we own. Accuracy of findings isn't the differentiator — a more accurate finding nobody acts on is still worth zero to the P&L.
Covered in Module 01
Six months in, the platform has surfaced 23 ranked findings. Your teams have acted on 4 and verified savings on 3. The vendor's renewal deck leads with "23 opportunities identified."
Q2 How do you read that deck?
A
As a data problem — ask the vendor to surface fewer, better findings. The bottleneck isn't finding quality; it's that the organization acted on 4 of 23. That's a sponsorship problem, and it's yours to fix.
B
Skeptically — findings aren't savings. The 19 un-actioned findings are the loop failing, and that adoption gap is my exposure, not my return. Insight is not savings. The thesis only works where a finding became a logged action and a verified dollar — 3 of 23 is the real scorecard.
C
Positively — 23 identified opportunities show the platform is delivering. A finding that never reached an action is exactly the kind of value that never reaches the P&L. Counting findings rewards the part that was always table stakes.
Covered in Module 01
A peer executive tells you: "We deployed the same platform and the savings never materialized. The software doesn't work."
Q3 Under the verified-savings thesis, where did that deployment most likely fail?
A
In adoption and data quality — nobody protected the time to act and log, so the loop never closed and nothing could verify. The verified thesis moves risk off the estimate and onto the loop. When savings don't materialize, the first suspects are un-acted findings and dirty reason codes, not the model.
B
In the projection — the vendor's model overestimated the opportunity. A verified-savings deployment doesn't stand on a projection; it stands on measured baselines. An overestimate would show up as a smaller verified number, not zero.
C
In the integration — the platform likely couldn't connect to their machines. Connectivity failures are loud and immediate. Quiet non-materialization over months is the signature of an open loop: findings without actions, actions without logs.
Covered in Module 01
The ledger shows a changeover fix on the filler at $2,856/wk gross, reported at $2,428/wk after a 0.85 confidence weight. A director asks why you're "leaving money off the table."
Q4 Your answer?
A
Agree and restate the full $2,856 — the platform measured it directly. Measurement isn't attribution. Some of that $2,856 may belong to confounders, and booking it at face value hands the board a number that cracks under one question.
B
Explain that the vendor sets the weight and it can't be questioned. Deferring to the vendor abandons the method you're supposed to govern. The weight reflects evidence quality — that's the thing to explain and interrogate.
C
The discount prices attribution certainty. $2,428 is the floor I can defend under audit; the gap to $2,856 is upside, not a claim. Confidence-weighting books the dollar at what the evidence supports. Under-claiming with proof is the sponsor's credibility engine.
Covered in Module 02
A site proposes measuring its savings against nameplate capacity: "The line should run 900 units/hr, we run 720, so every improvement counts from 900."
Q5 What's wrong with that ledger?
A
The baseline should be the line's best-ever week, to keep targets ambitious. A best week is a lottery ticket, not a baseline. Spec sheets and cherry-picked weeks fail the same test: comparable, measured, prior conditions.
B
Nothing — nameplate is objective and identical across sites, so it's the fairest baseline. Objective isn't the same as honest. Nameplate inflates every claim by the line's pre-existing gap, which no action of yours produced.
C
It isn't baseline-normalized — savings must be measured against the line's actual prior performance under comparable conditions, not a spec sheet. Counting from nameplate books the gap between theory and reality as your win. The first auditor who checks prior actuals will retire the whole number.
Covered in Module 02
Mid-quarter, a demand surge confounds two ledger entries and the system demotes them. Your plant manager asks you to override the demotion so the site's total holds up for the review.
Q6 What do you do?
A
Refuse — a ledger that demotes claims when evidence weakens is why its surviving claims are believed. Report the lower floor and say why it moved. The demotion is the audit working in real time. Overriding it once converts the ledger from evidence into advocacy, and the board will eventually price that in.
B
Split the difference and report the average of the old and new figures. An averaged number has no method behind it — not baseline-normalized, not confidence-weighted, not auditable. It fails all three properties at once.
C
Override it this once — the surge is temporary and the savings are probably still real. "Probably still real" is precisely what confidence-weighting exists to price. An overridden ledger can't be defended later with a straight face.
Covered in Module 02
Internal audit samples your reported $180K of annual verified savings and asks to see what's behind one line item.
Q7 What does a defensible ledger let you show them?
A
The board deck where the figure was previously accepted without challenge. Prior acceptance is not evidence. Circulating a number doesn't verify it — tracing it to source events does.
B
The vendor's methodology whitepaper explaining how savings are calculated in general. A general method document proves the vendor has a method, not that this dollar is real. Audit wants this entry's evidence, not the theory.
C
The source events — the downtime records, reason codes, and scrap counts the entry was computed from, plus its baseline and confidence weight. Auditable means every dollar traces to events an auditor can open. If the trail ends at a summary screen, the number was never verified — it was displayed.
Covered in Module 02
Choosing a pilot site. Option A: the flagship line — cleanest data, but its manager calls the pilot "another corporate project." Option B: a line with a chronic, expensive changeover problem and a manager who has been asking for help all year.
Q8 Where do you run the pilot?
A
Both — parallel pilots double the chance one succeeds. Splitting sponsorship halves it. A pilot's job is one unarguable, verified result on a small scope — two half-attended pilots produce two arguable ones.
B
Option A — clean data reduces technical risk, and the flagship gets attention. Clean data can't compensate for an unwilling owner. A skeptical manager quietly starves the loop of operator time, and the pilot dies looking like a software failure.
C
Option B — a real, painful loss and a plant manager who wants to win. The pilot proves your org can close the loop, and that takes a motivated owner. Adoption fails organizationally, not technically. A known loss plus a willing manager gives the pilot a target worth hitting and someone who'll drive it.
Covered in Module 03
Four sites went live last month, on schedule. The regional VP drafts a board update headlined "Rollout complete — projected $2M annual savings" before any site has a verified dollar.
Q9 What's your move as sponsor?
A
Rewrite it — go-live is not value. Report deployment status plus the pilot's verified floor, and gate the victory lap and further expansion on verified savings. Declaring victory at go-live is the classic rollout failure. The board will remember your headline number; make it one the ledger can already defend.
B
Approve it — momentum matters, and the projection is conservative. The moment you report a projection as an outcome, you've swapped the verified thesis back for the estimate you refused at signing.
C
Hold all board updates until every site's savings verify in full. Silence isn't the alternative to overclaiming. Report what's true — live sites, verified pilot floor, expansion gates — and let the verified number grow.
Covered in Module 03
Two months into rollout, reason-code quality is collapsing at two sites. Supervisors under output pressure have pulled operators off logging: "we'll backfill the codes at week's end."
Q10 What is actually at stake, and what do you do?
A
The loop is starving — backfilled codes are guesses, and every downstream savings claim inherits that noise. Re-protect logging time as a staffed expectation. Fund change-management and protect logging time, or the loop starves. Only the sponsor can reset the priority call that broke it.
B
Not much — the totals will come out roughly the same once backfilled. A week-old memory puts stops in the wrong buckets, and the verification engine attributes savings from those buckets. The totals may survive; the ledger's credibility won't.
C
Escalate to the vendor to make the logging screens faster. UX tweaks don't fix a priority decision made by supervisors. The floor was told output beats logging — only sponsorship can reverse that message.
Covered in Module 03
The vendor offers an add-on that writes recommended setpoints directly to PLCs, projecting faster savings capture. Your CISO scoped the original deployment as read-only on the OT network.
Q11 How do you evaluate it?
A
Decline it — advise-only keeps consequential actions with recorded humans and keeps OT access read-only. The add-on changes both the governance line and the threat model. AI advises; it does not actuate. Write access to PLCs isn't a feature upgrade — it's a different risk posture for safety, attribution, and security at once.
B
Pilot it on one low-risk line without reopening the CISO review. Quietly granting OT write access invalidates the security scoping you signed under. There is no low-risk way to cross the read-only line unreviewed.
C
Accept it — the vendor's security certification covers the new module. A certification is a baseline signal, not a threat-model analysis. Read-to-write on OT is exactly the change that needs your CISO's specific questions again.
Covered in Module 04
Two of your business units will share one KaizenFlow deployment. One unit's process data would be competitively valuable to a supplier who also serves the other unit's biggest customer.
Q12 Before go-live, what must you establish?
A
Avoid the risk entirely by giving each unit its own permanently disconnected deployment. Segregation is a design requirement, not a reason to forfeit network-scale comparability. Establish the walls and keep the shared verification method.
B
Nothing extra — the vendor's standard multi-tenant controls handle separation. Trusting defaults is delegating stewardship. You establish and verify the segregation model, because you — not the vendor — answer for a leak between units.
C
Ownership, segregation, and retention — who owns each unit's data, how it's walled between business units, and what's kept versus discarded. Plant data is operationally and competitively sensitive, and stewardship is your responsibility, not the vendor's alone. The sponsor owns the questions; the vendor implements the answers.
Covered in Module 04