Messy and chaotic desk illustrating the bottleneck created by inexperienced leadership

TL;DR

Inexperienced Leaders are Crippling Businesses.

The Problem in One Sentence: We're putting people in some form of leadership role based on CVs and credentials, not actual leadership capability, and it's costing organisations millions.

What Goes Wrong

  • Drowning in Their Own Tasks: Too busy firefighting to actually lead
  • No Real Questions Asked: They tell instead of listen; they don't coach
  • Communication Theatre: Meetings happen, but understanding doesn't
  • Accidental Bottlenecks: Everything flows through them; nothing progresses
  • Building Silos: Safe to stay in their domain than collaborate across teams
  • Missing the Big Picture: Focused on individual bricks, not the house
  • Fake Servant Leadership: Conflict-avoidance dressed up as inclusion
  • Paralysis by Committee: Everyone involved in everything = nothing gets done
  • The Real Cost: Revenue. Talent exodus. Brittle culture. Missed opportunities.
  • The Uncomfortable Truth: These managers often work incredibly hard. They just don't understand that leadership isn't about being the busiest person in the room; it's about ensuring the room is set up for success.

There's a problem festering in workplaces across the UK (and many other countires), one that's costing businesses far more than they realise. We've become rather good at putting people into leadership roles, whether through promotion based on technical expertise or by hiring impressive CVs that mask a lack of real-world delivery experience. The result? A generation of managers who are drowning in their own to-do lists, creating bottlenecks they don't even recognise, and building silos that would make Whitehall proud.

The CV That Promised Everything

It's not just about internal promotions anymore. Organisations are increasingly hiring Product Owners, Product Managers, Team Leads, and Heads of departments based on CVs that shout expertise whilst concealing a fundamental lack of practical leadership experience. Someone might have "10 years in marketing" on their LinkedIn profile, but that doesn't mean they know how to lead a marketing team, set strategic direction, or even establish the basics like brand guidelines.

These appointments often happen because we've confused knowledge with capability. We see someone who can talk eloquently about agile methodologies, servant leadership, or strategic frameworks, and we assume they can implement them. We're seduced by credentials, certifications, and polish, whilst overlooking whether they've actually led teams through complexity, delivered under pressure, or built anything sustainable.

Young professionals are entering senior roles, Product Owners at 26, Heads of Marketing at 28, Product Managers at 25, not because they've demonstrated mastery, but because they interviewed well and their CV ticked the right boxes. They're articulate, enthusiastic, and credible on paper. Then they arrive, and the cracks appear almost immediately.

And let's be honest: some of these folks aren't just young. They're simply in over their heads, regardless of age. You can be 45 with an impressive title and still have no idea how to actually lead people. Age doesn't cure incompetence; it just makes it more expensive.

The Endless To-Do List Syndrome

Picture this: a Head of Marketing who hasn't established brand guidelines. A Product Manager who's perpetually "too busy" to brief the team properly. A Team Lead whose backlog is a disaster because they've never learned to prioritise ruthlessly. A "Senior" anything who spends more time in meetings about meetings than actually doing anything useful.

This isn't just poor time management. It's a fundamental misunderstanding of what leadership actually entails. When someone in a pivotal role is constantly firefighting their own task list, they're not leading. They're occupying a position that desperately needs proper leadership whilst simultaneously blocking anyone else from providing it.

The truly insidious part? These individuals often work incredibly hard. They arrive early, leave late, and genuinely believe they're doing their job. But leadership isn't about being the busiest person in the room. It's about ensuring the room itself is set up for success. If your calendar looks like a game of Tetris played by someone having a breakdown, you're not leading. You're drowning with an audience.

Stop. Listen. Ask the Hard Questions.

Here's what separates inexperienced leaders from effective ones: the ability to stop, listen to their teams, and ask uncomfortable questions of themselves.

Mike Rother's research on Toyota's approach to continuous improvement, documented in his book Toyota Kata, reveals something critical about effective leadership. Toyota doesn't succeed because their managers have all the answers. They succeed because their managers have mastered the art of asking the right questions. The Coaching Kata that Rother identified consists of five essential questions leaders ask their teams:

  1. What is the target condition?
  2. What is the current condition?
  3. What obstacles are preventing you from reaching the target condition?
  4. What is your next step?
  5. When can we see what we have learned from taking that step?

