How can I learn faster from experience as a leader? (Learning agility tactics)

Two leaders can have ten years of experience and have learned very different amounts from it. One has spent ten years encountering new situations, noticing what worked and what didn’t, asking other people what they saw, trying different approaches and gradually changing how they lead. The other has accumulated roughly the same year ten times. They have plenty of experience, but much of it has simply reinforced what they already thought they knew.

The difference isn’t necessarily intelligence, ambition or access to better training. It is what happens to experience after it happens. A difficult meeting, a project that misses its target, a new role, a client who reacts unexpectedly, a decision that works far better than predicted: all of these contain information. But the information doesn’t arrive neatly labelled with the correct lesson attached. You have to construct the lesson yourself. And that’s where things get interesting, because you can construct the wrong one.

A senior stakeholder dismisses your proposal and you conclude that challenging senior people doesn’t work. Perhaps. Or perhaps you chose the wrong moment, misunderstood what they were trying to protect, buried your strongest argument, or simply encountered one person who wasn’t going to be persuaded that day. Experience gave you data. You supplied the explanation.

Learning faster isn’t therefore about cramming more experiences into your working life or reflecting endlessly on everything that happens. It is about becoming better at noticing which experiences contain useful information, extracting a provisional lesson from them, testing that lesson rather than simply believing it, seeing whether it travels to another context, and changing it when reality gives you better evidence.

What this actually buys you as a leader of yourself

Early in a career, a great deal of what you need to learn can be taught directly. There are procedures to follow, techniques to practise, people who know the answer and situations that recur often enough for you to improve through repetition. Leadership gradually removes many of those advantages.

The situations become less repeatable. The problems become more ambiguous. The feedback becomes less immediate and often less honest. The people involved have different interests. The answer that worked last time may be precisely the answer that fails this time because the context has changed.

That makes the ability to learn from experience increasingly important. You cannot prepare in advance for every difficult stakeholder, organisational shift, new team, failed initiative or unfamiliar problem you will encounter. What you can become better at is working out what each one is teaching you quickly enough to behave differently when something similar appears again. But even that isn’t quite enough. The most useful lessons aren’t trapped inside the situations that produced them. You learn something about resistance during a client conversation and recognise the same dynamic six months later during organisational change. You discover that silence after a difficult question produces better information in coaching, then realise the same principle improves a negotiation. You learn when autonomy works with one team and gradually understand the conditions under which it works with others.

That’s the difference between accumulating experience and becoming more agile in what you learn from it.

Why it matters

Experience isn’t the same thing as learning

The idea that experience can be deliberately converted into learning has deep roots. Dewey argued that experience and education aren’t interchangeable: experiences can promote future learning, but they can also constrain it. Later experiential-learning models, most famously Kolb’s, described learning as a cycle in which concrete experience is reflected on, interpreted and eventually tested through further action. The practical implication is easy to miss because it sounds almost too obvious: having an experience is only the beginning.

A project can fail without anyone learning why. A difficult conversation can reinforce a completely mistaken explanation of the other person’s behaviour. A successful decision can be even more dangerous if we attribute the outcome entirely to our own judgement when luck, timing or circumstances did most of the work. The raw material is experience. Learning requires some change in what you understand, notice or do as a result.

Learning agility adds something important

Learning agility grew largely from the world of leadership development and talent management, where researchers and practitioners became interested in why some people seemed particularly able to learn from experience and perform effectively when they encountered something new. The basic proposition is attractive for an obvious reason. Past performance tells you how somebody handled situations they have already encountered. Leadership potential often depends on how they respond when the situation is unfamiliar and their existing answers no longer fit.

But learning agility is worth handling more carefully than some of the practitioner enthusiasm around it suggests. DeRue, Ashford and Myers noted that the concept became widely used before the academic foundations were equally mature, with inconsistent definitions, measures and boundaries between learning agility and related constructs. That doesn’t make the idea useless. It changes what we should take from it.

