Knowledge management usually splits knowledge into two buckets:

• Explicit knowledge — things that can be written down: procedures, checklists, reports, data. This travels well. You can email it, file it, search it later.
• Tacit knowledge — the experience-based, contextual, often unconscious knowledge that lives in someone’s head. The “why we don’t do it that way,” the pattern recognition built from years of doing the job, the judgment calls. This is exactly what the TV protagonist was worried about losing.

‍

The sad truth is that most organizations are very good at capturing explicit knowledge and very bad at capturing tacit knowledge. A project closes, a case is transferred, an employee leaves — and the parts of the story that mattered most, the ones that would help the next person avoid the same mistake, quietly walk out the door with the person who knew them.

Knowledge that exists but never moves has no operational value. A lesson sitting in someone’s head, or buried in a report nobody reads, is functionally the same as a lesson that was never learned at all.

Why aviation had no choice but to solve this

Most industries can afford to lose a little context in a handoff. Aviation can’t. When the cost of an unlearned lesson is measured in lives, “we’ll write it up eventually” isn’t good enough. That pressure is exactly why aviation has built one of the most mature knowledge-management ecosystems of any industry — worth studying even if you’ve never set foot in a cockpit.

A few of the mechanisms worth knowing about:

Confidential reporting systems. In the US, the Aviation Safety Reporting System (ASRS) is a voluntary, confidential channel that lets pilots, air traffic controllers, cabin crew, dispatchers, and maintenance staff report near-misses and close calls in the interest of improving safety. Crucially, it’s run by NASA rather than the FAA, which gives it the neutrality people need to actually be honest, since NASA has no enforcement power over them. Report something within the right window, and you get limited immunity — the system is built on the premise that a mistake reported openly teaches the whole industry more than a mistake punished quietly. It was created in direct response to a fatal 1974 crash where investigators found that similar warning signs had existed before, but nothing was systematically capturing or circulating them.

Operator-level programs alongside the national one. Airlines run their own internal version, the Aviation Safety Action Program (ASAP), through formal agreements between the airline, employee unions, and regulators. This captures the tacit, day-to-day knowledge — the near-misses that never make headlines — before it’s lost to memory or turnover.

A shared global taxonomy. Different countries and airlines used to describe incidents differently, which made it hard to compare data or spot patterns across borders. ICAO and the European Commission have worked to promote a single shared repository and a common categorization scheme so that all aviation accidents and incidents worldwide can be reported the same way. That sounds like a bureaucratic detail, but it’s the difference between a lesson staying local and a lesson becoming global. Standardizing the “language” of the report is what lets a hazard identified in one country prevent an accident in another.

Institutionalized feedback loops. Incident data doesn’t just sit in a database — it feeds back into training curricula, cockpit procedures, aircraft design, and regulation. Crew Resource Management training, now standard worldwide, exists largely because of hard lessons from accidents where the technical flying was fine but communication and hierarchy in the cockpit weren’t. The knowledge didn’t just get recorded; it got re-injected into the system that produced the next generation of pilots.

The pattern underneath it all

Strip away the aviation-specific detail, and the model is transferable to almost any team, industry or project:

1. Make capturing knowledge low-friction and safe. People share the messy, honest version of what happened only when they trust it won’t be used against them.
2. Capture context, not just conclusions. A checklist item (“check altitude clearance”) is explicit knowledge. The story of why that checklist item exists — the confusion, the assumption that went wrong — is the tacit knowledge that actually changes behavior.
3. Standardize how knowledge is described, so it can be compared, searched, and aggregated across teams instead of staying siloed in one person’s notes.
4. Close the loop. A lesson learned that never gets fed back into training, onboarding, or process design is just an interesting anecdote. It has to change what the next person does.
5. Treat the handoff itself as a risk point. The TV show’s protagonist was right about one thing: transfer is where knowledge degrades. Overlap periods, structured debriefs, and “why” documentation — not just “what” documentation — are how you protect against that.

Knowledge existing in an organization is necessary but not sufficient. What determines whether it actually prevents the next mistake is whether it’s captured with enough context, shared without fear, standardized enough to travel, and looped back into the system before the next person needs it. Aviation didn’t get this right because it’s a more disciplined industry by nature — it got it right because the cost of getting it wrong left no other option. That’s the real lesson for the rest of us: build the system as if the stakes were that high, before something forces you to.

_________________________