Finding a bottleneck's location is not the same as understanding why it is slow. This page is for a production manager or industrial engineer who has already found which operation sets a line's pace and now must decide what actually caused it.
At work, a person in this position checks a slow operation against several possible causes: a standard minute value that is genuinely high for the task, too few operators for an achievable task, a machine mismatched to the work, or an operator not yet at standard pace. The correct fix depends entirely on which of these caused the slowdown.
Without this skill, a person applies the same fix, usually adding operators, to every slow operation, even when the real cause is a machine mismatch or an under-practised operator, and the wage cost of the added operator is paid for no output gain at all.
You need: this course's earlier lessons are useful background, not required; this lesson starts from a slow operation already identified as a line's pace-setter.
By the end of this lesson you can:
Not covered here: how to read a line-balancing chart to find the pace-setting operation in the first place (lesson 8.3.1), how to choose between splitting, combining and re-sequencing once a cause is known (lesson 8.3.2), and how to calculate the line's balancing loss as a percentage (lesson 8.3.3).
| Term | Meaning |
|---|---|
| Root-cause analysis | Asking why a problem happened repeatedly until the real underlying cause is found, instead of fixing only its first visible symptom. |
| Bottleneck | The one stage in a production flow whose limited output slows down every stage after it, even when every other stage has spare capacity. |
| Standard minute value (SMV) | The standard time, in minutes, a trained operator needs to complete one operation on one piece, used to calculate a line's expected output and workload. |
| Cycle time | The time the slowest operator on a line actually takes to complete one piece at their own station, which sets the pace every other operator must match. |
| Operation breakdown | The list of every separate sewing step needed to complete a garment, each assigned to one operator and one machine on the line. |
A slow operation's effective time can come from a standard minute value that is genuinely high for the task, too few operators assigned to an achievable task, a machine slower or less suited to the task than it should be, or an operator under-skilled or under-trained for the task. A bottleneck must be diagnosed, not just located, before it is fixed.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| A genuinely high SMV for the task itself | Some operations, by their nature, take longer per piece than others, for example a complex, multi-step waistband on a pair of jeans. | The SMV is not wrong here; the fix is to split the operation across more operators or accept it as a natural pace-setter. |
| Too few operators for an achievable task | The operation's own standard time is not unusually high, but only one operator is assigned to a task several operators could reasonably share. | The fix is adding an operator, splitting, not questioning the SMV itself. |
| A machine mismatch | The operator is working on a machine not well suited to the operation, for example a general single-needle machine used for a task a specialised machine would complete faster. | The fix is a machine change or investment, not adding operators, since more operators on the wrong machine still each work at the wrong machine's pace. |
| An under-skilled or under-practised operator | The machine and the operation's own SMV are both reasonable, but the specific operator assigned has not yet reached the standard pace, often visible when the same operation runs faster with a different operator on it. | The fix is training or reassignment, not splitting or a machine change. |
| A hand-off or material-supply delay masquerading as a slow operation | The operation itself, once running, keeps good pace, but it frequently sits idle waiting for cut pieces, trims or a hand-off from an earlier stage. | The true cause sits upstream, and no fix at the operation itself will help until the supply delay is addressed. |
Delta Garments is running Order B, 3,000 pieces of five-pocket jeans, and Karim, the production manager, is diagnosing why the waistband-attach operation is running with a noticeably higher effective time than the rest of the sewing line.
This lesson's worked number is the diagnostic checklist applied to Order B's own fixed jeans construction, five-pocket, 12 oz denim with 2% elastane: waistband-attach's standard minute value is checked against a reasonable range for that task's known complexity, multi-layer stitching through denim, a naturally longer operation than a straight seam; the operator count assigned, 1, is checked against whether the task could be split; the machine assigned is checked against whether a machine better suited to multi-layer denim stitching is available; and the specific operator's own pace is checked against another operator's pace on the same task, if one is available for comparison.
No specific SMV, machine speed or operator-comparison figure is fixed in the master cast for this operation, so none is invented; the diagnostic method itself, not a number, is what this lesson teaches.
methodA common mistake is assuming every bottleneck is fixed by adding operators, splitting, when the real cause is a machine mismatch or an under-trained operator. Adding a second operator to a task being slowed by the wrong machine simply gives the factory two operators working slowly on the wrong machine instead of one, without addressing the actual cause, while the correct fix, a machine change or training, is never applied. This trap is easy to fall into precisely because splitting worked so well as a fix elsewhere in this course, but splitting only helps when the cause is genuinely too little labour on an achievable task, not a machine or a skill problem wearing the same disguise.
A slow step on a line can be slow for different reasons, and each reason needs a different fix. Sometimes the step is just naturally long and needs another person sharing it. Sometimes the machine is not right for the job, and adding people will not help until the machine changes. Sometimes the person doing it has not yet reached full speed, and training helps more than adding anyone at all. Checking which reason is true before fixing anything saves money and actually solves the problem.
Karim, production manager at Delta Garments, is told by a colleague that the waistband-attach operation on Order B's jeans line is the bottleneck, and the colleague recommends adding a second operator immediately.
Should Karim's first action be to add a second operator to waistband-attach, as the colleague suggests?
No — Karim's first action should be to investigate the operator's own pace, not add a second operator.
First fact: only one specialised machine suited to the task exists on this line, so a second operator would have no suitable machine to work on and would not raise output.
Second fact: a more experienced operator elsewhere completes the same operation noticeably faster on the same machine type, pointing to an under-trained or under-practised operator as the root cause rather than a genuine SMV or machine-supply problem.
Karim should investigate training or reassignment for the current operator, or bring in the faster operator, before considering a second machine or operator.
If a second operator is added to waistband-attach without addressing the machine shortage or the operator's own pace, the factory pays for an extra operator's time while output at that operation stays capped at the single available machine's own throughput.
Meanwhile the real fix, training or reassigning to the faster operator, remains undone, and Order B's jeans continue to move through the line at the same slow pace at waistband-attach, with an added wage cost and no corresponding output gain.
This lesson uses the "Operation breakdown" sheet of the course's Line-balancing worksheet: for the operation identified as the current pace-setter, via the "Balancing-loss calculator" sheet's cycle-time figure, use the notes area alongside the sheet to record which root cause was checked, SMV, operator count, machine, operator skill, or an upstream hand-off delay, before writing down a chosen fix. Download the workbook at `templates/T08-C03-line-balancing-worksheet.xlsx`.
Download the Line-balancing worksheet with balancing-loss calculator (Excel)
1. Why might adding a second operator to a slow operation fail to raise output at all?
2. In this lesson's jeans case, what diagnostic fact points to the operator's own skill as the root cause rather than the SMV or the machine?
3. An operation is frequently idle waiting for cut pieces from an earlier stage, even though it runs at a good pace whenever cut work reaches it. What is the correct diagnosis?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| 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. |
| Bottleneck | عنق الزجاجة | Goulot d'étranglement | Darboğaz | The one stage in a production flow whose limited output slows down every stage after it, even when every other stage has spare capacity. |
| Standard minute value (SMV) | قيمة الدقيقة المعيارية (SMV) | Valeur minute standard (SMV) | Standart dakika değeri (SMV) | The standard time, in minutes, a trained operator needs to complete one operation on one piece, used to calculate a line's expected output and workload. |
| Cycle time | زمن الدورة | Temps de cycle | Çevrim süresi | The time the slowest operator on a line actually takes to complete one piece at their own station, which sets the pace every other operator must match. |
| Operation breakdown | تفصيل العمليات | Décomposition des opérations | Operasyon dökümü | The list of every separate sewing step needed to complete a garment, each assigned to one operator and one machine on the line. |
You now know how to diagnose a bottleneck's root cause before choosing a fix. The final lesson of this course combines every skill so far, reading a chart, choosing a rebalancing action, calculating balancing loss and diagnosing root cause, into one complete worksheet built from a raw operation list through to a checked, recalculated decision. Back to the course map