Kept for Operations.
The process on the wall and the process on the floor are different documents. Three films on keeping the one that works.
All industriesFor executives
Your process capital retires one veteran at a time.
The SOP describes a plant that has never existed. The plant that exists is run from memory.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The fix for the recurring exception is known. Known by three people, none of whom are on call tonight.
Every shift change and site handoff leaks the exceptions that keep operations running, and that leak shows up as downtime.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Tonight’s on-call hits the empty weight field and asks Kept. They get the workaround in one line, cited to the person who found it.
Exceptions stop leaking at handoffs, across shifts and sites. Kept. Keep the knowledge behind the work.
Twenty years on the floor produces knowledge no process document has: which machine drifts in humidity, which supplier's Friday truck is short, what actually happens when the line stops. That knowledge is capital, and it currently depreciates to zero on someone's last day.
Kept captures it from the people who hold it, in their words, and keeps it as memory the operation owns. Ask what the night shift knows about the packaging line and the answer arrives with a name and a date, or says nobody has said. Continuity you can point at.
For managers
The handoff meeting is fifteen minutes. The knowledge is fifteen years.
Every shift change compresses everything the last shift learned into whatever fits in the doorway.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The fix for the recurring exception is known. Known by three people, none of whom are on call tonight.
You get the eleven p m call because you’re the only one who remembers the workaround.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Tonight’s on-call hits the empty weight field and asks Kept. They get the workaround in one line, cited to the person who found it.
The workaround is where the on-call can find it, not in your phone. Kept. Keep the knowledge behind the work.
Your veterans hold the real manual: the sound the conveyor makes before it fails, the vendor who answers on the second call, the order the restart actually goes in. New people learn it by standing next to them for a year, if the veteran stays a year.
Kept interviews your crew about the work, keeps it in their words, and makes it answerable for whoever needs it next. Handoffs, cross-training, and coverage stop depending on who happens to be standing there. You see what your area has kept. It never scores your people.
For partners
You know things the manual never will.
The way you actually keep the line moving took years to learn and ten minutes a day to explain, if anyone asked.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The fix for the recurring exception is known. Known by three people, none of whom are on call tonight.
You’re on call with an S O P that stops right before the part that actually breaks.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Tonight’s on-call hits the empty weight field and asks Kept. They get the workaround in one line, cited to the person who found it.
The part the S O P skipped is one question away. Kept. Keep the knowledge behind the work.
Kept asks. It talks with you about the work like someone who wants to learn it, keeps your answers in your own words, and gives them to the next person with your name attached. The workaround you invented stops being anonymous folklore and starts being your contribution, on the record.
Capture starts with each partner's consent. They can skip a question, stop a session and review their captured knowledge. A business workspace's access rules determine who else can use it.
Knowledge captured for a business workspace belongs to that workspace. Partners retain visibility, removal from view and in-session retraction controls. Permanent deletion follows the workspace request process, unless a provisioned legal erasure window applies.
Kept's internal partner model is not employer-facing. A business workspace can see a red, amber or green capture band, based on contributed knowledge, alongside the access and audit records described in the Privacy Notice. It is not a score of a person's work or judgment.
Where it starts in operations.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a operations team:
- Knowledge kept from the outgoing expert before the handoff date, by topic
- Questions the successor asks that are answered with a source, against honest unknowns
- Questions asked of Kept per week, and the share answered with a source
- The ten most repeated questions, and whether each has a kept answer
Agreed before the pilot starts and measured from the workspace's own ledger over a window we set together, with a minimum number of partners using Kept through it. Nothing to pay to begin. A one-time payout when the KPIs are met, then the recurring rate.
How the proof of value worksUseful knowledge.
Visible limits.
Kept supports the work. It does not assess competence, monitor people or replace training, supervision or required qualifications. Business knowledge follows workspace access and ownership rules.
Kept is designed to ground answers about your work in available sources and say when it does not know. AI can still make mistakes. Inspect the sources and review important answers before relying on them.
Security and compliance