Experiential Learning Cycle
A four-phase learning model — do, review, theorise, test — where knowledge is built by transforming experience through reflection and application.
What is it?
In 1984, psychologist David Kolb proposed that real learning does not happen by passively absorbing information. Instead, knowledge is created through the transformation of experience.1 His experiential learning cycle describes four phases that a learner moves through: having an experience, reflecting on it, forming a theory, and testing that theory in practice. The cycle then repeats, with each iteration building deeper understanding.
Kolb’s model draws on the work of three foundational thinkers. John Dewey emphasised that learning requires active engagement, not just listening.2 Jean Piaget showed that people construct knowledge by interacting with their environment.2 Kurt Lewin, the gestalt psychologist, developed action-research cycles where practitioners alternate between doing and reflecting.2 Kolb synthesised these ideas into a single, practical framework.
The model works on two levels. The learning cycle describes the process — how anyone moves from experience to understanding. The learning styles describe preferences — which parts of the cycle different people gravitate toward.1 The cycle itself is well-supported by research and widely used. The learning styles, as we will see, are more controversial.
The central insight is that no single phase is sufficient on its own. You cannot learn to swim by reading about it (skipping experience). You cannot improve by repeating the same mistakes without reflection (skipping theorising). And a theory you never test remains untested speculation (skipping experimentation).3
In plain terms
The experiential learning cycle is like improving at a sport. You play a match (experience), review what went well and what did not (reflection), adjust your strategy or technique based on what you learned (theory), then play another match using the new approach (experiment). Each lap around the cycle makes you better — but skipping any step leaves a gap.
At a glance
The four phases of the cycle (click to expand)
graph LR CE[Concrete Experience] --> RO[Reflective Observation] RO --> AC[Abstract Conceptualisation] AC --> AE[Active Experimentation] AE --> CE style CE fill:#4a9ede,color:#fffKey: The cycle flows from doing (CE) to reviewing (RO) to theorising (AC) to testing (AE), then back to a new experience. You can enter at any phase, but effective learning requires completing all four.
How does it work?
Phase 1: Concrete experience — do it
The cycle begins with a direct, hands-on encounter. This could be a new experience or a familiar situation seen through fresh eyes. The point is engagement — not reading about something, but actually doing it or encountering it firsthand.1
The experience does not need to be dramatic. It could be writing your first lines of code, conducting a user interview, tasting an unfamiliar ingredient, or observing a team meeting that went poorly.
Think of it like...
Jumping into the pool rather than standing on the edge reading the instruction manual. You will swallow some water, but now you have something real to work with.
Example (click to expand)
A junior developer deploys code to a staging environment for the first time. The deployment fails with an error they have never seen before. This failure is the concrete experience — it is raw, unprocessed, and full of learning potential.
Phase 2: Reflective observation — review it
After the experience, the learner steps back and examines what happened. This is not passive reminiscing — it is deliberate analysis. What went well? What was surprising? What was confusing? How does this compare to what you expected?1
Reflection is where inconsistencies between experience and existing understanding become visible. These gaps are the raw material for learning.3
Think of it like...
Watching the replay of a match you just played. During the match you were reacting. Now you can pause, rewind, and see patterns you missed in the moment.
Example (click to expand)
The junior developer reads the error log carefully, talks to a colleague about what might have gone wrong, and writes down three things they notice: the error only appears in staging (not local), it references an environment variable they forgot to set, and the deployment script has a step they did not understand.
Phase 3: Abstract conceptualisation — theorise about it
From reflection, the learner forms or updates a mental model — a generalised principle, rule, or theory that explains what happened and predicts what will happen next.1 This is the phase where scattered observations become structured understanding.
Abstract conceptualisation connects specific experiences to broader conceptual knowledge. A single failed deployment becomes an understanding of why environment configuration matters and how staging environments differ from local environments.4
Think of it like...
Writing down the recipe after several attempts at cooking a dish. Your experiments have given you data; now you are turning that data into a repeatable framework.
Example (click to expand)
The developer formulates a principle: “Environment variables that exist locally may not exist in staging or production. Before deploying, I should verify that all required variables are configured for the target environment.” They also create a mental checklist of pre-deployment steps. This is a new piece of procedural knowledge — and it emerged from experience, not from a textbook.
Phase 4: Active experimentation — test it
The learner applies their new theory or mental model in practice. This is not repeating the original experience — it is deliberately testing whether the new understanding holds up in a real situation.1 The result becomes the concrete experience for the next cycle.
This phase is what transforms theoretical understanding into practical competence. It also generates new experiences that may challenge or refine the theory, keeping the cycle going.3
Think of it like...
Cooking the dish again using your new recipe, deliberately testing whether your adjustments actually improve the result.
Example (click to expand)
The developer prepares for their next deployment by checking all environment variables against the staging configuration first. The deployment succeeds. But they notice a new issue: the database migration ran but took much longer than expected. This becomes the concrete experience for their next learning cycle — this time about database performance.
Entry points and the spiral
Kolb emphasised that the cycle can be entered at any phase.1 Some learners naturally start with experience (jumping in), while others start with theory (reading first). Neither is wrong — the critical requirement is that all four phases are completed.3
Over time, the cycle forms a spiral rather than a flat loop. Each revolution deepens understanding, building more nuanced mental models. This aligns with Jerome Bruner’s concept of the spiral curriculum, where learners revisit the same topics at increasing levels of complexity and abstraction.5 The first time around the cycle, you grasp the basics. The fifth time, you see subtleties that were invisible before.
Concept to explore
This spiral pattern connects directly to constructivism — the idea that learners actively construct knowledge from experience rather than passively receiving it.
Kolb’s four learning styles
From the cycle, Kolb derived four learning styles based on which two adjacent phases a learner prefers:1
| Style | Preferred phases | Strengths | Example profile |
|---|---|---|---|
| Diverging | Experience + Reflection | Brainstorming, seeing multiple perspectives | Artists, counsellors |
| Assimilating | Reflection + Theory | Logical analysis, building models | Researchers, mathematicians |
| Converging | Theory + Experiment | Practical problem-solving, technical tasks | Engineers, technicians |
| Accommodating | Experiment + Experience | Hands-on action, adapting quickly | Entrepreneurs, salespeople |
A note on evidence
The four learning styles are less well-supported by research than the cycle itself. The idea that people have fixed learning “styles” has been widely criticised, and large-scale studies have found little evidence that matching instruction to a student’s preferred style improves outcomes.6 The cycle, however, remains a robust and useful model. Treat the styles as loose preferences, not fixed categories.
Why do we use it?
Key reasons
1. It explains how procedural knowledge is actually acquired. The cycle maps naturally to how people learn to do things: try, reflect, theorise, try again. This is the mechanism behind deliberate-practice and apprenticeship.3 2. It prevents common learning traps. Learners who only read (theory) never develop skills. Learners who only do (experience) repeat the same mistakes. The cycle insists on both.1 3. It provides a design tool for educators. Course designers can check whether their programme includes all four phases, ensuring that learning activities are complete rather than one-sided.4 4. It connects experience to understanding. The cycle gives structure to the intuitive sense that “we learn by doing” — specifying how doing becomes learning through reflection and conceptualisation.2
When do we use it?
- When designing a training programme, workshop, or bootcamp — ensuring all four phases are present
- When diagnosing why practice is not leading to improvement (typically: the reflection or conceptualisation phase is missing)
- When structuring iterative-development processes — each sprint or iteration is a mini learning cycle
- When mentoring or coaching someone through skill development
- When applying the scientific method — hypothesis, experiment, observation, revised hypothesis
- When learning any hands-on skill: coding, cooking, playing an instrument, public speaking
Rule of thumb
If you have been practising something repeatedly without improving, you are probably stuck in the “concrete experience” phase. Stop doing, start reflecting: what exactly is going wrong, and what would a different approach look like?
How can I think about it?
The scientific method analogy
The experiential learning cycle is essentially the scientific method applied to personal learning.
- Concrete experience = running an experiment and collecting data
- Reflective observation = examining the results and noting what was expected vs. what actually happened
- Abstract conceptualisation = updating your hypothesis or theory based on the evidence
- Active experimentation = designing the next experiment to test your updated theory
A scientist who only runs experiments without analysing results learns nothing. A theorist who never tests ideas against reality stays in the realm of speculation. The power is in the complete cycle.
The apprenticeship analogy
Traditional apprenticeships are the experiential learning cycle in its purest form.
- Concrete experience = the apprentice attempts a task under the master’s supervision (forging a hinge, baking a loaf)
- Reflective observation = the master and apprentice review the result together: “See how the metal warped here? That was because…”
- Abstract conceptualisation = the apprentice forms a principle: “If I heat the metal too quickly, it warps. Slower heating gives more control.”
- Active experimentation = the apprentice tries again with the new understanding, and the cycle repeats
After hundreds of cycles, the apprentice becomes a master — not because they read a book, but because each cycle refined their procedural and metacognitive knowledge through direct experience.
Concepts to explore next
| Concept | What it covers | Status |
|---|---|---|
| constructivism | The learning theory that knowledge is actively constructed, not passively received | complete |
| deliberate-practice | Structured, feedback-driven practice designed to push beyond current ability | stub |
| iterative-development | Building software (and other systems) in repeated cycles of design, build, test, refine | complete |
Some cards may not exist yet
A broken link is a placeholder for future learning, not an error.
Check your understanding
Test yourself (click to expand)
- Explain why all four phases of the cycle are necessary. What happens when each individual phase is skipped?
- Name the four phases in order and describe what the learner does in each one.
- Distinguish between reflective observation and abstract conceptualisation. Why are they separate phases rather than one step?
- Interpret this scenario: a team runs weekly retrospectives after each sprint but never changes their process based on the discussions. Which phase of the cycle are they skipping, and what is the consequence?
- Connect this concept to knowledge-types: which of the four knowledge types does the experiential learning cycle primarily develop, and why is it less effective for factual knowledge?
Where this concept fits
Position in the knowledge graph
graph TD LP[Learning Paradigms] --> KT[Knowledge Types] KT --> ELC[Experiential Learning Cycle] ELC -.-> CON[Constructivism] ELC -.-> DP[Deliberate Practice] ELC -.-> ID[Iterative Development] style ELC fill:#4a9ede,color:#fffRelated concepts:
- constructivism — the broader theory that knowledge is constructed through interaction with the environment, which the cycle operationalises
- deliberate-practice — a complementary framework for structured skill development that benefits from the reflection and theorising phases
- iterative-development — the software development practice that mirrors the cycle’s structure of build, review, learn, improve
Sources
Further reading
Resources
- Kolb’s Learning Styles and Experiential Learning Cycle (Simply Psychology) — Thorough, accessible overview with diagrams and educational implications
- Kolb’s Experiential Learning Cycle: A Complete Guide (Growth Engineering) — Practical guide with emphasis on workplace and training applications
- Kolb’s Learning Cycle: 4 Stages (Structural Learning) — Clear breakdown with classroom application strategies
- The Four Stage Learning Cycle by David Kolb (The Training Thinking) — Concise explanation with focus on the spiral nature of repeated cycles
- Bruner’s Spiral Curriculum (Helpful Professor) — The related concept of revisiting topics at increasing depth, which complements Kolb’s cycle
Footnotes
-
Kolb, D. A. (1984). Experiential Learning: Experience as the Source of Learning and Development. Prentice-Hall. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9
-
Wikipedia (2025). Kolb’s Experiential Learning. Wikipedia. ↩ ↩2 ↩3 ↩4
-
McLeod, S. A. (2025). Kolb’s Learning Styles and Experiential Learning Cycle. Simply Psychology. ↩ ↩2 ↩3 ↩4 ↩5
-
Cloke, H. (2024). Kolb’s Experiential Learning Cycle: A Complete Guide. Growth Engineering. ↩ ↩2
-
Drew, C. (2024). Bruner’s Spiral Curriculum — The 3 Key Principles. Helpful Professor. ↩
-
Ryder, M. & Downs, C. (2022). Rethinking Reflective Practice: John Boyd’s OODA Loop as an Alternative to Kolb. The International Journal of Management Education, 20(3), 100703. ↩
