Kolb Cycle Learning Sheet

Take one experience that did not go as planned, work through the four stages of the learning cycle in order, and leave with an experiment booked for the next real occasion. Come back after it to close the loop.

Mixed research: Kolb's cycle (Kolb, 1984) is one of the most used models in management education, but its logic has been criticized and revised (Bergsteiner, Avery & Neumann, 2010; Morris, 2020). The learning styles idea often attached to it is not used here. The time boxes are rules of thumb.

Use it when:

• A presentation, negotiation, meeting or decision went worse (or better) than expected and a similar one is coming.
• You keep hearing the same feedback and want to change one behavior on purpose.
• You want to try a new approach and learn from it, not just hope it works.

Skip it when:

• You want to review a whole project or month: use 1.11 Reflection Cycle Template.
• The episode was emotionally charged and you need to work through feelings first: use 1.13 Gibbs Deep Reflection Template.

Kolb's experiential learning cycle says that experience turns into learning through a loop: a concrete experience, reflective observation, abstract conceptualization and active experimentation (Kolb, 1984). Most people stop before the second half, before a principle is drawn and tested. The evidence is mixed. The cycle is widely taught, its logic has been criticized and revised, and the learning styles idea often bolted onto it has not held up. So this sheet uses the cycle as a working discipline, not settled theory.

What makes it worth using is the demand on the back half of the loop. Loose reflection tends to end in opinions about an event. The cycle insists on a principle you can carry elsewhere, then an experiment that puts the principle at risk.

So Step 1 wants facts before meaning. Step 2 gives your own behavior the same space as everyone else's. Step 3 pushes until the principle would survive new people and a new setting. Step 4 needs a situation, a date and a success test, and Step 5 closes the loop.

Describe the experience as a camera would have recorded it. No interpretation yet.

Strong answer: "I presented the new timetable proposal to the management group. Within five minutes the director asked twice why it mattered for passengers. They approved one of three changes and asked for a clearer case." Not "the presentation was a disaster."

What happened:

When, and in what context (what was at stake):

Who was involved (roles, not names):

Illustrative example: the role, the organization and all details are made up.

A team lead in the planning department of a regional public transport authority in Sweden presents a timetable change to the management group for the first time.

Step 1: Ten slides on route changes. The director interrupts twice: "Why does this matter for passengers?" One of three changes approved; the group asks for a clearer case.

Step 2: The team lead added detail each time they were challenged and spoke faster. The finance lead asked about cost three times with no clear answer. Surprise: the thorough preparation made it worse. Pattern: "too detailed" was also in last year's review.

Step 3: They prepared the talk they would want to hear, not the one the group needed. Principle: lead with the answer and the decision needed; detail only on request. Passes both portability tests.

Step 4: At the follow-up on 3 February: one opening slide with the proposal, passenger effect, cost and the decision needed; rehearse with a colleague who interrupts; answer the question asked before adding anything. Success: both changes discussed on their merits.

Step 5: Both approved. Next experiment: the same structure in a written board paper.