How to Capture Tacit Knowledge During Enterprise Change

What happens to critical organisational knowledge when the people carrying it move on?

How to preserve the context, judgement and institutional knowledge that formal systems often miss.

A leadership team sharing analysis and organisational context

The three foundations of effective enterprise change

A useful way to think about enterprise change is as a triangle. At each point sits one of the three forms of knowledge needed to understand the organisation properly.

1. Enterprise data

This includes the formal information the organisation already holds. Examples may include:

  • Business objectives

  • Applications

  • Suppliers

  • Projects

  • Risks

  • Budgets

  • Technology assets

  • Performance measures

  • Architecture

  • Contracts

  • Operating processes

This information is vital. It provides structure, evidence and a basis for comparison. But data usually records only what the organisation has chosen—or managed—to capture.

It may show that a process takes too long without explaining why. It may show that an application is expensive without revealing the undocumented dependencies that make it difficult to replace.

2. Expert opinion

The second point of the triangle is informed professional judgement. This may come from internal specialists, Xirocco advisers or an implementation partner. Experts can:

  • Assess the organisation against recognised practices

  • Identify structural weaknesses

  • Challenge internal assumptions

  • Compare the organisation with other environments

  • Interpret complex technical and operational evidence

  • Recommend actions based on wider experience

This perspective adds depth beyond formal records. But even the most experienced external adviser cannot immediately know everything that employees have learned through years of operating within the organisation.

3. Tacit knowledge

The third point is the knowledge held in people's heads. It includes the unwritten explanations, instincts, memories, relationships and practical understanding that employees rely on every day. This may include:

  • Why a process works in a particular way

  • Why a previous change failed

  • Which system is more critical than its documentation suggests

  • Where unofficial workarounds exist

  • Which supplier relationships are difficult

  • Who people rely on when something goes wrong

  • Which decisions are shaped by organisational politics

  • Where leadership ambition conflicts with operational reality

  • Which cultural barriers will affect implementation

  • Why certain risks are tolerated

  • Which dependencies have never been documented

This knowledge is often essential to successful change. Yet it is also the least systematically captured.

Why data and expert opinion are not enough

A change programme may have accurate data and experienced advisers and still fail.

That happens because organisations are not purely mechanical systems.

They are shaped by history, culture, trust, informal influence, local workarounds and decisions made under conditions that may no longer exist.

For example, the data may show two applications performing similar functions.

An external assessment may therefore recommend rationalising one of them.

But employees may know that one application supports a critical exception process, contains historic records that cannot easily be migrated or is relied upon during operational failure.

Without that tacit knowledge, a technically logical recommendation may create serious disruption.

The same applies to:

  • Operating-model redesign

  • Supplier consolidation

  • Application modernisation

  • AI adoption

  • Cost reduction

  • Process standardisation

  • Organisational restructuring

  • Cybersecurity remediation

The formal picture may be accurate but incomplete.

Why tacit knowledge is difficult to capture

Tacit knowledge is rarely stored in a form that can be searched or analysed.

It may emerge only through:

  • Informal conversations

  • Workshop discussion

  • Personal stories

  • Frustration

  • Historical explanation

  • Professional instinct

  • Local language and shorthand

  • Observation of how work is actually performed

Employees may not recognise what they know as strategically important.

The knowledge may feel too obvious to mention.

It may also be sensitive.

People may hesitate to document views about:

  • Culture

  • Leadership

  • Politics

  • Decision-making

  • Organisational resistance

  • Supplier performance

  • Poorly designed processes

  • Unofficial workarounds

Traditional questionnaires often make the problem worse by forcing nuanced experience into binary or overly structured answers.

A person may be asked whether a process is effective and given only a rating scale.

The useful answer may actually be:

"The process works for standard requests, but senior stakeholders regularly bypass it, which causes teams to reprioritise work informally and makes the portfolio data unreliable."

That narrative is far more valuable than a score alone.

Xirocco creates space for narrative knowledge

Xirocco includes features that allow employees and advisers to capture narrative-style observations, opinions and contextual information.

This content can reflect:

  • How work happens in practice

  • Employee sentiment

  • Cultural conditions

  • Organisational barriers

  • Political realities

  • Historical decisions

  • Operational concerns

  • Areas of disagreement

  • Confidence in current capability

  • Perceived risks and opportunities

This is important because tacit knowledge is often best expressed in natural language.

It does not always fit into a field, score, status or category.

