← All work
Kit 11 · Market Peach checkout-zero · case study Fictional client — portfolio build · targets, not field results

Week-One Cashier Training: Dignity Under Queue Pressure

“The scanner knows prices. The queue doesn't forgive. Week-one cashiers quit over moments no POS manual covers.”

A register simulator where each customer embodies one moment, the queue stays visible, and the scoring explicitly separates dignity from speed — teaching that the two usually align (calm pace beats panicked pace for both). Feedback names the trust consequence of each move.

Design rule
2 gauges
dignity and extra queue time, scored separately
Design rule
65 s vs 135 s
fastest set of replies vs the best set; the fastest fails on dignity
Assessment rule
≥ 6 / 8
dignity, within a 240 s queue budget, with no policy breach
Evidence status
Not piloted
no cashier data; the evaluation below is a plan

The Audience

First-week supermarket cashiers (often student or returning workers) — plus team leads who need a shared language for the moments that drive early quits.

Responsibilities

Moment taxonomy · queue-pressure simulation · dignity-vs-speed scoring · feedback writing — early attrition treated as a design problem.

The Build

Branching scenario design · pressure pacing · behavioral feedback writing · AI-assisted drafting (disclosed)

How I used AI in this case

AI drafted customer-moment dialogue variants and queue-pacing notes; the moment taxonomy, dignity-vs-speed scoring and feedback writing were authored by me. Edited, verified and disclosed.

[01] The Problem & Workplace Diagnosis

Why conventional training failed the operational reality

Exit interviews from week-one leavers cluster on four untrained moments, not on scan speed:

Training covers till mechanics and fraud rules. It never practices holding dignity and queue pressure in the same moment — which is what the job actually is.

Core diagnostic finding

In this fictional brief, the new cashiers who left in week one could all operate the till. What broke them were four moments no manual covers: a slow payer with a sighing queue, a rule to enforce, a chaotic family, a declined card in front of an audience. In each, the fast reply and the dignified reply pull apart, so the trainer has to score them apart.

Coins
Primary Failure

Dignity without sermon

Illustrative premise: the slow elderly payer — humiliation is contagious to the queue

Design Constraint → Build Rule: The scoring had to prove calm pace beats panicked pace for both dignity and speed — showing, not telling, so the lesson survives contact with a real Saturday rush.

Policy
Operational Friction

The queue is the clock

Illustrative premise: no-receipt returns — rule enforcement with or without a door

Design Constraint → Build Rule: Pressure must be felt, not narrated. The visible queue drives urgency honestly, so speed-panic stays tempting — and stays wrong.

Cards
Design Constraint

Moments a team lead recognizes

Illustrative premise: declined payments — the loudest failure a first-weeker fears

Design Constraint → Build Rule: Each customer embodies a real early-quit moment drawn from attrition patterns, not imagination — team leads should hear their own floor in the feedback.

[01b] Design brief: the reasoning on one page

Dignity and speed are two different scores

Performance problem

In this fictional supermarket chain, too many new cashiers leave in their first week. Onboarding drills scanning speed and the POS menu, which were never the problem.

Learners and context

New cashiers, often students or first jobs, mixed Dutch and English. Short attention window before their first shift; the trainer takes about 8 minutes and runs on a phone.

Is training the answer? Not on its own

  • Supervisor availability. If the only supervisor is 20 metres away with another lane, declined payments become public scenes. A “call button” or a floor rota is a store decision.
  • Terminal reliability. If card readers fail often, cashiers absorb the blame. Track terminal declines separately from card declines.
  • First-week rostering. Putting new cashiers alone on the busiest evening lane in week one is a rostering choice.

Alignment: every objective has practice, evidence, feedback and a route back to the job

ObjectivePracticeAssessmentFeedbackTransfer
LO1 Protect the customer’s face at moments that stall the lineFour customers at the beltDignity 0–2 per reply; pass needs 6/8Explains what the customer and the queue heard“One sentence to them, one to the queue” prompt card at the till (proposed)
LO2 Manage the queue’s time without making the customer pay for itEach reply costs illustrative seconds; budget 240 sQueue-time gauge, separate from dignityThe fastest set fails; the best set fits the budgetBuddy shift with an experienced cashier (proposed)
LO3 Keep the rule and offer a way throughDeposit without a receiptManual override is a breach that fails the shiftShows the machine routeRules card with the “door” for each rule

