top of page

Reflective Practice: How a Personal Debrief Helps You Learn and Grow

Oct 27
5 min read

Lost in Translation #12: Debrief


Infographic of sailing ships at sea with smoke, stating On 21 October 1805, the Royal Navy won the Battle of Trafalgar.


Trafalgar Day. The retrospective that changed how I think. And the one tool most people never use on themselves.


On 21 October 1805, the Royal Navy won the Battle of Trafalgar. Twenty-seven British ships faced thirty-three French and Spanish ships. Before the engagement, Nelson sent his famous signal: “England expects that every man will do his duty.” The victory was decisive, but the cost was significant. Nelson did not survive it.


For me, Trafalgar Day is a reminder of why reflection matters after significant experiences. In military life, debriefing and lessons identified are built into the way we learn. We look at what happened, what worked, what did not, and what should change next time.


In civilian life, we are often much quicker to move on.


The meeting ends. The project finishes. The difficult week passes. We immediately start the next thing without stopping to ask what the last experience actually taught us.


That is where reflective practice comes in.

 

What Is Reflective Practice and Why Does It Matter?


Reflective practice is simply the process of thinking about an experience, understanding what you can learn from it, and deciding what you might do differently as a result. Donald Schön's work on the reflective practitioner helped establish the concept within professional development, particularly the idea that experience becomes more useful when we actively think about and learn from it.


You can have years of experience without necessarily learning everything those years have to teach you.


The difference is often whether you stopped long enough to notice.


For me, one of the simplest ways to do that is a debrief.

What Scrum Taught Me About Reflection


A few years ago, I was working on the Naval Staff as we introduced Scrum and agile ways of working into how we operated. Scrum has since become increasingly visible across the Royal Navy, with senior leaders discussing how agile working can help teams respond faster and work differently in complex environments.


What stayed with me was not simply a framework for working more efficiently.

“I learned the concept of the retrospective. The built-in pause at the end of a sprint to ask: what worked, what did not, and what do we do differently next time?”

Then I started applying it personally.


Not in a dissect-every-moment, analyse-every-movement kind of way. In the simplest possible way. That was a good experience. I should do more of that, with those people. That was difficult. What would I change next time?


Whatever the experience, a quick retrospective gives you an opportunity to learn rather than simply move on.


I have brought that into ACSIS and into how our team operates. Honest feedback, reflection, retrospective, debrief. Call it what you will.


The principle is the same.


Pause. Learn. Then move.

Why We Keep Repeating the Same Patterns


The debrief has different names depending on where you stand. In military environments, you might call it a debrief or after-action review. Agile teams use retrospectives. Organisations talk about lessons learned or post-project reviews.

Personally, we often do nothing at all.

“We move on without processing what happened. And then we are surprised when the same things keep happening.”

That is the part I find most interesting.


We are often very good at reviewing performance when there is a formal requirement to do so, but much less likely to apply the same discipline to our own lives.


  • Why did that piece of work go so well?

  • Why did that relationship leave me exhausted?

  • Why was I at my best during that period?

  • Why do I keep saying yes to something I already know does not work for me?


Reflection creates just enough distance to see the pattern.


How to Do a Personal Debrief


Here is the simplest version I know.


At the end of the week, month, project or significant experience, ask yourself three questions.


What worked? Be specific. What did you do, with whom, and under what conditions that produced something positive? Make a note of it. Do more of it.


What did not work? This is not about blame or self-criticism. It is honest observation. What produced a result you did not want? What drained you, frustrated you or moved you away from what matters?


What do I take forward? Choose one thing. Not a long list of actions you will never look at again. One thing you will do differently, more of, or less of because of what you have learned.

“The debrief does not need to be long. It needs to be honest. And it needs to happen before you move on.”

That is reflective practice in its simplest form.


Experience. Reflection. Learning. Action.


How Reflective Practice Supports Personal Growth


Reflection does not mean endlessly analysing the past. The point is to use the past to make the next decision better.


Sometimes the lesson is significant. Sometimes it is incredibly ordinary. You work better in the morning. A particular person brings out the best in you. You keep agreeing to things that drain you. You feel better when you protect time to exercise. A project worked because the team communicated properly.


Those observations become useful when you do something with them.


Otherwise, they are just experiences.


The goal is not to spend your life looking backwards.


It is to look backwards for long enough to move forwards more deliberately.


Clarity, Courage, Connection


Clarity. The debrief creates it. It is difficult to see a pattern while you are still inside it. Reflection gives you enough distance to understand what is actually happening.


Courage. Honest reflection takes nerve, particularly when you have to consider your own contribution to something that did not go well. That is often where the most useful learning sits.


Connection. Some of the best reflection happens with other people. A trusted colleague, your team, a friend or a coach can sometimes ask the question you were avoiding or help you see something you could not see alone.


You do not need to analyse everything.


But every now and then, before racing towards the next thing, stop and debrief.


You might be surprised by what you already know.


Looking for More Clarity, Courage and Connection?


If you are ready to find your heading, ask better questions and build a future that feels like yours, the Free Clarity Call is where we start.


It is one conversation. No pressure. Just space to think clearly about what comes next.


Sam, Lloyd and Simon work with people who are carrying stress, pressure or emotional weight and want practical support to move forward with greater clarity, confidence and connection. Sometimes the shift starts with something big. Sometimes it starts with something smaller, a pause, a breath, a different perspective, a little more lightness.


👉 Book a FREE Clarity Session with ACSIS Life Coaching



👉 Visit acsis.co.uk or email contact@acsis.co.uk



Reflective Practice FAQs

What is reflective practice?

Reflective practice is the process of thinking about an experience, identifying what you learned from it and deciding how that learning should influence what you do next.

Ask three simple questions: what worked, what did not work, and what will I take forward? The aim is not to analyse every detail but to identify useful patterns and one or two practical lessons.

Reflection helps turn experience into learning. Without taking time to consider what happened and why, it is easy to repeat the same habits and patterns without recognising them.

The terms come from different environments but share a similar purpose. A debrief is commonly used in military and operational settings, while a retrospective is associated with agile working. Both create space to review what happened and identify lessons for the future.

There is no single rule. A short weekly reflection can help you notice everyday patterns, while monthly, quarterly or end-of-project reviews can help you look at broader changes and lessons.


 
 
 

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page