Base120 · Systems
Governance Patterns
Design decision rights, accountability structures, and coordination mechanisms
When to use
"Use when designing how decisions are made in a system. Specify who has decision rights, who is accountable, and how coordination happens. Governance patterns determine whether the system can act coherently."
Example
"A microservices architecture needs a governance pattern — who decides service boundaries, who owns API contracts, how are breaking changes coordinated. Without governance, services proliferate and contracts drift. With governance, the architecture evolves coherently."
Common misuse
"Governance that is all process and no decision. A governance pattern that requires 5 committees to approve a change produces paralysis. Governance should enable decisions, not prevent them."