Kolb's Experiential Learning Cycle: The 4 Stages and Styles

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Kolb's experiential learning cycle is a model, set out by David Kolb in 1984, which says people learn by moving through four stages: having a concrete experience, reflecting on it, forming general ideas from it, and testing those ideas in action. Skipping any stage leaves learning incomplete. It's a design structure for training, not a personality test.

Where the Model Comes From

David Kolb presented the full theory in his 1984 book, Experiential Learning. The official Kolb Learning Style Inventory guide describes the theory's core definition this way: learning is "the process whereby knowledge is created through the transformation of experience" (Kolb, 1984, p. 41), as quoted in the KLSI 4.0 guide.

That sentence matters more than the diagram most people remember. Kolb isn't saying experience alone teaches. He's saying experience becomes knowledge only after you do something with it. A salesperson who has made hundreds of calls has hundreds of experiences. Whether they've learned anything depends on what happened between one call and the next.

And that's the gap most corporate training leaves open. Training budgets pay for the content (a lecture, a course, a slide deck) and then assume the rest happens by itself. Kolb's cycle gives L&D teams, managers and team leads a way to check whether the rest actually has room to happen.

The Four Stages

According to the Kolb Learning Style Inventory 4.0 guide, the cycle has two ways of grasping experience (concrete experience and abstract conceptualization) and two ways of transforming it (reflective observation and active experimentation). The learner "touches all the bases" in a recursive process, so it's closer to a spiral than a loop.

Stage Short name What the learner does Example question to ask
Concrete experience Feeling or experiencing Takes part in a real activity, task or simulation What just happened?
Reflective observation Watching or reflecting Steps back and looks at the experience from several angles What did I notice, and what surprised me?
Abstract conceptualization Thinking Forms a general rule, model or theory from the reflection What's the pattern, and why does it hold?
Active experimentation Doing Tests the idea in a new situation What will I try differently next time?

1. Concrete experience

Learning starts with something real. A new hire shadows a customer call. A manager runs their first difficult feedback conversation. A finance analyst closes a month-end with an unfamiliar system. The experience can be live work, a role-play or a case simulation, but it has to involve the learner doing something, not just hearing about it.

2. Reflective observation

This is the stage most teams skip. The learner pauses and asks what they saw, felt and noticed, without rushing to a verdict. Good prompts are open and specific: "Where did the conversation change direction?" works better than "How did it go?" Reflection works best when it's separated from judgment, which is why a facilitator's skill matters here. Our guide to facilitation skills covers how to hold that space without turning it into a post-mortem.

3. Abstract conceptualization

Reflection produces observations. Conceptualization turns them into something portable: a principle, a checklist, a mental model. "The customer went quiet when I mentioned price" becomes "Price objections often hide a missing business case, so I should confirm value before quoting." If the learner can't state the idea in their own words, they haven't finished this stage.

4. Active experimentation

The idea gets tested. The new rule is applied in a real situation, and that situation becomes the next concrete experience. This is what makes it a cycle. Without the experiment, the learner has an interesting theory. With it, they have evidence.

The Four Learning Styles

Kolb noticed that people tend to lean on some stages more than others. The KLSI 4.0 guide describes four basic styles, each built from two adjacent modes. These are the original four, and the guide notes they came out of research with earlier versions of the inventory.

Style Dominant modes Tends to be good at Often prefers in formal learning
Diverging Concrete experience and reflective observation Viewing situations from many points of view, generating ideas, brainstorming Working in groups, listening with an open mind, personalized feedback
Assimilating Abstract conceptualization and reflective observation Taking in a wide range of information and organizing it into logical form Readings, lectures, analytical models, time to think things through
Converging Abstract conceptualization and active experimentation Finding practical uses for ideas and theories, solving problems Simulations, laboratory-style tasks, practical applications
Accommodating Concrete experience and active experimentation Learning from hands-on experience, carrying out plans Working with others to finish tasks, setting goals, field work

Those descriptions come straight from the KLSI 4.0 guide. The same guide ties each style to a cluster of skills: Accommodating to acting skills such as leadership and initiative, Diverging to valuing skills such as relationship-building and sense-making, Assimilating to thinking skills such as information analysis and theory building, and Converging to decision skills such as quantitative analysis and goal-setting.

