CDLA · Module 5 — Interaction design for transfer

Branch maps for architects

Decision nodes, preferred paths, and failure teaching — storyboard before Studio build.

About 16 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.

What this lesson covers

  1. 01

    Map decisions, not plot twists

    A branch map is a row per decision node: stakeholder pressure, 2–4 options, preferred path flag for SME review, and feedback text for wrong moves. Architects deliver this before producers open Studio — CEPD Module 4 builds from your map. Messick’s authentic assessment lens: branches must resemble the criterion situation, not trick questions.

  2. 02

    One node on the map

    1 · Pressure: Name the stakeholder or time pressure in one sentence.

    2 · Options: Write 2–4 parallel choices a real performer would face.

    3 · Preferred: Flag the SME-signed path — producers do not invent it in Studio.

    4 · Teach-on-fail: Each wrong move names the gap (knowledge vs environment).