Experience Is Not the Same Thing as Learning
Activities create experiences. Reflection turns those experiences into learning.
Have you ever run an activity that seemed to go great, only to discover during the debrief that half the room missed the point?
I have.
In fact, I’ve had activities where participants were fully engaged. They were talking, laughing, solving problems, and doing everything I hoped they would do.
Then I’d start asking questions afterward and realize they had taken away something completely different than I intended.
That’s when I learned an important lesson.
Activities don’t create learning.
Activities create experiences or opportunities for learning, but often learning comes later.
One of the easiest mistakes a trainer can make is confusing participation with learning. Just because learners are busy doesn’t mean they’re learning. Just because they’re talking doesn’t mean they’re making sense of what happened.
We’ve all attended sessions where people left saying, “That was fun.”
That’s nice.
What are they going to do differently on Monday?
That’s the question that matters.
The difference between an activity and a learning experience is usually the debrief.
I’ve become convinced over the years that the debrief is often more important than the activity itself.
The activity gives people something to think about. The debrief helps them figure out what it means.
That’s why I get nervous when I see trainers spend twenty minutes on an exercise and two minutes talking about it afterward.
The activity was the setup.
The conversation afterward is where much of the learning happens.
One of the simplest debrief structures I’ve used over the years goes something like this:
What happened?
What did you notice?
Why do you think that happened?
Where do you see that at work?
What will you do differently because of it?
Notice that none of those questions are asking for the “right answer.”
They’re asking learners to think. And that’s really the point.
The military figured this out a long time ago. You don’t just complete the mission and move on. You stop and talk about what happened. What worked? What didn’t? What would we do differently next time? (Jevon Wooden and I talked about after action reports in this podcast.)
The same idea shows up in sports.
Teams watch game film.
Coaches review decisions.
Athletes look at mistakes and successes.
Nobody assumes the experience alone is enough.
They reflect on it.
As trainers, we should do the same thing.
I think this is one place where AI can be genuinely useful.
A learner could use AI after a project, a presentation, a difficult conversation, or a training exercise and ask questions they may not think to ask themselves.
What assumptions did I make?
What might I be missing?
What are three other ways to look at this situation?
What would you want to know if you were coaching someone through this?
Those kinds of questions can deepen reflection.
But there is a risk.
If learners immediately ask AI for the lesson, they may skip the thinking that produces the lesson.
That’s my concern.
Learning isn’t something we download.
It isn’t something AI hands us.
It’s something we construct as we make sense of our experiences.
Two people can sit through the exact same activity and walk away with completely different lessons.
Reflection helps learners decide what matters.
It helps them connect the experience to their work.
It helps them figure out what they want to keep doing and what they want to change.
That’s why I’ve become less interested in asking whether participants enjoyed an activity.
I’m more interested in what happened afterward.
What did they notice?
What did they learn?
What will they do differently?
Because the learning often starts after the activity ends.
