By Chris Beckage, Procom Technology Consulting
BOTTOM LINE
Institutional knowledge is part of the implementation plan. Capture it, pair it with the build team and keep the people who hold it through cutover.
Legacy systems hold rules nobody wrote down
Ask how a claim, a billing exception or a policy endorsement gets handled on a core system that has run for decades, and the documented answer is often only part of the story. Over the years, systems pick up rules, exceptions and workarounds that were never formally recorded. The people who run them every day often hold the only complete picture.
That matters most during migration, testing and implementation. If the new platform is built to the documented process rather than the actual one, gaps can surface after go-live, where customers and brokers see them first. Before replacing a legacy system, identify the people who understand how it actually works.
Replacing the technology doesn’t replace the knowledge
A new platform is bought, configured and tested. Business knowledge has to be captured, transferred and checked, and that work often doesn’t get its own owner, schedule or budget in the program plan.
Replacing experienced people mid-program isn’t simple either. The Jacobson Group and Aon’s Q3 2026 study lists technology among the roles carriers find hardest to fill [1]. A program that loses the people who hold its knowledge can find itself short at a critical point.
What to do about it
- Inventory knowledge, not just systems. List who knows what, by system and business function, before the build is scoped.
- Capture the real rules. Have those people walk the new team through actual cases, not the documented process.
- Pair before you cut over. Put someone from the new build alongside each knowledge holder long enough to test what has been learned.
- Keep them through cutover. Treat the time of key people, for a defined period after go-live, as a budget line.
The people who know the old core belong on the program’s critical path. Part of technical debt is knowledge held by a few people, not just old code, and a plan that protects the platform timeline but not that knowledge can finish on schedule and still get answers wrong.
QUESTIONS TO TAKE BACK TO YOUR TEAM
- Who on our team knows how the old system actually behaves, and is that written down anywhere?
- Which processes depend on the old core in ways the documentation doesn’t show?
- How long will we keep key people involved after go-live, and is that funded?
- Which parts of the knowledge work do we keep in-house, and which could a partner own for an agreed scope?
Next steps
Protecting institutional knowledge is essential to a successful modernization. Connect with Chris Beckage to discuss how Procom can help address the expertise and delivery requirements of your next technology initiative.

About the author
Chris Beckage, Vice President, Consulting Services
With over 25 years in the staffing industry, Chris drives Procom’s Consulting Services efforts to expand market opportunities and partnerships across North America.
SOURCES
[1] The Jacobson Group and Aon, “Q3 2026 Insurance Labor Market Study Results Reflect Slowing Turnover and Modest Growth,” August 25, 2026 (press release). https://www.jacobsononline.com/about-us/press-releases/q3-2026-insurance-labor-market-study-results-reflect-slowing-turnover-and-modest-growth/

