The Unlicensed Asset: What Digital Transformations Get Wrong About Legacy Knowledge Retention

What Digital Transformations Get Wrong About Legacy Knowledge Retention

The transformation story always has the same cast. There is the bold new platform, the eager implementation team, and somewhere in the background, a person whose stomach quietly drops when the announcement goes up on the intranet.

They have spent years building something with no official name and no budget line: institutional knowledge. The project plan has no column for it. This is where most digital transformations begin to fail.

The conventional post-mortem for a failed transformation focuses on vendor selection, change management methodology, or executive buy-in. All valid problems. Yet the failure mode that shows up most persistently, and gets discussed least openly, is simpler and more expensive. Organisations treat expert knowledge as technical debt. Then they discover, too late, that it was load-bearing infrastructure.

When Expertise Gets Misread as Overhead

Consider what legacy expertise looks like from the inside. The accounts payable manager who knows which vendor routinely mislabels freight charges. The operations coordinator whose workaround prevents a quarterly reconciliation from taking two extra days. The field technician whose mental map of equipment failure patterns has never been written down because no system could hold it.

None of this appears on a skills inventory. None of it transfers automatically to a new ERP or CRM. And all of it carries significant economic value that organisations systematically strip out during their most expensive change programmes.

Prosci's change management research consistently shows that projects with excellent change management are six times more likely to meet their objectives than those without it. Yet most change management investment still focuses on communication plans and training schedules, not on extracting and migrating tacit knowledge. The result: a well-communicated transformation that still underperforms because the expertise that made the old system functional was never converted into anything the new one could use.

The NHS National Programme for IT offers one of the clearest documented cases. At an estimated cost of £10 billion before cancellation in 2011, the programme's failure attracted many explanations. One thread ran through nearly all of them: clinical staff who held deep, context-specific process knowledge were treated as obstacles to standardisation rather than as experts whose input could have shaped more workable implementations. Their disengagement was not irrational. It was a measured response to a clear signal.

The Rational Mechanics of Resistance

When experienced people look at a new system and find no obvious place for their expertise within it, they are reading the situation correctly. The message embedded in most transformation programmes is: your value was in your mastery of what we are replacing. From there, disengagement is just self-preservation running at full capacity.

IBM's Institute for Business Value found that 60% of employees would engage more actively in digital transformation if their knowledge and experience were formally recognised in the process. That is a significant latent resource sitting unused. It also means that most organisations are structuring their programmes in a way that signals devaluation rather than evolution, and then wondering why adoption curves stay flat.

This connects directly to what we explored in The 90-Day Reset: organisations that recover operational momentum fastest after a major change consistently treat experienced staff as diagnostic assets rather than as change management problems to be managed.

The Tacit Layer Nobody Budgets For

The knowledge management literature draws a useful distinction: explicit knowledge, which is documented, transferable, and searchable, versus tacit knowledge, which is learned through experience, contextual, and difficult to articulate without prompting. Most transformation programmes budget for migrating explicit knowledge. Tacit knowledge gets left behind by default.

In knowledge-intensive industries, tacit expertise is often the mechanism by which organisations outperform competitors running the same tools and processes. Research published in the Journal of Knowledge Management links tacit knowledge retention to sustained competitive advantage, particularly during periods of rapid technical change.

Boeing's decade-long push toward cost reduction and process standardisation included significant workforce restructuring that dispersed experienced engineering expertise. Multiple investigations into design and safety processes noted the reduction in institutional knowledge as a contributing factor to systemic failures. The knowledge did not disappear because people refused to share it. It disappeared because the systems around them had no mechanism for capturing what experienced engineers held in their heads. That is a design failure, not a culture failure.

The implication for transformation leaders is specific: the risk register needs a line item for tacit knowledge depletion. Most do not have one.

Legacy Knowledge Retention as a Risk Management Discipline

The framing shift that changes how this problem gets solved is straightforward. Digital transformation is a technical migration and an identity migration, simultaneously. The expert who built their professional value through mastery of the old system needs a credible, respected role in the new one. Without that, disengagement is the inevitable outcome. It arrives quietly, through slower hands and selectively forgotten context, long before it shows up in adoption metrics.

Three structural interventions make this work in practice.

The Certification Assignment

Assign legacy experts to certify that the new system handles the organisation's five most complex or highest-risk business rules correctly before go-live. This reframes their expertise as a launch requirement rather than a legacy liability. Their knowledge becomes a quality gate, not an obstacle. Procter & Gamble's "Connect + Develop" open innovation model offers a parallel: experienced internal knowledge holders were repositioned as connectors and validators. The programme contributed to P&G's innovation output doubling between 2000 and 2006.

The Formalised Role

Create named, time-bound roles within the transformation structure: Institutional Knowledge Champion, Historical Process Validator, Legacy System Translator. The title matters less than the signal it sends. Expertise is being built into the transformation architecture, not left to self-organise around its own obsolescence.

Recognition Tied to Transfer Outcomes

Tie performance recognition to knowledge transfer outcomes rather than adoption metrics alone. When an incentive structure rewards an expert for successfully documenting and handing off a complex process, sharing knowledge becomes professionally advantageous. When the only metric is adoption speed, experienced users have no structural incentive to explain what they know. The organisation ends up with no mechanism for capturing it either.

Measuring Knowledge Transfer Success

The knowledge migration challenge is more measurable than it appears. KPIs worth tracking across a programme include: undocumented process exceptions captured before system cutover; reduction in post-go-live support tickets that reference legacy process logic; time-to-competency for new users on complex business rules; and expert engagement scores tracked across the transformation timeline rather than only at go-live.

Gartner's research on ERP implementations found that organisations with structured knowledge transfer programmes experience 30–40% fewer post-go-live operational disruptions than those without. That number translates directly into cost: fewer escalations, less emergency remediation, faster stabilisation, and an ROI curve that resembles the one in the business case.

The 2009 spreadsheet in the finance team holds knowledge. Treat it as an artefact worth interrogating, not an embarrassment worth deleting.

What This Changes for Transformation Leaders

Transformation programmes need a knowledge architect role sitting alongside the project manager and the change lead. This person's job is to identify where tacit expertise creates value, map the people who hold it, and design the interventions that migrate that value into the new architecture before the old one is retired. The discipline sits at the intersection of organisational design, knowledge management, and risk, and it is underrepresented in almost every programme structure currently in the market.

This is a risk management discipline, full stop. The organisations treating it as one consistently close the gap between projected and delivered transformation ROI. Those treating it as a cultural nicety continue to pay for that choice in the stabilisation phase, when it is too late and too expensive to fix.

Vendors are starting to talk about "knowledge continuity" as a deployment success metric. Change management consultancies are building tacit knowledge extraction into their standard methodologies. The organisations whose programme structures already reflect this are building a competitive advantage that is genuinely difficult to replicate. By definition, it is locked inside the people who chose to stay and share.

For a related read on how enterprise operational intelligence systems support this kind of structured knowledge capture, see our post on Operational Intelligence Systems and Process Architecture.