Capturing what the last expert knows
When the one person who understands a system is two years from retirement, a structured hour of their time goes further than a year of shadowing.
MKMichael Kofman · Founder, ARC
The single point of failure is a person
Every estate has one: the engineer who knows why the month-end job runs twice, which customer has the special pricing rule, and what not to touch in the claims module. Their knowledge was never written down because there was never time, and now there isn't much time left.
Let the code do the remembering
ARC doesn't ask the expert to write documentation. It reads the system first, extracts the rules and journeys, and then asks the expert to confirm or correct them. Reviewing a rule takes seconds. Writing it down from memory takes an afternoon.
- A short intake. Ownership, users, known issues and what keeps them up at night, captured in a guided conversation.
- Rules to review, not to write. The expert confirms what ARC extracted, and corrects what it got wrong. Every correction is kept.
- Knowledge that outlives the person. An engineering wiki, a cited rule catalogue and decision records the next team can trust.
What you get
Hours, not monthsThe expert's time spent confirming, not documenting.
Rule catalogueBusiness rules cited to source and confirmed by the person who knows.
HandoverA wiki and decision records for whoever comes next.
Timelines depend on access to code and people; we confirm them on the scoping call.