When your best man leaves, his knowledge leaves too.
Half a day with your leadership. No sales talk, no software pitch. We show where your business is vulnerable and work out with you the conversation guide for talking to your knowledge holders about it, without it sounding like a goodbye.
Half a day, on site with you, at a fixed price. If a pilot project follows, half of it is credited.
No backup in place
Partly secured
Diagnostic tree documented, backup in place
The situation in German mechanical engineering
- of business-critical knowledge sits in heads, not in systems
- 60–70 %
- a new technician needs without predecessor knowledge to work independently
- 6–12 mo
- knowledge transfer without a system when someone resigns unexpectedly
- 0 %
The reality
Knowledge does not disappear loudly. It disappears quietly.
The wiki problem
Wikis and Confluence fail because technicians do not write there. Not because they do not want to, but because their knowledge arises on the job, not at a desk.
The ERP problem
ERP and ticket systems document processes, not the why behind them. What Thomas solves in 25 minutes is in no ticket.
The AI problem
Even the best AI can only find again what was made explicit beforehand. Knowledge is not demanded. It is captured where it arises.
Half a day, four steps
What happens in your business.
No standard programme. No slide deck from us. A facilitated working day about your business, with your people.
01
The starting point
Why knowledge quietly disappears, why previous tools change nothing about it, and which questions every business must answer first.
02
The knowledge map
Which machines, customers and fault patterns hang on individual people. Who leaves in the next five years. Where there is no second head.
03
The conversation with the knowledge holder
The part where most initiatives fail, because knowledge feels like bargaining power. This is where the conversation guide for your most experienced technician takes shape.
04
Next steps
One starting metric, one owner, one date. Usually the first diagnostic-tree workshop with three technicians on a real fault pattern.
The sore point
Sharing knowledge feels like self-abolition to your best people. And rightly so.
Force achieves the opposite. Order documentation and you get work to rule. Knowledge is collected, not demanded. The workshop works out what a knowledge holder gets back for it.
Legacy instead of loss
Those who pass on their knowledge do not experience their own departure as a loss of significance, but as a lasting mark in the company.
Reputation instead of replaceability
Whoever's solutions the whole team uses has their name on them. Visibility in the business is a currency that is underrated.
An advisory role after retirement
Those who leave their knowledge behind in a structured way have afterwards the strongest case for an advisory fee, and during their working life the better negotiating position.
The time factor
What you capture today, your company still carries in five years.
Every year without a system costs
A knowledge holder who resigns unexpectedly can still be captured to 60 to 70 percent within four weeks if a system is ready. Without a system, zero percent remains.
The Digital Product Passport becomes mandatory
From 2027 the EU requires maintenance and lifecycle data to be available in machine-readable form. Those who start today are then compliant with no retrofit effort.
Next step
We support you through the change.
No pitch, no slides from us. A facilitated working day about your business, with a knowledge map, a conversation guide and a starting metric as the outcome. Whether you continue with us afterwards or without us.
Half a day, on site with you, at a fixed price. If a pilot project follows, half of it is credited.