IDD concept: Scale across the organisation

Intent Hierarchy

The Intent Hierarchy structures shared intent at three levels, Organisation, Domain and Project, so that intent is defined once, inherited by default and refined continuously. It is how Intent-Driven Development scales from a single team to an enterprise without duplication and without losing alignment.

The scaling problem

As soon as a team writes its first few Intent Specifications, elements begin to repeat: the same regulatory requirements, the same infrastructure constraints, the same domain models and the same architectural patterns. Within one team that repetition is a minor irritation. Across an enterprise it becomes a liability, because every copy can drift, and a constraint that matters, such as a security baseline, ends up stated slightly differently in a hundred places.

The Intent Hierarchy solves this by giving shared intent a home of its own, at the level where it genuinely applies, and letting specifications inherit it rather than restate it.

Three levels of intent

Organisation Intent
Enterprise-wide standards, architectural patterns, security baselines, compliance approaches and ethical principles.
Domain Intent
Bounded context definitions, domain models, business rules and ubiquitous language, the territory that Domain-Driven Design describes.
Project Intent
Feature-specific goals, validation criteria and unique constraints, written to reference inherited intent rather than repeat it.

Inheritance and promotion

Intent flows downward through inheritance, so every project starts with what the organisation already knows. It also moves upward: patterns that prove effective in delivery are promoted into domain intent and, where they span the organisation, into organisational intent. This second movement, described in Intent Promotion, is what stops the hierarchy becoming a set of rules handed down from above; intent is not only inherited, it is earned.

Two rules keep the levels coherent. A project can extend the intent it inherits but may not silently override it. Ethical intent is inherited like any other, but where a conflict arises it is escalated, never quietly overridden.

Do not start with the hierarchy

A diagram of three tidy levels invites organisations to design the whole structure upfront, defining enterprise intent first, then domain intent, then project intent beneath it. In practice intent rarely appears that way. It begins as work, in the projects and domains where real problems are being solved, and only moves upward once patterns repeat and knowledge stabilises. Until delivery has produced enough evidence, the organisation does not yet know what should be standardised and what should stay local, and a hierarchy designed too early tends to produce abstractions that look neat and do not survive contact with reality.

The practical guidance is to begin without a hierarchy and introduce one when duplication becomes painful. The hierarchy is the result of learning, not its starting point.

Anti-patterns

  • God Layer: too much is defined centrally, leaving projects with little room to respond to their own context.
  • Orphan Projects: projects that inherit nothing and so rediscover shared constraints for themselves.
  • Abandoned Layers: shared intent that is defined once and never maintained, so that projects inherit stale assumptions.
  • Inheritance Spaghetti: inheritance paths so complex that nobody can say where a given constraint came from.
  • Premature Abstraction: a hierarchy built before the patterns it is meant to capture have emerged.

Architecture as promoted intent

The hierarchy changes the role of architecture. In traditional models, architectural standards are often predicted in advance and can become disconnected from delivery. In an intent-driven organisation, architecture is largely promoted intent: patterns that have proved themselves in projects, moved upward through the hierarchy and inherited by future work. Architecture shifts from prediction to promotion, and from control to governance.

Where it comes from

The Intent Hierarchy was introduced in The Intent Hierarchy, published on 23 March 2026, and developed further in Intent Evolution and Intent Shaping and The Learning Organisation. It forms Chapter 10 of the ebook.

Frequently asked questions

Should we design our Intent Hierarchy before we start?No. Start with project specifications and let the hierarchy emerge. When the same constraints and patterns appear repeatedly across projects, that repetition is the signal to define them once at domain or organisation level.
Can a project override organisational intent?A project can extend what it inherits but should never silently override it. Where a project genuinely needs to depart from inherited intent, that departure is made visible and resolved through governance, and conflicts involving ethical intent are always escalated.
How does the Intent Hierarchy relate to Domain-Driven Design?Domain Intent corresponds closely to DDD's bounded contexts. Each domain level holds the models, rules and ubiquitous language for a bounded context, which is why domain modelling remains a human-led activity in IDD.
How many levels should a hierarchy have?IDD defines three: Organisation, Domain and Project. The aim is the simplest structure that removes duplication, since overly complex inheritance paths are an anti-pattern in their own right.