While looking into why Design Ops often runs into trouble, I found an uncomfortable truth about Invisible Governance: the “Just This Once” trap. I’ve seen how one tiny exception acts like a high-interest loan that eventually bankrupts a design system. But identifying the trap is only half the battle.
The real question is: How do I stop people from setting it in the first place?
Intro
It turns out, the answer isn’t in a Jira ticket. It’s on my plate.
I can shout about “process” until I’m blue in the face. I can churn out 40-page PDFs that gather dust on a shared drive. But if I don’t embody the values I’m promoting, nobody’s buying them. As Patrick Lencioni (2002) argued, culture isn’t about master plans; it’s about the courage to be consistent with your team. This is where most leadership fails: we want the results of a disciplined system without the personal tax of following it ourselves.
DOPAMINO’S UPDATES
Get a notification in your mailbox whenever there’s new content
Invisible Governance: From the Boardroom to the Dinner Table
Last night, my investigation into management moved to my dinner table. 7:00 PM is usually a negotiation zone—a tactical standoff. I was bracing myself for the “broccoli standoff”—the shouts, the bribes, the exhausting debate. Then, something remarkable happened. No noise. No drama. The younger one just watched his older brother finish his greens without a word. And then, almost by instinct, he picked up his fork and followed suit.
In that second, the “just this once” excuses I dissected last week vanished. Why? Because the standard wasn’t a rule on a wall, it was a visible action. This is the core of Invisible Governance. It is the silent architecture of behaviour that shapes a team when no one is looking.
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”
Antoine de Saint-Exupéry (1939)
In leadership, perfection is removing the need for heavy documentation by being a living example. If you have to explain the rule ten times, the rule isn’t working—your example is.
Beyond the Policy: Leading by Example
When we talk about Design Ops, we often focus on technical debt, but we rarely discuss Cultural Debt. Every time a Lead Designer bypasses a naming convention “just to move faster,” they are adding interest to that debt. You might save ten minutes today, but you’ve just told your juniors that the system is optional.
This is the flip side of my Pizza Hawaii Rule. While that rule is about what you exclude to prevent chaos (the ananas), eating your broccoli is about the Invisible Governance you embrace to set the standard. One is about boundaries; the other is about fuel.
This mirrors Simon Sinek’s (2014) principle that “Leaders Eat Last.” True leadership is a selfless act of setting the pace. If the leader doesn’t respect the design system, why should the intern?
My teammates aren’t reading my manifesto—they’re watching my plate.
The Default of Accountability
To build a culture of excellence, I have to embrace the broccoli first. When I visibly live the standards I expect, I’m not just managing; I’m setting a benchmark that makes accountability the default. Documentation is a ghost, but example is a force of nature.
Next time I’m faced with the broccoli, I’ll remember: it’s not just a vegetable. It’s a leadership test and the ultimate proof of Invisible Governance in action.
The stratospheric stuff I should have read, listened to, or watched a long time ago
- Saint-Exupéry, A. (1939). Terre des hommes (Wind, Sand and Stars). Gallimard.
- Lencioni, P. (2002). The Five Dysfunctions of a Team. Jossey-Bass.
- Sinek, S. (2014). Leaders Eat Last. Portfolio/Penguin.
- Clear, J. (2018). Atomic Habits. Avery.
DOPAMINO’S UPDATES
Get a notification in your mailbox whenever there’s new content
Discover more from DOPAMINO
Subscribe to get the latest posts sent to your email.
