CDLA · Module 5 — Interaction design for transfer

Branch maps for architects

Decision nodes, preferred paths and failure teaching, signed before anyone builds.

About 20 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 has one row per decision node: the situation and pressure, two to four options, the preferred path flagged for SME review, the consequence of each option, and feedback text. Architects deliver the map before production opens the authoring tool. The CEPD program builds from this map.

  2. 02

    One node, complete

    Field | Entry

    Situation | Supervisor on the phone: "Skip the isolation, the line has to restart in ten minutes."

    Option A (preferred) | Refuse politely, explain the risk, offer the fastest safe route, inform the shift manager

    Option B | Comply this once and log it

    Option C | Refuse and hang up

    Consequence A | Line restarts 25 minutes late; no incident; shift manager supports the call

    Consequence B | Hand injury during restart; investigation finds the log entry

    Consequence C | Supervisor escalates a complaint; the safety point is lost in the conflict

    Signer | Site safety lead

  3. 03

    Where good wrong options come from

    The quality of a branch depends on its wrong options. Silly options teach nothing and make the right answer obvious. Take wrong options from evidence: QA findings, incident reports, complaint logs, the novice errors you found in the CTA interviews, and what new staff say they would do. A good wrong option is something a reasonable person under pressure would choose. If your SME says "nobody would do that", either it is a bad option or the SME is wrong; check the incident log.

  4. 04

    Map three nodes

    Write three complete nodes for your highest-risk decision using the template on slide 2. Source every wrong option from evidence and note where it came from. Send the map to your SME for the preferred-path review. This is your module artifact's core.