Home / The Hacker in the Huddle
STACK 000 // Root Access
THE HACKER IN THE HUDDLE
The Foundation of the Leadership Operating System
Mark Adjei
Why I wrote The Hacker in the Huddle
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.
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.
Alignment is slipping.
And people are starting to look around for direction.
I have been in that room on the field as a player, on the sideline as a coach, and in cybersecurity, leading teams and working in cyber risk and governance where the stakes are real and the consequences are visible.
Have you seen it in your own team?
In a capable colleague carrying more than their role was designed for?
In yourself, perhaps, already sensing the need to lead, even before the title, the team, or the formal responsibility has arrived?
In a capable colleague carrying more than their role was designed for?
In yourself, perhaps, already sensing the need to lead, even before the title, the team, or the formal responsibility has arrived?
That is where this began for me.
Not as a theory.
Not as a lucky idea.
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, sharpened, and stretched by the work, the people around me, and the responsibility that comes with leading.
I had been mentored.
And I am still learning, still being challenged, sharpened, and stretched 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 publicly, people recognised it straight away. They encouraged me to write it, but what stayed with me was not simply that they liked the idea. It was that they saw themselves in it.
They knew the room.
They knew the drift.
They knew what it felt like to be expected to lead before they felt fully ready.
They knew the drift.
They knew what it felt like to be expected to lead before they felt fully 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.
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.
How it grew into a system
Over time, it became clear this was not something that could sit as a single idea.
It needed structure.
Not in the traditional sense.
Not something to read once and set aside.
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.
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
System
Pressure
Impact
Not to complicate things, but to reflect how leadership actually unfolds over time.
You build it.
You apply it.
You are tested in it.
And ultimately, you are measured by what it produces.
You apply it.
You are tested in it.
And ultimately, 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 to return to when things begin to drift.
Preview the Interface ↩️
Why it had to be built this way
This was never meant to be static.
Leadership does not stand still.
The environments we operate in do not stand still.
The environments we operate in do not stand still.
So the system should not either.
That is why The Hacker in the Huddle is built as a digital, visual playbook.
Not to make it different for the sake of it, but to reflect how it is actually used.
You do not always enter at the beginning.
You enter where the need is.
You move through it.
You return to it.
You see something new in it as your experience deepens.
You return to it.
You see something new in it as your experience deepens.
Each STACK stands on its own.
Over time, each will be explored in greater depth, expanded into its own body of work, while still connecting back to the same underlying system.
This is not a finished piece.
It is something that grows
As the work continues and as the experience behind it deepens.
As the work continues and as the experience behind it deepens.
Where to begin
If this speaks to where you are now,
the next step is here.
the next step is here.
STACK 000 // Root AccessTHE BINARY PLAYBOOK SERIES
THE HACKER IN THE HUDDLE
Continue to the product page on Gumroad
Explore Mark's Work