Engineering Leadership
Leading through operational complexity
Leaders create scale by making the system easier for other people to operate.
As teams grow, leaders are often rewarded for being the person who can untangle every difficult situation. That is useful for a while. It also creates a ceiling: the organisation learns to wait for the leader instead of improving the system.
Make the work legible
When I built a delivery and support function across EMEA and APAC, the first challenge was not hiring. It was making the work visible enough that new people could make consistent decisions. We clarified intake, ownership, escalation, service expectations and the evidence used in reviews.
Process is helpful when it reduces cognitive load. It becomes bureaucracy when people maintain it without understanding which decision it is meant to improve. I regularly ask teams to name that decision. If they cannot, the process needs attention.
Standards and judgement must coexist
Runbooks provide a safe starting point, especially during incidents. They cannot anticipate every customer configuration or production failure. Teams also need permission to exercise judgement—and a clear way to record why they departed from the standard.
This balance matters in regulated environments. Good governance does not eliminate discretion; it makes discretion visible, accountable and learnable.
Operational excellence is a management system
I do not see operational excellence as a quarterly initiative. It is the rhythm through which a team reviews service health, incidents, customer friction and improvement commitments. The rhythm has to survive leadership attention moving elsewhere.
My preferred signal of maturity is not that I am invited to every decision. It is that the team makes a good decision, explains the evidence behind it and improves the playbook afterwards.