> Kit 2 · LaunchReady · deliverable · designed and built by Wayne — instructional design portfolio

## Design premise

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 plan

| # | Scene | On screen | The learner decides | Right path | Tempting path | Consequence shown |
|---|---|---|---|---|---|---|
| 1 | **Monday ticket flood** | Inbox with 6 tickets, KB link visible | escalate or search first | KB search resolves 4, two real escalations | escalate all six | day-30 KPI shows self-service target missed; the queue was never the problem |
| 2 | **The gap radar fires** | Search returns zero relevant articles | write the gap or improvise an answer | log the gap — article gets authored | improvise in a private reply | the same question returns next week; the KB stays stale |
| 3 | **Reseller onboarding call** | Reseller asks a setup question mid-demo | KB link or live answer | KB link plus guided path — reseller self-serves next time | live answer only | reseller dependence continues; ticket volume unchanged |
| 4 | **Day-30 review** | KPI dashboard with per-audience resolution split | read the split, name the next gap | diagnose which audience missed and why | celebrate the aggregate number | one audience masked the other's miss; the review becomes a real decision |

## Retry design

The decision-tree widget loops failed branches back to the triage step with the branch rationale shown.

## Debrief plan

Debrief scores search-before-escalate discipline and gap logging, not raw ticket counts.