What are kaizen event records, and why do AI buyers want them?
Kaizen event records are the written trail of a short, focused improvement effort: the problem statement, the current-state measurements, the countermeasures tried and the measured result. A3 reports compress the same reasoning onto one sheet. Because each file links a cause to an intervention to an outcome, AI developers value them as structured examples of operational reasoning, the kind of material that is thin on the public web.
For an operating partner, the useful point is that lean programs under sponsor ownership already generate these files on a schedule. If a portfolio company has run events for several years, it may hold a library of before-and-after cases that nobody has ever treated as an asset.
What do the records actually contain?
A complete kaizen file is more than a slide. The richer the set, the more useful it is to a buyer building or evaluating agents that reason about operations.
| Record | Typical content | Why it carries value |
|---|---|---|
| A3 report | Background, current condition, target, root-cause analysis, countermeasures, follow-up | Compact cause-and-effect reasoning in a consistent structure |
| Event charter | Scope, team, dates, goals, boundaries | Shows how a problem was framed before work began |
| Baseline data | Cycle times, defect counts, changeover minutes, walk distances | Gives the "before" side of the comparison |
| Root-cause artifacts | Five-whys notes, fishbone diagrams, process maps | Reveals the reasoning path, including hypotheses that were dropped |
| Action tracker | Owners, due dates, status, slippage | Shows which fixes were actually carried out |
| Results and audit | Post-event measurements, sustainment checks at 30, 60 or 90 days | The outcome label, and whether the gain held |
The sustainment audit is the part many teams skip. A file that records whether a gain stuck is worth noticeably more than one that stops at the closing presentation.
Which portfolio companies keep the best files?
Look for manufacturers, distributors and service operations that treat improvement as a routine, not a one-off campaign. Industry matters less than discipline. The who qualifies page sets the baseline: 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license and an authorized sponsor.
Use the P-A-R-T screen on a single plant or business unit:
- Paper trail: are A3s or event reports stored in a shared drive, SharePoint library or lean management tool, not on walls or in personal folders?
- Alignment of data: do reports cite measured baselines and results, not just opinions?
- Repetition: have there been dozens of events across several years, rather than three in a single burst after a consultant visit?
- Traceability: can a report be connected to its action tracker, the affected process and the later audit?
SharePointA company that passes three of four is worth a conversation. A company that passes only the first has pictures of whiteboards, which are a weak starting point.
When in the hold period should you raise it?
The lean calendar gives natural openings.
| Moment | Why it works | Question for the plant or COO |
|---|---|---|
| Annual hoshin or operating plan review | Improvement archives are being summarized for the board | Where do all of last year's event files live? |
| Change of lean lead or consultant | Institutional knowledge is about to walk out | Is the archive complete and exportable before the handover? |
| Plant consolidation or closure | Local shared drives are at risk | Who will preserve the event library from the closing site? |
| ERP or MES migration | Baseline data sits in the old system | Which event files reference data we will lose? |
| Pre-exit data room build | Buyers ask what the business owns | Do we want to treat the archive as a licensable asset before the process starts? |
If the company is already in a sale process, coordinate with the deal team and advisors first so that any license fits the transaction.
What are the rights and confidentiality traps?
Most kaizen files belong to the company that created them, which makes them cleaner than many other record types. Four issues come up in practice.
- Customer-specific content. Events run for a named customer may embed that customer's drawings, specifications or pricing. Those files may need customer consent or removal.
- Consultant materials. Templates and training decks from an outside lean firm may carry the consultant's copyright. The company's own event data is separate from the consultant's method documents.
- People data. Team rosters, performance remarks and safety incidents may include personal information. Redaction rules are agreed with the company before any work begins.
- Safety and regulated processes. Events touching incident investigation or regulated quality systems may sit under separate retention or reporting rules.
Where a file mixes these, the company usually licenses the clean subset. The first article inspection reports page covers a neighboring record type with stronger customer-ownership concerns.
How does the introduction work without anyone handling data?
You introduce; you never touch the files.
- You register and share a referral link, or submit the company through the referral form.
- SourceX qualifies the company on size, history, data breadth and rights, speaking with the sponsor.
- The company completes a data inventory describing where event files live, how many years they span and what can be exported. The data inventory builder helps list systems and records.
- Price and terms are agreed with the company before buyers see anything.
- AI labs and data buyers review; once a company is deal-ready, buyers typically respond within about two weeks.
- The deal closes, data is delivered under the agreed redaction rules, and the company is paid. Your reward follows only after SourceX receives payment.
Nothing is binding until the company agrees price and terms and signs. De-identification requirements are settled up front, and delivery happens only after an executed agreement and the company's authorization.
How do improvement records compare with other workflow data?
Kaizen files show planned, deliberate change. Exception handling shows what happens when a process breaks, which is what the guide on exception handling records covers. Complaint logs link a customer problem to a response, and the complaint handling records page explains how those differ. A company holding all three gives a buyer planned improvement, reactive resolution and customer-facing outcomes in one relationship. For background on the category, see what AI training data is.
What to say to a plant leader or CEO
Keep it factual and avoid promising an outcome. Do not ask anyone to send you reports; the screening call needs only a description of where files live.
How rewards work for a sponsor
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. Because the reward comes out of SourceX's fee, the plant sees no change to its price. Sponsors should check their fund documents and firm policies on fees tied to portfolio companies, and read the program terms.
When kaizen records are not worth pursuing
- The program is new, with only a handful of events.
- Files exist only as photographs of boards or in paper binders nobody can scan.
- Most events were run by a customer's supplier-development team, and the customer owns the output.
- The archive was deleted in a system change.
- The owner will not consider an exclusive license for an agreed term.
Next step
Pick one plant with an active lean program and run the P-A-R-T screen this week. If it passes, register as a partner and make the introduction, or have the CEO apply directly at sourcex.si/apply using your referral link.