← Back to friday-rush case
friday-rush · deliverable

Text-based Storyboard — Friday Rush

Kit 16 · Friday Rush · deliverable · designed and built by I Wayan Usada — 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

#SceneOn screenThe learner decidesRight pathTempting pathConsequence shown
1The ticket spikelive ticket counter climbing, four orders openprioritizecontrol protected: allergen order sequenced firstcomfort first: easy tickets clearedcounter shows the allergen ticket aging — the rush did not excuse it
2The allergen near-missticket marked ALLERGY, station busy, sub called awayrun the check or trust memoryfull check: separate board, gloves, confirm'I remember the allergen list'near-miss dramatization: what one forgotten swap costs — no lecture, the ticket tells it
3The blunt correctionhead chef: 'That was wrong. Again.'absorb or arguecorrected, task redone, service continuesargues the point mid-rushcontrol lens: the correction cost 8 seconds; the argument cost the station
4The closefatigue high, closing list long, ride waitingshortcuts or disciplineclosing steps in order — last walk doneskips the last walk to leaveclosing-discipline debrief: the shortcut is tomorrow's opening problem

Retry design

Moments replay from the shift start; the debrief marks each on the single control-vs-comfort lens.

Debrief plan

Debrief scores one lens across four moments and names the control habit the week needs.

Prefer the source? Download the raw markdown.