How I lead

I create clarity, raise the ambition, and build organisations where capable people make good decisions fast.

Strategy decides what matters. Execution decides whether it was ever real, and that's where most of my time goes.

My first move in almost any situation is the same short sequence: what are we trying to achieve, why does it matter, what's in the way, who owns it, what's next, and how will we know if it worked.

Where I differ

How I'm most useful, in practice.

  • A founder's ownership, without the title

    The business's outcome is mine, not a job I'm doing well. That changes what I'll take on: the calls no one wants to own, the unglamorous work when it's what moves things, and decisions made for where the business should be in years rather than for my time in the seat.

  • New domains fast, far enough in to lead them

    I get into an unfamiliar discipline quickly, whether that's finance, engineering, product or AI, and far enough in to lead the work rather than just sponsor it. I've had to do this across most of the functions a business like this runs on.

  • Strategy and execution, switched fast

    I set direction with the leadership team, then go into the detail to make sure what we decide actually ships. Being effective at both, and moving between them fast, is where a lot of otherwise strong leaders get stuck on one side.

Principles

The operating beliefs behind how I work and how my teams succeed.

How I decide

  • Start with reality

    Understand what's actually happening before deciding what the story should be. I'd rather hear "we're behind plan, and here's why" than a confident narrative. Watch the leading indicators even when they're uncomfortable, and change your mind when the evidence does. Consistency with the evidence beats consistency with what you said last quarter.

  • Move fast on reversible decisions

    Understand, decide, ship, measure, learn, improve. Not: understand, discuss, align, discuss again, perfect, eventually ship. Where I'm accountable and the information exists, I decide within 24 hours. Irreversible decisions get the deep analytical treatment; most decisions aren't that, and treating a reversible one as if it were is its own kind of risk.

  • Disagree before we decide, commit after

    Good decisions need intellectual conflict. I'd rather someone tell me "I think you're wrong, and here's why" than execute something they believe is a mistake, and I ask for criticism of my own thinking. Once a decision has been properly debated, I expect alignment and clear ownership. Strong opinions in the debate; one direction after it.

  • Go as deep as the outcome needs

    I go as deep as the outcome requires, and no shallower. Usually that's enough to ask sharp questions and make the call. But in the disciplines a business genuinely depends on, I go further, far enough to lead the work rather than sponsor it. SEO is the clearest example: it has underpinned my whole career, and I've stayed hands-on enough to hold my own with the specialists on the substance.

How I build organisations

  • Build systems, not heroics

    When something goes wrong repeatedly, the incident isn't the problem; the system that allowed it is. Incentives, ownership, decision rights, information flow, tooling, metrics. I'm drawn to mechanisms that make good outcomes repeatable rather than dependent on a few people trying harder.

  • Meet each person where they are

    What I want from someone is fixed: their best work, and the motivation to keep doing it. How I get there depends on the person. With some I am directive; with others I mostly ask questions and leave them the route; with others I put a lot of raw ideas on the table and let them choose. What I don't do is run one management style and expect everyone to fit it. I care about unlocking what someone is capable of, not the method.

  • Be exceptional where it creates advantage

    Every team is expected to aim for best-in-class delivery, real moats and clear USPs, and that standard doesn't move. But no organisation wins everywhere at once, and spreading effort evenly is how you end up exceptional nowhere. So I concentrate my own attention where being genuinely best-in-class makes the biggest difference, and keep the ambition alive elsewhere through the leaders who own it.

  • Build for compounding

    I favour capabilities, systems, people and advantages that are worth more over time. In practice it looks unglamorous: a 1% improvement every week, relentlessly. It's how 30-person teams became 300-person organisations three times over, and how a P&L grows 30%+ in seven of eight years.

How I run the operation

The mechanisms that keep the organisation moving without me in every room.

  • Place myself where the value is

    I delegate as far as the organisation can carry while still hitting the outcome, and build the system so it carries more over time. Being involved in less is the goal, because it multiplies where I add value, but it isn't a rule: sometimes I go into the detail on purpose. What stays constant is knowing what is actually being delivered everywhere, which tells me where to lean in and where to pull back.

  • A fixed operating cadence

    A fixed cadence is one of the things I rely on most. Weekly tactical reviews with each leadership team, monthly on strategy, quarterly on progress toward the vision; investment and ROI reviewed continuously, not on a clock. The calendar underneath it is my single source of truth, so no priority slips and most of my time stays on what unlocks the most value. My teams run this way too, at whatever cadence fits them.

  • Allocation is the real job

    Allocation is one of the most important things I do, and I run it continuously, not on a quarterly cycle. Every discipline has clear ROI metrics, or at least agreed leading indicators where direct ROI can't be measured. I allocate against a consistent formula built for both short-term results and long-term position, and I move fast in both directions: cut quickly once there's proof something isn't working, double down once there's proof it is.

  • Accountability, named

    This starts with me: I meet my commitments and my deadlines short of a real force majeure, and I'm known for it. I expect the same from the leadership team: clear outcomes, a named owner, a date, and an honest account of what got delivered. Sustained underperformance gets confronted, not absorbed. And I watch the micro-behaviour of my leaders closely, because it becomes the behaviour of the whole organisation.

  • Communication drives culture and performance

    Communication is one of the biggest levers on culture, performance and motivation: people do their best work with clarity on where we are, where we're going and why. So I design the flow deliberately, both directions. Outward: a note to the whole business unit every couple of weeks, in my own words with a short video, covering the real numbers, the strategic read, wins and lessons, and straight answers to the hardest questions. Inward: replies to every engagement-survey comment, time several levels down, early indicators across every team. Done well, it scales trust past the room I'm in.

Through change

Acquisitions on both sides, integrations, the normal run of ups and downs. The approach doesn't change. I'm direct about hard news rather than managing the message, so people keep trusting me when it isn't good, and I can carry a hard message in a way that holds buy-in rather than drains it. I protect the culture, people feel the stability under the change, and we come through it together.

What I'm still working on

Most of the above, taken too far, is a failure mode. The ones I watch for.

  • Bringing people along when my thinking has moved ahead

    What feels obvious to me after a few hours is new to everyone else. Executive clarity isn't organisational clarity, and closing that gap is my job.

  • Staying at the right altitude

    The curiosity that helps me spot weak assumptions, and my impatience with passive ownership, can both pull me into problems that belong to someone else, sometimes before they've had the room to solve it themselves.

  • Separating "interesting thought" from "let's do this"

    The more senior I get, the more easily a casual idea becomes a project. I have to make it unmistakable which one I mean.

  • Making high standards create ambition, not dependency

    Pace and expectations energise autonomous people; they can push others to optimise for guessing my answer instead of forming their own. That looks like alignment and quietly weakens the team.

  • Setting a pace people can sustain

    The pace and ambition that energise me can be draining for others, and I've had that feedback more than once. Keeping the intensity sustainable is on me: reading who is running hot and easing the load before it tips toward burnout instead of better work.