Writing

Notes on how organisations actually work.

Short pieces I write on leadership, operations, and teams. General perspective, plainly put — the ideas that keep showing up in my conversations with leaders.

On leadership

The calendar never lies

Every organisation has two strategies: the one in the deck, and the one in the diary. When they disagree, the diary wins — every time.

Leaders tell me their priority is developing people, then show me a week with no unhurried conversation in it. They say quality matters most, then spend their best hours in status meetings about speed. Nobody is lying. The deck strategy is what they believe; the diary strategy is what they've defaulted into, one reasonable-sounding meeting at a time.

This is actually good news, because a calendar is easier to change than a culture. If you want to know what your organisation really values, don't run a survey — print the leadership team's last month of calendars and read them like a bank statement. Every hour is a spend. Then make one honest trade: remove a recurring block that serves nobody and put the stated priority in its place, at a protected time, every week.

People don't learn what matters from what leaders announce. They learn it from where leaders reliably show up. The calendar is the announcement that gets believed.

On operations

Slow is a symptom

When an organisation feels slow, the first instinct is to push people harder. It's almost always wrong. In my experience, slowness is rarely a speed problem — it's an ownership problem wearing speed's clothes.

Watch a delayed piece of work closely and you'll usually find it moving quickly whenever someone actually has it, then sitting still in the spaces in between: waiting for a decision nobody feels entitled to make, a review nobody scheduled, an approval whose owner is a group rather than a person. The work isn't slow. The handoffs are.

So before any talk of urgency, ask three questions about the stuck thing. Who owns it — one name, not a team? What is the next decision, precisely? And who is allowed to make that decision without another meeting? If any answer is fuzzy, you've found the real bottleneck, and no amount of pressure on the people doing the work will fix it.

Speed isn't a virtue you demand. It's a by-product of clarity you design.

On teams

The quiet meeting problem

A quiet meeting looks like alignment. Usually it's the opposite: it's disagreement that has gone private.

When nobody pushes back in the room, the pushing back doesn't stop — it moves to the corridor, the direct message, the one-to-one where it can't change the decision, only undermine it. The team pays twice: first for the flawed decision that went unchallenged, then for the slow-motion resistance to it.

The fix isn't demanding that people "speak up more"; that instruction transfers the whole burden to the least powerful people in the room. The fix is making disagreement cheap. Ask for objections by name — "What would have to be true for this to fail?" — rather than waiting for volunteers. Have the most senior person speak last, so the room isn't just agreeing with rank. And when someone does dissent, treat the objection as material to work with, visibly, even when you overrule it.

You can tell a healthy team not by how little it argues, but by where it argues. Good teams disagree in the room and back each other outside it. Quiet ones do the reverse.


Want to talk about any of this?

If one of these pieces sounds like your organisation, that's usually a good conversation waiting to happen.

Get in touch