Organisations Need a Design Language

Every profession develops a language for describing and improving the things it creates.

• Architects use plans and elevations.
• Engineers use schematics.
• Accountants use financial statements.
• Organisations also need a language of design.

Without it, strategy becomes disconnected from execution, information gets scattered, and individuals find it difficult to build a collective understanding of how the organisation truly functions.

Business Architecture offers a common language. Fundamentally, it isn’t focused on technology but on developing a shared understanding of an organisation’s functions, the information it relies on, and how to implement changes consistently. It serves as a stable base for building processes, systems, projects, organisational structures, and transformation efforts.

The Foundation Before the Superstructure

An organisation’s ability to function cohesively hinges on the quality of its shared mental models. When members hold differing assumptions, use varied terminology, or perceive the organisation differently, coordination can become challenging and learning slows.

Business Architecture helps create a shared understanding by making key concepts, capabilities, and information visible and open to discussion. This offers a practical way to develop common mental models among teams, functions, and leadership.

An analogy is a house: the foundation stays stable over time, even as rooms are renovated, walls are moved, or systems are upgraded. The foundation endures.

The goal of Business Architecture is first to build a solid organisational foundation. With a shared understanding in place, it becomes simpler to design, communicate, oversee, and enhance all later elements. To facilitate this, Business Architecture uses two key models that clarify and make organisational knowledge easy to discuss.

These models do not aim to encompass every detail; instead, they focus on building a collective understanding of what the organisation does, the information it relies on, and how these components interconnect.

The two core models are the Business Capability Model (BCM) and the Common Data Model (CDM).

The Business Capability Model

A Business Capability Model (BCM) outlines what an organisation must be able to do. It does not specify the organisational structure, processes, or technology. Instead, it focuses on the core capabilities that are essential for success.

Examples may include:

• Product Development
• Customer Management
• Manufacturing
• Regulatory Compliance
• Sales
• Financial Management

Because capabilities stay stable over time, they provide a powerful organising framework.

A BCM allows leaders to:

• view the organisation at the executive level,
• identify capability strengths and weaknesses,
• prioritise investment,
• allocate ownership and accountability,
• support strategic planning,
• and guide organisational transformation.

The BCM provides a mind-sized representation of organisational activity that executives can readily understand and discuss.

The Common Data Model

If the BCM describes what the organisation does, the Common Data Model (CDM) describes what the organisation deals with.

The CDM provides a shared language of organisational meaning. It names the key concepts, entities, and relationships that exist within the business.

Examples include:

• Customer
• Product
• Supplier
• Order
• Account
• Employee
• Asset

The CDM serves as the organisation’s semantic backbone.

It supports:

• shared vocabulary,
• glossary development,
• systems integration,
• data quality management,
• reporting consistency,
• analytics,
• and AI enablement.

By creating a collective understanding of organisational information, the CDM helps ensure that diverse groups interpret key concepts consistently.

Shared Language Creates Shared Understanding

Many organisational issues are not related to technology but stem from gaps in understanding. Different teams often use the same terms with different meanings or different terms for the same concept. This leads to confusion, redundancy, and misalignment.

Business Architecture supports organisations in creating a shared language and common mental models. As organisations expand, diversify, and incorporate AI technologies, this shared understanding becomes even more essential.

From Shelfware to Workwear

Many organisations successfully build and distribute models. The challenge is not sharing the model. The challenge is integrating the model into the organisation’s everyday work.

A Business Capability Model or Common Data Model only becomes valuable when used to make decisions, design solutions, assign accountability, guide investment, and support learning.

Models that stay in repositories become shelfware.

Models in use that influence conversations and decisions become workwear.

The first value comes from the conversations used to create the model. The enduring value comes when the model continues to shape decisions, action, and learning at Gemba.

When people work together to build a capability model or data model, they share perspectives, challenge assumptions, and develop a deeper understanding of the organisation. This is building the Shared Mental Models that are essential for operations, design, and strategy.

The model becomes more than documentation. It becomes a learning tool.

