Quick answer
Build resilience through experience by reviewing stressful events once the immediate pressure has eased, and turning one credible lesson into a behaviour you can practise. Test that behaviour in later situations, keep what works and revise the lesson when new evidence does not fit.
Five ways to learn from stressful experiences and build resilience:
- Recover before analysing: Create enough physical and emotional distance to think clearly.
- Reconstruct the event: Separate the sequence, decisions and results from the story you first told yourself.
- Use other people’s evidence: Ask what colleagues, stakeholders and team members noticed from where they stood.
- Practise a specific change: Turn “communicate better” or “stay calm” into behaviour you can repeat and observe.
- Prepare for transfer: Decide where else the lesson applies, where it does not and what you will do when similar pressure returns.
A stressful experience offers information, not a guaranteed benefit. Learning also means changing the system, seeking support and recognising when recovery must come before development.
Learning is the L in Thompson’s (2010) ARSENAL framework, and it is the part of recovery where difficult experience becomes useful. Building resilience through experience depends on what happens after the demanding event. Leaders often describe difficult assignments, crises, mistakes and major transitions as important parts of their development. Ong (2008) reports interviews with 36 public sector leaders, drawn from a 2007 joint study by the Center for Creative Leadership and the Civil Service College, Singapore. Of those interviewees, 92% cited work assignments as significant or memorable learning events, while only 11% cited coursework or training. “Tough Jobs” is what a call these stretch experiences that allow us to learn and become even better.
Challenge by itself is not enough. Leaders can leave the same event with a better method, a misleading rule, a stronger avoidance habit or no usable lesson at all. In my experience, structured after-event reviews are one of the most practical ways to turn an experience into learning, provided the review is honest and specific.
Those ideas do not mean every painful event should be reframed as a gift. Stress that overwhelms coping capacity is a different matter from a manageable challenge. Resilience may grow more reliably through recovery, support, reflection, practice and changes to the environment than through pressure alone. People who learn most from a hard period are often those who were given time and a structured way to look at it.
What gets in the way of learning from pressure
The period after a difficult event is rarely quiet. There may be a board update to prepare, a client relationship to repair or another urgent problem already competing for attention. Teams move on before memories are tested and assumptions are challenged. The event is remembered, but little changes.
Emotion can distort the review in either direction. Shame and fear encourage blame, concealment or an overly broad conclusion such as “I am not suited to this role”. Relief can produce the opposite problem: because the crisis passed, the team concludes that the response worked. Seniority adds another complication, because people may soften what they tell the leader who made the decision.
| What happens after the event | The learning risk | A better response |
|---|---|---|
| The team celebrates survival and moves straight to the next priority. | Luck and last-minute recovery are mistaken for a sound process. | Review what worked, what nearly failed and what should change before the next event. |
| The review begins with who was at fault. | People defend themselves and withhold information needed to understand the system. | Establish the sequence and contributing conditions before judging responsibility. |
| The leader decides privately what the lesson was. | Intent and authority crowd out evidence from other positions. | Collect separate accounts before settling on an explanation. |
| The lesson is “communicate more” or “be more resilient”. | The conclusion is too broad to influence later behaviour. | Specify who will do what, at which point and under what conditions. |
| The organisation praises endurance while leaving the cause untouched. | Resilience becomes a reason to tolerate avoidable overload or unsafe practice. | Separate individual capability from the structural change the event exposed. |
Quick check: how well are you learning from pressure?
Think about the last difficult experience you went through, not your easiest recent week. Score each statement from 1 (rarely) to 5 (almost always), then add your five scores together. This is a reflection tool to prompt thinking, not a diagnostic measure.
- I review difficult events once the immediate pressure has eased.
- I rebuild the sequence of events before deciding what they meant.
- I ask people who saw the event from other positions what they noticed.
- I turn a lesson into a specific behaviour I can practise and observe.
- I test whether a lesson still holds when a similar situation returns.
How to read your total (out of 25)
- 5 to 11: Few of these habits are in place yet. Choose the statement you scored lowest and use the matching practice below at your next difficult event. If stress keeps you from thinking clearly about what happened, speak to a qualified health professional.
- 12 to 18: Some of these habits are in place. Strengthen the ones you use least, using the practices that relate to them.
- 19 to 25: Most of these habits are in place. Keep them going, and check again after your next demanding period.
Ten practical ways to learn from stress and prepare for future challenges
1. Stabilise before trying to extract the lesson
In the immediate aftermath, attend to safety, sleep, health, workload and the people affected. A tired or highly activated mind may rush towards a simple explanation because certainty is a relief. That explanation can harden before the relevant facts are available.
Choose the timing deliberately. An operational hot debrief may be needed within hours to capture facts and immediate risks. Deeper reflection often works better after a night’s sleep or once urgent consequences have been managed. Significant trauma can require much longer and may need clinical support.
Postponing analysis briefly is different from burying the event. Put a review in the diary, identify who should attend and preserve records while they are still available. Where serious harm, legal exposure or safeguarding is involved, follow the appropriate formal process rather than substituting an informal leadership exercise.
2. Reconstruct what happened before explaining why
Create a simple timeline: what was known, what decisions were made, what changed and what happened next. Use emails, meeting notes, customer feedback, operational data or other records where appropriate. Memory tends to reorganise events around the outcome, which makes the result look more predictable than it was.
Record the information available at each decision point. A decision that produced a bad outcome may have been reasonable with the evidence at hand. A good outcome may have followed a weak process rescued by luck. Learning improves when decision quality and outcome quality are reviewed separately.
Notice the gap between expectation and reality. What surprised you? What signal did you miss, discount or misread?
3. Run a structured after-action review
Use four questions: What did we expect? What actually happened? What explains the difference? What will we repeat, change or stop? Keep the discussion tied to a defined event rather than letting it become a general assessment of the team.
Ask people to prepare individually before the group discussion. This reduces the chance that the most senior or confident speaker supplies the explanation everyone else then follows. Bring objective evidence where it exists. Reviews are most useful when they are linked to real performance and backed by evidence.
End with a small number of owners and actions. A long list usually means the team has documented the conversation rather than made a choice. Record the lesson in language that someone who was not present could understand and use.
4. Review successful responses and near misses as carefully as failures
A result can hide a fragile method. The deadline was met, but only because two people worked through the night. The client stayed, but the relationship depended on one unrecorded intervention. The decision proved correct, but the team excluded dissent and could easily have missed a critical risk.
Ask what nearly went wrong, what recovery action saved the situation and which assumptions were never tested. Near misses are valuable because they expose vulnerability before the full cost is paid. Successes also reveal resources worth protecting: a trusted relationship, clear authority, useful expertise or a well-designed escalation route.
A balanced review avoids turning learning into a search for deficiency. Identify what should be repeated as well as what should change. People are more likely to use a review when it gives a clearer picture of capability rather than another ritual of criticism.
5. Borrow the perspectives you could not have had
You know what you intended and what information reached you. Other people know how the decision landed, what was happening at the edges and which concerns never travelled upwards. Ask direct reports, peers, customers, advisers and operational colleagues what they saw from their position.
Use questions that invite evidence: What changed first? When did you become concerned? What did I do that helped? What made the situation harder? What were people reluctant to say? Ask separately before bringing people together if hierarchy or conflict is likely to shape the answers.
Listen for differences rather than forcing one authorised account. Contradictory descriptions may reveal unclear roles, information gaps or different effects on different groups. The learning agility framework offers further ways to learn through other people, test assumptions and let go of methods that no longer fit.
6. Treat your first lesson as a working hypothesis
One experience can support several explanations. A stakeholder rejected the proposal. The lesson might concern the evidence, the timing, the relationship, the decision process, competing interests, or that particular stakeholder. “Bold ideas do not work here” is only one interpretation, and probably too broad to be useful.
Write the lesson in provisional language: “My current view is that…” Then ask what else could explain the result and what evidence would tell the alternatives apart. Look for information that conflicts with your preferred account, especially when that account protects your reputation or confirms what you already believed.
Define the boundary of the lesson. A response that worked in a fast operational incident may be damaging in a strategic discussion. Resilience includes flexibility: knowing which capability to reuse, which detail was specific to the context and when the previous answer no longer fits.
7. Convert insight into a behaviour you can practise
“I need to communicate better” cannot be rehearsed or observed. “During the first hour of an incident, I will state what we know, what remains uncertain, who owns each decision and when the next update will come” can.
Choose one component skill from the experience. It might be pausing before answering a challenge, checking who has not spoken, escalating earlier, setting a decision threshold or distinguishing a reversible choice from an irreversible one. Define what another person would see you doing.
Practise the component in lower-risk situations before the next major test. Ask someone to observe it and give feedback. Repetition turns a remembered lesson into an available response. Reflection without practice can leave the old habit untouched.
8. Rehearse the next pressure point
Identify a situation in which the previous pattern is likely to return: another board challenge, a product failure, a restructuring conversation, a cyber incident or a period of sustained demand. Decide in advance what signal will tell you the situation is developing and what response you want available.
Use scenario work, role-play, tabletop exercises or short mental rehearsal. Introduce complications rather than rehearsing an ideal script. What if information is incomplete, a key person is absent, the stakeholder is angry or two priorities conflict? The rehearsal should expose weak assumptions while the cost of discovering them is still low.
Include recovery and support in the plan. Resilience under pressure depends on who can challenge your thinking, take over part of the load and notice changes in your behaviour. Preparation is stronger when it covers the network and operating conditions, not only your individual response.
9. Build a varied learning network and seek unfamiliar work
Set learning goals over different time horizons and spend time with people who are curious, well informed and willing to disagree. Read beyond your own discipline, observe leaders with different styles, and use mentors, peers or coaches to examine experiences that are hard to interpret alone.
Choose occasional assignments that require something new: broader scope, a different function, unfamiliar stakeholders, cross-cultural work or a problem without an established solution. Challenge supports development when it comes with feedback, authority, time and appropriate support. More stretch is not always better.
DeRue and Wellman (2009) examined how developmental challenge, learning orientation and the availability of feedback shape leaders’ development. In my experience, more challenge helps only when there is feedback to make sense of it. Before accepting another stretch assignment, ask what capability it may develop, who will give you perspective and whether you have enough capacity to learn rather than simply endure.
10. Track whether the lesson survives real work
Set a review point. After the next comparable situation, ask whether the new behaviour occurred and what effect it had. Use evidence from outcomes and from people who experienced your leadership. Confidence that you have changed is weaker evidence than a different pattern that others can describe.
Keep a concise leadership playbook: warning signs, tested responses, important relationships, decision principles and the conditions that reduce your effectiveness. Update it when experience contradicts an earlier rule. A playbook should become more accurate over time, not simply longer.
A weekly leadership review can stop smaller experiences disappearing into the next deadline. Record one surprise, one piece of feedback, one experiment and one issue that needs a deeper review. This creates continuity between major events.
When the organisation prevents honest learning
Individual reflection has limited value in a system that punishes candour, hides weak signals or rewards leaders for appearing certain. Edmondson (1999) linked psychological safety with learning behaviour in work teams. Accountability remains necessary, alongside conditions in which people can report concerns, admit uncertainty and examine mistakes without humiliation or retaliation.
Senior leaders set those conditions. What happens when someone brings bad news? Are post-event reviews a search for evidence, or a performance designed to protect a preferred story? Do actions from earlier reviews receive funding and attention? If the same issue returns, is the individual blamed again, or is the unresolved system examined?
When reflection needs professional support
Coaching can be useful when the event concerns leadership behaviour, relationships, decisions, role transition or how to turn insight into practice. A mentor may bring experience from a similar context, while technical, legal, risk or governance questions need the relevant specialist.
Clinical support is more appropriate when the experience keeps producing intrusive memories, avoidance, panic, persistent low mood, disrupted sleep, increased substance use or difficulty functioning. Do not force an immediate lesson out of trauma. Recovery and safety come first, and growth is not an obligation.
If the event involved serious harm, bullying, discrimination, safeguarding, illegality or professional misconduct, use the proper reporting and investigation routes. A reflective conversation must not replace accountability, the preservation of evidence or protection for the people affected.
Conclusion
Learning is what turns experience into something you can use. Stressful experience does not automatically produce wisdom or resilience. It gives incomplete information, filtered through emotion, memory, hierarchy and the eventual outcome. Learning starts when that information is examined rather than simply remembered. Recover first, reconstruct the event, ask what others saw, and treat your first lesson as provisional. Turn the most credible insight into a behaviour, rehearse it and test it in later work. Keep what has proved useful and change what has not. The series begins with recognising when stress is changing your judgement, the awareness that makes this later learning possible.
Further reading
- How can I learn faster from experience as a leader?: A practical guide to extracting, testing, transferring and updating lessons from everyday experience, with five exercises
- Learning Agility: The Learning Agility Library, with 20 behaviours grouped into five facets. A deep dive on learning.
- Personal Learning: Closing the gap between your intended and actual impact through feedback and reflection
- Learning Orientation: Where you sit between experience-reliant and growth-oriented approaches, and what each costs you. This is the trait library.
Reflection questions
- Which recent experience still holds information I have not examined properly, and whose view is missing from my account?
- What explanation am I most invested in protecting?
- What evidence would make me revise the lesson I have drawn?
This article is part of a series of seven on executive stress. You can find the full series on the executive stress hub page.
Ready to turn experience into stronger leadership?
For you: Leadership Clinic
Bring one recent experience that still needs a proper look. In 90 focused minutes, we review what happened, what you learned and how you will know things have changed.
For you: Executive Coaching
Examine difficult experiences, test the lessons you have drawn and turn them into leadership practice that holds up in real work.
For your organisation: Team coaching and training
I help leadership teams build the review habits, conditions and candour that let them learn honestly from success, failure and near misses.
Choose the level of support that fits the leadership challenge you are working through.
Sources
- DeRue, D. S. and Wellman, N. (2009) ‘Developing leaders via experience: the role of developmental challenge, learning orientation, and feedback availability’, Journal of Applied Psychology, 94(4), pp. 859–875.
- Edmondson, A. C. (1999) ‘Psychological safety and learning behavior in work teams’, Administrative Science Quarterly, 44(2), pp. 350–383.
- Ong, P. Y. (2008) ‘Leadership development in the Singapore Public Service’, ETHOS, Issue 05, November. Available at: https://knowledge.csc.gov.sg/ethos-issue-05/leadership-development-in-the-singapore-public-service/ (Accessed: 2 November 2026).
- Thompson, H. L. (2010) The Stress Effect: Why Smart Leaders Make Dumb Decisions and What to Do About It. 1st edn. San Francisco: Jossey-Bass.



