Notes on building UX governance that doesn't suffocate
- Navin Mathew
- May 22
- 1 min read
Governance has a reputation problem. People hear it and think slowdowns, gates, committees. That's bad governance. Good governance does the opposite.
Rules vs rails
Rules tell people what they can't do. Rails tell people where the safe paths are, then get out of the way. The difference matters at scale.
When I introduced UX governance at PowerSchool — intake models, design review cycles, content standards — the goal wasn't control. It was reducing decisions. Most rework happens because the same questions get answered five different ways by five different people.
Governance done right reduces decisions, doesn't add them.
What actually compounds
Intake models. So requests don't show up half-formed at the wrong moment.
Review cycles. So critique happens early, with the right people, not at the end when it's expensive.
Content standards. So the third writer doesn't reinvent voice from scratch.
Reusable patterns. So the next team doesn't start blank.
30% iteration cycle reduction at PowerSchool came from this layer. Not from better tools. Not from new hires. From the rails.
The trap
Governance fails when it becomes someone's job to enforce instead of someone's job to maintain. Don't build a gate. Build a paved path that's easier to follow than to ignore.
Comments