Kit 19 · Desk Zero · deliverable · designed and built by I Wayan Usada — instructional design portfolio
A text-based storyboard, written before any code: every scene is a decision with a consequence, not a slide. The plan below is the build contract — scene count, interaction logic, feedback placement and the debrief arc.
| # | Scene | On screen | The learner decides | Right path | Tempting path | Consequence shown |
|---|---|---|---|---|---|---|
| 1 | Email 1: the urgent imposter | 'URGENT' course request that belongs to self-service | lane it correctly | lane 3 with SOP cite; auto-reply template offered | lane 1 because urgent | feedback cites the SOP that says otherwise; timer notes the 3-second decision |
| 2 | Email 3: the familiar sender | a manager who always wants exceptions | rule or relationship | SOP lane; exception process linked | special lane 'because it's her' | pattern debrief flags sender-based routing as the week's top autopilot |
| 3 | Email 6: the combo breaker | identical to email 1, three minutes later | notice and route | routes right AND slower — recognized, not reflex | sub-5-second wrong lane | combo-timer flags fast-and-wrong; the debrief shows the cost of autopilot |
| 4 | The debrief | 8 routed emails, lane map, SOP citations | defend the pattern | routes defended by rule, exceptions named | 'I went with my gut' | debrief scores pattern correctness and autopilot rate side by side |
Any misrouted email can be re-laned from the debrief; SOP citation is revealed after the lane commit.
Debrief scores lane correctness, SOP recall and the autopilot rate — the pattern is the score, not the inbox.
Prefer the source? Download the raw markdown.