Your senior shift supervisor knows which machine runs hot in the first 20 minutes. Your head of procurement knows which supplier quote always comes in low and why that is a problem. Your best dispatcher knows the two customer orders that always ship wrong if they go to the same carrier. None of this is in your ERP, your wiki, or your SOP. And it is all leaving.
Fortune named the bottleneck. In May 2026, Theo Saville wrote that the real constraint in American manufacturing isn't machines or capital: it's the knowledge embedded in the people who run them. The piece triggered a conversation operations leaders have been avoiding: that the most expensive thing in a plant isn't the equipment. It's what leaves with the operator.
This post is not a summary of that reporting. It is about the operational infrastructure that addresses what Saville identified.
The scale of what's leaving
The workforce transition is not hypothetical: the numbers define a specific, measurable exposure window for every manufacturing and distribution operation running today.
The operator who knows why Line 3 slows on humid days. The dispatcher who knows this customer's dock closes early on Fridays. The warehouse lead who knows the carrier's escalation shortcut when a pickup is missed before 8am. The plant supervisor who spent 20 years learning which supplier relationships need personal attention and which can go through the standard portal.
None of that is in an SOP. None of it is documented anywhere. And all of it is walking toward the exit.
In logistics and distribution, the problem hits with equal force: supplier recovery protocols after a disruption, freight routing exceptions for specific lanes, ERP workarounds for edge-case orders that would otherwise stall, customer-specific handling requirements that predate the current contract. The experienced dispatcher doesn't look this up: they know it. When they leave, no one does. The next disruption finds the gap.
Why traditional documentation systems fall short
Traditional documentation systems fail in operations because they require workers to know where to look and what to search for: precisely the institutional knowledge they don't yet have.
This is not a criticism of SharePoint, Confluence, manual SOPs, or video libraries. These are real investments made with genuine intent. The problem is structural, and it has three roots:
Not accessible at the point of work. A technician diagnosing a line stoppage does not open SharePoint. An operator handling a first-time exception mid-shift doesn't pause production to search a wiki. The knowledge may exist, but it is not available at the moment the decision happens. No context switching occurs during production.
Not embedded in workflow. Knowledge stored somewhere is not the same as knowledge used when it matters. Traditional systems require a separate action: open a browser, navigate, search, read. In active production and logistics environments, that step doesn't happen.
Documentation stops improving after it's written. Most SOPs are created once and drift from actual practice within months. Operations evolve. Documentation doesn't. Eventually, teams stop trusting it, and stop contributing to it.
Operational governance before the exit
Operational continuity is not just a documentation problem. It is a governance problem. Knowledge capture only works when it starts early enough, tracks against real progress, and escalates when it stalls. That requires a system running continuously in the background: not a project someone has to remember to launch.
This is what a knowledge continuity governance workflow can look like, each stage triggered by an operational event, tracked in Teams, requiring human sign-off before it closes:
We follow how plant and operations leaders describe retirement risk, in the sources this article cites. Across them, knowledge capture starts too late and stalls with no one tracking it. We are using that pattern to shape OpsGrid, our decision infrastructure for Business Central. What OpsGrid runs today in its beta, and what is on its roadmap, is listed on the OpsGrid page.
Teams using structured knowledge transfer protocols report meaningful reductions in troubleshooting escalation time and improved shift-to-shift consistency, reducing dependency on senior operators during handovers and shortening the window between a question arising and a reliable answer being found.
QHub Wiki: knowledge at the point of work
QHub Wiki is a self-hosted, open-source AI knowledge base built on WikiJS and Qdrant vector search, accessed via a Chrome extension from any browser tab: no new app, no new login.
The distinction from traditional wikis is not the interface. It is where the knowledge surfaces and how it answers.
The same architecture that handles machine maintenance queries on the plant floor handles equally high-value knowledge across logistics and distribution operations:
- Warehouse slotting knowledge: which lanes are configured for oversized pallets this week, and why
- Carrier escalation workflows: which rep to call when Carrier X misses a pickup before 8am on a Friday
- Dock scheduling exceptions: how Customer Y's Tuesday receiving window actually works in practice versus the contract
- Customs and compliance handling: correct classification when a specific product ships to the EU under current rules
- Customer-specific operational nuances: the account details that exist only in an experienced dispatcher's memory
New hire ramp time from 8–12 months to under 90 days when SOPs are structured and semantically searchable. The knowledge that previously required asking a senior operator is retrievable in under 10 seconds, available to any team member, on any shift, from any location on site.
QHub Wiki is infrastructure you own. That distinction matters when your operations depend on it, and when your IT and OT security requirements make external data hosting a non-starter. For mid-market operations specifically (where budget and implementation timeline determine whether a knowledge system actually gets deployed), see The mid-market knowledge problem that enterprise software won't solve.
Before and after
When knowledge capture is governed and knowledge is searchable at the point of work, the operational shift is visible within the first quarter.
Frequently asked questions
Self-hosted, open-source. Deploy in 45 minutes. No monthly subscription. Unlimited users. Semantic AI search built in.
Get QHub WikiDecision infrastructure embedded in Microsoft Teams. Human-in-the-loop governance for Dynamics 365 operations. Now in live beta.
Explore OpsGridFortune named the problem. We built the infrastructure.