What a working design authority looks like
A design authority should make programmes faster and safer. Many do the opposite. The difference is usually in a handful of habits.
Its job is to decide, not to review
A design authority exists to make significant technical decisions well, quickly and on the record. If papers come to it for comment and leave without a decision, it has become a discussion group, and teams will stop bringing things to it.
Most decisions should never reach it
Set guardrails and patterns that teams can work within on their own authority. Reserve the design authority for decisions that are expensive to reverse, cut across teams or depart from an agreed standard. A team choosing between two approved patterns does not need a meeting.
A simple test helps: if this turns out to be wrong, how hard is it to change? Easy to change means the team decides. Hard to change means it comes to the authority.
Keep the paper short
One or two pages is enough for most decisions:
- the context and the problem
- the realistic options, including doing nothing
- the recommendation and why
- what it costs, what it risks and what it rules out
If the options can't be explained in that space, the thinking usually isn't finished.
Keep the membership small and standing
A handful of people who attend every time will make better decisions than a large group that changes weekly. Include security and operations from the start, so their concerns shape designs instead of blocking them at the end. Invite the team presenting, and nobody else by default.
Commit to a turnaround
Teams plan around the authority when they know how long a decision takes. Meet on a fixed rhythm, publish the deadline for papers and agree a route for urgent decisions between meetings. A decision that takes a month will be made without you.
Publish the decision log
Every decision goes into a log the whole programme can read: what was decided, when, by whom and why. It stops the same argument being held twice, it gives new joiners the reasoning behind the architecture and it gives assessors and auditors the evidence they ask for.
Signs it has stopped working
- The queue of papers keeps growing.
- Decisions are made in the meeting but can't be found afterwards.
- Teams bring designs after they have built them.
- Nothing is ever rejected or changed.
Any one of these is worth acting on. Two or more usually means the authority needs resetting: narrower scope, fewer people and a firmer rhythm.