Word sprint — stitching Day 2 to Day 1
Day 2 opened with an activity the trainer picked up in Australia: the word sprint. Teams, one big sheet of paper, a tight time limit, and one instruction — write down as many words as you can remember from yesterday, and make them unique enough that the other groups don't have them. Then each group reads out its list; if another team has the same word, everyone strikes it off, and only the unique survivors score. Our sheets filled up with TNA, andragogy, behaviourism, congruence, forgetting curve, 70:20:10 — an entire day compressed back out of memory under time pressure. Then she stepped out of the game and did what she always does — named the mechanism: "When you want to energize, there are many ways to do it. But the main objective is to connect with the previous session." An opener should not just wake the room up; it should stitch today to yesterday, because the sessions are a chain, not beads. She promised a different connecting activity every morning of the five days — a live catalogue for us to steal from.
Design starts with must-haves, not ideas
Module 3 is training design — the D in ADDIE, the stage the course itself now enters. The trainer's way in was a car: before anyone designs a car, there are must-haves. Dimensions. Ergonomics. Left-hand drive or right? Asian market or European? Built for terrain or for speed? "Kalau you tak ada ni, you tak boleh design." No designer starts sketching until the must-haves are on the table. And the deeper point, carried straight over from yesterday's TNA module: the design cannot start from your own taste. "Kita tak boleh kata the design comes from my idea — because from your idea, perhaps it's not helping the performance problem." The gap analysis and the competency checklist it produced are the basis; the workbook draws it as a straight line — training needs analysis → training solution → training design. "Bukan kita plug, plug, plug" — the pieces are not bolted on because they look good, they are pulled through from the needs of the people, exactly like design thinking. I felt this one land: I have designed courses from what excited me. Rasa-rasa in a nicer outfit.
The five must-haves of a training design
So what are the must-haves for a course? The trainer gave four cores: you must have learning outcomes, and know how to write them. You must know how to sequence your content. You must know which methods you will use to deliver — "so many methods are there." And you must know what resources you need. Then she added the one that outranks decoration: assessment. "In your course design, this part must happen. Yang lain-lain semua tak apa, cantik saja — tetapi this one must." A course can be gorgeous and still be unverifiable. The assessment is what turns a nice experience into evidence that the gap closed — which, given yesterday's modules, is the entire point of the course existing.
Competency-based everything
The workbook's definition: Competency Based Training (CBT) is training designed and developed around the competency standards identified for a specific job, so that employee development is directly tied to job performance. The trainer's definition was better: "You masuk kelas, you tak tahu buat kek. You keluar kelas, you tahu buat kek. You masuk kelas, you tak tahu overhaul engine. You keluar kelas, you tahu overhaul engine." Entry state, exit state, and the training is whatever legitimately moves you between them. All three schools of learning theory from Day 1 live inside it — behaviourism, cognitivism, constructivism — but the proportions flip: CBT is 70–80% practical and 20–30% theory; university is the reverse. My margin note spells out the world this belongs to: TVET — Technical, Vocational, Education, Training. And competency-based is a family, not one thing — my note lists training, assessment, interview. Competency-based assessment: you cannot assess knowledge alone, you must make the person do it — and there is no fail. "Kompetensi assessment tak ada fail. You fail sebab tak cukup practice" — you are not yet competent, and with practice you will be. It also means free entry, free exit: learn anywhere, and when you are ready, come and be assessed — no sitting through four years to certify a skill you already have. Competency-based interview: the same outcome-orientation applied to hiring — don't say what you did, quantify it. "I have developed standards" is noise; "I have developed fifty-three industry standards" is evidence. Her footnote on why some cultures are so good at this: German family names. Schumacher — shoemaker. Müller — miller. Zimmermann — carpenter. Koch — cook. Whole families named after their vocation, because "nama dia tu adalah anugerah daripada Tuhan" — the craft was a gift from God, and they were proud enough of the skill to become it. A culture that names people after competencies will never confuse a certificate with one.
Output vs outcome — the sugarcane stall
The distinction that anchored the whole morning came from a sugarcane juice stall. The trainer described her regular air tebu auntie: what she measures when the juice comes out is not how much — it is the clarity of the juice, whether there is habuk floating in it, and on the other side of the press, whether the husk comes out properly dry and broken. "When you talk about outcome, it is the clarity and the quality of the juice. When you talk about output, it is the quantity of the juice and the quantity of the husk." Applied to education: output is the number of students who graduate; outcome is the quality of the people who go out. And so a learning outcome is the quality of the learning that walks out of the room — what the student is able to demonstrate at the end, not how many hours were delivered or how many heads were counted. Every training report I have ever seen leads with output. The auntie measures better than most L&D departments.
Case Study
auditing my DJC AI course against CBT
The cake line is an uncomfortable mirror for my own DJC AI course, so I audited it honestly against today's standard. Entry and exit states: never defined. The course promises topics (agents, automation, prompting), not competencies. What would CBT look like? A competency standard first: "masuk tak boleh bina AI automation, keluar boleh" — at the end of the course, the participant can build and deploy a working automation for one real task in their own business, unaided. That sentence immediately restructures everything downstream, exactly as the five must-haves predict: the outcome defines the assessment (they build one, live — not a feedback form), the assessment defines the sequence (each module ends with a piece of their automation working), and the 70:30 rule flips my ratio — currently I talk 70% and they build 30%, which is a university lecture wearing a workshop's clothes. The no-fail principle is the most useful import: a participant who doesn't finish their automation isn't a failed student, they are not yet competent — so the course needs a return path (office hours, a second assessment window) instead of ending at the last session. And the competency-based interview lesson applies to my own marketing: "learn AI for business" is noise. "Participants have shipped 40+ working automations" — quantified, verifiable — is the fifty-three-standards sentence. I don't have that number yet, which is itself the finding: I never designed the course to produce it.
Reflections
Day 2 connects backwards cleanly: the whistle cartoon said delivery isn't learning; TNA said the gap defines the need; today says the design must be built from that gap, with five must-haves, and measured as outcome, not output. The sentence I am keeping is the trainer's simplest one — masuk tak tahu, keluar tahu. If I cannot name what a participant can do when they walk out that they could not do when they walked in, I have not designed a course; I have scheduled a talk.