We don’t need to establish learning agility as one perfectly distinct psychological trait before using the behaviours that make learning from experience more effective. Noticing new information, reflecting on what happened, seeking different perspectives, experimenting with alternative responses and abandoning explanations that no longer fit are all behaviours a leader can practise.

My own learning-agility framework groups those behaviours into five domains: Sensing, noticing signals and changes; Socialising, learning through other people; Shedding, letting go of assumptions and methods that no longer fit; Sprinting, learning through rapid experiments; and Stepping back, creating enough distance from the action to examine what actually happened. Those five behaviours provide a useful way of thinking about why two people can pass through similar experiences and extract very different amounts of learning from them.

The richest learning often starts with surprise

One of the most useful signals that an experience contains something worth examining is simple: something happened that you didn’t expect. You thought the team would resist and they embraced the idea. You expected a client to care about price and discovered their real concern was implementation risk. You assumed giving someone greater autonomy would energise them and instead they became anxious and repeatedly asked for direction. The mismatch matters because expectations contain an implicit model of how you think the world works. When reality behaves differently, you have received evidence that some part of that model may be incomplete.

Yet surprise is easy to waste. We explain unexpected outcomes away, squeeze them into what we already believe, or move immediately to the next problem. A learning-agile response starts differently: What did I expect to happen, what happened instead, and what might that difference be telling me? That is Sensing in practical form: noticing the signal before explaining it away.

Experience can teach you the wrong lesson

Noticing the signal still doesn’t tell you what it means. Imagine you challenge a senior executive publicly and receive an unexpectedly hostile response. One possible lesson is: “Don’t challenge senior leaders.” Another is: “Don’t challenge senior leaders publicly.” Another is: “Understand what someone is trying to protect before challenging their position.” Another is simply: “That particular executive reacts badly when challenged.” All four lessons are compatible with the same experience.

This is why reflection is useful but insufficient. Reflection can deepen understanding, but it can also make us more articulate about an explanation that happens to be wrong. The discipline is to treat the first lesson you extract as a hypothesis rather than a conclusion. Ask what actually happened, what you’re assuming caused it, what else could explain it and what evidence would help distinguish between those explanations. This is the stepping-back part of learning agility: deconstructing the experience rather than letting your first interpretation harden into the lesson.

You can’t repeat the experience, but you can repeat the skill

This creates a particular problem for leadership development. Research on deliberate practice has shown the value of focused, effortful practice designed specifically to improve performance, usually involving clearly defined tasks, repetition and informative feedback. That works particularly well in domains where important elements of performance can be practised repeatedly. Leadership rarely gives you such clean conditions.

A pianist can repeat the same difficult passage. A tennis player can practise the same serve hundreds of times. A leader cannot normally finish a disastrous restructuring announcement and ask everybody to come back at three o’clock so they can have another attempt. What you can repeat is the component skill. “I handled that challenge badly” might become: “When somebody challenges me unexpectedly, I start answering before I’ve worked out what they’re actually asking.” Now you have something you can practise: pause, clarify the question, then answer. “I need to listen better” might become: “When I disagree, I start constructing my response while the other person is still talking.” Now you can experiment with asking two questions before offering your own view. The leadership equivalent of deliberate practice is often therefore not recreating the whole experience. It is extracting a behaviour from the experience that is specific enough to practise again.

Other people have data you don’t

There is another limitation to learning purely from your own experience: you only experienced it from where you were standing. You know what you intended. You know what you were thinking. You know why you made the decision you made. You don’t automatically know what the room noticed, how your explanation landed, what somebody else thought you were avoiding, or what changed in the conversation while your attention was elsewhere. That makes other people an important part of the learning process, not simply as providers of judgement but as additional sources of data. The question “Any feedback?” rarely helps much. A more useful question is: “What did you notice happening that I probably couldn’t see from where I was sitting?” Or, when you’ve already formed a lesson: “What do you think I might be getting wrong about why that happened?” This is the Socialising side of learning agility: intellectual humility, feedback solicitation and deliberate exposure to perspectives that can correct the limits of your own.

