Have you ever been in a room where everyone is capable, but the room is starting to drift?
The talent is there. The experience is there. The urgency is certainly there.
But clarity is missing. Alignment is slipping. And people are starting to look around for direction.
I have been in that room.
On the field. On the sideline. And in cybersecurity, where the stakes are real.
And one more thing…
It is rarely a capability problem. It is an alignment problem.
Have you seen it in your own team? In a capable colleague carrying more than their role was designed for? In yourself, perhaps, even before the title arrives?
That is where this began for me.
Not as a theory. Not as a lucky idea.
As a pattern I had lived.
I had been coached. I had been mentored. And I am still learning.
Still being challenged, by the work, the people around me, and the responsibility that comes with leading.
So when I started seeing the same signals surface across football, cyber teams, and mentoring …
I paid attention.
When I first shared those parallels, people recognised it immediately.
Not because it was new.
Because thet had seen it.
They knew the room. They knew the drift. They knew what it felt like to be expected to lead before they felt ready.
That stayed with me.
Because leadership is often presented in a static, polished, corporate way.
But real leadership does not feel like that.
It moves. It shifts. It stretches people. It asks for clarity, trust, discipline, communication, adaptability, and judgement…often all at once.
That is what led me to build The Hacker in the Huddle.
Over time, it became clear this was not a single idea.
It needed structure. Not something to read once and set aside. Something you could return to.
So The Hacker in the Huddle became a system.
Built around twelve STACKS.
Each one focused on a specific part of leadership in practice—bringing people together, communicating clearly, staying disciplined, adapting when things change, and continuing to lead when conditions are not ideal.
These are not abstract ideas.
They are the things that show up repeatedly— in teams, in organisations, on the field, and in the moments where leadership is tested.
The system is structured across four domains:
Foundation. System. Pressure. Impact.
Not to complicate things, but to reflect how leadership actually unfolds.
You build it. You apply it. You are tested in it. And you are measured by what it produces.
It is designed to be navigated, not just read. To be entered where the need is felt. And to give you something steady when things begin to drift.
Where to begin
If this speaks to where you are now, start with the →
Loading...
Then, when you are ready, step into the full system.