🏢 9,000+ Organisations
🏆 6 x L&D/HR Awards
⭐ 4.8/5 Highly Rated
🧠 24 Years' Experience
An agile leader is someone who doesn’t freeze when things go sideways. They read the room, make a call, and bring people with them. That sounds simple. In practice, most managers find it genuinely hard.
A few things this post will cover:
Here’s the honest answer: it matters because the old model is breaking down.
For a long time, good management meant being the person with the plan. You set the strategy, built the process, and kept things on track. That worked reasonably well when the environment was relatively stable. It works a lot less well now.
AI is changing entire job functions almost overnight. Economic pressure arrives without warning. Industries that seemed settled are being disrupted from the outside. And on top of all that, teams themselves are different, more distributed, more diverse, more willing to walk if they feel undervalued or under-led.
The leaders who are navigating this well aren’t necessarily smarter or more experienced than the ones who aren’t. They just respond to change differently. They treat uncertainty as a normal part of the job rather than an interruption to it.
Agile leadership is the ability to adjust how you lead based on what’s actually happening, rather than sticking rigidly to a plan that no longer fits the situation. It’s borrowed from agile methodology in software development, but the core idea translates pretty naturally to management.
The easiest way to see it is through contrast. Say a key team member hands in their notice two weeks before a major client deadline. A rigid leader tends to escalate, delay, or absorb the work themselves while quietly panicking. An agile leader takes stock, redistributes quickly, is upfront with the client about the situation, and keeps things moving. Same crisis, very different outcomes, and the difference isn’t luck or talent, it’s how they’re wired to respond.
Worth saying: agile leadership isn’t the answer to everything. It’s sometimes oversold as a cure-all, and that does it a disservice. It doesn’t replace the need for a clear strategy, strong technical skills, or good judgment. It’s one capability among several but it’s one that tends to make the others work better under pressure.
The practical case for developing agility in your leadership tends to show up in a few consistent ways.
Global events such as economic downturns, geopolitical instability, a new technology that rewrites the rules of your industry don’t tend to give advance notice. Leaders who’ve built the muscle of responding well to change don’t necessarily see these things coming earlier. They just don’t freeze when they arrive.
There’s a tendency in long-established teams to keep doing things a particular way simply because that’s how they’ve always been done. Agile leaders are less attached to that. They’re genuinely willing to test a new approach, see how it goes, and change course if it doesn’t. This is what actually drives innovation in most organisations, not grand strategy sessions, but a quiet willingness to experiment.
High staff turnover. A team that’s stopped taking initiative. Processes that everyone quietly knows aren’t working but nobody mentions. These are the internal warning signs that build up slowly and tend to explode at the worst possible moment. Agile leaders spot them earlier, partly because they pay closer attention, and partly because their teams feel safe enough to tell them.
It’s worth starting with someone who did this at scale. Jacinda Ardern’s leadership during the Christchurch attack in 2019 is as clear an example of agile leadership under pressure as you’ll find in recent history. She didn’t have a playbook for that situation. What she had was the ability to process what was happening, decide what mattered most in that moment, communicate with genuine humanity, and act. That combination of read, decide, communicate, act, is the same loop that plays out in every well-led team, just at very different stakes.
For most of us, the situations are smaller but the underlying skills are identical. Here’s how they show up day to day.
A lot of managers hold on to decisions that could quite reasonably sit further down the team. Sometimes it’s habit. Sometimes it’s a lack of confidence in others. Sometimes it’s just that it feels quicker to do it yourself. The problem is that it creates a bottleneck, and it signals to your team that you don’t fully trust them. Agile leaders push decisions down deliberately, not recklessly, but with clear boundaries and genuine support. Over time, this builds a team that can keep moving even when you’re not in the room.
Trust is easy to talk about and genuinely hard to build. It comes, mostly, from being consistent. Doing what you said you’d do. Not changing your position based on whoever was last in your office. Being honest when things are uncertain rather than projecting a confidence you don’t quite feel. These aren’t dramatic gestures, they’re small, repeated behaviours that compound over time into something real.
When change is announced without context, people fill the gap with anxiety. Agile leaders understand this. So instead of reassuring people that everything will be fine (which rarely convinces anyone), they get specific: what’s actually changing, what’s staying the same, what happens next, and what they need from their team right now. That specificity is what settles people down and gets them moving in the right direction.
The medium matters as much as the message. A quick message on Teams when the team needs to pivot. A proper conversation, face to face if possible, when someone is struggling. A written update when the whole organisation needs to understand what’s happening and why. This isn’t complicated in principle, it just requires paying attention to what each situation actually calls for, rather than defaulting to whatever’s most convenient.
There’s a meaningful difference between a team that waits to be told what to do and one that spots a problem and starts solving it before it’s been flagged. Getting to the second state takes time and deliberate effort. You have to be clear about expectations, create genuine psychological safety, and then actually let people get on with it without pulling things back at the first sign of discomfort. Most managers find the last part the hardest.
A few years ago, we worked with a senior operations manager at a logistics firm based in the East Midlands. She was good at her job, experienced, commercially sharp, well-respected by her peers. But she’d had a difficult twelve months. Two senior team members had left within six weeks of each other, a third followed shortly after, and the team that remained had gone noticeably quiet. They stopped raising issues. They stopped making decisions unless explicitly asked. They waited.
She came into the MTD leadership programme expecting to work on external challenges such as market pressures, team capability gaps, that kind of thing. What became clear fairly quickly was that the issue was closer to home. She had, without really intending to, built a team that was entirely dependent on her. Every significant decision came through her desk. Meetings existed largely for her to communicate what had already been decided. The people around her were capable, but they’d learned not to bother.
She found this uncomfortable to hear, which is understandable. But she took it seriously. Over the following months, she restructured how her team operated, shifting meetings from update sessions to actual working forums where problems got solved collectively. She started handing over decisions she’d always assumed had to sit with her, and resisting the urge to overrule when the team’s instinct differed from her own. It was, in her words, harder than any technical challenge she’d faced.
The turning point came about four months in, when a major supplier failed to deliver during one of their busiest periods. Previously, that kind of disruption would have gone straight to her. This time, her team handled it, sourced an alternative, renegotiated the timeline with the client, and told her about it after the fact. She said it was one of the best things that had happened in her career. Not because the problem was solved, but because she finally had a team that didn’t need her to solve it.
One of the things that often gets missed in conversations about agile leadership is that the goal isn’t just to make leaders more agile. It’s to build teams that have agility baked in at every level.
A team where only the leader can navigate uncertainty is fragile. Things slow down the moment that person isn’t available. Decisions queue up. Momentum stalls. The leader becomes, unintentionally, the bottleneck.
Building agility across a team takes longer and requires different things, psychological safety, genuine clarity on roles and decision rights, and a track record of leadership that follows through on what it says. It doesn’t happen quickly, but when it does, the difference is tangible. Teams become self-correcting. Problems get surfaced rather than buried. People stop waiting for permission to do the obvious thing.
These are well-documented examples, but they’re worth looking at because each one shows a different aspect of what agile leadership makes possible.
By the early 2000s, LEGO was in serious trouble. The company had expanded aggressively into areas it didn’t fully understand (theme parks, clothing, electronics) and lost sight of what it was actually good at. It came close to bankruptcy.
What followed was a significant reset. Leadership went back to basics, cut what wasn’t working, and, crucially, started genuinely listening to what customers wanted rather than what internal teams assumed they wanted. The pivot to licensed franchise products like Star Wars and Harry Potter wasn’t a marketing decision. It was a direct response to where the market was actually going. LEGO became one of the most profitable toy companies in the world partly because its leadership was willing to change course before the alternative disappeared.
Adobe’s decision to replace its annual performance review with a continuous Check-in model was controversial internally when it happened. Annual reviews are familiar. Managers know how to do them. Changing to something more fluid requires a different kind of management capability. more conversational, more responsive, more comfortable with ongoing feedback rather than a once-a-year verdict.
The results were significant. Voluntary turnover dropped noticeably, and managers reported spending more meaningful time with their teams rather than managing paperwork. But the more interesting outcome was what it revealed about leadership style. The Check-in model only works if managers are actually engaged with how their people are developing week to week. It forced a more agile approach to people leadership whether managers wanted it or not.
Spotify’s squad model is probably the most cited example of agile organisational design in recent years, which means it’s also one of the most misunderstood. The structure of a small, autonomous teams, each responsible for a specific part of the product, didn’t work because it was clever. It worked because leadership genuinely gave those teams the authority to make decisions and act on them.
That kind of delegation is harder than it sounds. Most organisations that have tried to copy Spotify’s structure have kept the terminology and quietly held on to the decision-making. The model fails because the leadership culture hasn’t actually changed. The lesson from Spotify isn’t really about structure but about whether leadership is genuinely committed to letting go.
Agile leadership gets talked about so much that it’s easy to lose sight of what it actually means in practice. Strip it back and it comes down to this: can you read a changing situation clearly, make a decision without perfect information, bring your team with you, and adjust as you go? If yes, or if you’re developing towards yes, you’re in reasonable shape.
A few things worth remembering from this post:
If you’re looking to develop your own agile leadership capability, or bring this thinking into your wider team, MTD’s leadership and management training programmes are built around exactly this kind of practical, applied development. Have a look at what’s available and find the right fit. Explore MTD Leadership Training Courses
Written by Sean McPheat
CEO of MTD Training and Amazon bestselling author. Sean writes about leadership, business, and personal growth, drawing on 20+ years of experience helping over 9,000 companies improve performance.
| 
| 
Updated on: 28 April, 2026
Originally posted: 19 February 2020
Related Articles
Search For More 