Kept for Product.
The roadmap remembers what you decided. Nobody remembers what you decided against. Three films on keeping the rationale.
All industriesFor executives
Your product is a stack of decisions. Keep the reasons.
The most expensive meeting in a product org is the one that reverses a decision nobody remembers making.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The research is in one folder, the decision in another, and the link between them in someone’s head.
Roadmap decisions lose their evidence, so the next debate reopens a call you already made with data.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Planning comes round and someone asks why export was cut. Kept answers with the interview count and cites your call.
Product decisions keep their evidence, so they don’t get relitigated. Kept. Keep the knowledge behind the work.
Every mature product carries a graveyard of considered-and-rejected: the pricing model you tried, the integration you deliberately skipped, the architecture you walked away from. When the people who made those calls rotate out, the org re-explores the graveyard, at full cost, one confident new hire at a time.
Kept captures the rationale from the people who decided, in their words, and keeps it cited. Ask why the product does not do the obvious thing and get the actual answer, with a name and a date, or an honest unknown. Institutional judgment, retained.
For managers
The spec says what shipped. Kept keeps why.
Inheriting a product area means six weeks of asking why until someone finally knows.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The research is in one folder, the decision in another, and the link between them in someone’s head.
You defend last quarter’s cut in every planning meeting because the interviews behind it are buried.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Planning comes round and someone asks why export was cut. Kept answers with the interview count and cites your call.
The interviews behind the cut are one question away. Kept. Keep the knowledge behind the work.
The documents describe the feature. The reasoning lives in whoever was in the room: why the flow bends there, what the churned customer said, which experiment quietly settled the debate. Every handoff loses a layer, until the area runs on cargo cult and confident guessing.
Kept interviews the people who shaped the area and keeps their reasoning as cited, searchable memory. New PMs ramp from the actual why. Revisits start from what was learned, not from scratch. You see what is covered. Nobody is graded on it.
For partners
The best thinking never made it into the doc.
You considered four options, killed three for good reasons, and shipped one. The doc mentions one.
Read the film transcript
Narration from this original film. Soft instrumental music plays underneath.
The research is in one folder, the decision in another, and the link between them in someone’s head.
You’re building a feature without the customer signal that justified it, so every edge case is a guess.
Kept is a voice interview. June calls, asks about your work, and keeps what you say, in your words, in your knowledge base.
Planning comes round and someone asks why export was cut. Kept answers with the interview count and cites your call.
You build with the customer signal, not a guess. Kept. Keep the knowledge behind the work.
Kept talks with you about your area the way a sharp new teammate would, and keeps your reasoning in your own words. The trade-offs, the rejected paths, the thing the data actually said. When the question resurfaces next year, the answer cites you instead of restarting the debate.
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 product.
One process, one question the team already asks.
Start at zero.
Pay once when the KPIs land.
The KPIs we would propose for a product team:
- Partners with capture on, and using Kept, through the whole window
- Knowledge kept per role in scope, and its coverage band moving from thin to covered
- Questions answered with a source, against honest unknowns
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