In this sense, effective Business Architecture is not simply about producing models.

It is about creating shared understanding and using it as workwear.

Business Architecture as a Social Process

Building a Business Capability Model or Common Data Model is fundamentally a social activity.

People from different areas of the organisation bring their knowledge, experiences, and perspectives into a shared conversation.

Through discussion, storytelling, and exploration, tacit knowledge becomes explicit.

• Understanding grows.
• Trust develops.
• Relationships strengthen.

The process itself often creates as much value as the finished model.

Across two books, we have Bruno’s BCM story:

📖 Narrative Example from Adapt, Survive and Navigate

Backstory:

Bruno was an EA consultant attached to the Tuesday Night Survivors Club and became involved in their efforts to help Sam Pinoak, the new CEO of NaturFlourish, transform his business. Bruno had only recently started using AI to generate a Business Capability Model straw man for the nutraceutical business. He had no work experience in pharmaceutical and nutraceutical manufacturing. Normally, in the consulting team, this type of work would have taken at least two or three consultants a couple of days to produce the level of detail AI produced in minutes. He was comfortable enough with the quality to present it to Sam at their first meeting.

Bruno’s AI Query:

“I am an Enterprise Architect, and my client is a privately owned nutraceutical company. Please generate a Business Capability Model to Level 2, based on Australian companies such as Blackmores, Swisse, and similar organisations.”

📖 Bruno’s Second Lesson: From Sharing to Socialisation

Narrative Example from Lead, Transform and Navigate

Following its first presentation (In ASF above), the Business Capability Model was adopted as a working reference within NaturFlourish.

Bruno did what he had always tried to do as a consultant: share the model with the business in a series of walkthroughs. During walkthroughs, the model appeared complete and coherent. Participants treated it as something to be explained rather than challenged.

Questions focused on understanding the structure, not on assessing its underlying assumptions.

Bruno was seen as the Enterprise Architecture expert, and the model carried added weight through Sam’s visible support.
As a result, the model was accepted and used operationally without significant challenge.

Over time, it began to shape conversations, decisions, and interpretations of how the business ran.

It was only when Mallory questioned specific elements of the model that its underlying assumptions were exposed.

Under scrutiny, inconsistencies and gaps became visible, and the model’s apparent coherence began to break down.

This led to a broader realisation:

The model had not been socialised in the SECI sense.

While it had been presented, explained, and shared, it had not been collectively interrogated, challenged, or confirmed through interaction.
Participants had not contributed to its formation or evaluated it against their own experience of the business.

In contemporary consulting practice, a presentation to an executive group, followed by minor refinement, is often described as “socialisation.”
In this case, that level of engagement proved insufficient.

The model had been communicated, but a shared understanding had not been established.

Communication is not understanding.

A model may be explained, distributed, approved, and even used.

Until people have challenged it, contributed to it, and tested it against reality, shared understanding has not yet been established.

Supporting Change and Transformation

Business Architecture provides a stable reference point for change.

It helps organisations answer questions such as:

• What capabilities are we investing in?
• What capabilities are being neglected?
• What capabilities do we need to strengthen?
• Where are our pain points?
• What information do we rely upon?
• Where should we invest?
• What impact will this change have?
• How do our initiatives fit together?
• How does our portfolio of systems support the business?

Rather than implementing isolated projects in silos, organisations can design coherent transformation pathways aligned with strategy and purpose.

A Foundation for Learning Organisations

Business Architecture is a tool for organisational learning.

• It helps make knowledge visible.
• It creates shared language.
• It supports collaboration.
• It improves decision-making.

It offers a solid base for developing adaptive, learning organisations.

In a world characterised by increasing complexity and uncertainty, shared understanding may be one of the most valuable organisational assets.

Business Architecture provides the language through which that understanding is created, supported, and continuously improved.

➰To return to Executive Pathway

🤿For a deeper understanding, see: Subject Area: Enterprise Architecture – Foundation of Shared Knowledge.

📝For examples of Bruno’s initial BCM see: NaturFlourish BCM V1.0