The later updates: from four styles to nine

The model didn't stay frozen. The KLSI 4.0 guide says the inventory has been revised several times since it was first published in 1971, with version 4.0 revised in 2011 as the first major revision since 1999. Version 4.0 added a nine-style typology, an assessment of learning flexibility, an expanded personal report and improved psychometrics.

The nine styles are Initiating, Experiencing, Imagining, Reflecting, Analyzing, Thinking, Deciding, Acting and Balancing. The guide says the finer typology was introduced to reduce the confusion caused by borderline cases in the original four-style system. Four of the nine emphasize a single mode, four combine two modes, and Balancing draws on all four.

The same guide also acknowledges a technical issue with the instrument's forced-choice format, which some statisticians have criticized because it produces scores that depend on each other (a property called ipsativity). It's worth knowing before anyone treats an inventory result as a precise measurement.

What the Evidence Says About Matching Styles

Here's the part of the Kolb story that gets lost in workshop handouts. The cycle and the styles are two different claims.

The cycle claim is that effective learning involves experiencing, reflecting, generalizing and testing. That's a description of a process, and it gives you a sensible checklist for designing learning.

The style claim, in its popular form, is that you should identify each person's style and teach them in that style. Researchers call this the "meshing" hypothesis. A major review by Pashler, McDaniel, Rohrer and Bjork, published in Psychological Science in the Public Interest in 2008, found no adequate evidence base to justify using learning-styles assessments in general educational practice. To count, the authors argued, a study would need to sort learners by style, randomly assign them to different teaching methods, give everyone the same test, and show that different styles do best under different methods. They found virtually no studies showing that pattern, and several well-designed studies contradicted it.

So where does that leave Kolb? Two practical conclusions:

  • Don't sort people into style boxes and teach each box differently. The evidence doesn't support spending training money that way.
  • Do use the cycle to make every learning experience complete. The point isn't that a Converging learner needs a lab and an Assimilating learner needs a lecture. It's that everyone benefits when a program includes real practice, honest reflection, a clear takeaway and a chance to apply it.

Used this way, the styles are useful as a conversation about habits. A person who realizes they always jump straight from experience to action can try adding a reflection step. That's a flexibility exercise, not a label.

Kolb vs. Other Learning Frameworks

Kolb's cycle sits alongside several other models that L&D teams use. They answer different questions.

Framework Core question Structure Best used for
Kolb's learning cycle How does experience turn into learning? Four stages in a cycle: experience, reflection, concepts, experiment Designing workshops, simulations and after-action reviews
70-20-10 learning model Where should learning time come from? A rule of thumb that splits development across on-the-job work, other people and formal courses Planning the mix of a development program
Four stages of competence How aware is someone of what they can and can't do? A progression from unaware incompetence to unconscious competence Diagnosing where a learner is on a skill
Gibbs reflective cycle How do I reflect on a specific event in a structured way? A staged prompt sequence covering description, feelings, evaluation, analysis, conclusion and action plan Written or guided reflection after a single event

The simplest way to combine them: use 70-20-10 to decide where learning happens, Kolb to decide what happens inside each learning moment, the four stages of competence to know where each person starts, and a Gibbs-style prompt list when the reflection stage needs more structure.

How to Apply the Cycle Step by Step

Here's a workable process for designing a workshop or running a post-project review. Both follow the same shape.

Step 1: Define the one skill or decision you want to improve

Keep it narrow. "Better stakeholder communication" is too broad. "Running a status update that doesn't trigger a flood of follow-up questions" is something you can practice and observe.

Step 2: Design or pick the concrete experience

Choose a real task, a realistic simulation, or a recent project. The experience should be close enough to real work that the lessons transfer. If you're running a review, name the specific episode you're examining, not the whole project.

Step 3: Schedule reflection before teaching

Give participants time to write or talk about what they noticed before anyone explains the "right" answer. Ask for observations, not conclusions. Use questions like "What did you expect, and what happened instead?" Pair people up if the group is quiet.

Step 4: Build the concept from their observations

Now draw out the pattern. Ask the group what rules or principles seem to follow from what they saw. Add a framework or reference only after they've offered their own. This is where a mentor or coach adds the most value, a topic covered in our pages on coaching skills and self-awareness.

