Kolbs Experiential Cycle
Kolbs Experiential Cycle
Kolbs is a write-up after one attempt that turns what happened into a changed next attempt. The four steps name that motion in ordinary words: what happened, what it meant, what rule that suggests, what changes next time. The product is a different next attempt, not a better understanding of the last one.
The four steps
Experience is one line: what was tried, and how it went. The data has to be real, and it has to be a process, not an outcome. “The test went badly” is a result; the experience is sitting the exam or preparing for it. The exception is when the reaction to the result is what needs understanding — then the reaction is the experience. The line is specific, isolated, targeted, and recent. A whole week or a whole subject cannot be reflected on at the depth the later steps need, so a big experience is split into its processes and run one at a time, starting with the process most likely to pay.
Reflection mines the process. It is not rumination: repetitive focus on feelings and causes without a next change predicts worse mood and blocks action. It also fails in two other directions. Run as a checklist, it collects too little. Run long, it can still restate feelings with the process untouched. The kind of information collected decides the kind of repair produced, so skewed input produces a confident repair to the wrong thing. A feeling — discomfort, anxiety, the sense that a step was harder than it should be — is often easier to recall than the process itself; the feeling is a marker to follow back, then the process is what gets examined. A fixed question set, answered in full including the questions that feel repetitive, blunts the pull to collect only what supports the story already held. The vault’s own Kolbs Template is that set.
Abstraction is an observational hypothesis: a short prediction read out of the reflection, probably not yet right. It is not pulled from what was already believed. If no pattern comes, the reflection was thin — go back and pad it rather than ramble here. When a cycle feels vague, one residue question from Red Teaming is enough: why did this happen, and what deeper condition made that possible? Repeat only until the answer is actionable. The first explanation is usually not the useful one.
Experimentation designs the next attempt from that hypothesis. “Try harder” changes nothing and is allowed once, the first time a problem is noticed; after that something actionable changes — environment, pacing, order, number of pieces, the trigger. A fourth failure is an experiment connected to nothing the abstraction found. One to three experiments, ideally one or two, because fixing one root issue commonly resolves several others. The exception is a one-off effortless change that stays fixed once made. When an experiment goes nowhere, the usual cause is upstream: the abstraction was not observational.
What a cycle is run on
A cycle needs a real attempt that produced data. The attempt need not be dramatic. It needs enough friction, emotion, result, or surprise to teach something. The first line of the write-up is what was tried and how it went; deliberately testing something expected to fail is a legitimate reason to run one.
| Worth a cycle | Weak as a cycle |
|---|---|
| A session that started slowly | Abstract planning with no attempt |
| A session that went better than expected | Venting with no next experiment |
| A technique that looked correct and did not work | Too many variables at once |
| A moment where a [[wiki/Concepts/The Shortcut Problem | shortcut]] appeared |
| A repeated failure mode | A long reflection where a quick note would do |
| A meaningful conversation | |
| A workout that revealed a bottleneck | |
| A language session where attention rose or collapsed | |
| An agent workflow that produced a useful or a bad result |
A failing established script, rather than a one-off attempt, is the subject of How to Unlearn Old or Bad Habits Efficiently. A session whose weak frame showed is a clean experience for Interleaving for Complex Problem Solving.
| Full cycle | Quick note |
|---|---|
| Emotional weight, repeated friction, or a real performance lesson | The lesson is obvious and the next experiment is already clear |
| Repeated shortcut; strong emotional reaction; technique failure; relationship repair or conflict | Minor logistical issue; simple reminder; one-off low-stakes slip; obvious next action |
End of the day where possible, at least twice a week, and never a week compressed into one cycle, because each session is a separate experience with its own variables.
Experience: a language session, attention held for twenty minutes and then collapsed.
Reflection: collapse arrived when the next item needed a word that would not come; frustration, then a switch to easier items.
Abstraction: switching down protects the session clock and starves the retrieval that would have rebuilt the missing word.
Experiment: on the next miss, stay with the item for one more retrieval before switching.
Next cycle's experience: that stay-with-it attempt, and how it went.A cycle cannot be run on every problem every day, and a beginner has dozens of candidate directions, so something has to choose which problem gets the thirty minutes. Marginal Gains chooses the improvement that is worth making next; this page runs the cycle that makes it. One is the road, the other the vehicle. Together they do four jobs: Marginal Gains stops improvement from being random and names the target; Kolbs stops reflection from staying passive and improves the method. The few areas with first claim on time are the ones where a cycle is worth its half hour — Priority 0+1. The page lives with Self-Management and is used as the Self-Regulation loop.
The arrow back
A single write-up is not the unit. The loop is. The experiment of this cycle is the experience of the next; they are the same object seen twice. The abstraction is a hypothesis, the experiment is its test, and the first test usually does not fix the problem. Several cycles are normally needed to see the problem’s nature, and more to repair it. The same hypothesis is retested until the problem goes away. The stopping rule is the problem, not a cycle count.
The recognisable failure is diligent, daily, and stuck: a fresh problem every cycle, technique correct, nothing compounding. The next experiment is also cleaner feedback, but only if it comes back as tomorrow’s experience. A typed, kept log makes the previous cycle findable, which is the precondition for the arrow. The Kolbs Template already asks whether this cycle reflects an experiment from a previous one.
Where cycles go thin
An experiment that goes nowhere usually points upstream to an abstraction that was not observational. A limit at any step caps every step after it.
| Step | What thin looks like | What changes it |
|---|---|---|
| Experience | A week in one sentence; an outcome in place of a process; reflection with no attempt behind it | One recent process, highest-yield first |
| Reflection | Circling feelings with the next attempt unchanged; a checklist; long and still only feelings | Mine the process, then force a hypothesis and an experiment |
| Abstraction | Observations with no principle; a theoretical guess; more reflection wearing the heading | Name the pattern the record shows, or go back and pad the reflection |
| Experimentation | No next action; “try harder” a second time; too many experiments; unconnected to the findings | One or two actionable changes drawn from the hypothesis |
Time, and what to expect
The cycle leans on self-awareness at every step, which is self-limiting: limited introspection limits what can be seen as worth reflecting on. Reflecting feels tedious or confusing when that awareness is still thin. Awareness deepens over weeks of repeated sessions, on the order of four to twelve, not in one sitting. That skill is Metacognition: The Control Layer.
Early cycles can take hours. With practice they settle around fifteen to twenty minutes. Cap at thirty minutes, leave steps unfinished, and let speed arrive. A capped cycle done consistently beats an exhaustive one done rarely. The cap is practical. It is a floor-holder on that curve, not a verdict.
It should feel like turning a messy experience into a better next experiment: what happened, then why, then what changes. Four signs a cycle is working: the experience gets more specific as it is written; emotions and triggers become usable information; a pattern appears rather than an event; the next experiment is smaller and clearer than the problem that started it. The first cycles diagnose rather than fix. Several are normally needed before a repair lands.
The quit signal is felt: the write-up has become journaling when it records the experience and does not change the next attempt. Where insight into one’s own process is still thin, the write-up runs shallow and produces little. The repair is the metacognition build, not more cycles.
The four steps are a discipline for practice, not a claim that minds move through four boxes in order. The cycle is criticised as too linear and thin on the social side.
What the write-up is training
After long practice the loop starts running inside the experience, with the noticing happening live and the write-up thinning out. What accumulates across cycles is a clearer diagnosis, a smaller next experiment, better awareness of mistakes and conditions, a more accurate model of cause and effect, and a practical next action. The write-up is scaffolding for a way of noticing. The end state is running the loop with no write-up at all.
Open Questions
How many cycles on one hypothesis before the hypothesis itself is the thing to change.
Related
- Upgrading Your Dimensions — dimensions as the things a run of cycles is aimed at upgrading.
- Mindset — a mindset trains on the same loop: name the problem it answers, meet that problem often enough to practise, and arrange the encounter deliberately when it is rare.
Sources
- Kolb, D. A. 1984. Experiential Learning: Experience as the Source of Learning and Development. Prentice-Hall. Also 2015 2nd ed. Four-stage cycle this version is built on.
- Kolb, D. A. & Fry, R. 1975. Earlier statement of the cycle.
- Nolen-Hoeksema, S. 1991; 2000. Journal of Abnormal Psychology. Rumination as repetitive focus on symptoms and causes without problem-solving.
- Pashler, H., McDaniel, M., Rohrer, D. & Bjork, R. 2008. Psychological Science in the Public Interest 9(3), 105–119. With Coffield, F., Moseley, D., Hall, E. & Ecclestone, K. 2004, and Newton, P. M. & Miah, M. 2017, Frontiers in Psychology 8:444. Why a learning-styles half is not taught here.
- Bergsteiner, H., Avery, G. C. & Neumann, R. 2010. Studies in Continuing Education 32(1), 29–46. With Jarvis, P. 1987, and Holman, D., Pavlica, K. & Thorpe, R. 1997, Management Learning 28(2). Linearity and social-context critiques.
- Schenck, J. & Cruickshank, J. 2015. Journal of Experiential Education 38(1). Update the cycle without the styles.
- Schön, D. A. 1983. The Reflective Practitioner. Reflection-in-action as the live end state.
- Gibbs, G. 1988. Learning by Doing. Six-stage teaching cousin.