These aren't rhetorical questions designed to make you look thoughtful in a stand-up. They're disciplined, recurring inquiries that force both leader and team to think scientifically, experiment rapidly, and learn continuously. As Rother discovered, the manager's role becomes that of a coach, guiding through questioning rather than providing all the answers.

But inexperienced leaders skip this entirely. They don't ask questions because they're terrified of appearing ignorant. They don't listen because they're too busy telling. They don't reflect on obstacles because acknowledging them feels like admitting failure. Or worse, they ask questions they've already decided the answers to, then get irritated when reality doesn't comply with their preconceptions.

When was the last time your Product Owner genuinely asked the development team what obstacles were blocking them? When did your Head of Marketing sit down with the team and ask, "What's not working in how we operate?" Not in a performative stand-up where everyone says "fine," but in a real conversation where uncomfortable truths can surface?

Inexperienced leaders don't do this because they haven't learned that questions are more powerful than answers. They're still operating from the old playbook where leaders are supposed to know everything and demonstrate certainty at all times. Spoiler: that playbook was rubbish when it was written, and it's aged about as well as milk left in the sun.

Communication: The Myth of the Feedback Loop

We talk endlessly about "open communication" and "feedback loops" in business. We have stand-ups and retrospectives and quarterly reviews. Yet somehow, information still moves like treacle through most organisations.

Why? Because inexperienced leaders confuse activity with communication. They send emails, sure. They attend meetings, absolutely. But are they creating genuine, bidirectional understanding? Are they ensuring their team knows not just what to do, but why it matters and how it fits into the bigger picture?

The Agile Manifesto emphasises that those delivering the work and those making business decisions must collaborate continuously throughout a project. Not quarterly. Not when there's a crisis. Continuously. This requires leaders who understand that communication isn't a checkbox. It's the operating system.

Too often, the answer is no. Communication becomes a tick-box exercise rather than a living, breathing exchange. Junior managers nod along in senior meetings, then return to their teams with vague directives and crossed fingers. The feedback loop isn't a loop at all. It's more of a cul-de-sac where information goes to die, surrounded by motivational posters about "synergy."

The Accidental Bottleneck (Or: How to Ruin Everything Without Trying)

Here's an uncomfortable truth: the biggest bottlenecks in your organisation are probably people, not processes. And they might have no idea they're the problem.

When someone lacks the experience to delegate effectively, to prioritise strategically, or to simply let go, they become a chokepoint. Every decision must flow through them. Every approval sits in their inbox. Every initiative waits for their sign-off, which never quite comes because they're "just finishing something else."

This isn't always malicious. Some inexperienced managers genuinely want to do well. They're terrified of dropping balls, of making mistakes, of losing control. So they hold on tighter, review everything twice, and insist on being cc'd on every email. The result? A team that moves at the speed of one person's capacity rather than its collective potential.

But let's not be too generous here. Some managers simply enjoy being the bottleneck. It makes them feel important. Necessary. Irreplaceable. If everything has to go through them, surely that proves their value? No, mate. It proves you're insecure and your team has learned helplessness.

And then there's the flip side: the inexperienced leader who doesn't seek consensus at all. They've decided what's good, what's acceptable, what fits their vision, and everything else gets shot down faster than you can say "but the data suggests..." They're not bottlenecks through indecision. They're bottlenecks through obstinate certainty. Same outcome, different flavour of dysfunction.

Robert K. Greenleaf, who coined the term "servant leadership" in 1970, described a servant leader as someone whose primary objective is to enhance teamwork and personal involvement. Servant leaders empower employees by sharing power and decision-making. The critical test, according to Greenleaf, is this: "Do those served grow as persons: do they, while being served, become healthier, wiser, freer, more autonomous?"

An inexperienced leader, whether paralysed by indecision or drunk on their own certainty, fails this test spectacularly. Their team doesn't grow. It atrophies, waiting for permission, waiting for direction, or simply waiting for this person to leave so actual work can resume.

Silos: Not Just an Organisational Chart Problem