Step 5: Commit to an experiment

Each person picks one specific thing to try in the next week or two. Write it down in a sentence: what, where, with whom, and how they'll know it worked.

Step 6: Close the loop

Schedule a short follow-up in which people report what they tried and what they learned. That conversation is the next concrete experience and reflection, which keeps the cycle turning instead of ending at the workshop door. It also builds the habit described in continuous learning.

Ready-to-Copy Template: Kolb Cycle Planner

Copy this table into a doc and fill it in for any workshop, onboarding module or project review.

Stage Prompt or activity Owner Time Output
Concrete experience Describe the task, simulation or episode A shared, specific event
Reflective observation Each person writes three observations. What happened? What surprised me? What did I feel? A list of observations
Abstract conceptualization Group names the pattern. What principle explains what we saw? One to three written principles
Active experimentation Each person commits to one experiment A dated, specific commitment
Follow-up Check-in on what was tried and what was learned The next cycle's starting experience

Examples by Business Function

These are illustrative scenarios, not case studies.

Function Concrete experience Reflection Concept Experiment
Sales Role-play a discovery call with a skeptical buyer Where did the buyer disengage? Open questions about the cost of the problem hold attention longer than feature talk Ask two cost-of-problem questions on the next three real calls
Customer support Handle a simulated escalated ticket Which phrases calmed or inflamed the customer? Acknowledging the impact before explaining the fix lowers tension Use an acknowledge-first opener on escalations this week
Engineering Run a blameless review of a production incident What did we assume that turned out false? Unverified assumptions in handoffs are the recurring failure point Add an assumptions line to the handoff template
HR Practice a difficult performance conversation When did the employee stop listening? Specific observations land better than general judgments Prepare three specific examples before the next review
Marketing Launch a small campaign test What did the results show against what we predicted? Our audience responds to concrete outcomes more than to brand claims Rewrite two ads around outcomes and compare
Operations Walk through a delayed shipment end to end Where did information get stuck? Delays cluster at handoffs without a named owner Name one owner for each handoff in the next cycle

Dos and Don'ts

Do

  • Treat reflection as a scheduled activity. If it isn't on the agenda, it gets cut when time runs short.
  • Keep experiences close to real work. Transfer is easier when the practice looks like the job.
  • End with a small, specific experiment. One concrete change beats a list of good intentions.
  • Use the styles as a prompt for self-awareness. Ask people which stage they tend to skip, then give them a way to practice it.
  • Close the loop. Follow up on the experiments so the cycle continues.

Don't

  • Don't sort people into style groups and change the teaching for each. The research review above found no adequate support for that practice.
  • Don't present the inventory result as a fixed trait. The guide itself describes styles as shaped by the person and the environment at multiple levels, and individuals vary by task.
  • Don't stop at the experience. A fun simulation with no debrief is entertainment.
  • Don't force a strict order. Real learning often loops back. The cycle is a checklist for completeness, not a rigid script.
  • Don't treat reflection as blame. If people fear judgment, they'll give polite answers instead of honest ones.

Key Facts

  • What it is: A four-stage model of how experience becomes knowledge: concrete experience, reflective observation, abstract conceptualization and active experimentation.
  • Who created it: David Kolb, who presented the theory in his 1984 book Experiential Learning.
  • The four original styles: Diverging, Assimilating, Converging and Accommodating, each built from two adjacent modes.
  • Later update: KLSI 4.0, revised in 2011, introduced a nine-style typology and a learning flexibility assessment.
  • What the evidence supports: The cycle works as a design structure. Matching teaching to learners' preferred style isn't supported, according to a 2008 review in Psychological Science in the Public Interest.
  • Best use: Workshops, simulations, onboarding and after-action reviews that need practice, reflection, a takeaway and an experiment.

About the author

Kevin Kim

Kevin Kim

Senior Customer Retention Strategist

Kevin Kim is Senior Customer Retention Strategist at Rework, writing for HR leaders and people managers on growing their people. Kevin covers job descriptions and role design, employee competencies, and organizational competency frameworks: the building blocks for hiring the right people and developing them once they join.