Governance before heroics.

How I think about leadership

Leadership is the work of creating conditions in which good decisions and coordinated action can happen. Technical expertise matters, but at broader levels the leader cannot personally solve every problem. The task becomes setting direction, creating clarity, connecting the right expertise and maintaining control of the outcome.

Governance before heroics

A project should not depend on one person repeatedly rescuing it. Good governance establishes a workable baseline, decision rights, review cadence, evidence and escalation paths. It makes exceptions visible before they become crises.

Governance is not paperwork for its own sake. It is a practical control system for the project.

Decision-making under uncertainty

Perfect information is rarely available when a decision is due. My preferred approach is to separate what is known, what is assumed and what remains uncertain; assess the consequence of being wrong; identify reversible and irreversible decisions; and make the next decision with an appropriate level of evidence.

The objective is not to eliminate uncertainty. It is to avoid being surprised by uncertainty that should have been visible.

Influence without authority

Cross-functional delivery often depends on people who do not report to the project lead. Influence therefore comes from credibility, context, clear expectations, useful structure and consistent follow-through.

I try to make it easy for stakeholders to understand why their contribution matters, what decision is needed, by when, and what is affected if it is delayed.

Risk and accountability

Risk management is most useful when it changes behaviour. A risk register that no one uses provides little protection. Material risks need an owner, a response, a trigger or review point, and a clear relationship to the decisions that leaders must make.

Accountability also needs to be explicit. I distinguish between doing the work, owning the outcome, providing specialist advice and approving decisions.

Building capability

Projects end, but capability should remain. A successful change should leave behind clearer work, better documentation, trained people, maintainable systems and a way to recognise when performance is drifting.

Long-term thinking

Short-term delivery pressure can hide future operating cost, maintenance burden, quality risk or dependency on individuals. I try to include those consequences in the decision rather than treating handover as the end of the problem.

Systems over individual dependency

Strong organisations make knowledge and control visible. Standard work, sensible governance, traceability, reliable data and clear ownership reduce the need for memory and heroics.

Learning as a leadership discipline

After meaningful work, I want to know not only what happened but how the decision process worked: which assumption mattered, what risk changed, who was influenced, what capability improved and what I would do differently next time.