Architect before you build.
Most transformations design under fire, improvising the operating model and inventing governance as they go. That is the most expensive possible time to design anything.
With reality understood, the next discipline is to design the future deliberately. Architect is the work of designing the operating model, the governance structure, and the execution roadmap that the transformation will actually run on. This is where strategy stops being a direction and becomes a structure.
Most transformations under-invest here because the design work is abstract and the pressure to start doing something visible is intense. So they begin building before they have designed, and they design under fire, improvising as they go. This is the most expensive possible time to design anything, because every improvised decision becomes a constraint on the next one.
Design the operating model on purpose
Most organizations have an operating model by default, inherited and accreted over years, never designed and rarely examined. A transformation is a rare opportunity to design one on purpose: how the work will be organized, who will own what, how decisions will flow, and how the parts will fit together to produce the outcome.
The organizations that take that opportunity seriously gain an advantage that compounds long after the transformation ends. The ones that skip it get a structure that is an accident of sequence rather than a product of intent.
Architecture done well makes the later phases possible. Architecture skipped guarantees you will improvise the structure under pressure.
Sequence by dependency, not by volume
Architecture also means sequencing the change by return and by dependency rather than by what is loudest. There is always pressure to start with the most visible thing. The disciplined architect does first the things that unlock the most and that everything else depends on, even when those things are unglamorous and generate no immediate applause.
Governance designed in, not bolted on
Crucially, this is where governance and decision rights are designed in, rather than bolted on later when the first conflict reveals their absence. The architecture specifies who decides what, how trade-offs will be resolved, and the cadence of decision-making, before the transformation generates the decisions those structures will need to handle.
You cannot improvise governance at the moment you need it. By then the decisions are already piling up. Architect first, and the rest of the work has something solid to stand on.