Architecture must survive implementation.

A target state is only the beginning

A coherent architecture makes choices visible. It explains how capabilities fit together and where important boundaries sit. But the value of that architecture depends on a second question: how does the organisation move from what it has today to what it needs tomorrow?

Treat constraints as design inputs

Existing platforms, organisational responsibilities, engineering capacity, control requirements and investment cycles all influence the path. They are part of the problem to solve. A design that assumes them away may look elegant while leaving the hardest decisions to the implementation team.

Describe the intermediate states

Most substantial transformations operate in more than one state for a period of time. Old and new systems coexist. Data moves across boundaries. Ownership changes at different speeds. Each intermediate state needs a credible operating model, clear controls and a decision about how long it can remain in place.

Make trade-offs reviewable

Good architecture records the alternatives, the assumptions and the reasons for a decision. This helps people revisit a choice when circumstances change. It also gives senior stakeholders a useful conversation about cost, risk and capability instead of asking them to approve a technical diagram in isolation.

Close the feedback loop

Implementation provides evidence that the original design could not contain. An effective architecture practice uses that evidence to refine the plan. The aim is a direction that remains coherent while responding to what engineers and operators learn. Advisory work becomes stronger when it has been shaped by the experience of delivering change.