There's no substitute for expert know-how, but how do you share it effectively?
Completely fictitious case study: You are the founder and director of BrouetteCorp, the Limousin-based market leader in connected three-wheel wheelbarrows.
Jean-Philippe, aged 54, has been the in-house expert for twenty years on one of your key processes: wheel rounding. He set it up, and he alone knows all the details. He's very efficient and rather helpful, though not with everyone. During meetings, he brings up problems with rubber vulcanization that nobody understands, only to explain after half an hour of collective panic how he's already solved them, for which he is congratulated.
Jean-Philippe is not yet a problem for your organization: he's meeting his targets, production has never been so fast, and the wheels are so round.
But what happens if he falls ill? If he leaves the company? Or simply if his commitment wanes?
You have already tried to convince him to formalize his know-how in one (or several) Word documents, in Notion, in Excel, in Powerpoint... Without success: "no time with the production to ensure", "too complicated to synthesize"...
You gave him an intern, then a deputy, with the secret mission of doing this formalization work. They left, disgusted, because he didn't delegate much to them and didn't explain anything. "Oh, by the way, it's not up to date, we've customized the product a lot".
You began to suspect that Jean-Philippe was a little reluctant... unless it was a fear of losing his central position in the company if he shared his knowledge?
But what to do?
"With Komin, we have documented our operating procedures 10x faster than with paper"
- J. Cerruti (Methods & Industrialization Manager)