> Kit 9 · Turbine 7 · 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 | **Cleared and green** | alarm cleared 20 min ago, SCADA green, production calling | restart / hold / inspect | inspect first: cleared-with-inspection pattern | restart on green | consequence: masked vibration — the cascade replays next shift |
| 2 | **The rising trend** | vibration rising slowly, production promises overtime bonus | restart / hold / inspect | hold + inspection order | restart — 'we'll monitor it' | the trend was real: €8-12wk gearbox and a crane lead time |
| 3 | **The recurring alarm** | third alarm this week, same subsystem | restart / hold / inspect | escalate with pattern evidence | clear it again | consequence: recurrence was the pattern; the desk's patience was not evidence |
| 4 | **The external cause** | grid-side disturbance, not the turbine | restart / hold / inspect | restart — correct, and scored as correct | over-cautious hold | the debrief: discipline includes restarting when the pattern says safe |

## Retry design

Patterns re-deal on retry; the production desk argues harder each retry.

## Debrief plan

Debrief scores the decision pattern per scenario — rising-with-no-inspection vs cleared-with-inspection — never the outcome.