Skip to content
Enter IPI

Operational memory from real work

Find the handover gap while the person who knows is still there

“Everything is in the folder” is the beginning of a handover, not its finish. Give the new employee one realistic job and see whether they can choose the next step from what you have supplied. Their first hesitation shows which explanation needs to stay before the experienced person leaves.

IPIUpdated October 3, 20263 min read

A complete folder can still leave the first order waiting

Imagine Anton takes over supplier ordering from Mei. He has the order template and the contact list. His first order arrives just after a supplier’s weekly cutoff, so it will miss the date the customer needs.

Mei always checked that supplier’s cutoff before promising a delivery date. The fact was in an old email. The reason to check it was in Mei’s head.

A handover built around Anton’s first order would expose the gap quickly: which date can he promise, and what does he need to verify first?

Give the newcomer a small pack they can use

For Anton, the trap is the weekly cutoff. A general instruction to “check delivery” is weaker than a real example showing how the order date changed the customer’s start date.

  • The current steps for the job and who keeps them up to date.
  • A completed example with a short explanation of why it worked.
  • One familiar trap, including the detail that reveals it.
  • The files and access needed to do the work.
  • The person who decides when a new situation changes the promise.

Ask for a proposed action, not “Does that make sense?”

Give Anton a sample order and ask which delivery date he would offer. Let him find the answer before Mei explains. If he has the information but cannot see why it matters, improve the example. If he understands but cannot find the source, fix the path to it.

Then change one fact. A customer needs an unusual delivery schedule. Does Anton recognize when the normal rule is insufficient and who must decide? That is stronger evidence of a useful handover than a read receipt.

Keep producing knowledge after the handover meeting

Trainual’s guide to knowledge transfer before a departure recommends capturing the reasoning and relationship context alongside procedures. The enduring benefit comes when that capture continues during ordinary work.

In IPI, employees propose jobs, receive responses and submit results for checking. The owner can follow the work without personally conducting every clarification. A useful lesson discovered in that flow can become part of Inherited Will.

Bring the previous attempt into the newcomer’s next job

Once Anton is set up to receive relevant teaching, Inherited Will can bring lessons from available earlier work to his next proposals before he carries them out. He can learn why the cutoff mattered and plan the right check.

Mei’s departure then does not have to erase the understanding already captured. The owner still handles new commercial choices, but has fewer old explanations to recreate.

After Anton’s first order, keep the question the handover missed. The next new employee should inherit that improvement too.

Make the handover useful in the work itself

See the IPI overview, then bring a first job and the earlier lesson that should help with it. Judge success by what the newcomer can do with less help.

See how IPI works