Learning that starts in the body
The definition on the page earns its length: experiential learning is learning that takes place when a person engages in some activity, reflects on it, gains some useful awareness from the reflection, and applies the results to work through a change of behavior. Four clauses, four checkpoints — and the trainer stressed that losing any one of them collapses the method. Activity without reflection is recreation. Reflection without application is a diary. And the finish line is the same one Day 1 drew under the whole course: a change of behaviour, or it didn't happen. This is the method behind every team-building retreat ever booked — and the reason most of them evaporate by Monday is that organisations buy the activity and skip the cycle. The rope course is not the learning; the rope course is the raw material. What the workbook adds is the machinery that processes the raw material: five stages, run in order, none skippable.
Five stages — around the cycle after the ropes
The workbook's wheel is the five-stage cycle that training houses took from Pfeiffer and Jones's handbooks: experiencing, publishing, processing, generalizing, applying — stitched together by the three questions the field owes to Terry Borton: What? So What? Now What? The trainer taught it the only sensible way — by replaying an outdoor team-building she had run, stage by stage. Experiencing is the activity itself, and the crucial detail is its timing: the learning conversation happens immediately, "masa penat-penat tu" — while the sweat is still drying, she sits everyone down. Publishing: "dia tanya — how do you feel?" And because "masa tu kita full emotions, kita jawab" — the reactions are honest because they haven't been edited yet. One person shares an observation — I noticed this person helping me — and the sharing itself is the stage: reactions and observations, into the open. Processing is where the facilitator starts weaving: you felt that; he also felt that — "so everybody is feeling the same thing actually." Patterns and dynamics, named. Generalizing lifts the pattern out of the mud: "this is what happens when you are put in a situation you don't know and you try to solve problems as a group" — a real-world principle, minted from an afternoon. And applying closes Borton's third question: "from this experience, what can you do in the working environment? How do you want to apply it to make your team better?" Written out like that, the cycle is exactly the role-play debrief scaled up — which is why the two methods share the same secret-keeping rule: the LO stays in the facilitator's pocket until the debrief needs it.
Facilitating ELA — ask everything, answer nothing
The guidelines page for facilitating an ELA — experiential learning activity — reads like a monastic rule, and the trainer performed its hardest clause live. Resist temptations to give answers; ask questions only. "Lepas soal — pause." Then she acted out the trainer whose "mulut dah gatal nak bagi jawapan" — the itch every expert knows, the answer fully formed and pressing against the teeth. "Stop. Stop." The pause after a question is where the participants' thinking happens; fill it, and you have quietly taken the learning back. The other clauses orbit the same humility. Have faith in people's ability to learn for themselves — "have faith that they can do. You can, you can." Facilitation to be light and subtle: the facilitator of an ELA is at their best nearly invisible, which connects straight back to the clown from the discussion module — "the task is difficult, so what you need to do is be a clown. Senyum, open your eyes, jangan tolong." Don't prejudge reactions — "tak boleh, tak boleh" — the same activity lands as triumph for one group and frustration for another, and both are usable raw material. Build confidence before addressing attitudes and behaviours — safety before surgery, the role-play rule again. Engage learners in meaningful debriefing, because the debrief is the factory floor. And accentuate the positives — which is the feedback formula, three-things-that-went-well first, now installed as a standing disposition.
Unconditional positive regard
My margin note on this page is three words that carry a whole philosophy: unconditional positive regards. The phrase is Carl Rogers's — the same Rogers whose congruence gave Day 1 its integrity lesson — and it is the founding condition of his person-centred practice: the helper's acceptance of the person does not fluctuate with the person's performance. The trainer's translation into classroom terms was direct: "kita kena ada positive regard. Dia boleh buat. Kita tak boleh ada prejudgement. Kita kena treat semua sama." Every participant gets the same baseline of expectation and warmth — the slow one, the difficult one, the one who froze during the activity. It is the deepest of the eight guidelines because it is the one you cannot fake through technique: faith in people's ability to learn, refusing to prejudge, accentuating positives — all of them are unconditional positive regard wearing different work clothes. Rogers gets quoted twice in this course now, once for what the trainer must be (congruent — the same person inside and out) and once for how the trainer must see (everyone as capable, in advance, without conditions). Between those two, most of facilitation is already decided.
Case Study
the DJC lab, run around the full cycle
My DJC AI course already worships experience — the lean-learning post committed me to 20% content, 80% practice — but today exposes that my labs run one-fifth of the cycle. Participants build an AI assistant (experiencing), it works or it doesn't, and we move on. No publishing, no processing, no generalizing, and applying is a hopeful sentence in my closing slide. I bought the rope course and skipped the debrief, exactly like the team buildings I make fun of. The rebuilt lab, cycle-complete. Experiencing: the build mission as it stands — construct a working assistant for one of your real tasks, forty minutes, and I stop rescuing people. The guideline is ask-questions-only, so my new rule when someone's prompt fails is three questions before any answer — what did you expect, what did it return, where do those differ — with the pause held even when my mulut gatal. Publishing, immediately after, energy still high: everyone states one feeling and one observation from the build — "stuck then suddenly clear" is data, not chatter. Processing: I collect the observations on the board and hunt patterns with the room — every stuck moment traces to a vague instruction; every breakthrough came from adding an example. Generalizing, and this is the stage I have never once run: the room writes the principle, not me. Last cohort would have minted something like specific instructions beat clever ones — a real-world principle they own because they mined it. Applying: each participant names the workplace task they will point their assistant at this week, out loud, to a neighbour — Borton's Now What with a witness. And the meta-change: the lab's LO comes off my opening slide. It gets revealed at the debrief, after the generalizing, where it lands as confirmation instead of spoiler. The experiential methods keep their secret; from next cohort, so do I.
Reflections
The day's methods now sort themselves by where the learning lives. In lecture it lives in the trainer's sentences; in demonstration, in the trainer's hands; in discussion, between the participants; and in experiential learning it lives in the participants' own hides — the facilitator merely refuses to let it stay buried there unexamined. The five stages are really one instruction repeated: don't leave the experience raw. And the two Rogers threads — congruence for who I am in the room, unconditional positive regard for how I see who's in front of me — are quietly becoming the course's spine. The techniques change every module; the stance doesn't.