The control tower playbook for Tiruppur factories

When KM Garments brought us in, their three units in Tiruppur were running on twelve WhatsApp groups, four spreadsheets, and a whiteboard that nobody trusted after 11am. Orders slipped not because the teams were slow, but because no one could see the whole board at once.

A control tower is not a new piece of software you bolt on. It is a discipline: one screen that every role looks at, updated by the work itself rather than by someone remembering to update it. Here is the exact sequence we used to get there in a single quarter.

1. Make the order the single source of truth

Every conversation on the floor was really about an order — fabric pending, a sampling delay, a buyer changing a size break. We moved each of those from a chat message to a field on the order itself. The rule was simple: if it is not on the order, it did not happen.

2. Give every stage a visible state

Cutting, stitching, finishing, packing, dispatch — each order sits in exactly one stage, and each stage shows how long the order has been there. Ageing is the signal. An order that has been in finishing for four days when the average is one is a problem you can see before the buyer calls.

• Colour-code by days-in-stage, not by stage name — red means stuck, regardless of where.
• Surface the three oldest orders per stage at the top. Nobody scrolls.
• Let the floor update state from their phone, in two taps, in Tamil or English.

3. Run a five-minute morning standup off the board

The owner, the unit managers, and the merchandiser open the same view at 9am. They do not discuss everything — only the red rows. Within three weeks, the standup shrank from forty minutes to under ten, because the board had already done the triage.

The 40% drop in overdue orders did not come from working harder. It came from everyone finally looking at the same board — and the board telling them where to look first.