More than 30 million Americans will reach retirement age by 2030, and the workers leaving carry a disproportionate share of what their organizations know. Estimates put the lost economic output at $6.9 to $9.6 trillion. The scale is hard to overstate, but the real risk is what those numbers represent: decades of accumulated judgment, relationship context, and operational knowledge concentrated in people who are heading for the door.
Despite widespread awareness, 92% of organizations still fail to consistently capture knowledge from soon-to-be retirees. The problem is well understood, but the response, in many organizations, has barely started.
Improved documentation can play a role. Knowledge bases, exit interviews, and recorded institutional history all help capture what can be written down. But the deeper issue is workforce architecture, including how you hire, how you structure teams, and whether your planning horizon extends far enough to see departures coming before they happen.
The most valuable institutional knowledge is the kind that accumulates over years of doing the work. It consists of judgment calls, relationship context, and the understanding of why a process exists and how to adapt it when conditions change. Researchers call it tacit knowledge, and it lives almost entirely in people's heads.
Most preservation efforts focus on explicit knowledge, the procedures and documentation that can be written down and transferred. But the majority of what makes experienced workers effective is built through repetition, improvisation, and exposure to situations that never made it into a handbook. When those people leave, the organization loses knowledge it didn't know was concentrated in one place.
Replacing an employee can cost 50% to 200% of their annual salary depending on their level, and that estimate doesn't account for the months a new hire needs to reach full productivity. More than a quarter of U.S. workers aged 55 to 64 have been with their current employer for 20 years or more. That kind of depth, spread across relationships, systems, and institutional memory, doesn't reconstitute when a new hire reads the onboarding docs.
When someone in a critical role gets a better offer and is gone in two weeks, that knowledge loss is sudden and unavoidable. But a lot of institutional knowledge loss follows patterns that organizations could plan around if they were watching for them.
Only 20% of HR leaders say they have leaders ready to fill their most critical roles, and most succession planning that does exist focuses on the C-suite rather than the operational and technical positions where institutional knowledge concentrates. Effective knowledge preservation starts while the departing person is still in the building, ideally three to five years before a planned retirement. That lead time is what turns a backfill into a true knowledge transfer.
Even when departing workers are replaced, the replacements are unlikely to rebuild the same depth of knowledge. Median tenure across the U.S. has dropped from 4.6 years to 3.9 years over the past decade, and for workers ages 25 to 34, it sits at just 2.7 years. Fewer people are staying long enough to accumulate deep institutional knowledge in the first place, and when organizations don't invest in growth and development, their most capable people leave for roles that offer it, taking institutional context with them.
Some roles are built to turn over, which means the knowledge loss that comes with them is predictable. "Every 18 months a DevOps engineer leaves their job," says Chris Walek, VP of Sales & Operations at Motion Recruitment, a Kelly company. "Why? Because they did everything that you thought could be done and now they're bored."
Walek is describing a pattern that extends well beyond DevOps. Cloud migrations, platform builds, and other project-scoped work attract senior talent who solve the hard problem, automate what they can, and move on when the interesting work is done. The knowledge they built about your systems walks out on a schedule you could have predicted at the scoping stage. Organizations tend to treat this turnover as individual attrition, when it’s really a foreseeable knowledge event built into the engagement model.
The most effective knowledge preservation looks a lot like workforce planning. It’s built into three decisions organizations tend to treat separately: how you hire, how you structure teams, and how far out you plan. We asked workforce leaders across the Kelly network to share strategies they’ve seen work.
Walek, whose team at Motion Recruitment places senior technical contractors, sees a missed opportunity in how most organizations scope those engagements. The typical brief focuses on delivering a specific capability. But when the scope also includes mentoring permanent team members, the contractor transfers knowledge in real time.
The 3+1 model. Walek recommends pairing three junior-to-mid-level permanent hires with one senior contractor whose deliverables explicitly include developing the team. "Part of that contractor's role is taking that group of three through everything that they're fixing and doing," Walek says. "All of that knowledge transfer is happening in real time over six months to a year." The numbers will vary by team and budget, but the principle holds: the premium rate you pay for a senior contractor is also buying institutional knowledge that stays with your permanent team, as long as mentoring is part of the deliverable.
Too many succession plans are built around org charts, designed to replace titles rather than capabilities. Amie Butchart, Director of Science, Engineering, and Technology at Kelly in Canada, recommends starting further upstream. "You need to forecast out three to five years and look at where those shortages are going to come in," Butchart says. "Who do we have that may be retiring? Where would our risk be if these particular people left the organization? And who's interested in upskilling that maybe just hasn't put their hand up?"
Many workforce plans only account for permanent headcount. Contingent workers, contractors, and project-based consultants carry institutional knowledge too, and when they're excluded from planning, the organization has no strategy for what happens when their engagements end.
Matt Yeager, who leads enterprise sales at KellyOCG, has seen what happens when organizations learn this the hard way. One company cut its contingent workforce from 45% to 6% and discovered it had eliminated the pipeline that had been converting contractors into permanent hires, carrying accumulated knowledge with them. "They found themselves in a bit of a pickle," Yeager says, "because a lot of that contingent labor, their practices had been basically hiring from a contingent or temporary perspective and then hiring those employees six months down the road." Without that feeder system, the organization lost both the immediate capacity and the conversion path that had been sustaining its knowledge base.
The first step is an audit. Map the roles in your organization where institutional knowledge is most concentrated, identify who holds it, and assess how exposed you would be if those people left. Regular, voluntary career conversations give people room to share their plans on their own terms, and contract end dates and workforce-wide tenure trends show where knowledge is draining on shorter timelines.
From there, build transfer into how you structure teams and scope engagements, extend your succession planning to cover capabilities rather than titles, and make sure your workforce plan accounts for every labor category carrying institutional knowledge, not just permanent headcount.
Kelly works with organizations to identify where knowledge risk sits in their workforce and build the team structures, hiring models, and succession plans to address it before the loss occurs. Start a conversation with the Kelly team about where your knowledge risk sits.