You capture what a retiring technical expert knows by recording their reasoning against real customer questions while they are still answering them, then structuring that know-how so it stays retrievable after they leave. Kimia, a chemical intelligence platform, captures application know-how, formulation history and reasoning, organises it against each product's record, and keeps every answer validated by your own experts.
Exit interviews record information, and an expert's value is intelligence
The instinct when an expert announces retirement is to schedule interviews and commission handover documents. Those record information: the products supported, the open projects, the customer contacts. The expert's value sits a level higher. A viscosity reading on a data sheet is information. Knowing a grade suits flexible packaging lamination is knowledge. Knowing which grade to recommend for a customer bonding polypropylene to aluminium who needs open time under 30 seconds is intelligence, and intelligence is what a document handover fails to carry.
In practice: a handover file lists the dispersions a retiring application engineer supported. It does not record why he steered customers running high-speed lamination towards one polyurethane dispersion and away from a similar grade that fails above 200 m/min, so his successor reruns trials the business had already paid for.
Capture happens while the expert is still answering questions
Succession planning for technical roles usually starts in the final quarter, when the expert's time is shortest and recall is at its weakest. The know-how worth keeping is expressed earlier, daily, in answers to real customer questions. Kimia captures it there. Experts answer through Kimia as part of normal work, each answer is recorded against the products it concerns, and every interaction adds to the knowledge base.
The record builds over years of service rather than weeks of notice.
In practice: a technical service lead with eighteen months to retirement answers rep questions on hot-melt adhesives through Kimia today. Each answer on open time, substrate compatibility and line speed is stored against the grades involved, so her reasoning accumulates while she works instead of surfacing in a leaving interview.
Know-how becomes retrievable when it is structured against the product record
A transcript of an expert's answers is another document to search. Retention comes from structure. Kimia builds a record for each product from existing TDS, SDS and application documents, then attaches the unwritten layer to it: application know-how, formulation history and the reasoning behind past recommendations. A caveat captured once is tied to the grade it concerns, so it surfaces whenever that grade comes up, for any rep, in any region.
In practice: a TDS states a dispersion's viscosity at 3,000 mPa·s and its pH at 7.5. The retiring formulator knows the grade also tolerates hard water in the let-down. Captured against that product's record, the caveat appears every time the grade is queried, long after its author has left.
Expert validation keeps captured knowledge safe to use
Captured know-how carries risk if nobody checks it, because a wrong recommendation fails under customer conditions or regulations. Kimia is designed for verification: every answer draws on your knowledge base with sources for review, and outputs go live only after your own technical experts validate them. Validation is also the highest-value use of a retiring expert's remaining time. Reviewing and correcting answers takes minutes per item and leaves a corrected record behind, where writing documentation from scratch consumes the notice period and still misses the judgment.
In practice: before an answer recommending an alternative plasticiser for an EU application goes live, the expert who owns that product line reviews it against the REACH restriction involved, corrects it and approves it. The correction is retained, so the next person asking gets the corrected answer.
Captured expertise decouples growth from a shrinking expert pool
A chemical company's revenue is tightly coupled to its number of technical experts, and in Western markets that pool is shrinking. A retiring specialist's depth took decades to build, and no replacement arrives with it. Capturing know-how changes what the departure costs. Commercial teams answer customer questions without waiting on technical experts, the captured knowledge serves every region at once, and growth stops depending on the availability of a handful of people.
The expert's judgment keeps earning revenue after the leaving date.
In practice: a rep in her first month fields the question a 20-year veteran used to handle, a replacement for a competitor product in an automotive interior application that must meet EU REACH. The answer comes from the captured record, with sources, before the customer contacts a second supplier.
What changes
Know-how outlives tenure: application reasoning stays retrievable after the expert leaves.
Knowledge retention compounds: every answered question adds to the record.
Faster onboarding: new hires answer from captured expertise in their first month.
Experts freed for expert work: routine technical questions stop routing through specialists.
Succession for technical experts is a capture problem before it is a hiring problem. Record the reasoning while it is still in daily use, and retirement becomes a planned handover.
Customer stories
Kimia is live in production with several enterprise customers, including Bostik, Univar Solutions and Stahl. Univar Solutions deploys Kimia to accelerate technical sales. At Bostik, Aldric Tourres, Global Director of Digital, says: "Kimia has become our partner of choice within Bostik for scaling technical expertise globally."
FAQ
Is an exit interview enough to capture a retiring expert's knowledge?
No. An exit interview records what the expert can recall in a few sessions, and decades of formulation know-how does not surface on request. The reasoning appears when a real customer question demands it, so capture has to happen where questions are answered, over time, while the expert is still working.
Can knowledge capture start with the documents we already have?
Yes. TDS, SDS, application guides and brochures are the starting material, and Kimia consolidates them into a structured record for every product. The expert know-how that was never written down is then captured on top of that record, through the answers experts give and validate in daily work.
Does captured expertise help new salespeople start selling faster?
Yes. A new rep answers from the captured record instead of learning the portfolio one escalation at a time. Questions that once waited on a veteran's availability are answered with sources the rep can check, so onboarding shifts from memorising products to handling customers.
What happens to the captured knowledge when the expert leaves?
It stays in the knowledge base and keeps working. Every answer Kimia gives draws on the captured know-how, each interaction adds to it, and the experts still in the business continue validating what goes live. The departure stops being the loss of a capability and becomes a normal succession event.
Does capturing expert knowledge require an IT project?
No. Kimia is up and running without a single IT ticket raised, and the people involved are the ones who benefit, your product owners and technical experts. The work is consolidating existing documents and having experts validate outputs, which is domain work rather than systems integration.
