Lesson 5 · Running the Proof

🎓 PHASE 1 · DAY 5

A demo invites questions — a proof ends them. Today you shift the conversation from "does this work?" to "where do we scale it first?"

minutes

photo

11 wks

it sells

☑️ Before — setting the stage (~10 min)

Walk through the instruction yourself one last time

Every own hesitation = a final gap.

Choose a tester who has NEVER done the task

Office, apprentice, another team.

30-second briefing: "Scan the code. Follow what you see. I won't help."

Invite witnesses to the machine

Plant manager, works council, shift lead — not the meeting room.

Have ready: stopwatch, notepad, phone

☑️ During — observe, don't help (15–30 min)

Tester scans, stopwatch runs, you stay SILENT

Step in only if it gets genuinely unsafe.

Note: total time · hesitations · success per step

Take THE PHOTO: the tester completing the task

Good light. Clear shot. This is your asset for 11 weeks.

Let it run to the end

Half proofs are no proofs.

☑️ After — bring everyone on board (~10 min)

Ask the tester: "Where were you unsure? What was clear?"

90 seconds — honest feedback is gold.

Ask ALL the viewers: "What did you think? Where do you see this in your area?"

Every colleague who names an idea now is a supporter tomorrow. Write the ideas down — that is the start of your phase-2 backlog.

Document the result: passed · time · hesitations

Send photo + result to the stakeholders — today

Repeat with a second tester

Three proofs = three pieces of evidence.

⚠️

The 3 killers

A "stranger" who did it once two years ago — is not a stranger.
Helping during the proof — you will want to. Every word breaks the proof.
Treating failure as the end — if tester 1 fails, that is data. Fix, run again.

ℹ️

Drill question

A stakeholder says: "A proof with apprentices isn't realistic — they aren't real shop-floor employees." Your answer?

The Proof Week covers all 4 days — on Friday (3 pm) we are there live.

Verwandte Artikel

Next: Phase 2 · Pilot Smart

Day 5 · 45 min · the moment