Operational memory from real work
The company should keep its understanding when people move on
The shared drive can be full while the business still depends on one employee to explain it. Company memory is useful when a replacement can find the current instruction, understand an earlier exception and decide what to do next. IPI helps keep the lessons created during work available beyond the person who learned them.
The new branch manager inherits a folder and a queue of questions
Imagine Ellen moves from one service branch to another. Her replacement, Mo, receives the opening checklist and the old reports. By Tuesday, Mo has three questions for the owner: why one customer gets a different confirmation, why a supplier is checked separately and whether last quarter’s temporary workaround still applies.
Nothing was deleted. The missing part is the reasoning between the documents. Without it, the owner becomes the person who has to translate the company’s history.
Separate today’s rule from yesterday’s exception
A policy says what the company requires now. A work record says what happened in one case. A lesson explains what someone should notice next time. Keep those meanings clear, even if the information lives in the same system.
If an exception lasted until a supplier fixed its system, leave that condition with the explanation. Mo needs to know why it was reasonable then and what to check now. A dated exception should not quietly become a permanent instruction.
A real company made the experienced person part of the answer
In Cybozu’s Nissan purchasing case, experienced employees checked and corrected system-generated answers so their know-how could improve later responses. The 2025 initiative connected kintone with a separately built system.
The useful detail is the checking. Preserving understanding required more than gathering documents. For Mo’s branch, the same practical question applies: which reason would Ellen need to explain before the next person could use the answer?
Keep learning as the job happens
In IPI, the employee proposes work and receives a response. The submitted result is checked against what was agreed, and the owner or chosen reviewer decides completion. That leaves a work history the owner can read without interviewing each participant.
Inherited Will can retain useful lessons from those attempts and bring relevant teaching to a later employee who has been set up to receive it. Mo can learn why the unusual confirmation mattered before making the same mistake.
Current policies still need an owner who keeps them current. Inherited Will adds the experience from doing the work, so a staff change does not have to erase the explanation behind it.
Try a handover without the usual interpreter
Pick one recurring branch job. Give another colleague its current instructions and a relevant lesson. Ask what they would do, which detail changes their decision and what still needs approval.
Where they need Ellen’s explanation, improve that part. You will learn more from this exercise than from counting how many files were transferred. The goal is a branch that can keep moving with less dependence on one person’s memory.
Help the company keep what its people learn
Watch the IPI overview, then choose a recurring job whose explanation should survive the next handover. Start building the work history the next person can use.