What is operational knowledge capture?

Operational knowledge capture is the discipline of getting tacit, experience-based expertise out of practitioners' heads and into formats that can be taught, audited, and used by others. In public services — and especially in policing — it is what stops decades of operational judgement walking out the door with the people who hold it, and what makes training, technology adoption, and reform actually land.

What is operational knowledge capture?

Operational knowledge capture is the structured practice of surfacing the tacit knowledge that experienced practitioners use to do their job well — the judgement calls, the heuristics, the workarounds, the "why we actually do it this way" — and converting it into a form other people can learn from, audit, or build into a system. It sits between subject matter expertise and formal training: closer to the work than a curriculum, but more transferable than what lives in one person's head.

Why does it matter in policing and public services?

A large share of operational competence in policing, the NHS, and the wider public sector is held tacitly. It was learned on shift, alongside more experienced colleagues, under real conditions. When those people retire, move forces, or leave the service, that knowledge usually goes with them. The result is forces that re-learn the same lessons every few years, training programmes that miss what actually matters at the front line, and digital transformation projects that fail because the underlying operational logic was never written down.

How is it different from documentation or SOPs?

Standard operating procedures describe the official process. Documentation describes the system. Operational knowledge capture describes what experienced practitioners actually do — including the things that diverge from the SOP because the SOP doesn't fit the situation, the cues they read off a scene or a system that aren't written anywhere, and the decisions they make in seconds that would take a new joiner weeks to reason through. It is the layer underneath the documented process.

What does the process look like in practice?

Done well, it combines structured interviews with operational practitioners, observation of work as it happens, scenario walk-throughs of consequential decisions, and triangulation across multiple experienced people to separate personal preference from genuine craft. The output is usually a mix of teachable artefacts: decision frameworks, annotated case studies, role-specific playbooks, and content that can feed directly into training, system design, or AI tooling.

When is operational knowledge capture the right intervention?

It is the right intervention when an organisation is about to lose experienced people, is rolling out new technology that will only land if existing practitioner judgement is preserved, is redesigning a training programme that currently teaches the official process but not the real one, or is responding to inspection findings that point at a gap between policy and frontline practice. It is the wrong intervention when the problem is genuinely structural — workload, resourcing, governance — and no amount of better-captured knowledge will fix it.

How does it relate to AI adoption?

AI tools in public services are only as useful as the operational judgement embedded around them. Capturing how experienced practitioners actually make decisions is what makes it possible to design AI workflows that augment rather than replace that judgement, to write prompts and guardrails that reflect real operational risk, and to train users on what the tool is genuinely good and bad at in their context. AI adoption programmes that skip this step tend to produce either rejection or over-reliance — both of which damage operational performance.

Who at EnlightenWorks works on this?

Operational knowledge capture has been part of EnlightenWorks' core practice since the firm was founded in 2013. It runs through our L&D design, our work on AI-enabled skills and adoption programmes, and the integration layer between strategy and frontline delivery. If you are facing a knowledge-loss risk, a transformation programme that depends on existing practitioner expertise, or a training redesign, we'd be glad to talk.