Businesses love a good silo. Marketing doesn't talk to Sales. IT operates in its own universe. Finance says no to everything without understanding why it's being asked. Customer Service knows what customers actually want, but nobody asks them because they're "just" Customer Service.

But silos aren't created by organisational structures. They're created by leaders who don't know how to collaborate across boundaries. An experienced leader understands that their success is inextricably linked to adjacent teams' success. They build bridges, facilitate introductions, and actively break down barriers.

Inexperienced managers, by contrast, often retreat into their own domains. It's safer. It's more controllable. It requires less political navigation and fewer uncomfortable conversations. But it's also how you end up with three departments independently working on solutions to the same problem, none of them fit for purpose, all of them convinced the other departments are idiots.

Leading from the Front: Vision, Not Just Velocity

There's a nostalgic notion in business culture about "leading from the front." We invoke great leaders, we talk about captains and ships, we nod sagely about visible leadership. Then we promote or hire someone who spends 90% of their time responding to emails and the other 10% in back-to-back Zoom calls with their camera off because they haven't showered.

Leading from the front doesn't mean doing everyone else's job. It means:

Setting clear, compelling direction. Not just goals, but vision. What does success actually look like? Research consistently shows that teams sharing a vision conveyed by leadership are significantly more motivated and deliver better output than those simply following orders. If you can't paint that picture clearly enough that your most junior team member could explain it to their mum, you haven't done your job.

Making decisions. Proper ones. With conviction. Inexperienced leaders either agonise over every choice, seeking consensus until the moment has passed, or they make snap decisions based on gut feel and then defend them to the death regardless of new information. Neither approach is leadership. The former is cowardice dressed as collaboration. The latter is arrogance dressed as decisiveness.

One of the Agile principles reminds us to embrace changing requirements because adapting to change creates competitive advantage. You can't harness change if you're either paralysed by it or pretending it doesn't exist.

Removing obstacles. This is where the Toyota Kata approach becomes transformative. Your job isn't to add layers of approval or create new bureaucratic hurdles so you feel involved. It's to clear the path so your team can run. As Rother's research showed, effective leaders spend their time identifying and eliminating obstacles, not creating them. That might mean challenging upwards, pushing back on bureaucracy, or simply saying "I'll handle that, you focus on this."

Being present. Not physically hovering, nobody wants that and it's creepy, but genuinely available. Your team should know they can reach you when it matters, and that you understand what they're working on without them having to brief you from scratch every time. If your team has to schedule a meeting to ask you a question, you're not present. You're a bureaucratic obstacle with a job title.

The House, Not the Bricks

Here's where inexperienced leadership reveals itself most starkly: the inability to maintain perspective on the whole whilst managing the parts.

Imagine you're building a house. A poor leader focuses on each brick, are they level, is the mortar right, should we use a different technique, has anyone considered the thermal properties, did we get three quotes for these bricks? Meanwhile, no one's checked if we're still building the right house, in the right place, for the right client. Or if the client's moved to Spain and doesn't need a house in Manchester anymore.

Experienced leaders hold the vision of the completed house in their minds constantly. They communicate it relentlessly. They ensure every team member understands not just their individual bricks, but how those bricks form walls, how the walls create rooms, how the rooms become a home.

The Agile Manifesto teaches us that the most effective way to convey information within a team is through direct, rich conversation. Not because face-to-face is magic, but because it allows for the kind of contextual understanding that keeps everyone focused on the house, not just their brick.

More importantly, experienced leaders build in flexibility to adapt. Because in today's business environment, the plans will change. The client will request modifications mid-build. The market will shift. Agile thinking explicitly addresses this: welcoming changing requirements isn't a nice-to-have, it's a survival skill.

An inexperienced leader sees these changes as failures of planning and gets defensive. An experienced one sees them as inevitable and prepares their team accordingly. They've built the muscle memory, through practices like the Toyota Kata, to adapt quickly without panic, recrimination, or a three-month consultation process.

The Servant Leadership Myth

Let's address the elephant in the room: somewhere along the line, British management culture embraced "servant leadership" as if it meant keeping everyone happy and avoiding difficult conversations.

