Sequence is the strategy.

Sequence is usually treated as a planning question — something the programme office resolves once funding is approved. It is not. Sequence decides which decisions are made with evidence and which are made under pressure.

When technology is introduced before the operating model is settled, the platform becomes the place where unresolved business questions are argued. Configuration debates stand in for decisions about ownership, process and accountability that leadership never closed.

The result is familiar: a technically successful deployment that changes very little about how the enterprise performs.

In the Enterprise Transformation Framework™, Technology & AI sits at dimension seven — after vision, strategy, operating model, governance, people and data have been resolved. The sequence is deliberate: technology is meant to amplify a foundation that already holds.

In practice, many enterprises begin there anyway, because it is the most visible thing to start. Technology has a vendor, a date, a budget line and a demonstrable milestone. Operating-model clarity has none of those.

There is also a reporting incentive. A platform programme produces progress that can be shown to a board within a quarter. Decision rights, data ownership and process accountability produce progress that is harder to display and easier to defer.

So the enterprise begins where movement is easiest rather than where the constraint actually sits — and the dimensions before dimension seven are left to be discovered later.

In a simple enterprise, order errors are recoverable. A single business unit, one process owner and one data source can absorb rework.

At enterprise scale — multiple markets, shared services, a large application estate, regulatory obligations — the same error compounds. Each layer built on an unstable foundation inherits its ambiguity and adds its own.

This is why the same programme design behaves differently in two organisations. The method did not change. The complexity it was applied to did.

Skipped foundations reappear later, at higher cost and lower discretion. An unresolved operating-model question returns as an integration problem. Unowned data returns as a reporting dispute at the point a decision is needed. Undefined outcome measures return as a board challenge to the business case.

None of these appear as foundation problems when they surface. They appear as delivery problems, which is why they are handed to delivery teams who cannot solve them.

The work was never avoided. Only the moment of paying for it was moved.

The Enterprise Transformation Framework™ orders the enterprise in nine dimensions, organised across five domains, from vision through to business outcomes. Technology & AI sits at dimension seven — not because technology matters less, but because it inherits everything above it.

Read as an architecture, the sequence describes dependency. Read as a leadership instrument, it describes the order in which executive decisions have to be made and the order in which they can reasonably be defended.

Its value to an executive team is diagnostic. When a transformation stalls, the question is not which workstream is behind. It is which dimension was passed over.