What I believe.

I believe that leadership starts with example. One of the maxims I absorbed from the military is that we should not ask others to do something that we are unwilling or unable to do ourselves.

This doesn't mean a leader needs to be the best at everything. It means being willing to step forward, take responsibility and demonstrate the standards expected of others.

Trust is fundamental to how I work with people, but I don't believe trust means the absence of accountability.

People come from different backgrounds, experiences and beliefs, and they naturally have different ideas about what good work looks like. I try to give people the trust and autonomy to do their jobs well, while staying close enough to understand how things are progressing and whether they remain aligned with the broader intent.

To me, verification isn't about suspicion. It is about stewardship — making sure that the trust placed in people, and the responsibilities that come with it, are being honoured.

In large organizations, good ideas rarely fail because someone deliberately set out to make them fail. More often, information was missed, assumptions were different, or people were brought in too late.

I therefore prefer to communicate earlier than feels necessary and involve people who have a legitimate interest in the outcome, even when their role is simply to be informed. Alignment takes time, but misalignment costs far more.

Moving from the military into healthcare taught me that people want to do good work, regardless of their position in an organization. The challenge is often helping them see why their work matters.

A role can feel very different when someone understands how it contributes to a patient's experience, a team's success or the institution's larger mission. I believe leaders have a responsibility to make that connection visible.

When people understand the importance of their contribution, they often find an extra degree of ownership, motivation and determination that cannot be created through instructions alone.

I naturally gravitate toward ambitious ideas. Entrepreneurship has taught me that ambition alone doesn't build anything.

When faced with a large vision, I try to find the smallest useful version that can be built, launched and tested. It creates momentum, reveals what actually works, and exposes assumptions before too much time and money are committed.

The goal isn't to think small. It is to learn quickly enough to know where to think big.

As a Guardsman, I grew up with the idea of being ready — ready to move, ready to respond, ready to act when called upon. That mindset has stayed with me beyond military service.

In organizations, opportunities often arrive before we expect them. Being prepared means building capabilities, relationships, systems and people before they are urgently needed.

I don't believe preparation means waiting until everything is perfect. It means being ready enough to act when the opportunity appears.

One of the most enduring lessons from Lean and Six Sigma is that meaningful improvement rarely comes from a single breakthrough. More often, it comes from a disciplined process of identifying waste, understanding root causes, testing solutions and making small improvements consistently over time.

Throughout my career, I have been drawn to roles that involve building, fixing or transforming organizations. Whether opening a hospital, redesigning a service process or developing new capabilities, I try to leave systems stronger, more resilient and more sustainable than I found them.

Improvement is not a project with an end date. It is a mindset. Every organization can be made better, and every leader has a responsibility to contribute to that process.

My goal is simple: to leave every team, institution and system in a better state than when I first encountered it.

I have long believed that the best way to understand a problem is to experience it as closely as possible to where it occurs.

Whether in military operations, healthcare, or entrepreneurship, reality is often very different from the reports, dashboards and summaries that reach leadership. The most important insights are usually found where customers are served, where teams operate, and where processes break down.

This belief led me to introduce Gemba walks into my workplace. By observing work where it happens, speaking directly with frontline teams, and occasionally experiencing the process as a user myself, I have found that problems become clearer, root causes become more visible, and improvements become far more practical.

Seeing may not solve the problem, but it is often the first step toward understanding it properly.

I am naturally curious about problems that don't seem to have obvious answers. That curiosity often leads me to explore ideas across very different industries — healthcare, technology, human performance, real estate and others.

Not every idea becomes a successful business. Some never get beyond an experiment. But I have found that building something forces you to understand a problem differently: you encounter the customer, the economics, the operational realities and the constraints that aren't visible from the outside.

I am still learning to balance curiosity with discipline. One lesson I am actively working on is doing more market validation before becoming too attached to an idea.

I have become increasingly convinced that the fastest way to understand an idea is to make something tangible and let people use it.

Technology — particularly the emergence of AI-assisted development — has dramatically lowered the cost of turning an idea into a working prototype. I now find myself building and testing ideas that previously would have remained on a piece of paper.

But building the product is only one part of building a business. Distribution, trust, relationships, positioning and execution still require people. Technology can dramatically accelerate creation; it cannot remove the human work required to make something matter.

I don't believe good ideas belong neatly to one industry.

My interests have taken me across healthcare, technology, human performance, real estate and other fields. Each has its own language, constraints and ways of thinking, and moving between them often reveals connections that are harder to see from within a single domain.

Breadth, however, only becomes useful when paired with depth. My aim is therefore not to know a little about everything, but to remain curious enough to explore widely and disciplined enough to go deep when something matters.

Experience can make us more confident, but it can also make us less willing to question what we think we know. I try to stay conscious of that.

Every industry, organization and person has something to teach me. Being willing to listen — especially when the answer challenges an existing assumption — is one of the most important disciplines I can cultivate.