I recently wrote about architecture's real value: clarity that leads to better decisions. Simple artefacts. Alignment without friction.
The follow-up question was the same: "If this is the right way to work, why don't organisations do it?"
Because many have built processes that prevent clarity.
Nothing exposes this more than the 80-page monolithic design document — the template that merges HLD, LLD, Detailed Design, As-Built, risks and standards into a single artefact that serves no one. Produced out of obligation, reviewed out of ceremony, and outdated the moment it's saved.
Its real damage isn't size — it's the destruction of Architectural Integrity.
When documentation is prioritised over decisions, the monolith becomes a governance checkbox. It replaces clarity with noise and alignment with contradiction. Nobody reads it. Teams cherry-pick whatever supports what they were already going to do. It looks like rigour but hides risk and buries decisions.
The problem gets worse when organisations copy vendor-style templates without the vendor's discipline or context. What once protected a contract becomes, internally, a point-in-time fiction — endlessly reworked to maintain the illusion of accuracy.
This isn't architecture. It's Theatre.
And the hidden cost: the architect becomes the organisational shock absorber.
Unclear scope? "Put it in the design." Conflicting teams? "Let the architect propose something." No one wants to decide? "Capture it in the architecture."
The monolith enables this because it holds contradictions and is vague enough for everyone to interpret differently, while the architect's name sits on the front. Instead of shaping decisions, architects become document producers. Instead of enabling delivery, they drown in ceremony.
You can't have clarity and a monolithic design at the same time. You must choose.
Modern delivery needs intentional architecture: decisions with rationale, simple visuals that communicate, guardrails that guide, documentation that earns its place.
Two-page ADRs. One meaningful diagram. One-page standards. Artefacts that connect strategy to execution — architecture that accelerates teams, not burdens them.
Where do you start? Pick one monolithic document. Ask three people who use it: "What part of this influenced a decision in the last six months?" If the answer is "maybe two pages," you've found your target.
Start small. Fix one artefact. Prove the value. Expand from there.
The monolith isn't a legacy — it's a warning.
Clarity is the craft. Alignment is the outcome. Architecture — done well — moves organisations forward.