Xirocco allows that narrative material to become part of the wider strategy rather than remaining isolated in workshop notes, interview transcripts or individual memories.

Narrative content should support the strategy

Capturing employee views is not the same as running a standalone engagement survey.

The value comes from connecting those views to the wider enterprise picture.

Narrative content in Xirocco can be referenced alongside:

  • Business objectives

  • Applications

  • Capabilities

  • Suppliers

  • Risks

  • Projects

  • Operating-model design

  • Diagnostic findings

  • Technology strategy

  • Investment decisions

This means employee knowledge can support, qualify or challenge the formal evidence.

For example:

  • A supplier may score well contractually, while employee narrative reveals persistent delivery friction.

  • A process may appear mature, while operational teams describe widespread workarounds.

  • A transformation programme may appear on track, while staff report low confidence in leadership decisions.

  • An application may appear replaceable, while employees explain critical undocumented dependencies.

The resulting strategy becomes more realistic because it reflects both formal structure and lived experience.

How Maeros AI uses tacit knowledge

Maeros AI operates across the connected enterprise context held in Xirocco.

That context can include:

  • Structured data

  • Expert assessments

  • Narrative employee input

  • Institutional history

  • Observations about culture and politics

  • Explanations of operational reality

This gives Maeros a richer basis for analysis.

It can help leaders explore questions such as:

  • Which cultural barriers could prevent this transformation from succeeding?

  • Where do employee accounts conflict with formal process documentation?

  • Which applications have undocumented dependencies?

  • Why have previous change initiatives stalled?

  • Which recommendations may be impractical because of organisational constraints?

  • Where does critical knowledge depend on a small number of employees?

  • Which operating-model changes are likely to face resistance?

  • What institutional knowledge should be captured before key people leave?

  • Where is leadership perception different from operational reality?

This is not simply sentiment analysis.

The purpose is to bring human context into strategic reasoning.

Tacit knowledge helps explain causality

Enterprise data often shows symptoms.

Tacit knowledge helps explain causes.

A project may be late.

The formal explanation may refer to resource constraints.

Employees may know that priorities change weekly because decision rights are unclear.

An application may be expensive.

The data may show high support cost.

Employees may know that the cost is driven by multiple unofficial integrations created after an acquisition.

A supplier may repeatedly miss expectations.

The contract may appear adequate.

Internal teams may know that responsibilities between the supplier and the organisation were never clearly defined.

Maeros can analyse these different sources together and help identify the relationships between formal evidence and lived experience.

That gives leaders a stronger basis for deciding what must change.

Tacit knowledge reduces the risk of technically correct failure

Many enterprise recommendations are technically valid but organisationally unworkable.

A target architecture may be sound.

A new operating model may be logically designed.

A rationalisation plan may identify genuine duplication.

But implementation may fail because the recommendation overlooked:

  • Cultural resistance

  • Informal ownership

  • Political sensitivity

  • Hidden dependencies

  • Historical mistrust

  • Skills concentrated in one team

  • Unrecorded workarounds

  • Local operating constraints

Capturing tacit knowledge makes these conditions visible earlier.

It does not mean every employee opinion should determine the strategy.

It means those opinions should be available as evidence to be interpreted, challenged and considered.

Employee knowledge should not be treated as unquestionable fact

Tacit knowledge is valuable, but it can also be partial, outdated or influenced by individual experience.

Different employees may provide conflicting accounts.

One team may view a process as effective while another sees it as a major barrier.

This is why tacit knowledge should sit alongside data and expert assessment rather than replacing them.

The three points of the triangle strengthen one another:

  • Data provides formal evidence

  • Expert opinion provides independent interpretation

  • Tacit knowledge provides lived organisational context

Where all three support the same conclusion, confidence increases.

Where they conflict, the disagreement itself becomes important and should be investigated.

The role of trust and psychological safety

Employees will not share meaningful knowledge if they believe doing so is unsafe or pointless.

A tacit-knowledge capture process must consider:

  • Who can see the input

  • Whether comments are attributed

  • How sensitive views are handled

  • Whether leadership genuinely wants challenge

  • How conflicting perspectives will be treated

  • Whether employees will see evidence that their contribution mattered

The objective is not to create a repository of complaints.

It is to create a disciplined mechanism for surfacing the realities that affect strategic success.

Xirocco advisers can support this through structured interviews, workshops, guided assessments and facilitated knowledge capture.