The real test is whether the learning travels

Suppose you handle a difficult client conversation differently and it works. You slow down, ask what is behind the objection rather than arguing against it, and discover that the apparent resistance is really concern about implementation. You could store the lesson as: “When this client objects, ask more questions.” Useful, but narrow. Or you might extract a broader principle: “Resistance often contains information about what someone is trying to protect.” Now the lesson can travel. You can test it in a negotiation, a change programme, a difficult feedback conversation or a disagreement within your team. Learning researchers distinguish between transfer to relatively similar situations and transfer across more distant contexts. The latter is especially difficult because recognising that two superficially different situations share an underlying structure doesn’t happen automatically. That makes transfer something worth doing deliberately.

Ask: “If I’ve understood the principle correctly, where else should this work?” Then find out. And then be willing to unlearn it. There is one final trap. Once we’ve learned something useful, we tend to keep it. That sounds sensible until the conditions change. Perhaps experience teaches you that giving people more autonomy improves motivation and performance. You apply the lesson successfully with several experienced teams. Then you inherit a newly formed team, give them the same freedom, and performance deteriorates.

The easy responses are either to abandon the original lesson entirely or insist that the new team simply isn’t responding properly. A better response is to update the rule. Perhaps: “Autonomy improves performance.” becomes: “Autonomy tends to improve performance when people have sufficient capability and clarity about the outcome.” The lesson has become more conditional, but also more useful. This is Shedding: assumption testing, conscious unlearning and updating your mental model when the evidence no longer fits it. Learning agility isn’t therefore just the speed with which you acquire lessons. It also involves the speed with which you’re prepared to revise them.

How experience becomes learning

This isn’t intended as another formal model of learning agility. It’s a practical cycle for using the research and behaviours in everyday leadership: Experience → Extract → Test → Transfer → Update.

The important point is that the lesson remains provisional throughout. You aren’t trying to extract the correct answer from every experience at the first attempt. You’re getting better at constructing explanations, exposing them to evidence and improving them over time.

Five practices for learning faster from experience

Exercise 1: Find the surprise

The most useful experiences to examine aren’t always the biggest successes or failures. Often they’re the ones where reality behaved differently from your expectations. Surprise exposes a gap between your internal model of the situation and what actually happened.

Steps:

1. Choose a recent meeting, decision, conversation or piece of work where something happened differently from what you expected.
2. Complete the sentence: “I expected ________, but instead ________.”
3. Ask what assumption sat underneath your original expectation. What did you believe about the people, situation or likely outcome that reality didn’t fully support?
4. Identify any signals that were available beforehand but that you missed, discounted or interpreted differently at the time.
5. Finish with a question rather than a conclusion: “What might this be telling me about ________?”

Variations: Do this with positive surprises as well as failures. When something works much better than expected, there may be an equally valuable lesson hidden in why.

Why it matters: Asking “What did I learn?” invites you to retrieve something you already believe. Asking “What surprised me?” starts with evidence that your existing understanding may be incomplete.

Exercise 2: Deconstruct the experience

Your first explanation of an event is only one possible explanation. This exercise separates observation from interpretation so that you don’t become more confident in the wrong lesson simply because you’ve reflected on it.

Steps:

1. Write down what actually happened using only things an observer could have seen or heard.
2. Write down what you did and what other people did, without yet explaining why anybody behaved that way.
3. Now write your current explanation: “I think this happened because…”
4. Force yourself to generate at least two plausible alternative explanations, including one that challenges your preferred interpretation.
5. Ask: “What evidence would help me distinguish between these explanations?”

Variations: If the event still feels emotionally charged, leave some time before doing the exercise. Stepping back is much harder while you’re still defending yourself, blaming somebody else or replaying what you wish you’d said.

Why it matters: Experience doesn’t arrive with causality attached. Treating your first explanation as provisional makes it less likely that one difficult event turns into a rule you carry into every similar situation afterwards.

