Building A Modern Design Authority
A design authority that meets weekly to review documents is not the same thing as a design authority that shapes decisions. Here is the difference.
Key Takeaways
- Design authority membership should reflect where risk actually sits, not organisational hierarchy.
- Decision rights and escalation paths need to be explicit and tested, not assumed.
- A modern design authority operates continuously, not as a periodic committee meeting.
Start with decision rights, not membership
Most attempts to build a design authority start with the wrong question: who should be in the room. The right starting question is: what decisions does this body actually have authority to make, and what happens when it disagrees with a delivery team, a vendor or a budget holder. Without a clear answer, the design authority becomes an advisory group whose recommendations are optional — which is a polite way of saying it has no real function.
Decision rights should be documented in plain language: what can the design authority approve unilaterally, what requires escalation, and to whom. This sounds bureaucratic, but the alternative — ambiguity resolved informally, case by case — is what allows political pressure to override architectural judgement without anyone quite deciding that it should.
Membership should track risk, not seniority
A design authority stacked with senior stakeholders who have limited technical depth produces governance that is easy to overrule and hard to trust. Effective membership is drawn from the people who understand where risk actually concentrates — security architecture, data, integration, identity — with senior sponsorship attached to give the body standing, not to substitute for technical judgement.
Continuous, not periodic
The committee model — a design authority that meets fortnightly to review a stack of submissions — is the most common reason governance falls behind delivery. Modern design authorities operate closer to a continuous service: lightweight triage for routine decisions, fast-tracked slots for time-sensitive ones, and full review reserved for genuinely high-risk architecture. The goal is to be fast enough that delivery teams engage early by choice, not slow enough that they route around governance out of necessity.
Facing this challenge inside your own organisation? Schedule a strategic architecture review to talk it through.