The Shortage You Can See Coming: Designing a Line-Side Signal Assemblers Actually Trust

Walk any assembly line and you will hear the same postmortem after a line-down: the bin was empty and nobody knew. That is rarely true. Somebody knew. The trouble is that the knowing happened too late, in a spot where nobody with a forklift or a purchase order could act on it. A line-side kanban is not a software project or a corporate ceremony. It is a way to move that knowing earlier, closer to the work, and into a signal that gets a response.

Put the Trigger Where the Work Happens

A good line-side signal lives at the point of use, not in a planning meeting. The simplest version is two bins. Two containers of the same part sit at the station. When the first one runs dry, the assembler slides the empty into a marked return lane or drops the card into a holder. The second container keeps the line running while replenishment catches up. The empty bin is the signal, and the person pulling parts is the sensor.

For small parts, a card system often works better than a full bin. Tape a card to the last bag or the last box in the sequence. When the assembler opens that last container, the card goes to a visible board at the end of the station. No counting every cycle. No spreadsheet update. One motion, one signal.

The trigger point is where most homemade kanban systems go wrong. Do not guess from a spreadsheet. Watch two or three shifts. If a station burns one box every four hours and replenishment takes ninety minutes, two bins may be too thin. Add a third bin or set the card trigger earlier. The goal is not a perfect formula. The goal is enough warning that the line never has to stop and wait while somebody searches for a part number.

A Signal Needs a Response Time, Not a Slogan

A kanban card without a response time is decoration. The board can be clean, the labels can be sharp, and the system can still fail because nobody agreed on what happens after the card lands. Write the route time on the board itself: material handler checks at set intervals, or on a fixed route. Put the backup name on the board too. That way the assembler is not hunting down a person while the second bin drains.

This is also where the signal stops being an assembler problem. The assembler owns the trigger. The material handler owns the response. The team lead owns the escalation when the response does not happen. If those three roles blur together, the card becomes a suggestion and the empty bin becomes a surprise.

Make the response visible. A card that sits for two hours should look different from a card that just landed. A simple time block, a colored clip, or a magnetic marker can show age without turning the board into a science fair. The point is not to track every minute. The point is to make a late response obvious before the line is down.

When the Signal Gets Ignored

The first time a card sits past its response window, the assembler should not have to become a dispatcher. Tell the team lead. Keep the empty bin or the card where it is so the problem is visible. If it happens once, it may be a bad shift. If it happens twice, it is a route problem. If it happens three times, it belongs in the shift huddle with the actual card and the actual empty bin in hand.

A useful escalation ladder is short. Same shift: tell the team lead. Same day: review the material route and the trigger point. Same week: adjust the standard or raise the issue in the huddle. Do not build a fifteen-column log to prove the point. Three hash marks on the corner of the board can show a pattern without creating another clipboard chore. The signal itself is the evidence. An empty bin with a two-hour-old card tells a clearer story than a paragraph in a notebook.

If the signal is ignored repeatedly, resist the urge to blame the assembler for not calling louder. The system failed to answer. That is a process problem, not a personality problem.

Keep It From Becoming Another Chore

The fastest way to kill a line-side kanban is to make it feel like extra work. That means no counting every hour, no filling out a form for every empty bag, and no twelve-field card that requires training. The card should carry only what a material handler needs: part number, description, station location, standard pack quantity, and who to call. If the card needs a legend, it is a form, not a signal.

Reset the signal during replenishment, not at the end of the shift. When the material handler drops the new bin or bag, the card goes back to its starting position. That small habit keeps the system honest. It also keeps the assembler from inheriting a cleanup task that belongs to replenishment.

Once a week, take a short walk down the line and look at the boards and bins the way a new hire would. Are the empty return lanes obvious? Are the cards where they belong? Is the response time still realistic? Five minutes of looking beats an hour of meeting about why the system is not working.

The Assembler's Job Is to Build, Not to Chase

A line-side kanban does not ask assemblers to manage inventory. It asks them to send a clear signal at the moment they see the need. That distinction matters. The assembler is not the warehouse. The assembler is not the purchasing department. The assembler is the person closest to the work, and that person should have the easiest possible way to say, this part is running out.

When the system works, shortages show up hours before they become line-down events. When it does not work, the empty bin is still a message. It is just a message that arrived too late. Build the signal where the work happens, give it a response time, and let the empty bin speak while there is still time to act.