One Thing I Have Learnt¶
The story of M5L Consulting¶
I have spent 30 years working in engineering teams of various sizes, and one thing I have learnt above all else: the difference between teams that scale well and teams that don't isn't talent. It's leadership. This is the story of how I finally did something about it.
But let me start at the beginning.
I was nine, maybe ten. My dad came home and told us his company had folded. I remember the panic. My thoughts went very quickly from him handing back the company car to imagining us selling the house. I decided something that day: I was never going to have that conversation with my children.
So I played it safe. For a long time. I took jobs that were offered to me. I was good at them. I worked hard, built teams, fixed things that were broken — and quietly abdicated the bigger risk. The one where I was in charge.
And then, somewhere in a career that took me from Mercedes-Benz to Nominet to Cloudflare to Imperva, I realised something uncomfortable. I did my best work when the stakes were highest and there was no one else to step in. When the ambiguity was total and the pressure was real.
That's when I came alive.
Thirty years of walking into broken teams, scaling organisations, fixing things that shouldn't have broken in the first place. Doing it well. Doing it for other people's companies. At some point that stops being caution and starts being a waste.
M5L isn't me finally being brave. It's me deciding it was time.
What Corporate Scaling Gets Wrong¶
I've seen a lot of technical organisations under pressure. I've watched the same thing happen, over and over again, when a company starts to scale fast.
They hire brilliant people. Then they bury them in process. They stand up teams without giving them a model to operate in. They promote strong individual contributors into leadership roles and give them no support. They ship products at pace and let the operational foundations crumble quietly underneath.
And then, when it starts to break, the incidents get more frequent and more complex, the team gets noisier, the attrition creeps up — they reach for more process. More governance. More oversight.
It never fixes it.
The problem isn't process. The problem is that no one stopped to build the foundation before they started building the floors.
I've spent most of my career walking into those situations. Sometimes I was hired specifically to fix them. Sometimes I just couldn't stop myself.
There's a particular kind of technical leader who is drawn to ambiguity. Who looks at a broken team and sees a puzzle worth solving. Who would rather rebuild something — or stand something up from scratch — than inherit something tidy.
I am that person. Probably to a fault.
But here's what I've learned: the companies that scale well don't fix problems faster. They build teams that create fewer of them.
The Gap That's Difficult to Fill¶
Here's a pattern I kept seeing, in every organisation I worked in.
There's no shortage of strategy consultants. No shortage of recruitment firms. No shortage of coaches, advisors, and frameworks for technical leadership.
But when a CTO or VP is staring down a scaling crisis — a team that's tripled in size, a global structure that's held together with goodwill and spreadsheets, an engineering org that's technically capable but operationally fragile — what they actually need is someone who's been in the room.
Not someone with a framework. Someone with scar tissue.
Someone who's made the 2am call when the platform went down. Who's restructured a team across a dozen time zones and got it wrong the first time. Who's stood in front of a board and explained why the thing that was supposed to work didn't. And then fixed it.
That person is genuinely hard to find on a consulting basis. They're usually still inside a company — because the companies that have them hold on to them tightly.
M5L Consulting exists to change that. I've built the thing I wished existed when I needed it. Senior, experienced, operational. Not advisory in the abstract sense, but actually with you in the work.
What "Without the Chaos" Actually Means¶
Our tagline is Scaling technical teams without the chaos.
People sometimes ask what the chaos bit refers to. They assume it means something dramatic — a production outage, a public incident, a team in open revolt. Sometimes it does. But usually it's quieter than that.
Chaos, in my experience, looks like this:
It looks like a VP who hasn't slept properly in three months because they're the only person who knows how everything connects. It looks like a team that's technically excellent but has no shared model for how they operate. It looks like an engineering org where the on-call rota is held together by a combination of heroism and guilt. It looks like a company that's grown faster than its foundations.
The opposite of chaos isn't control. It's clarity.
Clarity about how decisions get made. About ownership. About what good looks like, and how you know when you're not there yet. About how to build a team that scales without losing the things that made it good in the first place.
That's what I do. Mostly in the middle of the chaos, which is a perfectly acceptable time to start.
What We're Building, and Who It's For¶
I opened this piece by admitting something I'd been avoiding for years: it was time to do this for myself. M5L Consulting is my answer — and here's exactly what that means.
M5L Consulting works with technical leaders and the companies and investors that back them.
If you're a CTO, VP of Engineering, or founder whose technical organisation is under the strain of growth — this is for you. If you're a Private Equity or Venture Capital business and you need someone to walk in, assess what (if anything) is broken, and help fix it, this is for you. If you're a board that needs a senior technical voice in the room, this is for you.
What I actually do:
Operational transformation. Walking into scaling organisations and helping build the foundations — team structures, operating models, delivery practices — where none exist or where what exists isn't working.
Board advisory. Providing senior technical perspective to boards and investors who need someone who's done it, not just studied it.
Investor-appointed troubleshooting. The work that happens when something has gone wrong and someone needs to understand why — and what to do about it.
Mentoring & coaching. Working directly with technical leaders who are brilliant at their craft and want to get better at the leadership bit.
I'm based in the UK. I work globally. I'm a builder in ambiguity — which is a polite way of saying I'm most useful when the situation isn't well defined.
If any of this sounds like what you need, I'd love to talk. Drop me a message or connect.
M5L Consulting. Scaling technical teams without the chaos.