True servant leadership, as defined in Agile contexts, isn't about being a doormat or everyone's mate. According to research from the Agile Business Consortium, servant leaders focus on collaboration, trust, empathy, and the ethical use of power. They recognise that empowerment exists on a continuum. It's not all or nothing. They adapt their approach based on the team's capability and the situation at hand.

This means servant leadership includes:

  • Having difficult conversations about underperformance
  • Making unpopular decisions when necessary
  • Challenging your team to stretch beyond their comfort zones
  • Saying no to protect focus and resources

An inexperienced manager mistakes servant leadership for conflict avoidance. They let mediocrity slide because they want to be liked. They fail to address toxic behaviour because confrontation is uncomfortable. They pile more work on high performers because it's easier than developing weaker ones. Then they wonder why their best people leave and their worst people thrive.

Real servant leadership is demanding because you care about people's growth, not because you're a tyrant. Letting someone coast in mediocrity isn't serving them. It's abandoning them. And frankly, it's lazy.

The Inclusion Illusion

"I want everyone to feel included," says the inexperienced manager, before inviting twelve people to a meeting that should involve four, creating a committee where a decision-maker is needed, and ensuring that nothing can progress without everyone's input.

Inclusion doesn't mean everyone is involved in everything. That's not inclusion. That's paralysis dressed up as democracy, and it's exhausting for everyone involved.

Real inclusion means:

  • People understand the decisions that affect them
  • Everyone's expertise is valued when it's relevant
  • The team trusts that decisions are made fairly, even when they're not personally involved
  • Credit is shared, not hoarded by the person who talked loudest in the meeting
  • Voices from all levels are genuinely heard

Agile thinking emphasises that the best solutions emerge from self-organising teams. Self-organising doesn't mean leaderless chaos where everyone has a vote on everything. It means teams empowered to make decisions within a clear framework, with leaders who remove obstacles rather than micromanage.

Inexperienced leaders confuse process with inclusion. They create elaborate frameworks for input, then ignore them. Or they seek consensus on everything, valuing agreement over outcomes, and spending six weeks deciding what colour to paint the bike shed whilst the actual product rots.

Forge New Paths: The Courage to Change How We Work

The hardest thing for inexperienced leaders to do is admit that their current way of working isn't fit for purpose. It requires humility, self-awareness, and courage, qualities that don't always correlate with impressive CVs or smooth interview performances.

Toyota Kata's fundamental insight is that organisations don't achieve excellence through one-time improvements, but through developing a systematic capability for continuous improvement.

This requires leaders willing to question their assumptions, experiment rapidly, reflect honestly, and develop others through coaching rather than command.

The British Reticence Tax (And Other Cultural Peculiarities)

There's a particularly British dimension to all of this: our cultural aversion to directness, our preference for politeness over clarity, our tendency to hint rather than state.

In the hands of an inexperienced manager, these cultural traits become magnified into genuine dysfunction. Issues aren't addressed. They're mentioned in passing. Poor performance isn't tackled. It's touched on during the quarterly review.

Experienced leaders learn to cut through this fog. They're direct without being rude, clear without being brutal. They understand that kindness isn't about avoiding difficult truths. It's about delivering them with respect and support.

What This Costs

Revenue. Talent. Culture. Agility. All suffer when leadership is inexperienced, defensive, or absent. Opportunities are missed. Good people leave. Teams lose confidence. Organisations become brittle.

The Way Forward

Inexperience isn't a permanent condition. But improvement requires honest training, mentorship, feedback, accountability, better hiring decisions, and sometimes reassignment.

A Challenge for Anyone with Influence, Seniority, or a Nice Title

If you're in a position of influence, stop and ask yourself whether you're enabling progress or quietly blocking it. Bottlenecks rarely announce themselves. They usually think they're indispensable.

A Final Thought

Every day we tolerate inexperienced people in pivotal roles, whether promoted internally or hired on the strength of an impressive CV, we weaken the foundations of our organisations.

The house might look fine from the outside. But the structure won't hold when the weather changes.


Further Reading

  • Toyota Kata by Mike Rother (2009)
  • The Agile Manifesto (2001)
  • The Servant as Leader by Robert K. Greenleaf (1970)
  • Scrum.org Resources on Servant Leadership
  • The Nine Principles of Agile Leadership by the Agile Business Consortium