The review cycle runs on things nobody wrote down.
One person on your team knows how the comp cycle actually goes. That person would like a vacation.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
Onboarding runs on one person’s memory. When they’re out, the new hire’s first week stalls.
You answer the same approval question every week, and it still gets escalated back to you.
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 coordinator asks what a contractor conversion needs. Kept gives the three steps and cites the call where you explained them.
The approval questions stop landing on your desk twice. Kept. Keep the knowledge behind the work.
The people calendar looks documented until the person who runs it is out. Then the questions start: the order of operations, the manager who needs early warning, the edge case from last cycle and how it was handled. The process is fine. The knowledge of the process is a single point of failure.
Kept interviews your team about how the work really goes and keeps it in their words, cited and searchable. Coverage becomes real, handoffs keep their judgment, and the answers stay when people move on. You see what is kept. It never rates the people who kept 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.