New to this topic?
We recommend reading these guides first to get the most out of this one:
3
Components of Standard Work
4
TWI Training Steps
≠
Office SOP ≠ Standard Work
Kaizen
Requires a Baseline

What Standard Work Actually Is — Not What Most People Think

Standard Work is the most important document in your facility. It is also the most commonly treated as a compliance checkbox — a binder on a shelf that nobody opens, containing procedures that nobody follows, written by someone who has never performed the operation.

That is not Standard Work. That is a fantasy.

Real Standard Work has three defining characteristics:

CharacteristicWhat It MeansWhy It Matters
DocumentedWritten down in a format that can be read, trained, and auditedKnowledge that exists only in an operator’s head is not Standard Work — it is tribal knowledge (a Black Book)
Field-validatedThe times and sequences have been observed and confirmed on the actual shop floor, not estimated in an officeTheoretical times generate shadow systems; validated times generate trust
Operator-writtenDeveloped collaboratively with the operators who perform the work, incorporating their knowledge of key points and practical detailsThe operator knows things the IE does not. Their participation produces accurate content and psychological buy-in.

Standard Work contains three components from the Toyota Production System:

  1. Takt time: The pace at which the operation must complete (Guide 04)
  2. Work sequence: The specific order of work elements that the operator follows
  3. Standard WIP: The minimum WIP required at the station for the process to flow continuously

💡 Taiichi Ohno: “There Can Be No Kaizen Without a Standard”

Without a documented baseline, you cannot prove an improvement — you can only observe coincidence. Did cycle time decrease because of your process change, or because a different operator ran it, or because the raw material was better this batch? A stable, documented standard gives you the reference point to answer that question. No standard = no measurement = no improvement = no continuous improvement culture.

Building Standard Work with Operators

The collaborative session is a 2–4 hour workshop at the workstation (not in a conference room) with the IE, 2–3 operators who run the process, and the line lead. Here is the method:

Observe and decompose

Watch the operation performed by the most experienced operator. Break it into elements — discrete steps with clear start/end points. Record video if possible (with operator permission) for later review.

Identify key points and reasons

For each element, ask: “What could go wrong here if done incorrectly?” The answer is the key point. Then ask: “Why does this key point matter?” The answer is the reason. Key points are the knowledge that separates a competent operator from a novice.

Multi-operator validation

Show the documented elements, key points, and times to 2–3 other operators. Ask: “Is this how you do it? What would you change? What did we miss?” Incorporate their feedback.

Finalize and post

The Standard Work sheet is posted at the workstation, not filed in a binder. It is a working reference, not an archive document.

📊 Worked Example 1: Standard Work Element Sheet Sealant Application on Frame Joint
#Important StepKey PointReasonTime
1Verify sealant batch number and expiryCheck expiry within 30 days; verify batch matches paperworkExpired sealant fails adhesion test — requires full rework and NDT re-inspection1.5 min
2Prepare joint surfaceSolvent wipe with MEK; allow 3-min flash-off before applicationResidual solvent under sealant causes voids that fail NDT — common rework cause5.0 min
3Apply sealant bead to faying surfaceContinuous bead, 3mm width ±0.5mm; no gaps, no overlap at cornersGaps create corrosion paths; overlap creates interference with mating part8.0 min
4Mate joint and install temporary fastenersStart from center, work outward; torque temps to 15 in-lbCenter-out sequence prevents sealant squeeze-out and void formation6.0 min
5Clean squeeze-out and fillet sealant45-degree fillet; smooth, continuous; no tool marksTool marks trap moisture and create cosmetic non-conformances4.0 min
6Document application and initiate cure timerRecord batch, time, operator stamp; set cure timer for 4 hoursTraceability requirement; cure verification prevents premature handling2.0 min

Total cycle time: 26.5 minutes

Notice: The key points contain the knowledge that makes the operation succeed. “Apply sealant” is not useful. “Continuous bead, 3mm ±0.5mm, no gaps at corners” is useful. This is the difference between Standard Work and a generic work instruction.

⚠️ Standard Work Written in an Office Is Not Standard Work

Standard Work written in an office without operator validation is not Standard Work — it is a template for creating Black Books. The IE who writes “apply sealant: 15 minutes” based on an engineering estimate, when the actual validated time is 26.5 minutes, has just guaranteed that every operator assigned to this job will miss the standard. The operator will either be blamed for “poor performance” or will maintain a private record of the real time. Both outcomes are system failures.

TWI Job Instruction: Transferring Knowledge That Sticks

Having Standard Work documented is necessary but not sufficient. The knowledge must be transferred to new operators in a way that actually produces competency — not just exposure. “I showed them” is not training. “I told them” is not training. TWI Job Instruction is training.

📊 Worked Example 2: Complete TWI-JI Training Session Sealant Application

Step 1: Prepare the Worker

  • Put them at ease: “This is a learning session, not a test. Everyone takes time to learn this.”
  • State the operation: “Today you’ll learn to apply PR-1440 sealant to a frame joint.”
  • Find out what they already know: “Have you worked with sealant before? Which types?”
  • Create interest: “This is one of the highest-value operations on the wing — getting it right prevents $15K rework events.”
  • Position them: place the trainee where they can clearly see the work, as if they were performing it

