Leadership profile
My approach to leadership has developed over years of building technology, leading teams, and working through complex transformations. I start by creating clarity around what the business needs to accomplish, making the economics and tradeoffs visible, and giving people the context, trust, and accountability they need to lead.
A practical leadership system
I believe the best leadership creates clarity and accountability while giving people meaningful ownership of the decisions and outcomes they are responsible for.
I've learned that if I'm unwilling to let people make decisions, take risks, and occasionally get something wrong, it's very easy to become too prescriptive. My job isn't to make every decision. It's to make sure people understand the outcome we're trying to achieve, the constraints we're operating within, and where they have the authority to lead.
That doesn't mean stepping away from the work. I stay connected through regular operating cadences, clear measures of progress, and direct conversations with the people closest to the work. I ask questions, challenge assumptions, and pay attention to early signals that something may be getting off track. When intervention is needed, I intervene. When it isn't, I give people the room to solve problems, make decisions, and learn from the experience.
I want leaders to own outcomes rather than wait for direction. That requires enough transparency to identify risk early, make tradeoffs together, and keep the work connected to what matters to the business.
How I lead
Technology decisions should begin with the business outcome, not the technology. I want teams to understand what we're trying to accomplish, what it means for the business, and how we'll know whether it worked. That context helps people make better decisions throughout the work without having to escalate every tradeoff.
Cost isn't something I consider after the architecture or strategy is decided. It's an input to the decision from the beginning. I want teams to understand the cost to build, operate, support, and change a solution so we can make informed tradeoffs between capability, resilience, speed, and economics.
Trust grows when people can see what's happening, understand how decisions are being made, and know who is accountable for what. I create that transparency through clear ownership, regular communication, visible measures of progress, and commitments people can rely on.
I want people to grow into leaders who can make sound decisions without waiting for me to make them. That means giving them meaningful ownership, being clear about expectations and decision rights, coaching when needed, and allowing room to learn from mistakes. My role is to help people become more capable and confident as leaders.
Leadership scope
I've applied these principles across IT strategy, enterprise architecture, software engineering, cloud and data platforms, infrastructure, AI, data privacy, resilience, global teams, sourcing, and vendor strategy. That breadth has reinforced my belief that good technology leadership starts with the business problem and aligns the technology, operating model, and investment decisions around it.
Leadership in action
The best evidence of a leadership approach is what happens when it's applied to real problems. These case studies show how I've worked through complex decisions, competing priorities, technical constraints, and organizational change to produce measurable results.
Explore the case studies ↗