This page shows a production manager, merchandiser, or continuous-improvement lead how to tell a kaizen apart from a one-off large project, and how to choose correctly between the two for a floor problem they have already named as one of the seven wastes. A person who has just classified a waste on a gemba walk needs to know what to do next: try a small fix themselves within days, or raise a formal proposal for new equipment or a rebuilt layout.
Without this skill, every improvement idea gets routed the same way, usually through the slower, formal path meant for genuinely large changes. A small, no-cost fix that could be tried on the floor within days then sits waiting for budget approval it never needed, and the delay itself becomes a new waiting waste layered on top of the original problem. This lesson gives you the rule for telling a kaizen apart from a one-off project, a real case from Delta Garments' own floor, and the method for routing a floor problem correctly the first time.
You need: to already know the seven classic wastes and how to classify a floor observation into one of them (lesson 5.2).
By the end of this lesson you can:
Not covered here: the seven classic wastes themselves (lesson 5.2), how to track a single improvement idea through to a measured result (lesson 5.4), and how to build a complete tracker for a factory floor (lesson 5.5).
| Term | Meaning |
|---|---|
| Kaizen | A small, low-cost improvement made by the people who do the work, tried and measured quickly, instead of a large one-off project planned and installed by someone else. |
| Gemba walk | Going to the actual place where the work happens — the sewing floor, not the office — to see a problem directly before deciding how to fix it. |
| Root-cause analysis | Asking why a problem happened repeatedly until the real underlying cause is found, instead of fixing only its first visible symptom. |
| Standard work | The one best-known way to do an operation, written down and followed by every operator doing that operation, so an improvement can be measured against a fixed starting point. |
| The seven wastes (muda) | The seven named categories of non-value-adding activity a lean factory looks for: transportation, inventory, motion, waiting, overproduction, overprocessing and defects. |
Kaizen is a small, low-cost improvement made by the people who actually do the work, tried and measured quickly, then either adopted, adjusted, or rejected based on the result. This is different from a large one-off project, such as installing new machinery or redesigning the whole line layout, which needs planning, budget approval, and outside specialists before it can start, and takes much longer to show a result.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Kaizen (small, fast cycle) | An operator or supervisor notices a waste, proposes a small change, tries it on the floor within days, and measures the before/after result. | No budget approval is needed beyond what the line already has, so the fix can start the same week it is proposed. |
| One-off large project | A change requiring new equipment, a rebuilt layout, or outside specialists. | Needs a budget request, planning time, and often weeks or months before it can be tried, let alone measured. |
| Gemba walk as the source of kaizen ideas | A gemba walk — going to the actual sewing floor to see a problem directly, rather than discussing it from the office. | The person who sees the waste first-hand is best placed to propose a small fix for it, so most kaizen ideas start on a gemba walk. |
| Repeated small cycles versus a single large change | Kaizen works through many small cycles over time, each one tried and measured before the next. | A one-off project delivers one large change at one point in time, with no further cycle built in, so it does not repeat the way kaizen does. |
| Domestic hybrid business, same choice | Cedar & Co., a domestic brand supplying its own shops, faces the same kaizen-versus-project choice on its own cutting floor as an export factory does on a sewing line. | The rule does not change with market or business model: a small, no-cost fix is still a kaizen, and a large fix still needs planning, whether the buyer is export or domestic. |
On Delta Garments' Order A T-shirt line, Karim, the production manager, notices during a gemba walk that operators at neck rib attach keep pausing to search for trims kept in a shared bin at the far end of the station. Rather than requesting a new trim-storage system, which would be a one-off project, he proposes a kaizen: move a small labelled tray of pre-kitted trims directly beside each operator's chair.
The fix needs no new equipment, no rebuilt layout, and no outside specialist. It uses a tray the line already owns, placed differently. Karim can try it at one station the same week he notices the problem, then decide whether to roll it out to the whole line based on what he measures.
The worked numberNot a cost figure here: the worked output is a timeline comparison between Karim's kaizen cycle for the trim-tray idea and a one-off project to install a new automated trim-feed system.
A common mistake is routing a small, no-cost fix like moving a trim tray through the same budget-request process as a genuinely large project, delaying a fix that could have been tried on the floor within days. The delay itself is a form of waiting waste (lesson 5.2) layered on top of the original problem: the trim-search delay keeps happening at every shift while the proposal sits waiting for a signature it never needed.
There are two very different ways to make things better on a factory floor. A kaizen is a small, cheap change that the people doing the work try themselves within a few days, then keep it, adjust it, or drop it based on what they see. A one-off project is a big change, like new machines or a rebuilt layout, that needs money approved and outside help before anyone can even start, and takes much longer before anyone can tell whether it worked. Most kaizen ideas start when someone actually walks the floor and sees the problem with their own eyes, not when someone discusses it from an office. Forcing a small, free idea through the same slow approval process meant for a big change wastes time for no reason at all.
Sara, the buyer at Cedar & Co., a domestic brand that places orders with Delta Garments for its own shops, visits Delta Garments and asks Karim to explain the factory's approval process for any change on the sewing floor, expecting to hear that every change goes through a formal project proposal.
Sara's question is the document Karim reads:
Should Karim tell Sara that his trim-tray idea needs to go through a full project proposal before being tried? Decide before opening the answer.
No. Karim should explain to Sara that a small, no-cost change an operator or supervisor can try on the floor within days is run as a kaizen, not routed through the formal project process.
First fact. The trim-tray idea costs nothing and uses a tray the line already owns, moved to a new position beside each operator's chair.
Second fact. It can be tried on one station within a day and measured within another day, well inside the kind of fast cycle a kaizen is meant for.
Requiring a full written proposal for every such idea adds a delay — a waiting waste (lesson 5.2) — with no benefit, since the whole point of kaizen is to try and measure a small fix quickly, then adopt it if it works. Karim should tell Sara that Delta Garments' formal project process exists for changes that need new equipment, a rebuilt layout, or outside specialists, and that his trim-tray idea is not one of those.
Framed qualitatively, since this lesson compares two processes rather than pricing one order: forcing every small, no-cost idea through a slow, formal approval process risks operators and supervisors giving up on proposing fixes at all, since a genuinely low-cost improvement that could have shown a result within days instead sits waiting for approval. This is the same waiting waste this lesson's kaizen cycle is designed to avoid, now applied to the improvement process itself rather than to a single station on the line. Every day the trim-tray idea sits unapproved, the same trim-search delay it was meant to remove keeps happening at neck rib attach.
Open the continuous-improvement idea tracker. Log Karim's trim-tray idea in the "Improvement idea" column with its status set to "Proposed," then update the status to "Trial," "Measured," "Adopted," or "Rejected" as the small cycle proceeds, using the method in this lesson to decide it belongs on the kaizen path rather than the one-off project path in the first place. Download link: `templates/T07-C05-continuous-improvement-idea-tracker.xlsx`.
1. What is the difference between a kaizen and a one-off large project?
2. Why should Karim's trim-tray idea not need a full written project proposal?
3. A different floor observation, this time on a small 300-piece domestic order, needs a rebuilt cutting-room layout and a new specialist machine. Kaizen or one-off project?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Kaizen | كايزن | Kaizen | Kaizen | A small, low-cost improvement made by the people who do the work, tried and measured quickly, instead of a large one-off project planned and installed by someone else. |
| Gemba walk | جولة جيمبا | Tournée gemba | Gemba turu | Going to the actual place where the work happens — the sewing floor, not the office — to see a problem directly before deciding how to fix it. |
| Root-cause analysis | تحليل السبب الجذري | Analyse des causes profondes | Kök neden analizi | Asking why a problem happened repeatedly until the real underlying cause is found, instead of fixing only its first visible symptom. |
| Standard work | العمل المعياري | Travail standardisé | Standart iş | The one best-known way to do an operation, written down and followed by every operator doing that operation, so an improvement can be measured against a fixed starting point. |
| The seven wastes (muda) | أنواع الهدر السبعة (مودا) | Les sept gaspillages (muda) | Yedi israf türü (muda) | The seven named categories of non-value-adding activity a lean factory looks for: transportation, inventory, motion, waiting, overproduction, overprocessing and defects. |
You now know when to run a small kaizen cycle and when a problem needs a one-off project instead. The next lesson looks at how to track one kaizen idea, from a gemba walk finding through to a measured before/after result. Back to the course map