The dashboard is confident. Is anyone sure why?
Every revenue number rests on definitions somebody chose, for reasons somebody knew, who may no longer work here.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Three teams use the word qualified and mean three different things. The routing rules assume a fourth.
Definitions and routing logic drift between teams, and the pipeline numbers you’re steering by drift with them.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in a jar that’s yours.
A new ops hire asks why rule 17 exists before changing it. Kept answers with the capacity reason and cites your call.
Shared definitions hold, so the numbers you steer by hold too. Kept. Keep the knowledge behind the work.
Stage definitions, attribution rules, the exception logic in the commission calc: revenue truth is a stack of decisions, and the stack's documentation is usually a person. When that person leaves, the numbers keep printing, and the ability to defend them quietly does not.
Kept captures the reasoning from the people who built the engine and keeps it cited: why the stage gate sits there, what that field actually means, which report is trusted and which is decoration. When the board asks why, the answer has a name and a date on it.
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
Read personal and workspace controls. The overview above is available as text; explore the guided text walkthrough for a step-by-step example.