110
10
99.9
700
Case study · Cloud transformation
Case study · Identity at scale
Leading with integrity I have spent more than twenty years running infrastructure and security across 110-plus sites, where the wrong call has real consequences, so integrity for me is not a slogan but the thing that has to hold up under pressure. When I own enterprise IAM or run incident response, people need to trust that what I say matches what I do and that I will make the hard call in the open. Completing a leadership program at the University of Illinois pushed me to ground this in real research rather than instinct, and the principles below are the ones I actually lead by. Grounded in research on ethical and authentic leadership (Brown and Trevino; Avolio, Gardner, and Walumbwa), behavioral integrity (Simons), team psychological safety (Edmondson), and Level 5 leadership and leader humility (Collins; Owens and Hekman).
Tony Simons calls this behavioral integrity, the perceived alignment between what a leader says and does, and his research names it a core antecedent of trust. In infrastructure work I keep my word on maintenance windows, access decisions, and timelines, because that track record is what earns trust for the next hard decision.
Amy Edmondson's work on team psychological safety found that the strongest teams report more errors, not fewer, because people feel safe to speak up. Running incident response, I built that same climate so problems surface fast, which is a large part of how we came through with zero data loss.
Jim Collins describes Level 5 leaders who look out the window to credit the team and into the mirror to own failure, and Owens and Hekman show that leader humility spreads through a team by example. When a system I own goes down, I take the call on myself, because owning it is what earns the room to lead the fix.
Brown, Trevino, and Harrison define ethical leadership as demonstrating right conduct through your own actions and holding others to the same, and Ng and Feldman's meta-analysis shows this reaches performance through trust first. Owning enterprise IAM means I set the standard for how access and privilege get handled, so I hold myself to it before anyone else.
Founder venture
