CDLA · Module 5 — Interaction design for transfer
Dialogue branch, mission interaction, simulation beat, or job aid — pick one primary pattern per action.
About 15 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
1 · Name the action: Observable verb from the action map — one row.
2 · Name the risk: What goes wrong if they skip or shortcut?
3 · Match pattern: Judgment → branch; sequence → mission; environment → job aid.
4 · Debrief: One sentence tie-back to policy or workflow — Merrill integration.
02
Name the action in one observable verb from the action map. Name the risk if the person skips or shortcuts it. Then match a single pattern: judgment under conversation becomes branching dialogue; a sequence that must be performed becomes a mission; something the person must look up while working becomes a searchable job aid. Applying a refund policy with empathy is a branch. Completing a safety checklist in order is a mission-style sequence. Finding the escalation path during a live call is pull, not another quiz. Debrief in one sentence that ties the attempt back to policy or workflow — Merrill’s integration, not a second lecture. Stacking a branch, a game, and a quiz on the same screen raises extraneous load without making the practice clearer. It does not create LTEM tier 7 evidence, and it does not replace SME review of the preferred path.
03
A pattern chosen because the template is free in the library is decoration. Write the failure first — unauthorized override, a skipped lock, a missed escalation — in one observable sentence. Then pick the single interaction that makes that failure visible: a branch for a judgment, a mission for a sequence, a job aid for a lookup. If you cannot name the failure, you are not ready to choose a slide type.