Exercise 3: Turn the lesson into a test

A lesson that never changes your behaviour remains an interesting thought. Turning it into a small experiment allows the next experience to tell you whether your interpretation was actually useful.

Steps:

1. Take one lesson you’ve drawn from a recent experience and write it down as clearly as possible.
2. Translate it into one observable behaviour. “I need to listen more” might become “When I disagree, I’ll ask two questions before giving my view.”
3. Choose the next situation where you can safely try that behaviour.
4. Decide beforehand what you’ll look for. What would suggest the change helped, made no difference or made things worse?
5. Run the experiment, capture what happened, and decide whether to repeat, modify or abandon the behaviour.

Variations: Keep the experiment smaller than your instinct suggests. “Become better at stakeholder management” is impossible to test. “Ask what concern sits behind an objection before responding to it” can be tested this afternoon.

Why it matters: Leadership situations are difficult to repeat, but component behaviours aren’t. Small experiments create some of the repetition and feedback that deliberate practice relies on without pretending leadership can be practised like a tennis serve.

Exercise 4: Borrow someone else’s eyes

You can only reflect on the information you noticed. Someone else who experienced the same situation may have seen reactions, dynamics or consequences that were invisible from your position.

Steps:

1. Choose someone who observed the same meeting, decision or interaction and whose perspective is likely to differ from yours.
2. Instead of asking “Any feedback?”, ask: “What did you notice happening that I probably couldn’t see from where I was sitting?”
3. Listen without explaining your intentions or correcting their interpretation.
4. Share the lesson you currently think you’ve drawn and ask: “What do you think I might be getting wrong about why that happened?”
5. Compare their data with yours. Decide whether it strengthens, weakens or changes your current explanation.

Variations: Ask two people who occupied different positions in the same situation. The disagreement between their accounts may be more informative than either account on its own.

Why it matters: Learning from experience doesn’t have to mean learning only from your own experience of it. Other people give you access to data that your role, attention and assumptions prevented you from seeing.

Exercise 5: Transfer and update the rule

A lesson becomes more valuable when you understand the principle underneath it well enough to recognise it elsewhere. But transfer also exposes the limits of what you’ve learned, allowing you to replace simple rules with more accurate, conditional ones.

Steps:

1. Choose one lesson that currently seems useful and express it as a short principle: “Giving people autonomy increases ownership,” for example.
2. Identify one situation similar to the one where you learned it and one situation that looks quite different but where the same underlying principle might apply.
3. Ask: “If I’ve understood this correctly, what should I expect to happen in each situation?”
4. Test the principle and pay particular attention to where it doesn’t work as expected.
5. Update the rule by adding the conditions you’ve discovered. “Autonomy increases ownership” might become “Autonomy tends to increase ownership when capability and outcome clarity are already sufficient.”

Variations: Revisit a leadership rule you’ve carried for years rather than a recent lesson. Ask where it came from, where it still works and what evidence you’ve encountered since that should have changed it.

Why it matters: Expertise isn’t simply accumulating more rules. The useful rules become more conditional and context-sensitive as experience tests their boundaries. Learning faster therefore includes becoming faster at changing your mind.

Exercise wrap up

These five exercises work at different points in the learning cycle. Exercise 1 uses surprise to identify where experience has challenged your existing understanding. Exercise 2 stops your first explanation becoming the lesson too quickly. Exercise 3 turns that provisional lesson into something you can test through action. Exercise 4 brings in data that your own perspective couldn’t provide. And exercise 5 tests whether the learning travels, then updates it when the conditions change.

Together they shift reflection from “What did I learn?” to something more demanding: “What do I currently think this experience is teaching me, and how could I find out whether I’m right?”

Five micro-practices to start today

Learning faster doesn’t require turning every experience into a formal review. A few small routines can make it more likely that useful experiences get noticed, examined and carried forward rather than disappearing into the next working day.

