CDLA · Module 5 — Interaction design for transfer
Activate, attempt, feedback, a harder instance, then a plan for work. The loop is specified in the storyboard, not left to the developer.
About 18 min
Practice in the lesson player
Sorting, matching, quizzes, and the module gate stay behind a free account so scored answers are not public. The teaching notes below are the same cited curriculum.
01
Architects specify loops: the learner attempts a case, feedback names the gap (consequence first, then the rule), and a new case follows with something changed. One correct answer is not mastery. Retrieval and application across varied cases is.
02
Field | Example
Decision | Approve, reject or escalate a refund above policy
Case 1 | Loyal customer, SAR 600, receipt present
Case 2 (varies) | New customer, SAR 600, no receipt, angry
Case 3 (varies) | SAR 1,400, manager claimed to have approved by phone
Advance rule | Two correct in a row, or three attempts then the expert path
Feedback style | Consequence, rule, link to job aid
03
You do not need an adaptive engine to adapt. Simple rules in the storyboard do most of the work: a learner who gets the first two cases right skips to the hardest case; a learner who misses twice gets a worked example before the next attempt; confident errors (wrong answer, high confidence) trigger a short explanation before moving on. These rules apply the expertise reversal and feedback research directly, and most authoring tools, including Studio, can implement them with variables and branching.
04
Fill the loop table from slide 3 for your highest-risk decision: three cases that vary in the ways real cases vary, an advance rule and a feedback style. Add it to your branch map.