Step 2: Present the Operation (Three passes)

Pass 1 — Important Steps only: Demonstrate the full operation at normal pace, naming each Important Step as you do it: “Step 1: Verify sealant batch. Step 2: Prepare surface. Step 3: Apply bead...”

Pass 2 — Important Steps + Key Points: Demonstrate again, this time adding the Key Points: “Step 1: Verify sealant batch — key point: check expiry within 30 days and match batch to paperwork. Step 2: Prepare surface — key point: MEK wipe, 3-minute flash-off before application...”

Pass 3 — Important Steps + Key Points + Reasons: Demonstrate again, adding the Reasons: “...key point: 3-minute flash-off — because residual solvent under sealant causes voids that fail NDT, which means full rework and re-inspection.”

Step 3: Try Out Performance (Three passes by the trainee)

Pass 1: Trainee performs the operation silently. Trainer corrects errors immediately.

Pass 2: Trainee performs while stating each Important Step and Key Point aloud.

Pass 3: Trainee performs while stating Important Steps, Key Points, AND Reasons.

If the trainee cannot state the Reasons, they have memorized the procedure without understanding it. Go back to Step 2, Pass 3.

Step 4: Follow Up

  • Assign the trainee to the operation with a designated “go-to” person for questions
  • Check quality of work frequently — first shift: every hour. First week: twice per shift. First month: daily.
  • Taper off as competency develops. The trainee should be able to perform the operation independently, explain the Key Points and Reasons, and identify deviations within 2–4 weeks depending on complexity.

Standard Work as a Living Document

Standard Work is not a one-time documentation project. It is a living document that must be updated every time a better method is validated. The continuous improvement cycle:

The Standard Work Improvement Cycle
Current Standard
→
Operator proposes improvement
→
IE validates with data
→
New Standard documented
↩

The danger: unauthorized deviations that harden into undocumented new methods. If an operator discovers a better way but it is never validated and documented, it becomes a new Black Book entry — knowledge trapped in one person’s practice. The Standard Work system must have a clear, low-friction path for operators to propose improvements and for validated improvements to become the new standard.

🎯 The Bottom Line

Standard Work is the baseline for everything: continuous improvement, training, quality, and scheduling. Without it, there is no deviation — only variation. Without deviation, there is no improvement — only coincidence. Write it with operators. Validate it on the floor. Train it using TWI-JI. Update it when a better method is proven. And never, ever confuse a binder on a shelf with operational Standard Work. Next: Toyota Kata — making scientific thinking a daily habit, not a periodic event.

Free forever · Every feature included

Stop reading, start modeling

Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.

Open Workbench →

Take this to a room

The running order

For IEs writing standard work. They should leave committed to validating on the floor with operators before publishing anything.

7 beats · 13 min
  1. 1

    No kaizen without a standard

    Ohno's line, and it is the whole argument for doing this work.

    • Without a documented baseline you cannot prove an improvement - only observe a coincidence.
    • Did cycle time drop because of the change, a different operator, or a better material lot?
    • No standard means no measurement, which means no improvement.

    Ask the room Could we prove our last improvement actually caused the change?

  2. 2

    Three components, and none is a work instruction

    Takt, work sequence, and standard WIP. That is standard work.

    • A work instruction tells someone what to do.
    • Standard work defines the sequence, the timing and the in-process stock, tied to takt.
    • An office SOP is not standard work, however thorough it is.
  3. 3

    Written in an office, it manufactures black books

    The sharpest warning on the page and it is worth quoting directly.

    • An IE writes apply sealant, 15 minutes, from an engineering estimate.
    • The validated time is 26.5 minutes.
    • Every operator on that job will now miss the standard, be blamed, and start keeping their own numbers.

    Ask the room How many of our standards were validated on the floor?

  4. 4

    Build it with operators

    They know which elements have hidden difficulty and which instruction skips a step that is actually required.

    • Observe, time, then validate the sequence with the people who run it.
    • Their objections are usually specific and correct.
    • A standard they helped write is one they will follow.
  5. 5

    TWI Job Instruction, four steps

    Prepare, present, try out, follow up. Each one has substance.

    • Prepare: put them at ease, find what they know, state why it matters.
    • Present: three passes - major steps, key points, reasons.
    • Try out: three passes - silent, then stating steps, then stating key points and reasons.
    • Follow up: name a helper, check back, taper as confidence builds.
  6. 6

    The element sheet

    What, how and why per element - and the why column is the one that gets dropped.

    • Major step: what to do. Key point: the knack that makes it work.
    • Reason: why that key point matters - safety, quality or ease.
    • Without the reasons, operators improvise when conditions change, because they were never told what the step protects.
  7. 7

    It is a living document

    Updated when a better method is proven, not annually.

    • Every improvement updates it before the team disbands.
    • A binder on a shelf is not operational standard work.
    • No standard means no deviation - only variation, which nobody can act on.

    Ask the room When was one of our standards last changed by an operator's idea?