Relational vs Transactional Knowledge Management

The Pattern

Organisations tend to invest in what can be seen, measured, and reported.

In Knowledge Management, this leads to a dominance of transactional approaches—systems, repositories, metrics, and outputs—while the relational conditions that enable learning are underdeveloped.

The result is not balance, but structural fragility.


Transactional KM (Structure)

Transactional KM focuses on:

  • Capturing knowledge in systems
  • Producing measurable outputs
  • Creating reusable artefacts

It provides:

  • A common language
  • A shared reference point
  • The foundation for coordination and decision-making

👉 This is necessary. Without it, coherence collapses.


Relational KM (Activation)

Relational KM focuses on:

  • Trust and psychological safety
  • Dialogue and shared experience
  • Learning through practice

It enables:

  • Socialisation and Internalisation
  • The development of judgement
  • The formation of shared mental models

👉 This is essential. Without it, knowledge does not live.


The Failure Mode

Most organisations do not have too much transactional KM.

They have:

Transactional KM without relational activation

This creates:

  • Knowledge that is captured but not used
  • Models that are defined but not believed
  • Systems that are implemented but bypassed

👉 Codified knowledge becomes knowledge-in-form, not knowledge-in-use


The Governing Law

Knowledge only becomes real when it is re-internalised at Gemba

Until knowledge is:

  • tested in practice
  • shaped by consequence
  • shared through experience

…it remains incomplete.


Domain Mapping (KOS)

  • Sensemaking Domain → Codified knowledge (models, data, artefacts)
  • Relational Domain → Trust, dialogue, shared context (Ba)
  • Learning Domain → SECI activation (Socialisation & Internalisation)
  • Action Domain → Gemba (where knowledge is tested and confirmed)

Executive Insight

Transactional KM provides control signals.
Relational KM enables adaptive capacity.

Optimising the former without the latter leads to:

coherent systems that fail under real conditions


One Line

Transactional KM stores knowledge.
Relational KM makes it usable.
Only one of them creates learning.


Explore Further

This pattern connects to the broader framework:

  • Sensemaking Domain — how organisations structure knowledge
  • Relational Domain — how trust and coordination emerge
  • Learning Domain — how knowledge becomes capability
  • Action Domain — how knowledge is tested at Gemba

👉 Explore the full framework via the Source Notes hub