A second-generation owner called me last year with a familiar problem. His father built a plastics manufacturing business in Tangerang over thirty years, and it ran on a whiteboard, a foreman's memory, and a handful of Excel files that only one person knew how to open. This manufacturing digitalization case study is about what actually worked when we fixed it, and it was not what either of us expected going in.
He wanted an ERP. Full production planning, inventory, HR, accounting, the works. I told him no, not yet, and that conversation is the real subject of this piece.
The business made injection-molded plastic parts for appliance brands, three shifts, around 60 factory staff. The father, now semi-retired, still walked the floor twice a week. The son, MBA-educated, wanted dashboards. The senior staff, some of whom had worked there for 20 years, wanted nothing to change.
Why the Full ERP Pitch Was the Wrong Start
Every ERP vendor who had pitched them before started with a company-wide rollout: modules for planning, procurement, warehouse, finance, HR, all live in month one. None of it stuck. Staff reverted to the whiteboard within weeks because the system asked more of them than the whiteboard did, for no visible benefit to their daily work.
This is the same mistake I see across manufacturing digitalization projects in Indonesia: the tool is scoped to what the owner wants to see, not to what the floor needs to do. A dashboard the owner checks once a day is worthless if the person who is supposed to input the data has no reason to bother.
So we scoped down. Hard.
Starting With One Production Board
We built exactly one thing first: a digital production board, tablet-based, one per production line, replacing the whiteboard directly and doing nothing else. Each shift lead logged:
- Job order number and target quantity
- Units completed, updated every two hours
- Downtime reason, picked from a short dropdown (machine fault, material shortage, changeover, other)
- Reject count with a photo option
That was the entire first release. No inventory module, no costing, no HR. The board looked almost identical to the whiteboard it replaced, just on a screen, because familiarity was the point.
The skeptical senior staff, three shift leads who had run the floor for years, were the actual reason this worked. We sat with them before writing a line of code and asked how they already tracked production in their heads. The dropdown reasons, the two-hour cadence, even the order of fields on screen came from them, not from us. They stopped resisting once they saw their own routine reflected on the tablet instead of a system nobody had asked their opinion about.
What Changed in the First 90 Days
Within three months, three things became visible for the first time:
- Real downtime causes. The father had always suspected machine faults were the main issue. The data showed material shortages were actually costing more hours, which pointed straight at a supplier scheduling problem, not a maintenance problem.
- Line-level output gaps. One line consistently ran 15 percent below its stated capacity on the same job orders. Nobody had noticed because the whiteboard got erased at shift change.
- A reject pattern tied to a specific mold, caught because photos were attached to reject logs instead of a verbal note that evaporated by end of shift.
None of this needed AI, forecasting, or a costing engine. It needed accurate, timestamped data that used to exist only in someone's head for eight hours and then disappeared.
Sequencing the Next Layers
Once the production board was in daily use with no pushback, we added the next layer, and only then: a simple inventory count tied to job orders, so raw material draws matched what was actually consumed on the board. Finance connected to that later, once inventory numbers were trustworthy enough to feed into it.
The sequence mattered more than the features:
| Phase | What we added | Why it came at this point |
|---|---|---|
| 1 | Production board (replace whiteboard) | Lowest friction, highest immediate visibility |
| 2 | Material draw tied to job orders | Inventory data only useful once production data was trusted |
| 3 | Basic costing per job order | Needed both of the above to be accurate first |
| 4 | Owner-facing dashboard | Last, because it aggregates data that now actually exists |
This is the same principle behind a digital maturity model for growing SMEs: you cannot skip from paper-and-memory straight to data-driven operations. Each level has to be earned with working habits before the next layer has anything real to build on.
The Human Part Nobody Puts in the Proposal
The father's twice-weekly floor walks changed in a quiet way. Instead of asking the foreman what happened yesterday and getting an answer shaped by whoever was easiest to blame, he pulled up the board on his phone before he arrived. Conversations on the floor got shorter and more specific. That shift in trust between generations, and between owner and shift leads, mattered as much as any number in a report.
Practical Takeaway
If you run a family manufacturing business still tracking production on a whiteboard, resist the full ERP pitch. Pick the one process your senior staff already do reliably by memory, digitize just that, built with them rather than for them, and let the next layer wait until the first one is boring and habitual. That is what actually survives contact with a factory floor. If you want a second opinion on where to start, get in touch through partner.