Implementation Guide
5S.
5S is a five-step method for organizing a workplace, sort, set in order, shine, standardize, sustain, so that any abnormality, a missing tool, a leak, overstock, is visible in seconds. It is not a cleaning program. The first four steps take a few weeks; the fifth decides everything, and it is a leadership behavior, not an audit score. 5S survives only when daily 3-minute checks and weekly leader audits are wired into leader standard work.
What 5S is actually for
5S is usually introduced as housekeeping, and that framing kills it. A tidy workplace is a side effect. The real product of 5S is a workplace where abnormality is visible in seconds: a tool missing from its shadow, a hydraulic leak on a floor that is otherwise clean, a pallet of overstock standing outside its marked square. In a cluttered area those same signals exist, but they are invisible, buried under the noise of stuff that has always been there.
That visibility is worth real money. A missing tool found at the start of a changeover instead of in the middle of it, a leak caught while it is a drip and not a bearing failure, WIP that cannot silently accumulate because the space for it is finite and marked. 5S is the physical layer of visual management: it makes the normal state so obvious that any deviation from it asks a question.
Which is why the fifth S carries the whole method. Sorting, arranging, cleaning and documenting are projects; anyone can run them once. Sustain is a leadership behavior, a few minutes of checking and coaching repeated daily and weekly, and it is the only step that cannot be delegated to a launch week. Most 5S programs do not fail at step one. They finish step four and discover nobody planned step five.
The five S, step by step
Each step exists to produce something specific, and each has one mistake that accounts for most of its failures. If a step's output does not exist, the step did not happen, however busy the week felt.
| Step | What it means operationally | Output | Most common mistake |
|---|---|---|---|
| 1. Sort Seiri | Remove everything from the area that the current work does not need. Anything questionable gets a red tag and moves to a quarantine zone with a decision date, so nothing is thrown away by argument. | Only what the work needs remains, plus a red-tag register with a disposition and an owner for every tagged item. | Keeping things just in case because nobody owns the decision, or discarding without a register, which teaches people to hide private stashes before the next sort. |
| 2. Set in order Seiton | A place for everything, sized by frequency of use: hourly items within reach, daily items in the area, weekly items further away. Shadow boards, labels and floor markings make the place obvious. | Anyone finds any item in under 30 seconds, and a missing or misplaced item is visible at a glance from the aisle. | Arranging for the photo instead of for the motion of the work, and labeling everything including the label maker. If a location needs no decision, it needs no label. |
| 3. Shine Seiso | Clean to inspect. Cleaning is a check of wear, leaks, loose fasteners, damage and contamination sources, with a defined method, materials and time budget. | An initial deep clean, a short cleaning-and-inspection standard, and a first defect list handed to maintenance with owners. | Cleaning as cosmetics the day before an audit. If shine never produces a defect tag, it is decoration, not inspection. |
| 4. Standardize Seiketsu | Make the state after the first three steps the documented standard: photos of the correct state at the point of use, zone ownership named, checks and their frequency defined. | A visual standard anyone can audit against in minutes, owned by the team that works in the zone. | Photographing the before instead of the standard, and filing the standard in a binder instead of posting it where the work happens. |
| 5. Sustain Shitsuke | The habits and leadership routines that keep the standard alive: a 3-minute daily self-check by the team and a weekly leader audit from the leader standard work routine card. | Audit findings become actions with owners and dates, and the standard itself evolves when the work changes. | Treating sustain as a monthly audit score instead of a daily habit. A score can be inflated; a habit either happens or it does not. |
Where 5S sits in the transformation roadmap
On the TeamGuru deployment roadmap 5S belongs to the standard work and 5S practice in the Run stage, launched in parallel with daily management. That pairing is deliberate: the daily meeting gives 5S findings somewhere to go, and 5S gives the daily system something honest to look at. It also runs beside standardized work, because a workplace where every tool and fixture has a known home is what makes a work sequence physically repeatable.
- Before Baseline KPIs
- You are here Standard Work & 5S
- In parallel Daily Management
- After Structured Problem Solving
When 5S is the wrong start
5S is often sold as the safe first Lean move: visible, cheap, low risk. That is half true. As a first visible win it works, but only if the sustain mechanism ships with it, meaning a daily check, a weekly leader audit, and a board where findings become actions. A cosmetic 5S launched before any management rhythm exists decays in roughly 90 days, and it takes the credibility of the next initiative down with it, because the workforce has now seen a program come and go. Do not start when:
- There is no daily management rhythm. A 5S launch with no daily meeting to review the checks and no board to put findings on decays in about 90 days, because nothing in the plant's routine ever asks about it.
- Leaders will not commit audit time. If the area manager cannot protect ten minutes a week for a zone audit, the program is being launched to fail, and the failure will be blamed on operator discipline.
- The goal is a corporate photo report. If the deliverable is a before-and-after slide deck for a steering committee, you will get exactly that, and nothing else.
- Maintenance has no capacity for findings. Shine will surface leaks and worn parts within days; if defect tags go into a backlog nobody works, the team learns that looking closely is pointless.
How to implement 5S, zone by zone
Take one zone to full 5S, including four weeks of proven sustain, before touching the second. This feels slow next to a plant-wide blitz and is faster in every way that counts: the pilot builds the auditors, the templates and the proof, and every later zone copies a working example instead of a slide. The counts below are illustrative, from a pilot in one assembly cell of the 450-person components manufacturer used across these guides.
| When | What happens |
|---|---|
| Week 0: prepare | Pick one pilot zone: one team, clear physical boundaries, visible from the aisle. Name the zone owner from that team. Agree the red-tag rules and set up a quarantine area with a decision date. Book two hours per week of the team's time on the schedule, not as overtime. |
| Week 1: sort | Run the red-tag event with the whole team. Everything not needed for current work is tagged and moved to quarantine; the register records item, reason and disposition owner. Illustrative scale for one assembly cell: about 140 items tagged, roughly 60 discarded, 45 relocated, 35 returned after a real decision. |
| Week 2: set in order | The people who work in the zone design the layout: shadow boards for tools, labeled homes for fixtures and consumables, floor markings for carts and WIP. Trial the layout with tape and cardboard for a week before anything becomes permanent. |
| Week 3: shine | Initial deep clean as inspection: every surface, guard and connection gets looked at, and every leak, worn part and loose bolt gets a defect tag for maintenance. Write the cleaning-and-inspection standard: who, what, when, how long, which findings go where. |
| Week 4: standardize | Photograph the standard state, not the before, and post the photos at the point of use. Define the 3-minute daily self-check and the weekly audit questions. Confirm zone ownership and what the team does with a finding it cannot fix itself. |
| Week 5 on: sustain | The team runs the 3-minute check at the end of every shift; the area leader audits weekly from the routine card. Findings become actions with owners on the team board. Spread to the next zone only after the pilot has held its standard for four consecutive weeks. |
Rules that keep the rollout honest
- The people who work in the zone decide what stays and where it lives. Facilitators bring the method and the rules; they do not bring opinions about someone else's tools.
- Photograph the standard, not the before. Before-and-after photos entertain a steering committee once; photos of the correct state audit the workplace every day.
- Every red-tagged item gets a disposition with an owner and a date. An unresolved quarantine pile is just clutter that moved twenty meters.
- Give the pilot real scheduled time. 5S done in overtime or between cycles signals exactly how much the plant values it.
- Spread only after the pilot holds its standard for four consecutive weeks. A second zone launched while the first is decaying doubles the decay, not the progress.
Shine is inspection, not decoration
The most underused step is the third one, because it is read as janitorial. It is not. Cleaning a machine with your hands on it is the cheapest inspection a plant owns: the person wiping the guideway is the person who feels the scoring, sees the oil film where no oil belongs, and notices the fastener that backs off every week. In the illustrative pilot above, the initial deep clean of one cell produced a dozen defect tags, among them two slow leaks and a worn guard hinge, all found while they were still cheap.
For that to keep happening, two things must be true. The cleaning standard has to say what to look at while cleaning, wear, leaks, loose bolts, contamination sources, not just what to wipe. And every finding needs a route to someone who will act: small items fixed by the team, the rest tagged for maintenance and visibly tracked. This is the same operator-led inspection logic that TPM builds autonomous maintenance on; a plant that does shine seriously has already started TPM without announcing it. The moment defect tags stop being worked, shine collapses back into cosmetics, because people stop reporting what nobody fixes.
Sustaining: the fifth S is leadership
Sustain is two routines, and both must be visible on a calendar, not implied by a poster. The first is the team's own 3-minute check at the end of each shift: walk the zone against the photo standard, return what wandered, note what cannot be fixed on the spot. Three minutes is the design target, not an accident; a check that takes fifteen minutes will be skipped on the first busy day, and every day is busy.
The second routine is the weekly leader audit, and it belongs on the area leader's leader standard work routine card, one zone per week, ten minutes, at the workplace with the team. The audit exists to produce findings and coaching, not a grade. Every finding gets one of three dispositions within a week: fix it, train it, or change the standard because the work changed. A finding without a disposition teaches the team that the audit is theater. As the program matures, these zone audits fold naturally into layered process audits, where plant leadership checks a zone monthly and the questions rotate.
Notice what is absent: a score target. Track the trend and whether findings close, and treat a rising count of small findings as health, not failure. An area that reports nothing for a month is not perfect. It has stopped looking.
Common failure modes
5S fails in recognizable patterns, and all of them are management failures wearing an operator-discipline costume. Four account for most of the funerals:
The corporate 5S week
Every area blitzed in five days, banners, t-shirts, photo walls. Six weeks later the shadow boards have gaps and the aisles are refilling, because a blitz builds the first four S everywhere and the fifth S nowhere. One zone taken to full 5S including sustain beats twenty zones taken to standardize.
Red-tagging other people's areas
An improvement team or an office function sorts a workplace it does not work in. The people who own the area quietly bring everything back, and they are right to: they know what the work needs. Sorting is a decision the zone's own team makes against agreed rules, with support, not on their behalf.
Audit score inflation
When the score is the target, scores rise and workplaces do not. Areas learn the checklist, auditors soften to keep the peace, and a 94 percent plant looks worse every month. Track the trend and whether findings get closed; celebrate found problems, not clean sheets.
Labeling as an end in itself
Every drawer, shelf and stapler gets a label, including the label maker, and the zone looks organized while the flow of work is untouched. Set in order exists to shorten motion and make absence visible. If a label never prevents a search or reveals a missing item, remove it.
What happens next
A zone at full 5S changes what the practices around it can do. It makes standardized work auditable: when every tool has a home and the correct state is photographed, checking whether the standard is followed takes minutes instead of arguments. And it makes daily management visual: the state of the zone walks into the morning meeting on its own, and 5S findings share the same SQDIP board lanes as every other deviation, with owners and dates instead of a separate 5S bureaucracy.
The administrative load of sustain, scheduled checks, rotating audits, findings that must not evaporate, is where paper systems quietly give up and where TeamGuru fits the practice: the checklists and audits use case runs the daily checks and weekly zone audits on a tablet at the workplace, with photo findings that become owned, dated actions the daily meeting can see aging.
On the roadmap, the practice that follows is structured problem solving. That order is not accidental: a workplace that surfaces abnormality in seconds produces a steady stream of small, well-described problems, which is exactly the raw material a problem-solving system needs to practice on before the big ones arrive.
