Transformation Under Scale — Part I: Constrain the Possible, Not the Ideal

Mon, 24 Aug 2026 00:00:00 +0000

When a transformation begins, the instinct is to draw the target: a clean picture of the system as it should be, planned backward from. Over an existing estate, that is the wrong first move.

You do not design the ideal system. You constrain the possible one, and the constraints come from what the company is trying to do, not from taste. Each objective, taken seriously, becomes a constraint that rules some designs out.

That is what I mean by architecture as practiced constraint. A transformation is that practice at estate scale: a set of limits drawn from the company’s objectives and held over the estate you have, not a picture to build toward. Get the limits right and the program follows from them. Reach for a picture and you spend three years learning it was a wish.

The examples in this series come from one program: an architecture-led transformation at a national wireless carrier serving millions of subscribers, on a fifteen-year estate that had grown without a central architecture function. Everything concrete is genericized, but the decisions are real.

Enterprise Architecture on Andrew Hunter — Systems, Architecture, and Engineering Governance

Transformation Under Scale — Part I: Constrain the Possible, Not the Ideal