blog/why-factory-software-dies-on-the-floor · June 30, 2026

← all posts

Why two-thirds of factory-software rollouts die on the shop floor

AJ

Anurag Joshi

Walk any custom manufacturer in India and you can find the graveyard. The ERP module the sales team demoed for an hour that nobody has opened since. The tablet mounted on the shop floor being used as a place to rest a mug. The login for the last 'production tracking' system, taped to the side of a monitor, long expired. Every one of these was bought in good faith to fix production. Every one of them died on the floor.

This is not bad luck, and it is not unique to your shop. By most estimates only about a third of digital initiatives succeed; two out of three quietly fail. Once you see the pattern behind the failures, it becomes almost obvious — and, more usefully, avoidable.

It is not the reason you have been told

The usual explanations are cost and computer-literacy. Neither survives contact with the evidence. Indian manufacturers are, in fact, buying software — surveys put roughly two-thirds of smaller firms as 'digitally equipped,' though only about a quarter have moved past basic ERP and cloud into anything that changes decisions. And the same owners who supposedly cannot handle technology run their entire operation on WhatsApp with total fluency.

The most telling number is this: among manufacturers who hesitate to adopt, the large majority — around eighty-four percent in one study — say they simply cannot see clear value in what they were sold. That is not a literacy problem or a budget problem. That is a fit problem.

The tool that asks the floor to change how it works will lose

Here is the single pattern under almost every failed rollout. The software required the floor to change how it already communicates — and the floor's existing habit won.

Every one of these systems, at its heart, says the same thing: from now on, enter it here. Log the job completion in this screen. Report the breakdown in this form. Update the status in this field. And every time, that instruction competes with a WhatsApp message the supervisor can send in four seconds, from his phone, while standing at the machine, in the moment the thing actually happened. The group chat wins because it is faster, simpler and more human. It wins every time, in every shop, within about a month. You cannot out-discipline it.

Software that adds a step dies. Software that removes one sticks.

That is the whole principle, and it sorts the survivors from the graveyard. A tool that adds a step to the floor's day — one more screen, one more login, one more thing to remember after the job is done — is fighting human nature and will lose. A tool that removes steps, or asks for nothing new at all, gets adopted without a fight, because there is no habit to overcome.

Three failure patterns follow directly from ignoring this.

  • The data-entry tax — the tool only works if the floor becomes clerks, entering after the fact what they already reported in the group chat. They won't, for long.
  • The big-bang migration — ripping out a working system, however imperfect, to replace it wholesale. The disruption is immediate and the payoff is distant, so people revert.
  • The dashboard that informs but does not act — it shows you the problem in high definition and leaves all the work of solving it exactly where it was. Impressive in the demo, ignored by Wednesday.

What actually sticks

The systems in the surviving third tend to share a short list of traits, and none of them is about budget.

  • It meets the floor where it already is — listening to WhatsApp, email, phone notes and Excel, rather than demanding a new place to type
  • It sits on top of the ERP you already run — Tally, SAP, Busy or a homegrown system — instead of asking you to replace what works
  • It asks the floor to change nothing about how they communicate
  • It shows a visible win in the first week, not a payoff promised for next year

The four questions to ask before you buy anything

You can predict whether a system will join the graveyard before you ever sign, by asking the vendor four blunt questions and listening for honest answers.

  • Does my floor have to change how it communicates to make this work? If yes, expect it to fail.
  • Does this sit on top of my existing ERP, or does it want to replace it? Replacement is a multi-year disruption most shops never finish.
  • Does it just show me problems, or does it help me act on them? A prettier alarm is still only an alarm.
  • Will I see real value in the first week, or am I being asked to believe in year one? Trust on a shop floor is earned fast, or not at all.

The third of projects that succeed are not the ones with the biggest budgets or the most modern screens. They are the ones that understood a simple thing: your floor already has a system that works, and it runs on the channels people naturally reach for. The tools that win do not fight that. They fold into it — and quietly make it feed the plan.

sounds like your floor?

Bring one messy week. We'll show you the same week, organised.

Book a walkthrough