The ability to rapidly learn from experience, adapt to new situations, and apply insights to solve unfamiliar or complex problems. It involves curiosity, reflection, experimentation, and the capacity to remain flexible, question assumptions, and continuously evolve in the face of change.
“Learning is a treasure that will follow its owner everywhere.” Chinese proverb
Why learning agility matters
Learning agility matters because most of the genuinely hard problems a leader faces won’t come with a precedent attached, the situation won’t match anything in their existing playbook closely enough for experience alone to supply the answer. A leader’s raw stock of knowledge matters far less in these moments than how quickly they can update that knowledge once reality contradicts it, and that speed advantage compounds over a career much the way a small difference in interest rate compounds over decades, producing leaders who look, ten years on, dramatically more capable than peers who started from roughly the same point.
Without this capability, a leader’s early career successes can quietly become a ceiling rather than a foundation, since the very expertise that got them promoted was built for conditions that have since moved on. The gap rarely announces itself as a crisis, it shows up instead as a leader who keeps reaching for what worked before, one cycle too late to notice that this particular problem needed something they hadn’t yet learned.
“In times of change, learners inherit the earth, while the learned find themselves beautifully equipped to deal with a world that no longer exists.” Eric Hoffer
What good and bad learning agility looks like
| What bad looks like | What good looks like |
|---|---|
| Assumes that relearning a skill in a new context will take about as long as the original learning did. | Recognises that relearning is almost always faster than the original learning, and budgets time accordingly rather than assuming it will take just as long again. |
| Treats “we’ve never done it that way” as a real objection to a new approach. | Treats “we’ve never done it that way” as a description, not an argument, and asks separately whether the new way is actually better. |
| Only invests in learning something new once the team is already visibly behind on it. | Invests in learning something new while it’s still optional, so the team isn’t starting from zero the moment it becomes mandatory. |
| Keeps the lesson from a hard-won mistake as personal experience, without passing it on. | Actively translates a hard-won lesson into something the rest of the team can use, so the same mistake doesn’t have to be repeated by someone else to be learned from. |
| Judges a new hire or team member’s potential mainly by how much they already know coming in. | Judges potential mainly by how fast someone updates once they’re shown they were wrong about something, since that predicts more than existing knowledge does. |
| Treats “I was wrong” as an admission to be minimised or buried inside a longer explanation. | States “I was wrong” plainly and moves straight to what’s been learned, since how a leader handles being wrong is itself something the team is watching and learning from. |
| Responds to a team member’s honest mistake in a way that discourages anyone else from taking a visible risk again, without ever saying so directly. | Responds to an honest mistake in a way that visibly rewards the risk-taking itself, regardless of the outcome, so people don’t quietly stop taking risks too. |
| Treats a stretch assignment as a reward reserved for people who’ve already proven themselves in that exact area. | Uses stretch assignments specifically to put people in unfamiliar territory, treating the resulting discomfort as the point, not a design flaw. |
“We do not learn from experience… we learn from reflecting on experience.” John Dewey
Barriers to learning agility
Low reflection: Experience only becomes insight after it’s been examined, and without that step, a leader can accumulate years of activity without accumulating much actual learning. The lesson sits there available in the experience itself, but it never gets extracted, because extracting it takes a deliberate pause that busy leaders rarely build in.
Singular problem resolving process: A method that has reliably worked before earns a leader’s trust, reasonably enough, but that trust can harden, without much notice, into the only lens they bring to a new problem. When a genuinely unprecedented challenge doesn’t fit that lens, the instinct is often to force it to fit rather than to reach for a different method.
Risk aversion: Avoiding risk feels like the safer choice in the moment, but it also means avoiding most of the situations where real learning actually happens, since unfamiliar territory is exactly where existing knowledge runs out. Over time, this trades a small, visible cost now for a much larger, harder-to-see cost later: falling behind leaders who took the discomfort on directly.
Lack of self-confidence: When a leader doubts their own capacity to pick up something genuinely new, that doubt shows up less as a stated fear and more as a preference for tasks they already know they can do well, one that never gets named as fear at all. The avoidance protects their sense of competence in the short term, at the direct cost of ever building the competence they’re avoiding.
Perfectionism: A leader who needs to get things right the first time will naturally steer away from ambiguous, evolving tasks, since those are precisely the tasks where an early, rough attempt is part of the process. The standard that serves them well in familiar, well-defined work becomes an active obstacle in exactly the territory where learning agility is most needed.
Stuck in the past: A method that once defined good practice can keep its authority long after the conditions that made it effective have changed, simply because it’s familiar and has a track record. Letting go of it can feel like abandoning a standard, when it’s really just recognising that the standard has moved on without the leader noticing.
Narrow casting: Searching for a parallel to a new problem naturally starts with what’s familiar, but for some leaders it also ends there, never extending to less obvious or less comfortable comparisons. The most useful parallel is often the one that isn’t immediately obvious, which is exactly the one this habit is least likely to surface.
Overconfidence in current expertise: Deep expertise built in one context can create an unexamined assumption that the same expertise will transfer smoothly to a new one, without the leader actually testing whether it does. The more successful that expertise has been, the harder it often is to notice the moment it stops applying cleanly.
Uncomfortable with ambiguity: Ambiguous problems don’t offer the reassurance of a clear right answer along the way, and for leaders who find that discomfort hard to sit with, the natural response is to look for a problem that offers more certainty instead. The complex, unresolved problems avoided this way are usually exactly the ones with the most learning available in them.
Settling too quickly: Accepting the first outcome that clears the bar of “good enough” ends the search before the deeper, more interesting layer of the problem has been reached. The extra effort needed to push past an adequate answer is often exactly where the most transferable learning was waiting.
“Life is trying things to see if they work.” Ray Bradbury
Enablers of learning agility
Uncover root causes: Instead of collecting surface-level information, consistently ask “why” to uncover underlying causes. Aim to understand identifying patterns and categorise unearthed data into meaningful sets.
Search for structures and principles: Rather than focusing on immediate solutions, aim to look for the fundamental principles behind a challenge. Deeper understanding enables you to take a more systemic view and reapply learning across topics.
Review your experiences: Examine both successes and failures to identify recurring themes. While failures offer lessons, analysing your successes can provide insight into what works. You should be able to distil these findings into actionable principles that can be applied to future challenges.
Iterate at pace: Learning agility improves with frequent experimentation or probes. Be prepared to try multiple solutions and iterate based on the results. Shortening your feedback cycle maximises learning opportunities and enhances adaptability.
Engage with expertise: Collaborating with experts in any given field can provide valuable insights into new problem-solving approaches. Leaders can benefit from understanding how experts analyse problems, think through solutions, and identify key drivers, enabling faster learning as well as problem solving.
Reverse your thinking: Consider approaching problems from the opposite direction. Ask what the problem is not, explore least-likely causes, or consider alternative perspectives.
Create and engage with diversity: Teams with varied backgrounds can offer fresh perspectives and innovative solutions. By collaborating with others who think differently, you can challenge your assumptions, uncover new ideas, and improve your capacity to adapt.
Be unconventional: Draw inspiration from unlikely sources or nature to help you find creative solutions to complex problems. Identify odd parallels and unexpected anomalies to reveal new insights that can support you breaking out of your traditional thinking patterns.
Embrace failure: Treat a failed attempt as information about the problem, not as a verdict on your own competence. The leaders who learn fastest are usually not the ones who fail less, but the ones who spend less time recovering emotionally from each failure before extracting what it taught them.
Ask questions first: Leaders often rush to offer solutions without fully defining the problem. Devoting time to asking insightful questions can help you clarify the challenge, leading to better-informed decisions. Spend close to 50% of your time on defining the problem in order to set the stage for more effective solutions.
“Anyone who isn’t embarrassed of who they were last year probably isn’t learning enough.” Alain de Botton
Reflection questions on learning agility
How do you describe your approach to problem-solving? How could you dig deeper to uncover root causes? What patterns or connections can you see in the data that you have previously missed? How could you reframe issues to help you develop more innovative solutions?
Are you identifying the core elements of a challenge, or rushing too quickly to solutions? Are you too focused on the end result without considering the deeper factors driving it? What would change about your approach if you spent twice as long defining the problem before trying to solve it?
How often do you reflect on what has worked well in the past? What commonalities exist in the problems you have solved successfully? How can you apply these patterns to current and upcoming challenges?
Are you experimenting enough with different approaches? How comfortable are you trying multiple solutions before settling on one? Are your feedback loops frequent enough to accelerate your learning? What may be preventing you from experimenting more with unfamiliar or riskier solutions?
Do you regularly seek out experts to help you learn more effectively? How often do you consult others who may have a deeper understanding of the problem? How could you raise the amount you engage with people outside your usual network?
How often do you deliberately challenge yourself to think from a different perspective, rather than defaulting to your first instinct? How could you build this into a habitual practice rather than an occasional effort? Whose perspective do you least often seek out, and why?
Are you leveraging the diversity of your team and network to generate better solutions? How often do you actually engage with the perspectives available to you, compared to how often you should? Who on your team offers a viewpoint you rarely ask for, and what would it take to change that?
How comfortable are you dealing with uncertainty and ambiguity? How could you get more comfortable not knowing and forging ahead regardless? What’s your usual tell that you’re reaching for false certainty just to escape the discomfort?
How do you currently learn from mistakes and failed probes or experiments? How could you build this into a regular routine rather than something that only happens after a big failure? When did you last analyse a success as closely as you’d analyse a failure?
Do you spend time asking questions before jumping to solutions? What would happen if you allocated more time to problem definition before looking for solutions? How could you make this a habit?
“It is impossible to begin to learn that which one thinks one already knows.” Epictetus
Micro practices for learning agility
1. Write down what you expect before you try it: Before running an experiment or attempting a new approach, write one sentence predicting the outcome. Comparing the actual result to your prediction afterward is one of the fastest ways to spot exactly where your thinking was off.
2. Set a “kill deadline” for the first idea: When you land on a first solution, give yourself a fixed, short window to actively try to disprove it before committing further. Treating your best current idea as something to attack, not defend, catches weak ideas while they’re still cheap to abandon.
3. Ask the newest person in the room first: In your next problem-solving discussion, ask for input from whoever has the least history with how things are usually done before anyone more senior speaks. Their answer often reveals an assumption the rest of the room has stopped noticing.
4. Revisit a closed decision on purpose: Once a month, deliberately reopen one decision you already consider settled and ask whether the conditions that justified it are still true. Most decisions are never revisited simply because reopening them was never scheduled.
5. Name what you’d have to see to change your mind: Before defending a current approach, say out loud what specific evidence would actually convince you to abandon it. If nothing comes to mind, that’s a sign you’re holding a conclusion rather than a hypothesis.
6. Debrief the win, not just the loss: After a clear success, spend ten minutes asking what you got right and whether you could reliably repeat it, with the same rigour you’d apply to a failure. Wins analysed this closely reveal patterns just as often as failures do.
7. Retire one outdated habit on purpose: Identify one tool, process, or rule of thumb you still default to mostly out of habit rather than current usefulness, and deliberately stop using it for a month. Removing something old often creates more room to learn than adding something new, and it’s the only one of these practices that’s actually about subtraction rather than addition.
“Anyone who stops learning is old, whether at twenty or eighty.” Henry Ford
Explore related leadership resources
To further develop this capability, examine how it intersects with other core leadership dimensions across the libraries:
Leadership library:
- Experimenting: Embrace a “trial and learn” approach, using small-scale tests to gather real-world data and refine your strategy in real-time.
- Initiative (Taking): Move from reflection to action by proactively identifying and seizing opportunities for growth and improvement.
- Insight Seeking: Actively broaden your perspectives to uncover the deeper patterns and “lessons learned” that others might miss.
- Navigating Uncertainty: Maintain high performance and focus even when the path forward is unclear, using agility to adjust as new information emerges.
Supporting libraries
- Learning Agility Library: Explore a dedicated research-based directory of 20 capabilities designed to help you learn more effectively from every experience.
- Risk orientation (Traits): Leverage your natural comfort with calculated risks to step outside your comfort zone and accelerate your development.
- Ambiguity tolerance (Traits): Stay cognitively flexible in complex situations, preventing the need for “perfect information” from stalling your progress.
- Problem solving (EQ-i): Combine analytical logic with emotional awareness to find sustainable solutions to unfamiliar or recurring challenges.
Continue exploring: Return to the Leadership Library to view the full directory of competencies and resources.