Decision Aliasing

The same decision often appears under different names.

Product calls it prioritisation. Engineering calls it scope control. Finance calls it cost management.

Each domain believes it is discussing something different.

The underlying decision is the same.

The illusion of difference

Aliasing creates the illusion that multiple decisions exist.

Conversations fragment. Ownership becomes unclear. Resolution is delayed.

The system appears more complex than it actually is.

Different domains optimise for different perspectives.

Language evolves locally. Concepts are framed through domain-specific concerns.

This is natural.

It becomes problematic when the shared decision is no longer recognised.

Aliased decisions behave poorly.

Teams duplicate work. Conflicts emerge late. Decisions are revisited unnecessarily.

The organisation spends effort reconciling language rather than resolving outcomes.

Healthy systems identify shared decision objects.

Different representations are mapped to a single underlying structure.

Interfaces become clearer. Ownership becomes visible. Resolution accelerates.

The organisation stops debating terminology.

Many coordination problems are not about disagreement.

They are about misidentification.

Recognising when multiple conversations refer to the same decision reduces unnecessary complexity.

Different names do not imply different decisions.