5S and Visual Management

5S is not a cleaning program. It’s the foundation for visual management and standard work — the prerequisite for everything else.

The 5 Phases — DC Specifics

1. Sort (Seiri)

Remove everything that doesn’t belong. In a DC: cardboard scraps, broken dunnage, orphaned pallets with no location, personal items, borrowed equipment never returned.

Tool: The red tag. Tag any item whose ownership, purpose, or need is unclear. Tagged items go to the red tag area (designated staging, not permanent storage). No claims in 5 days → leaves the building. No exceptions — one exception turns the red tag area into permanent purgatory.

Also apply to information: obsolete SOPs, out-of-date WMS reference sheets, procedures for systems two upgrades ago. Outdated information creates confusion, not value.

2. Set in Order (Seiton)

A place for everything, everything in its place — and every place labeled.

DC specifics:

• Every pallet position has a location address label, visible from the aisle, at consistent height
• Floor lanes painted and labeled: yellow (pedestrian/forklift travel), blue (staging), green (production), red (reject/quality hold)
• Pick faces: SKU labels at consistent heights and orientations
• Charging stations: shadow boards with foam-cutout shapes for every scanner, headset, charger — empty shape = immediate visual signal
• Pack stations: shadow boards for scissors, tape, box cutters, labeling supplies
• Dock doors labeled sequentially with carrier assignments and cutoff times posted

Design principle: Anything misplaced or missing is detectable at a glance — without asking anyone, without checking a system.

3. Shine (Seiso)

Clean as a method of inspection, not as housekeeping.

Examples of what cleaning surfaces:

• Forklift leaving oil drips → reveals seal leak
• Worn floor markings in travel lane → equipment cutting corners, creating collision risk
• Damaged rack uprights hidden behind accumulated debris

Each zone has a posted cleaning standard: what gets cleaned, when, by whom, with what tools. End-of-shift cleaning is the expectation — not a periodic event. If Shine is an event, it degrades to quarterly, then “before the audit.”

4. Standardize (Seiketsu)

The first three S’s become the documented standard.

• Before/after photos of each zone posted at the Tier 1 board and zone visual management boards
• Zone maps showing the correct 5S state
• Shift-end 5S checklists completed by zone lead, reviewed at start of next shift

“The packing station should look like the photo on the wall” is a standard. “The packing station should be clean and organized” is an aspiration. One can be audited; the other cannot.

5. Sustain (Shitsuke)

Where 5S programs die. The primary failure point — Sort through Standardize are achievable; Sustaining past month six is what separates mature programs from decoration.

Requirements for Sustain:

1. Scored 5S audit, conducted weekly, results posted publicly on Tier 2 board (numeric score per zone, per S)
2. Zone ownership by supervisor, not CI engineer (CI engineer trains supervisors on scoring rubric, then spot-checks)
3. Maintenance SLA: 48 hours for safety-related items (floor tape, safety markings), 5 business days for everything else. If maintenance can’t commit to this SLA, 5S physically cannot be sustained — surface this constraint to leadership

The Decay Pattern — Month 4–6

Month 1–2: Event is fresh. Before/after photos are dramatic. Supervisors engaged. Associates feel ownership. Month 3: Red tag area accumulates unclaimed items. One shadow board spot sits empty (device out for repair, nobody updates the board). Month 4–5: Audit cadence slips from weekly to biweekly (“we’re in surge”). Results stop going up on the board. Month 6: Floor tape peeling in two travel lanes. Nobody replaced it — work order takes 3 weeks. Standard work documents reference equipment relocated in the last slotting event. Nobody updated them.

How to hold it:

• Scored audits posted publicly, every week — no exceptions for surge. Score surviving surge proves the system works. Score disappearing during surge proves it only worked when things were easy.
• Leadership Gemba walks that specifically check 5S. When DC manager stops at a shadow board with an empty spot and asks “what’s the plan for this?” — that communicates it matters.

Visual Management

Anyone — including someone who’s never been in the building — can walk the floor and understand whether the operation is on plan, where the problems are, and what the current state of SQDC looks like. Without asking anyone.

If the visual management system only makes sense to someone who already knows the context, it’s a reporting system, not a visual management system.

SQDC Boards (Safety, Quality, Delivery, Cost)

Requirements:

• Posted at zone level, not just in the manager’s office
• Updated daily for daily metrics, hourly for real-time metrics
• Color-coded: green (on plan) → yellow (at risk) → red (off plan)
• Red status requires a written root cause and countermeasure — it is an accountability trigger, not just a status indicator

The SQDC board is the physical anchor for the daily management conversation. It is not a reporting artifact updated once a week.

Hourly Accountability Boards

Track target vs. actual output by hour. If the pack line is at 160 units/hr against a 200-unit target at 10am, the supervisor should be in root-cause mode — not waiting for the noon summary.

Critical requirement: cause codes. Each hour below target gets a cause code:

• Equipment downtime
• Staffing shortage
• Material shortage (stockout)
• Quality hold
• Training

At shift end, cause codes are Pareto’d. Top 3 causes → root-cause conversation at Tier 2 huddle. Same cause code for 3 consecutive days → Kaizen event target.

Hourly boards that track numbers without cause codes are worse than no board — they show you the problem but not the story.

Andon Systems

Visual or audible signal communicating zone status: green (running), yellow (needs attention), red (stopped/critical).

DC trigger examples:

• Pick zone below 80% of hourly target → yellow (supervisor attention required)
• Conveyor jam → red
• Replenishment stockout in critical zone → yellow until resolved

Value: A problem taking 30 minutes to surface through visual floor observation has been causing damage for 30 minutes. An andon surfaces it in real time. The response protocol for each trigger (who responds, what they check first, escalation if unresolved in X minutes) is part of standard work.

See also: Standard Work Documentation and Tier Huddle System