Method vs approach — and the spectrum
First a vocabulary correction: method and approach are not the same thing — "satu adalah kaedah, satu adalah pendekatan." A method is a concrete activity: lecture, demonstration, case study, simulation, discussion. An approach is the philosophy the methods serve — and the modern one is student-centred learning. Her sketch of why: "dulu, cikgu adalah source of information. Tetapi sekarang, anak murid punya source of information maybe sama dengan cikgu punya." When the learner can google what the teacher knows, the teacher's monopoly is over, and the design question changes from what do I tell them to what do they do. Then she drew a line on the whiteboard — teacher at one end, student at the other — and made us place each method on it. Lecture and demonstration sit at the teacher end: the trainer prepares, the trainer performs. Case study sits toward the student end — "teacher prepare case study, yang jawab case study student." Simulation further still. Discussion floats near the middle depending on how much the trainer steers. No method is banned; the point is to know where on the line you are standing at every moment of your course, and whether the outcome you wrote this morning is best served from there.
Selecting a method — and the preference trap
The selection criteria mirror content selection — the LO first, always — plus the practical ones: time (a demonstration eats far more clock than a lecturette on the same point), types of learners, learning styles (a room full of activists will mutiny during a two-hour lecture; reflectors need pauses the practical-only trainer never gives), variety of activities, and availability of resources. Resources got a sharp refinement born of obvious experience: available is not enough — functional. "Bukan sahaja availability, functional pun kena ada." The simulator exists but the battery is dead; the meter exists but was never calibrated, so its readings are wrong. Checking that the equipment works is part of method selection, not part of the morning-of panic. And then the criterion she put last on purpose: trainer's preference. "Tapi ini yang selalunya jadi. Kalau trainer tu suka lecture, lecture saja habis. Kalau dia suka demonstration, demonstration saja." The trainer teaches the way the trainer likes to learn, the four learning styles in the room be damned — and the participants who needed reflection time leave hating the class and the teacher with it. "You don't be like that." It is Day 1's learning-styles lesson wearing its consequences: preference is real, it just isn't a criterion.
Five common methods, one mind map each
The workbook's common five: lecture, role play, demonstration, experiential learning, discussion. Rather than lecture us about them — the irony was clearly deliberate — she split the room into groups, made each group claim one method fast ("cepat-cepat pilih, wajib pilih satu"), and assigned the study format: a mind map, built to Tony Buzan's rules, presented after lunch. Our group drew lecture — the method I use most and have examined least. The mind map itself came with a mini-lecture on its inventor, delivered with real affection: Tony Buzan, "the world's leading author on the brain and learning," whose mind-mapping system she credits with changing the lives of over 250 million people. The rules are stricter than the colourful posters suggest, and each has a cognitive reason. Start with a central image, because the brain thinks radiantly, not in lists. Branches must be curved and tapered, never straight — "nature is curvilinear; straight lines are rigid, similar, and therefore boring." One word per branch: "if you put two words together, you've stuck them together with glue" — a single word radiates associations freely. The word should run the length of its branch so connected ideas sit close in space. Colour everywhere, because the research says colour and image improve recall. Images throughout — "the picture is worth a thousand words" — and the closing flourish: Leonardo did it, Darwin did it, Beethoven did it. "If you start to use images and associations, you will join the pantheon of the great geniuses." Traditional list-notes fail, in Buzan's account, because they have no associations: no association, no connection; no connection, no memory. The assignment structure was tight: five compulsory branches — advantages, limitations, guidelines, other interesting points, and use cases. Sources: the manual, Google, AI, or your own experience. It is, I notice, a perfectly-built activity by her own frameworks: the outcome is clear (analyse a training method — HOTS), the condition is set (Buzan's rules, five branches), the method is student-centred, and the trainer has not lectured about lecturing for even one minute.
The gallery walk — and the lecture, upgraded
After lunch the mind maps went up on the walls and we did a gallery walk: the posters numbered, the groups rotating station to station "macam caravan," the map's own authors staying behind to explain while everyone else took notes — advantages, limitations, guidelines. It is, again, her frameworks eating their own cooking: instead of five groups presenting to a seated room (a lecture about lectures), the room walked, asked, and wrote. Even the coffee break was designed — she pointed out afterwards that the food and the music outside were deliberately part of the learning experience. Then she stood in front of our lecture map and rebuilt the method from the floor up. Her definition kept the workbook's words — "a period of uninterrupted talk" — but her example was better: her mother. Come home late and you get one period of uninterrupted talk, no questions entertained. A sermon is a lecture; a briefing is a short one; a university lecture is a long one. The cartoon on the page — "No, you can't ask a question" — is only funny because it is accurate. The fix comes from Mel Silberman's Active Training school (his 101 Ways to Make Training Active is the book on the slide, and she urged us to hunt down the PDF): build interest, maximise understanding and retention, involve participants, reinforce the lecture. Reinforce got the sharpest gloss — reinforcement is retention, "so that you do not contribute to the statistics" — the forgetting-curve statistics from Day 1. And the discipline that makes it work is ruthless arithmetic: keep it short, moderate content. "Twelve minutes, four points. Three minutes, one point." Four points that land beat fifteen points machine-gunned at a sleeping room. How to inspire while you talk? My margin note has the whole toolkit in five words: inspire your audience — use stories. Storytelling, cara cakap, body language, voice tone.
Case Study
mind-mapping the lecture, my default method
Our group chose lecture, and mapping it honestly turned into an audit of my own defaults — because lecture is exactly what I reach for at DJC, and the spectrum exercise had already told me why: preference, not selection. The five branches, as we built them. Advantages: economical — one trainer, unlimited audience; efficient — the most content per hour of any method; control — sequence and time entirely in the trainer's hands; consistent — every batch hears the same thing. Limitations: one-way — no feedback loop, so the whistle problem from Day 1 in its purest form; passive — the audience's hands never move, which the forgetting curve punishes within the hour; style-blind — perfect for theorists, slow death for activists and pragmatists. Guidelines, the branch that changes my practice: keep each lecture block short — a lecturette, fifteen to twenty minutes, never the full hour; break it with questions or retrieval; pair every abstraction with a story or visual; and always follow with a method from the student end of the spectrum, because a lecture can open a loop but cannot close one. Use cases: large audiences, theory foundations, introductions and overviews, safety-critical content where the message must be exact and identical for everyone. Interesting points: it is the oldest method in the room and the most abused; it sits at the extreme teacher-centred end of the spectrum; and paired with Q&A or discussion it stops being a monologue and becomes a cycle. And one branch the assignment didn't require, added afterwards: stages. Every lecture, however short, runs the same arc — intro (hook the room, name the outcome), body (the content, in lecturette-sized chunks), recap (retrieval, not repetition), and Q&A (the feedback loop a pure lecture lacks). Mapping the stages makes the guidelines branch actionable: the lecturette rule lives in body, the questions rule lives in Q&A, and a lecture that skips recap hands the forgetting curve a head start. What the exercise actually taught me is in the Buzan constraints. Forced to one word per branch, you cannot hide behind sentences — economical, passive, lecturette are each a decision, not a description. And the five compulsory branches force the balance my own thinking skips: I would happily have filled a page with lecture's advantages; the limitations branch had to be dug out, and it is the one that matters. At DJC the ratio I promised myself in the lean-learning post — 20% content, 80% practice — now has a mechanism: lecture survives, but only in lecturette-sized rocks, each one followed immediately by the participants' hands on the tools.
Reflections
Two things travel forward from this session. First, the spectrum as a self-check: at any minute of any course I can ask where am I standing — and if the answer is "teacher end, again, for the third hour," that is my preference talking, not my design. Second, the meta-lesson in the assignment itself: she taught training methods by not using her own — the groups analysed, mapped, and will present; she curated. Two days in, the course keeps demonstrating itself, and the demonstration keeps being the deepest content in the room.