Governance That Outlasts Your Tenure
I've watched organizations build elegant operating models, governance frameworks, and decision architectures—and watched them collapse the day a key leader left.
This is the real test of organizational design: Does it survive leadership transitions?
Most frameworks fail because they're built around people, not principles. "This is how we do things because this is how [Leader] does things." Remove the leader, and the whole structure becomes a cargo cult—people performing rituals they don't understand toward purposes that no longer exist.
True governance outlasts individual leaders because it's built on principles, not personalities.
I was asked to help a major financial institution design governance for their enterprise technology function. They had 3,000 people, unclear decision rights, and constant escalation loops. Every decision felt urgent because nobody knew who should be deciding.
We built governance around principles: - Principle of subsidiarity: Decide as close to the work as possible - Principle of transparency: Every decision route is documented and visible - Principle of reversibility: Low-cost decisions should be made fast; high-cost decisions should require more scrutiny - Principle of accountability: Every decision route has a clear owner
From these principles, we built decision trees. Not org charts. Decision trees. For every category of decision—hiring, vendor selection, technology architecture, policy changes—we made explicit who decides, who informs, what criteria matter, and what escalation looks like.
The framework became permanent because it didn't depend on any individual's judgment. It was written down. It was teachable. New leaders could inherit it without reinventing it.
Did they modify it? Yes. But they modified the principles, not the personalities. They added rigor, not reinvention.
That's how you build governance that outlasts tenure. You codify principles. You document decision routes. You remove personality from the framework.
When your successor arrives, they inherit clarity, not confusion.
Copyright Notice: This article is the intellectual property of GeneralArc and Amrita Sandhu. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form without prior written permission. For permissions or inquiries, contact amrita@generalarc.com.
Disclaimer: The views and opinions expressed in this article are for informational purposes only and do not constitute professional advice. Readers should consult with qualified professionals before making any decisions based on this content.
About the Author
Amrita Sandhu brings 22 years of experience in organizational transformation, talent strategy, and enterprise architecture. She has held senior leadership roles at JPMorgan Chase, Nomura, and McKinsey & Company, leading transformations across 100,000+ employees and delivering significant organizational impact through structured change management and governance frameworks.
More from Operating Model
The Operating Model as Competitive Weapon
Most organizations confuse org charts with operating models. The difference determines whether strategy succeeds or stalls.
Capability Architecture at Scale
How to build a taxonomy that actually works across 2,000+ roles — and why most capability frameworks fail.