• Keep a learning diary: At the end of the day, capture things thing you know, suspect or would do differently because of what happened that day. Keep it to two or three sentences. After a few weeks, look back for recurring lessons, contradictions and things you appear to be learning repeatedly without actually changing.
• Use a coach as a thinking partner: Bring one recent situation to a coach, mentor or trusted colleague without starting with your conclusion about what went wrong. Describe what happened and let them question your interpretation. A good thinking partner doesn’t need to give you the answer; their value is often in exposing assumptions you didn’t realise you’d made.
• Watch someone who does it differently: Choose a capability you’re trying to develop and deliberately observe someone who handles it well. Don’t ask whether they’re “better” than you; look for specific differences in what they notice, say, ask or do. Borrow one behaviour and try it yourself.
• Create a learning pair: Find a colleague and spend ten minutes together every week or two exchanging one thing each of you has learned from recent work. The discipline of explaining a lesson to someone else often makes it clearer, while their questions can expose where you’ve generalised too quickly.
• Deliberately do something unfamiliar: Occasionally volunteer for a task, conversation or problem where your usual approach isn’t guaranteed to work. Take on a different role in a meeting, work with someone outside your normal circle or tackle a problem from another function. Learning agility needs novelty occasionally; if every situation is familiar, there is less reason to examine the assumptions you already rely on.

Conclusion

The leaders who learn fastest aren’t necessarily the ones having the most experience. Senior leadership will give you plenty of that whether you ask for it or not. The difference is what happens afterwards. Experience gives you information. You notice where it differs from what you expected. You step back far enough to resist making your first explanation the answer. You turn the emerging lesson into something you can test. You borrow perspectives that reveal what you couldn’t see yourself. You carry the underlying principle somewhere else and discover where it works, where it doesn’t and what conditions you hadn’t noticed before. Then you update what you think you know: Experience → Extract → Test → Transfer → Update.

The cycle matters because experience gives you data, not lessons. The lesson is something you construct, and that means you can construct the wrong one. You don’t need to reflect on everything that happens to you. You need to get better at recognising the experiences that challenge what you thought you knew, extracting something worth testing from them, and changing your mind when reality gives you a better answer. The goal isn’t to accumulate more experience. It’s to waste less of the experience you’re already getting.

Reflective questions

• Think about something that surprised you at work recently. What did you expect to happen, what happened instead, and what assumption might the difference be challenging?
• What leadership lesson do you currently treat as obviously true? Where did you learn it, and what evidence would cause you to modify it?
• Where are you repeatedly experiencing the same problem without changing what you do? What component behaviour could you turn into a small experiment?
• Who sees your leadership from a sufficiently different position that they probably have useful data you don’t? What could you ask them?
• What useful lesson have you learned in one part of your work that you haven’t yet deliberately tested somewhere else?

Explore further

• The Learning Agility Library, for the five domains of Sensing, Socialising, Shedding, Sprinting and Stepping back and the 20 behaviours that sit underneath them
• Leading yourself: self-awareness, for more on seeing your own behaviour and impact accurately enough to learn from it

Sources

Barnett, S.M. and Ceci, S.J., 2002. When and where do we apply what we learn? A taxonomy for far transfer. Psychological Bulletin, 128(4), pp.612–637.

DeRue, D.S., Ashford, S.J. and Myers, C.G., 2012. Learning agility: In search of conceptual clarity and theoretical grounding. Industrial and Organizational Psychology, 5(3), pp.258–279.

Dewey, J., 1938. Experience and education. New York: Macmillan.

Ericsson, K.A., Krampe, R.T. and Tesch-Römer, C., 1993. The role of deliberate practice in the acquisition of expert performance. Psychological Review, 100(3), pp.363–406.

Kolb, D.A., 1984. Experiential learning: Experience as the source of learning and development. Englewood Cliffs, NJ: Prentice Hall.

Schön, D.A., 1983. The reflective practitioner: How professionals think in action. New York: Basic Books.