A £700k enterprise travel portfolio was in flight with no stable architectural baseline. Multiple prior contributors had left scope that had grown ahead of any shared definition of done, a fixed budget, and a timeline already under pressure. The environment called for a Design Authority posture, not schedule recovery.
The Architectural Pivot
The pivot was establishing end-to-end architectural baselines before resuming delivery. BDD-led requirement specifications introduced shift-left discipline, resolving ambiguity before it reached the implementation layer. Highly available cloud ecosystems in C#, .NET Core, Azure, Redis, and ElasticSearch gave the portfolio a coherent technical backbone. The baseline then became the primary scope management tool: a change request that lacked architectural grounding was returned with a documented rationale. Reading the genuine technical requirement behind each commercial ask, and maintaining architectural boundaries where scope additions would have compromised system stability, rebuilt delivery confidence faster than any schedule recovery could have.
The Friction
The true friction was not the schedule. It was the absence of a stable architectural baseline across a portfolio shaped by multiple contributors over time, combined with scope evolution driven by commercial priorities arriving ahead of architectural review. The work was translating high-level commercial objectives into governed technical scope, and holding architectural boundaries under pressure. The friction was the cost of that governance: maintaining technical positions under commercial pressure, backed by documented rationale. The governance artefacts made that position sustainable without turning every decision into a negotiation.
The Rulebook
- Inherited scope is a liability until it is documented as a baseline. Never begin delivery on a portfolio without first establishing what the architecture is and is not permitted to do.
- Scope evolution in enterprise programmes is an architectural governance problem, not a project management one. The Design Authority’s role is to translate commercial intent into governed scope and hold structural boundaries under pressure.
- Client confidence is rebuilt through architectural evidence, not schedule recovery. A client who can see a coherent, governed baseline trusts the delivery; one who cannot will find the next change request just as destabilising as the last.
This engagement established the foundation. The client subsequently retained SCITAS Ltd directly for independent Design Authority.
