What the authority covers
Say who can approve a high-impact interface pattern, who can block a deceptive one, and how exceptions are escalated.
What is design authority?
Design authority names the accountable owner who can approve, change, or halt a system’s design.
Design authority is the named owner who can approve, change, or halt a system's design. Naming one person or office keeps responsibility from spreading so thin that no one holds it.
When challenges against the design are upheld, the count goes to this owner. The owner changes the design or records why not.
A hypothetical case. A platform names a design authority for its recommender system. That role must sign off on any change to the ranking logic or the safety thresholds.
In the glossary: Design authority.
In practice
What to look for
Sign-off before launch
Where the authority is symbolic, risky experiments skip review as growth exceptions. Require a record of sign-off before launch.
A record of the authority used
Keep design decision records, a log of rejected patterns, and release gates that show the authority signed off before deployment.
Where the standards use it:
- Ethotechnics for agents. Match design authority to the standard's oversight, receipt, and challenge requirements.
- STD-02 evidence pack. Keep the ownership records and decision logs that show the authority was used.
How is design authority different from product ownership?
A product owner is responsible for delivery. A design authority can approve, halt, or require changes to a design because of the risk it poses to people.
What happens when authority changes?
Update the authority record and issue a receipt for the handover. Earlier decisions stay traceable to the former owner.