Enterprise Leadership · Judgement · 10 min read
There Is No Leadership Hack
Why compressed knowledge can accelerate learning without replacing the experience, reflection and judgement leadership still requires.
I have lost count of how many variations I have seen of the same idea: five things successful leaders do, seven habits of great managers, three questions that will transform a team. Leadership certainly isn't unique in this respect. Almost every profession has its own versions, and every platform has people trying to make complicated subjects easier to understand. There is nothing inherently wrong with that. In fact, some of those lists contain excellent advice.
What interests me is what gets lost when complicated experience is compressed into something simple.
A leader with twenty years of experience may genuinely be able to identify five principles that have shaped how they lead. Those principles might be thoughtful, useful and entirely correct. But the five principles are unlikely to be what made that person capable of applying them. Behind those five sentences sit thousands of conversations, decisions, mistakes, disagreements, consequences and adjustments. There were probably situations where one principle worked beautifully and others where applying exactly the same principle produced an unexpected result.
The shortcut isn't necessarily wrong. It just isn't the journey.
That distinction matters because leadership is relatively easy to understand in principle. Most of us don't need much convincing that leaders should build trust, communicate clearly, empower people, take accountability and create an environment where people can speak openly. The difficulty begins when those principles encounter a real situation and stop pointing neatly in the same direction.
Empowerment is a good example. It is easy to agree that leaders should give people enough autonomy to make decisions. It becomes considerably harder when someone you have empowered makes a decision you strongly disagree with. At that point, the principle doesn't tell you whether to intervene. Perhaps stepping in is responsible leadership because you can see a consequence they cannot. Perhaps stepping in teaches them that their authority exists only while they agree with you. Both interpretations can be reasonable.
Transparency creates similar tensions. I believe strongly in giving people enough context to understand what is happening around them, but leaders also hold information that isn't theirs to share. Accountability can mean taking responsibility for something your organisation has done, even when you personally had nothing to do with causing it. Trust sometimes means allowing someone to make a mistake you could have prevented.
This is where leadership becomes much more difficult than its vocabulary suggests. Knowing what empowerment, transparency, accountability or trust mean is not the same as knowing what to do with them in a particular situation.
And increasingly, acquiring that vocabulary is becoming very easy.
When the Language of Expertise Becomes Cheap
AI has accelerated something that was already happening. We now have extraordinary access to knowledge. Someone can ask an AI system to explain psychological safety, executive presence, organisational transformation, accountability or incident management and receive a polished explanation within seconds. I see enormous value in that. Making knowledge more accessible should help more people learn from ideas and experiences that previously took much longer to find.
But it also creates an interesting distinction between knowing the language of something and understanding what it feels like when you are responsible for the consequences.
AI can explain how a critical production incident should be managed. That is useful knowledge. It is still different from owning one at two in the morning when a customer's business is affected, engineers disagree about the cause, executives want an update, and every new piece of information changes what you thought you understood ten minutes earlier.
It can explain accountability perfectly well. That is different from standing in front of a customer and accepting responsibility for a failure you personally didn't cause because, from the customer's perspective, the internal organisational boundaries behind the failure are largely irrelevant.
It can explain empowerment too. It cannot remove the discomfort of watching someone you trust make a decision you would not have made yourself and having to decide whether your responsibility is to intervene or to let them own it.
None of this makes AI less useful. Quite the opposite. I use AI precisely because access to knowledge, alternative perspectives and structured thinking can improve the quality of a decision. But faster access to knowledge is not the same thing as faster acquisition of judgement.
The danger is mistaking borrowed language for earned understanding.
Experience Doesn't Automatically Solve It
There is an equally tempting argument in the opposite direction: that experience is what matters and therefore someone who has spent twenty years leading people must possess better judgement than someone who hasn't.
I don't think that is necessarily true either.
It is perfectly possible to spend twenty years accumulating experience while repeatedly making variations of the same mistake. Time creates opportunities to learn; it doesn't guarantee that learning takes place. Experience becomes much more valuable when it is accompanied by reflection, feedback and adaptation.
Something happens. We make a decision. We see the consequences. Perhaps somebody challenges us. Perhaps the outcome forces us to question an assumption we hadn't realised we were making. We adjust our thinking and carry that adjustment into the next situation. Then the next situation teaches us that our improved answer doesn't quite work there either.
Over time, knowledge, experience, mistakes, reflection, feedback and adaptation can produce progressively better judgement. Never perfect judgement. Just better judgement.
This is also why I don't see leadership frameworks, books, coaches, mentors or research as the problem. Quite the opposite. We don't have enough time to personally make every mistake required to become better at what we do. Learning from someone else's experience is one of the most valuable shortcuts available to us.
A good framework compresses experience. It allows somebody else to benefit from lessons they haven't yet had to learn personally. It may save them from making a mistake that took somebody else years to understand.
What it cannot do is guarantee that the compressed lesson applies unchanged to the situation now sitting in front of them.
The Slight Problem With My Own Argument
There is an obvious irony in me writing this article.
I have **five Core Principles** myself.
Five.
They grew out of the same process I have just described: experiences across customers, teams, difficult situations and leadership roles gradually becoming a set of ideas that I found useful enough to write down. But I don't think of them as five steps that produce successful leadership. They are closer to lenses through which I examine a situation.
That distinction matters because principles interact. Sometimes they reinforce each other and sometimes they create tension. Trust may encourage transparency while judgement tells me that certain information must remain confidential. Proactive Value may encourage action while Deliberate Design suggests slowing down long enough to understand whether we are solving the right problem. Visibility can make a problem impossible to ignore without providing any answer for what should happen next.
The value isn't in having five principles. The value is in thinking about how they apply when reality refuses to fit neatly around them.
Principles aren't shortcuts to judgement. They are tools for exercising it.
The same thinking sits behind **Really, Another Leadership Book?** The book doesn't attempt to provide a formula for becoming a leader; its opening pages explicitly describe it as “a workshop to think with” and say that the judgement the reader develops should be their own. That wasn't accidental. The experiences in the book are mine, and so are the conclusions I reached from them. A reader can learn from those experiences without being required to reach exactly the same conclusions.
In fact, disagreement can be useful. If someone reads one of my experiences and decides they would have handled it differently, then thinks carefully about why, the story has probably done something more valuable than simply giving them another rule to remember.
That may be the most useful role any leadership advice can play. The best advice doesn't tell us what to think. It gives us better things to think about.
There Is Still Work to Do
So perhaps the next post promising five things great leaders do really does contain five excellent things. Perhaps those five points represent twenty years of experience compressed into three minutes of reading. If they do, there is something valuable in being able to learn from them so cheaply.
But I think we should remain conscious of what disappeared during the compression.
We didn't experience the mistakes that created those principles. We weren't in the conversations that changed the author's mind. We didn't see the occasions when the principle failed, or when two principles contradicted one another. Most importantly, we haven't yet developed their understanding of why the principle matters, when it applies and when circumstances might justify doing something completely different.
That understanding has to become our own.
We have become extraordinarily good at compressing knowledge, and AI is going to make us dramatically better at it. That should be celebrated. We can learn from more people, access expertise more easily and potentially avoid mistakes that others have already made.
But we shouldn't confuse faster access to knowledge with faster acquisition of judgement.
Read the books. Learn the frameworks. Listen to coaches. Find mentors. Use AI. Learn from people who have already made mistakes you haven't made yet. All of those things can shorten the learning curve.
They cannot remove the learning.
There is no leadership hack. There are simply better ways to prepare ourselves for the situations in which leadership becomes difficult.
And when that situation eventually arrives, the judgement still has to become our own.
Read Really, Another Leadership Book?
A practical examination of trust, judgement, ownership and leadership for the moments when the situation is more complicated than the advice.