Evidence register: what is real, what is invented

  • Fictional premise The chain, the leavers and their “exit interviews”.
  • Illustrative values Seconds per reply and the 240 s queue budget.
  • Design decision Dignity points per reply and the pass rule.
  • Not measured Week-one attrition or customer complaints. The earlier “≥7/8 dignity” was a target.
[02] Learning Objectives & Solution Architecture

Measurable Performance Objectives

Three objectives. The case promised two separate axes; the build now has them (it previously added both into one score out of 8).

LO1 · Protect

Protect the customer’s face when their payment or shopping stalls the line.

Evidence in the build: dignity per reply (0–2), 6/8 to pass.

LO2 · Manage

Manage the queue’s waiting time with a sentence or a sign, without rushing the customer.

Evidence in the build: extra queue time, kept within 240 s.

LO3 · Enforce

Enforce a till rule while offering the customer a legitimate way through.

Evidence in the build: the deposit moment; a manual override fails the shift.

Why This Modality Won (Trade-Off Analysis)

Before committing to the final architecture, we evaluated and rejected lower-transfer alternatives against the workplace constraints:

More POS system training Considered · Rejected

The obvious operational fix. Rejected because, in the brief’s premise, leavers never mentioned the till — adding scanning drills addresses the one thing that wasn't failing while the queue keeps burning new hires.

A customer-dignity e-learning module Considered · Rejected

Well-intentioned and cheap. Rejected because dignity under pressure cannot be conveyed as content — it has to be felt with the queue visibly growing. The module would teach the value; the simulator trains the moment where the value survives or dies.

Selected Architecture: Week-One Cashier Training Shipped Build

A register simulator where each customer embodies one moment, the queue stays visible, and the scoring explicitly separates dignity from speed — teaching that the two usually align (calm pace beats panicked pace for both). Feedback names the trust consequence of each move.

[03] Action Map & Instructional Architecture

Why two axes

A trade-off you can see

One combined score hides that the fastest reply often costs the most. Two gauges make the trade-off visible, and the debrief shows the fastest set failing.

Why defensible wrong answers

Kind, fast or by the book

Paying the 48 cents yourself or calling the supervisor are well-meant. They are scored as workable, not wrong, with the cost named.

Why 3D here

The queue is the clock

The lane makes the pressure physical: shoppers join while you read. Posture shows the dignity outcome; the queue shows the time cost.

Interactive Action Map Mapped from the fictional brief’s exit interviews of week-one leavers (a premise, not research): the churn clusters on four untrained moments, not scan speed. The leavers could all operate the till — so the map routes everything through dignity under queue pressure.
Open Action Map Design Doc ↗
Checkout Zero — Action Map
[05] Evaluation plan (proposed, not run)

What would tell us it worked

A proposed plan. Nothing below has been measured.

QuestionMeasure / instrumentWhenWhat we would do with the answer
Do new cashiers choose dignified replies?Dignity score and the share choosing the fastest reply per momentPilot with one store’s new startersIf the pin moment is mostly failed, add a short in-store role-play with the supervisor
Does it help in week one?New starters’ confidence rating after shift 1 and 3 (short pulse)First two weeksCompare with a store that has not used the trainer yet
Does attrition change?Week-one leavers per storeTwo quartersToo many causes to credit training alone; review with store managers alongside rostering changes

Instructional Design Takeaway

“Why this form wins: the problem is dignity collapsing under visible time pressure, so the solution puts the queue on-screen and scores the two things separately — because decoupling them is the design thesis: week-one quits are dignity events.”

Week-one cashier churn was not a scanning problem — the leavers could all operate the till. The exits clustered on four untrained moments: the slow payer, the no-receipt return, the party cart, the declined card. Each is a dignity event under queue pressure. The proposal was a register simulator with a visible queue: those four customers, live, with dignity scored separately from speed — teaching that calm is usually also the fast path.

Transparent Portfolio Scope

Honest limitation: four moments and illustrative seconds. Real queues and customers vary; the trainer rehearses first reactions, not every situation.