S³ Paper 005

The Decision Object

Why every important organisational decision deserves a digital identity.

Introduction

Every modern organisation invests heavily in managing its digital assets. Customer records are maintained in Customer Relationship Management platforms. Financial transactions are recorded in Enterprise Resource Planning systems. Engineering teams manage product data throughout its lifecycle, while architects coordinate increasingly sophisticated Building Information Models. Across every industry, organisations have become exceptionally good at creating digital representations of the things they build, buy, sell and operate.

Yet one of the most valuable organisational assets has never been modelled in its own right.

The decision itself.

Every project is shaped by thousands of decisions. Some are operational and made within minutes. Others influence investment, design, procurement, sustainability or organisational strategy for years. They determine what organisations build, where they invest, which opportunities they pursue and how they respond to uncertainty.

Despite their importance, these decisions rarely exist as first-class objects within enterprise systems. Instead, they are scattered across meeting minutes, email threads, reports, presentations and conversations, making them difficult to understand once the moment has passed.

The consequence is familiar.

Teams spend considerable time reconstructing why previous decisions were made. Projects revisit questions that had already been resolved. New colleagues inherit outcomes without inheriting the reasoning that produced them. Organisations preserve information while gradually losing the judgement that gave that information meaning.

This paper argues that organisations should begin treating significant decisions as digital assets in their own right.

I describe these as Decision Objects.

We Model Everything Except Decisions

The modern enterprise is built upon digital objects.

Enterprise Resource Planning systems model orders, invoices and suppliers.

Customer Relationship Management platforms model customers, accounts and opportunities.

Building Information Modelling represents walls, doors, spaces and equipment.

Product Lifecycle Management systems model products, components and configurations throughout their lifecycle.

Each object possesses its own identity, attributes, relationships and history. Together, these digital representations allow organisations to understand how different parts of the enterprise interact and evolve over time.

Curiously, the very thing these systems exist to support—the decision—rarely receives the same treatment.

Instead, decisions become invisible.

A specification changes.

A budget is approved.

A supplier is selected.

A strategy evolves.

The organisation remembers what changed.

It often forgets why.

This absence is striking because decisions influence every organisational outcome, yet they remain fragmented across documents, presentations, meeting notes and individual memory rather than existing as identifiable organisational assets in their own right.

Decisions Already Have Structure

One reason organisations have struggled to model decisions is the assumption that judgement is inherently unstructured.

While every important decision contains elements of professional experience and interpretation, significant organisational decisions are remarkably consistent in how they are formed.

They begin with a question requiring resolution.

They draw upon available evidence.

They are influenced by assumptions and constraints.

They involve identifiable stakeholders.

They evaluate multiple alternatives.

They lead to a recommendation.

They produce an outcome.

Finally, they generate consequences that can be observed and evaluated over time.

Seen in this way, decisions are not simply conversations or isolated moments of judgement.

They are structured organisational objects whose properties can be understood, improved and managed throughout their lifecycle.

Defining the Decision Object

A Decision Object is a persistent digital representation of an important organisational decision together with the information required to understand, evaluate and revisit it over time.

Unlike a document, which primarily captures information, a Decision Object captures reasoning.

Unlike meeting minutes, which record discussion, a Decision Object preserves judgement.

Unlike a report, which describes a situation, a Decision Object explains why one course of action was considered preferable to another.

Like every other organisational object, a Decision Object possesses identifiable characteristics.

It exists for a specific purpose.

It belongs within a defined organisational context.

It draws upon evidence.

It contains assumptions.

It evaluates alternatives.

It records ownership and accountability.

It evolves as new information becomes available.

Ultimately, it produces outcomes whose consequences can be understood and learned from over time.

At a practical level, every Decision Object should answer a small number of fundamental questions.

• What decision is being made?

• Why is the decision necessary?

• What evidence supports the available options?

• Which assumptions influence the recommendation?

• What constraints exist?

• Which alternatives were considered?

• Who is responsible for making the decision?

• What level of confidence exists?

• What outcome was ultimately achieved?

Remarkably, these questions remain largely consistent regardless of whether an organisation is designing a building, manufacturing products, developing software, allocating investment capital or shaping public policy.

A Different Way of Thinking About Enterprise Architecture

Every major advance in enterprise software has been built upon better representations of organisational reality.

Accounting systems introduced digital representations of financial transactions.

CRM platforms introduced digital representations of customer relationships.

Building Information Modelling transformed physical assets into structured digital models.

Product Lifecycle Management systems created persistent digital representations of products throughout their lifecycle.

Each of these developments fundamentally changed organisations because they made previously invisible organisational objects visible.

Decision Objects extend the same principle.

Rather than allowing important organisational decisions to remain fragmented across documents, meetings and individual memory, organisations begin treating them as persistent organisational assets with their own identity, structure, history and relationships.

This changes more than documentation.

It changes what organisations are capable of understanding.

Instead of asking which project a document belongs to, enterprise systems can begin asking which decision that information supports.

A sustainability assessment becomes evidence supporting a design decision.

A customer meeting becomes evidence informing a commercial decision.

A financial model becomes evidence supporting an investment decision.

A digital twin becomes a continuously evolving source of evidence informing operational decisions throughout an asset's lifecycle.

Information does not become less important.

Its purpose becomes clearer.

Building Organisational Intelligence

Organisations often describe themselves as knowledge-driven.

Perhaps the more appropriate ambition is to become judgement-driven.

Knowledge informs decisions.

Decisions create outcomes.

Outcomes generate experience.

Experience, when systematically connected back to the decisions that produced it, becomes organisational intelligence.

Decision Objects provide the missing link between information and organisational learning.

Rather than treating decisions as isolated events, organisations begin connecting them into an evolving network of organisational reasoning. Every project strengthens future decisions. Every investment refines future judgement. Every lesson learned becomes attached to the decisions that generated it rather than existing as an isolated recommendation detached from its original context.

Instead of repeatedly solving familiar problems, organisations begin accumulating judgement.

Experience becomes cumulative.

Learning becomes measurable.

Organisational intelligence begins to compound.

Conclusion

For decades, enterprise software has transformed organisations by giving digital identity to the things they create, manage and operate.

Customers became digital objects.

Products became digital objects.

Assets became digital objects.

Projects became digital objects.

Perhaps the next evolution is to recognise that decisions deserve the same treatment.

Decision Objects represent more than another data structure.

They represent a different way of understanding organisations themselves.

Rather than viewing organisations primarily as collections of documents, processes and information, they encourage us to see organisations as networks of interconnected decisions whose quality ultimately determines every outcome they achieve.

If this perspective is correct, then the future of organisational design may depend less upon creating more information and more upon giving decisions a permanent place within the digital architecture of the enterprise.

Because organisations are ultimately defined not by the information they possess, but by the decisions they make.