The method should be designed around the sensitivity of the organisation and the nature of the change.

Where tacit knowledge matters most

Tacit knowledge is useful across enterprise strategy, but it becomes especially important during:

Leadership transitions

When a new CIO or executive inherits an organisation, formal reports rarely explain the whole environment.

Long-serving employees often understand why the estate, culture and operating model developed as they did.

Major transformation

Employees can expose practical barriers, failed assumptions and dependencies that programme plans do not show.

Mergers and acquisitions

Critical knowledge may be distributed across legacy teams and may be lost during restructuring or departure.

Application rationalisation

Users and support teams may understand business-critical functions and workarounds that are absent from application records.

Operating-model redesign

Formal organisation charts rarely show how decisions, influence and delivery actually flow.

AI adoption

Employees may understand where data quality, process variation, trust or local practice will affect whether an AI use case succeeds.

Cost optimisation

Tacit knowledge can help distinguish genuine waste from capability that appears redundant but performs an important hidden role.

Workforce change

When experienced employees leave, years of organisational knowledge may disappear with them.

Knowledge loss is an enterprise risk

Institutional knowledge is often concentrated in a small number of people.

These individuals become unofficial repositories of organisational memory.

They may understand:

  • Legacy technology

  • Supplier history

  • Critical recovery procedures

  • Historic architecture decisions

  • Regulatory commitments

  • Operational exceptions

  • Stakeholder relationships

  • Why previous programmes failed

The organisation may not realise how dependent it is on them until they retire, resign or move role.

Capturing this knowledge should therefore be treated as part of resilience and change readiness—not merely documentation.

Xirocco gives organisations a way to bring that knowledge into a maintainable enterprise context before it is lost.

A practical approach to capturing tacit knowledge

The detailed method will vary, but a strong approach usually includes five stages.

1. Identify where critical knowledge may be concentrated

Focus on long-serving employees, subject-matter experts, operational leaders, support teams and roles with high dependency.

2. Use narrative prompts, not only structured questions

Give people space to explain:

  • What really happens

  • Why it happens

  • What the documentation misses

  • What they would change

  • What they believe could go wrong

3. Connect the input to the enterprise context

Link observations to relevant applications, processes, suppliers, capabilities, risks or initiatives.

4. Validate and compare perspectives

Test employee accounts against data, expert assessment and other stakeholder views.

5. Make the knowledge usable

Use Xirocco and Maeros AI to bring the insight into strategy, diagnostics, operating-model design, investment and implementation planning.

The goal is not simply to collect stories.

It is to make the knowledge available at the points where decisions are made.

From interviews to a living organisational memory

Traditional consulting often captures tacit knowledge through interviews and workshops.

But much of that insight is then compressed into a presentation.

The original context may remain in personal notes or disappear when the project team leaves.

Xirocco changes this by retaining narrative knowledge within the same environment as the strategy and assessments it supports.

As new information emerges, the enterprise picture can be updated.

Employees can contribute additional context.

Maeros can revisit earlier conclusions in light of new evidence.

This turns knowledge capture from a one-time discovery activity into part of a living organisational memory.

The question leaders should ask

The question is not simply:

What does our data tell us?

The stronger question is:

What do our data, our experts and our people collectively tell us about how this organisation really works?

That is the full triangle of enterprise change.

Without data, decisions lack evidence.

Without expert opinion, the organisation may struggle to interpret what it sees.

Without tacit knowledge, the strategy may miss the human and operational realities that determine whether change succeeds.

Bring institutional knowledge into enterprise change

Xirocco helps organisations combine:

  • Formal enterprise data

  • Structured expert assessment

  • Tacit and institutional knowledge

Its narrative features give employees and advisers a way to capture the context, opinions and lived experience that cannot be represented adequately through binary fields or conventional records.

Maeros AI can then use that richer context to identify hidden dependencies, explain why problems persist and test whether proposed changes are likely to work in practice.

The result is a more credible view of:

  • How the organisation really operates

  • Why previous change may have struggled

  • Where culture and politics affect delivery

  • Which critical dependencies remain undocumented

  • What knowledge is at risk of being lost

  • How strategy and implementation should respond

Start a Conversation

Share the change your organisation is planning and where critical knowledge may be undocumented or concentrated in a small number of people.

Xirocco can help capture that knowledge and bring it into the wider strategy so that Maeros AI, advisers and leadership teams can use it to make better-informed decisions.

Start a Conversation