Just sentences — with a measurement inside
The first must-have of training design gets its own deep dive. The workbook's definition: learning outcomes are statements of what a learner is expected to know, understand and/or be able to demonstrate at the end of a period of learning — in the Malay half of the slide, "jangkaan apa yang pelajar tahu atau boleh buat di akhir kursus." The trainer stripped it further: "Dia hanyalah ayat" — they are only sentences. Sentences that communicate to everyone — trainer, company, participant — what is expected when it ends. The technician reading them knows what to prepare; the HR manager reading them knows what she is buying. Two disciplines hide inside the sentence. It starts at the end — "kita tak pernah measure awal-awal, kita measure at the end" — which is why every outcome opens with the same clause: at the end of the course / session / programme, learners will be able to. And it must be measurable. My margin notes from this page are all about that: measurable — what is the measurement? Need measurement techniques. She reached back to the morning's sugarcane stall: the auntie has measuring tools — clarity of the juice, dryness of the husk. An outcome you cannot measure the same way is decoration, not an outcome. The workbook wheel for this module runs definition, rationale, domains, characteristics, components — and the rationale is exactly the sugarcane point: outcomes are the standard you will later translate into sequence, methods, resources and assessment.
Terminal and enabling — the pizza decomposition
My margin note next to the definition slide reads terminal / enabling — there are two kinds of outcome, and confusing them wrecks course designs. The terminal outcome is the trainer's objective, the sentence the course exists for: repair a leaking pipe. But the learner walks away with far more, because to repair a leaking pipe, Faiz — our course's recurring everyman — must know the types of pipe, the types of leakage, the repair materials, the cutting procedure. "Faiz dapat lebih banyak outcome. And these are all enabling." Her second example was food, as usual: at the end of the course, the students will be able to make pizza — terminal. The enabling outcomes are the must-haves on the way there: dough, sauce, topping, baking. And note what is not on the list — the equipment. "Buat doh, pakai KitchenAid ke, Kenwood ke — tak kisah. Kena bakar — oven ke, arang ke — tak kisah." The enabling outcome is baking, not owning an oven brand. This decomposition is also a product map: once you can see the enabling outcomes, you can design the next course horizontally (pizza → bun, near-identical enabling structure, different pillar) or stack vertically into an advanced course — and you can tell a student holding a basic certificate honestly: skip this one, take the advanced.
K, S, A — and the colour test
The examples page is a list of finished outcomes, and in class it became a decoding exercise — the slide printed them in three colours, and we had to say which was which. Identify five key provisions of the Clean Air Act; distinguish conduction from convection; determine nutrients for a soil — black, and my margin bracket says Knowledge (K). Manoeuvre a car into a tight parallel parking spot; create a new gymnastic routine; repair a leaking pipe — blue: Skill (S). Question new ideals in order to fully understand them; collaborate as a member of a production team; adhere to workshop safety requirements — red: Attitude (A). So when you write learning outcomes, the focus is K, S, A — every outcome belongs to one of the three, and a complete course usually needs all three represented. Someone asked whether the order is sacred: can a course lead with S, or with A? Her answer was pragmatic — it depends what the training is for. "Kalau you punya training untuk skills, you letaklah S dulu. Tak ada masalah." A motivation programme leads with A. The taxonomy is a checklist, not a liturgy.
Three domains — Head, Hands, Heart
Behind K-S-A sits the formal classification: the cognitive domain (recall or recognition of specific facts, procedural patterns and concepts), the psychomotor domain (physical movement, coordination, use of the motor-skill areas) and the affective domain (feelings, emotions, values, appreciation, motivations, attitudes). The trainer was strict about vocabulary: "Ada tiga domain, bukan kategori. Ini bahasa ilmiah akademik." Domains, not categories — and it is affective, not effective. For audiences who glaze over at taxonomy, she offered the 3H translation: head, hands, heart. Cognitive she tied back to Day 1's memory work: you can only recall what has actually been organised into long-term memory — no assimilation, nothing to retrieve. For psychomotor she told the best story of the morning. As a teenager in Penang she was a serious speed roller-skater — buses to the rink, skates over her shoulder. Decades later, in Germany, relatives took her to an empty ice rink. She had never ice-skated in her life; everyone positioned themselves to catch her. She stood up, held the ring, let go — and skated. Round the whole rink, music playing, feeling briefly like the queen of the ice — on nothing but roller-skating muscle memory from her school days. The body had kept what the calendar should have erased. Her other proof: a former Swan Lake ballerina with Alzheimer's who, when the music plays, still dances the movements. "You bring it to the grave." Which led to her self-description I want on a poster: "I am a fundamentalist. Get your fundamentals correct. Be grounded." Skills built properly on basics become permanent in a way content never does.
The tricky one — writing the affective domain
The affective domain got the longest treatment, because it is the easiest to write badly. Her example was parenting: telling your child "be good at school" communicates nothing — the child sits alone, talks to nobody, and reports back "I was being good." My margin note: be specific when teaching your children. Say thank you when you receive something — that is specific, observable, and teaches the value underneath. Same with appreciation between adults: "Emotions have to be translated into actions" — my note again — because sincerity that never becomes visible action is indistinguishable from its absence. She detoured through love languages — some people receive appreciation as gifts, some as time, some as presence — the point being that even feelings land through observable behaviour. The training translation: write affective outcomes so that people can see them. Not "appreciate workplace safety" — apply PPE; comply with DOSH requirements. The attitude is invisible; the compliance is not. This is the same move the whistle cartoon made on Day 1 — if you cannot observe it, you cannot claim it happened.
Case Study
rewriting the check-in training's outcomes
In the TNA case study I designed a front-desk check-in training for Mana Mana; today's session exposes that I never wrote its outcomes. So, applying the full toolkit: Terminal outcome, measurement included: at the end of the session, front-desk staff will be able to complete a standard check-in within eight minutes, to checklist standard, unassisted. That is the sentence the whole course serves — and the eight minutes and the checklist are the sugarcane measurements. Enabling outcomes, K-S-A tagged. K: state the deposit policy and its three exceptions correctly (tested verbally — the TNA showed this genuinely varies by person). S: process a test booking end-to-end in the PMS, including the OTA edge case (observed on a mock guest). A — written so it can be seen, per today's rule: greet every arriving guest within thirty seconds, by name where the booking allows it. Not "deliver warm hospitality" — nobody can measure warm. The decomposition also cleanly separates what training cannot fix: the slow PMS terminal is equipment, and as the pizza example established, equipment is not an enabling outcome — it is the non-training solution from the TNA, already on the capex list. What surprised me is how the outcome sentences write the assessment for free: the eight-minute mock check-in is the test, the verbal deposit quiz is the test, the observed greeting is the test. Yesterday's lesson said assessment must happen; today's lesson makes it nearly automatic — if the outcomes are written right, the assessment is just the outcomes read aloud with a stopwatch.
Reflections
Two days in, the course's architecture is showing: learning is a change in behaviour (Day 1), the gap defines whether training should exist (TNA), and the learning outcome is the sentence that promises exactly which behaviour will change and how we will measure it. Head, hands, heart is the version I will actually remember — and the affective rule generalises beyond training: any value I care about, at work or with family, only exists once it is translated into something observable. Everything else is rasa-rasa.