Enterprise Architecture as a Sensemaking Lens

Enterprise Architecture is the primary lens through which organisations surface, work through, and stabilise shared meaning.

🧠 Meaning does not start with models

Meaning does not originate in frameworks, systems, or diagrams.

👉 It emerges through interaction between people when:

perspectives are shared,
assumptions are questioned,
differences are brought up and discussed,
and a shared understanding of the organisation develops.

This is where organisations begin to “see” reality.

🧱 Where Enterprise Architecture becomes critical

Without structure, that emerging meaning remains:

Fragmented and hidden.
Localised in silos.
Expressed without a common language.

👉 It cannot be captured, coherently expressed and shared.

This is where Enterprise Architecture plays its role.

Through:

Business Capability Modelling (BCM),
Common Data Modelling (CDM),

Organisations build a shared view of reality.

📖 Narrative Example from Adapt Survive and Flourish

Chapter: Mario, Bruno, Bill, and Mary’s Site Visit: Bruno’s Pitch

Bruno introduces a Business Capability Model to Sam and his team.

Initially sceptical, they begin to see how it reveals what is actually happening in the business.

The introduction of the Common Data Model then exposes underlying data issues and inconsistencies.

👉 The models do not provide answers. They make reality visible and open to discussion.

🧭 In the Guidelines — Adapt, Survive and Flourish

The Knowledge Management guideline provides detailed guidance on BCM and CDM
Their role in building a shared knowledge base.

👉 If people are performing roles rather than exposing reality, you are seeing defensive routines in action.

🔁 Modelling as sensemaking

In practice, building these models is not a technical exercise.

They are structured conversations.

People describe how the organisation actually works.
The BCM provides a holistic, “mind-sized” view.
Definitions are debated and refined.
Dependencies between capabilities surfaces.
Relationships between data entities become explicit.
Gaps and inconsistencies are exposed as they are tested in Gemba.

👉 The model is not the outcome. Shared understanding is.

🔍 What the lens reveals

Enterprise Architecture does not simplify reality.

It makes it visible.

Connections between perspectives.
Dependencies across the organisation.
Conflicts between goals and assumptions.

Without this holistic perspective:

Stakeholder perspectives remain disconnected.
Meaning is assumed rather than tested.
Decisions lack coherence.

⚖️ The role of tension

Shared meaning is not achieved through agreement.

It is formed through:

challenge
negotiation
refinement

👉 Differences are not a problem to eliminate. They are the raw material of understanding.

🔗 How this fits the system

Stakeholder Engagement → creates interaction.
Enterprise Architecture → structures meaning.
Gemba → tests meaning in reality.
SECI → deepens and spreads understanding.

⚠️ When it goes wrong

When Enterprise Architecture is separated from participation:

Models become abstract.
Consultants produce artefacts without ownership.
Knowledge remains external.
Organisations receive shelf ware instead of workwear.

👉 Meaning appears to exist, but is not shared or lived.

🎯 Practical insight

Enterprise Architecture is most effective when:

people build the models themselves,
conversations are prioritised over artefacts,
structure supports understanding, not replaces it.

👉 Enterprise Architecture does not create meaning. It makes meaning visible, shared, and usable.

➰To Return to the Executive Pathway

📝 To understand more and a more advanced discussion, see:

Adapt, Survive & Flourish