Every highlighted passage extracts a training requirement. Click a highlighted phrase to see what was captured from it — and which downstream artifact it feeds. Eight critical tasks, misconceptions and vocabulary items, plus two hard constraints.
Question: walk me through the last batch that went wrong — not the report, the actual evening.
Founding operator Sanne de Zwaan: "It was the temperature log that was signed but never measured. My cousin filled in the sheet from the previous day's numbers because the probe was 'somewhere'. Two days of data, invented. We found out because the culture test came back off."
"People think the danger is the big failure. It isn't. It's the routine step everyone does from memory. Connecting the CIP lines, switching the valve manifold. If you've seen it done fifty times you don't think. We had two near-misses in cleaning-in-place this spring — both by people who were told once, weeks earlier."
When someone new starts, what do you actually want them to be able to do on day one — and what can wait?
"Day one: the tank line checks, in order, out loud. Temperature, CIP confirmation, line identity, then the release decision. If they can't say it out loud, they don't touch the manifold. The rest — cheese turning, brine, packaging — can grow over weeks."
"And write it down the way we say it. My nephew asked me for 'the protocol'. I said: there is no protocol, there's what I do before I open that valve. Now there are twenty-four of us and 'what Sanne does' is not a system."
Where does the hesitation sit — what decision do people get wrong when they know the steps?
"The release call after a temperature excursion. A batch sits at 8.4 for a bit — under 30 minutes, core comes back down. People either dump it — panic — or pour it and hope. Both are wrong. There's a protocol question with a yes/no, and then the note. The note is the part everyone skips."
"Half my new people read Dutch only, half read English only, and everyone is standing up in noise when they need the answer. Whatever you build: it has to survive a glance, one-handed, in boots. And I want it on the wall and on the phone — same words, or they'll argue about which one is right."
I Wayan Usada (notes): language split, standing-use context, single-source rule. Feeds the floor manual format and the print/digital parity constraint.
Budget and system reality: no LMS, no PCs on the floor, one shared tablet in the break room. What can't change?
"No screens on the production floor — hygiene rules, and honestly, wet gloves. Print lives at the tank. The tablet gets the module. Nothing that needs a login — agency staff rotate too fast for accounts."