Most knowledge crises do not announce themselves. They build quietly — one undocumented workaround at a time, one long-tenured employee closer to the door — until a retirement notice lands and the department realizes how much was being held together by one person's institutional memory. The signs are visible before the crisis. You just have to know what to look for.
Sign 1: There Is One Person Everyone Goes to With Questions
You know who this person is. So does everyone on your team. They may not have the highest title. But when something comes up that nobody knows how to handle — an unusual permit situation, an edge case the policy manual does not cover, a vendor relationship that needs navigating — there is one person who gets the call.
That person is your department's single point of failure. In software engineering, this is called a bus factor of one: if that person disappears tomorrow, operations degrade immediately and significantly. What to do: name the person, then ask what they know that no one else does. Which decisions do they make that others cannot? Which processes stop when they are on leave? That list is your knowledge risk inventory.
Sign 2: Your Process Documentation Lives in a Shared Drive Nobody Opens
Ask yourself three questions. When was it last updated? Can a new employee find what they need without asking someone? Does it document what people actually do — including exceptions, workarounds, and judgment calls — or only what the policy says they should do?
"SharePoint folders with cryptically named PDFs no one ever opens" is how one government professional described their documentation on GovLoop. The response from peers was recognition, not disagreement. A folder stores the file. It does not preserve the judgment behind it.
Sign 3: You Have Retirement-Eligible Employees and No Succession Plan
Most administrators know which employees are approaching retirement. The awareness-to-action gap is where the damage occurs. Succession planning in government has historically meant identifying who will fill the role. That is necessary. It is not sufficient.
A succession plan that addresses headcount but not knowledge continuity is not a succession plan. It is a hiring plan. What to do: for each retirement-eligible employee, write down two things — who replaces them, and what they know that is not documented anywhere. If the second list is blank, your succession plan is incomplete.
Sign 4: Institutional Memory Is Older Than Your Documentation System
Why is this policy worded this way? Why does the approval always go through that office? Why does the agency always call that state contact and not the listed number? The answers exist in the memory of the people who were there when the decision was made. When those people retire, the answers retire with them.
Ask your most senior employees why three things in your department work the way they do. Pay attention to how much of the explanation is "because of something that happened a long time ago." That is tacit institutional history. It is valuable. It is at risk.
Sign 5: New Hires Still Struggle After Six Months
If a new employee is still regularly asking basic operational questions six months in, the problem is usually not the employee. It is the absence of a knowledge transfer system. New hires in government learn one of two ways: from documented guidance they can access on their own, or from colleagues who remember what the previous person used to do. The first is scalable. The second is not.
Track time to independent performance for new hires. If it consistently exceeds six months, interview both the new hire and their manager. You will find the same themes: undocumented exceptions, unclear contacts, processes that exist in practice but not on paper. Those themes are your capture priorities.
What To Do If You Recognized Your Department
If two or more of these signs apply, you are not in unusual company. The path forward is sequential. Name the risk — identify which roles hold the most concentrated, undocumented operational knowledge. Act before the notice — effective knowledge capture requires time and access, which means starting months before departure, not after the announcement. Build something usable — captured knowledge is only valuable if the next person can find it and act on it in under two minutes.
The knowledge cliff is visible before you reach it. That is the point.