Organisations exhibit recurring decision architecture patterns

Software engineers recognise design patterns as recurring structural solutions.

Certain configurations appear repeatedly across systems.

Organisations display similar behaviour.

Certain structural mistakes appear again and again across industries and companies.

Decision systems produce recognisable architectural patterns.

Delegation without authority

This pattern appears when responsibility moves without authority.

A team receives ownership of a system.
Strategic decisions remain elsewhere.

The team becomes accountable for outcomes it cannot fully control.

Escalation becomes constant.

Engineers experience responsibility without power.

Delegation without authority produces structural instability.

The committee trap

Some organisations attempt to distribute decision authority widely.

Committees review architecture.
Working groups evaluate direction.
Consensus becomes the mechanism for convergence.

Consensus feels inclusive.

In practice it often prevents decisions from closing.

Disagreement becomes a permanent condition.

Shared authority frequently produces decision paralysis.

Phantom authority

Another pattern appears when authority exists formally yet cannot operate in practice.

An architect holds responsibility for system design.

Teams however may ignore architectural direction without consequence.

Authority therefore exists only on paper.

Real decisions occur elsewhere.

Authority without enforcement becomes phantom authority.

Escalation cascades

When authority boundaries remain unclear decisions travel upward through multiple layers.

Local teams hesitate to commit outcomes.
Managers escalate to directors.
Directors escalate to executives.

The organisation begins to behave like a queueing system.

Decision latency increases with each layer.

Delivery slows even when engineering capability remains strong.

Escalation cascades signal poorly designed authority surfaces.

Why patterns matter

Patterns help engineers reason about complex systems.

They compress experience into recognisable shapes.

Decision Architecture may benefit from the same approach.

If organisational behaviour can be described through recurring patterns diagnosis becomes easier.

Leaders can recognise structural problems earlier.

Understanding the patterns reveals how organisations actually behave.