Digital transformation projects rarely fail because of the technology. The ERP, the CRM, or the dashboard usually does roughly what the vendor promised. They fail because leadership treats the project as a one-time IT purchase instead of a multi-year change program. What fails to happen is not the installation. It is people changing how they work, and that only happens when the owner or director keeps pushing for it.
The pattern is familiar. A vendor is selected, a contract is signed, and leadership steps back to wait for results. Eighteen months later the system is live, but adoption is low, the data is messy, and nobody measured whether the original goals were met. Sales still keeps its own spreadsheet. Stock is still counted on paper and typed in at the end of the month. The new system has become a place to record what already happened elsewhere.
Why does this sit at the leadership level and not with the IT team? Because most of the hard decisions are about people and process, not software. When the sales manager refuses a new approval step, or the warehouse insists on keeping its own stock card, a project manager cannot overrule them. Only the owner or a director can settle disputes between departments, decide which process wins, and free up staff time for training and data cleanup.
Part of the problem is expectations. Owners often expect results within weeks of go-live. The reality is that master data has to be cleaned, processes have to be decided, people have to be trained, and productivity usually dips for a while after the switch, because everyone is slower on a system they are still learning. Saying this plainly at the start prevents the panic that leads to workarounds and, eventually, a return to the old way.
A simple framework helps, and it starts with one sponsor. Choose one owner or director who is accountable for the outcome, not the IT staff and not the vendor. That person chairs a short monthly steering meeting, makes decisions within a week when the team is stuck, and is visibly seen using the new system. A committee of five equal sponsors usually means nobody owns the result.
Second, turn the business case into measurable goals before signing anything. Not better visibility, but numbers you can check: close the books within a set number of working days, cut the time from customer request to quotation, raise stock accuracy at the monthly count. Measure the current baseline first. Without a baseline, nobody can say eighteen months later whether the project worked, and the conversation turns into opinions.
Third, decide which process changes before configuring the system. Write down the habits that will stop: no sales order outside the system, no manual stock card, no purchase without a purchase order. Then decide who enforces each rule. If the software is configured around the old process, the company pays for a new system and keeps the old problems.
Fourth, make the change stick through what leadership does every week. Give key users real time for the project instead of adding it on top of their normal job. Use reports from the new system in management meetings. If the owner still asks for the Excel version, everyone learns that Excel is what really counts, and the new system quietly becomes optional.
Fifth, keep going after go-live. Review the goals at three, six, and twelve months, fix what is not working, and add the next improvement only once the current one is being used. Transformation is a habit, not a project. The companies that benefit most are the ones that keep iterating long after the consultants have left.
If you are about to start an ERP or digital project, or one is already live and not delivering, talk to Kerja Itu Mudah before more budget goes in. In an advisory session, starting from IDR 1 million, we review your goals, your sponsor setup, and where adoption is stuck, then give you a written list of what leadership needs to decide next.