The LO is the nadi
After lunch the module moved from writing outcomes to using them, and the trainer opened with the strongest dependency claim of the course: "bila dah ada LO, LO ini jadi the nadi — the heartbeat of your program. You punya LO salah, semua salah." Get the outcome wrong and everything downstream — content, methods, assessment — inherits the error. She also planted a flag about where the craft lives: "ada orang yang fokus on delivery. Saya tak nak fokus on delivery. Saya nak fokus on the design." Delivery is the visible 10%; the art and the science are in the design. Then the hierarchy. Outcomes nest exactly the way content does: a training title breaks into modules, modules into submodules — and every level carries its own outcome. A programme learning outcome is measured years after graduation; a course learning outcome at the end of the course; a session learning outcome after every session — "learning outcome kena measure after every session." An eight-hour course splits into four sessions, so that day carries eight-ish session outcomes plus one course outcome above them. It sounds bureaucratic until you see what it buys: at every scale of the design, there is a sentence that says what must be true when this block ends — and therefore a way to know, immediately, whether the block worked.
Choosing content — five filters, all pointed at the LO
With the outcome as compass, content selection stops being taste. The workbook lists five criteria, and the trainer rephrased each one as a question aimed at the LO: significance — does this content support the outcome, or is it just interesting to me? Utility — is it useful to this audience? Validity — is the source valid, the act current, the standard the real one? Learnability — can they adopt and adapt it back at their workplace ("ingat: contextual and meaningful is coming already")? Feasibility — do I actually have the resources to deliver it? "I nak buat, equipment tak ada — tak bolehlah." Validity came with a working lecture on plagiarism, which I did not expect in a trainer course but makes complete sense: trainers assemble content for a living. The rules as she gave them: if you take a sentence word-for-word, cite it in the text — not just a reference list at the back. If you paraphrase, you still cite the source. "Kalau you letak source, dia tak ada masalah." And the meta-rule that saves you from most of it: if the content doesn't support your LO, tak payah ambil — don't take it. "Kenapa you nak ambil, sedangkan dia tak membantu?" Half of content bloat is material that was never for the learners in the first place.
The big rocks, the pebbles and the jar
For scope she retold the famous big-rocks story, deliberately re-purposed: a professor brings a jar and puts big rocks in until no more fit. Is the jar full? Yes, say the students. He pours in pebbles, which rattle into the gaps. Full? Some go quiet. Then sand. Then water. "Now the jar is full." Everyone uses this story for time management; she claims it for content development, and the mapping is exact. The big rocks are the must-haves — "the core that supports the learning outcome. Those are your big rocks." The pebbles are good-to-have: if they don't go in, "the rocks are already in — the students can achieve the outcome." Sand and water are nice-to-have. And the jar? The jar is the time. "You write your learning outcome based on how much time you have." Two hours of jar fits a fixed number of rocks, and no amount of enthusiasm changes the geometry. The failure mode is sequence: "some trainers focus on the water and the sand, so the big rocks cannot go in. Because the sequence is wrong." That is the training everyone has attended — a fun, story-filled first half, and a trainer sprinting through the actual syllabus at 4pm. My margin note: big ones first, then the smallers, and then the smallest. Sequence is very important. She even gave it a nutrition analogy: what enters your stomach first determines the sugar spike — vegetables before carbohydrates. Same meal, different order, different result.
Breadth, depth and seven ways to sequence
Scope has two dials — how deep and how broad — and both are set by the jar and the outcome, not by how much you know. The workbook's checks: usefulness of contents, content that caters to diverse abilities, enough time to cover, balance between domains. Her own example of the discipline: she could lecture on pedagogy for days, but for this room it is not significant, not relevant, not useful — so we get andragogy and she keeps the pedagogy to herself. Knowing what to leave out is the expertise. Then sequencing, seven patterns from the workbook wheel: job performance order (teach in the order the job is done — identify the problem, diagnose, rectify, test), simple to complex ("yang simple-simple ajar dulu"), known to unknown, most frequent to less, chronology, critical first, and logical sequence. Critical first is for safety: the thing that kills goes at the start, non-negotiable. And logic she delivered as a run of one-liners from her mathematics-lecturer past: "I teach algebra before I teach calculus — it's only logic. I teach integration before I teach Laplace transform — it's logic. You don't need rocket science." There was also a sly practical one: identify the question every audience always asks early, and sequence its answer near the front — so it stops being an interruption and becomes a landing.
Duration, group size and the name on the brochure
How long should a module take? The workbook's factors: learner type, complexity of the competency (information load), criticality (layering to form a learning block), and the type of activities — activities eat time, and higher taxonomy levels eat more: "kalau kita nak ajar dia justify, kita kena pastikan the LOTS dah settle dulu. So you take longer time." One operational gem: group sizes. Two people per group means too many groups to facilitate; more than five and "yang keenam akan jadi — they're sitting." Three to four is her working number, big enough to discuss, small enough that nobody can hide. Then naming, which turned out to be the most entertaining ten minutes of the day. A module name must be catchy, content-related, and sensitivity-checked — non-sensitive to race, culture, religion or language. Her collection of names that sell: a colleague's finance course renamed The Numbers That Tell a Story — "she teaches how to read management reports, but numbers that tell a story — interesting!" A high-voltage electrical safety module titled Touch Me and You Die, which nobody who reads it will ever forget. A tyre-structure course from a Continental trainer called Black Donut. A coal-industry one: The Black Rocks That Lighten Our Lives. My margin note kept two of them, which proves the technique works — the number that tells a story; touch me and you die. The catchy name is not decoration: it is the first line of the marketing, and the participant has decided how they feel about your course before the outline is read.
Case Study
re-packing the DJC AI course jar
My DJC AI course, audited against the jar. The course learning outcome (written this morning, ABCD-complete): participants construct a working AI assistant using common AI tools within an hour. So what are the big rocks? Prompting fundamentals, tool selection, the build itself, and testing against a real task. Those four directly produce the outcome — nothing else does. Now the honest inventory of what currently fills my jar: AI industry news, model comparisons, my favourite automation war stories, two live demos of things only I can operate. Against the five filters: the war stories fail significance (they support my credibility, not the LO), the model comparisons fail learnability (nobody adapts a benchmark table at work), and one demo fails feasibility on the participants' side — they cannot reproduce it without my accounts. It is sand and water, poured first because it is the fun part — the exact failure she described, laughing at 2pm, sprinting at 4.30pm. Re-packed: rocks first (the four above, in job performance order — the order you actually build an assistant in), pebbles next (a prompt-pattern library, error-recovery habits), sand only if the jar still has room (news, comparisons — probably a handout, which is where sand belongs). Sequence fixes: the question every DJC class asks in the first ten minutes — "will this replace my job?" — gets its answer moved from my closing remarks to the opening, where it stops being a background hum. And the name: the course is currently called something like AI for Business Productivity, which is a category, not a hook. Working candidates, sensitivity-checked: Masuk Tak Tahu, Keluar Boleh Buat — or, in the Touch Me and You Die register: Your 30-Minute Task, Done in 5. The numbers tell the story.
Reflections
The through-line of the day is dependency: the gap writes the outcome, the outcome chooses the rocks, the jar disciplines the rocks, and the sequence protects them. What the big-rocks story adds to yesterday's must-haves is the geometry — it is not enough to know what matters; the things that matter must physically go in first, because the sand does not politely wait its turn. I have been a sand-first trainer more often than I want to admit. The jar does not lie.