We have worked with government bodies and companies that had tried more than once to build systems, and were using them, yet departments stayed disconnected and work stayed slow. When we look back at what happened, the problem usually started before delivery.
Buying the software first
When the first decision is choosing a platform, the organization ends up reshaping itself around the product. Transformation starts with a different question: what needs to change in how we work? The tool comes after.
Nobody owns the decision
A project that belongs to every department and is owned by none usually ends with a system nobody likes. Every transformation needs clear leadership and governance: who decides, who delivers, and how progress is measured.
Leaving it to IT alone
The IT department is an essential partner, and in our work with state-owned companies its cooperation was the reason for success. But IT can't change how finance or the warehouse works on its own. The real users need to be in the room from day one.
A system your staff don't use isn't a system. It's a cost.
Changing everything at once
A big-bang launch raises risk and delays any benefit until the very end. Small phases that each genuinely go live build trust, and surface problems early, when they're cheap to fix.
Treating launch as the finish line
The first months after go-live are the riskiest: people drift back to old habits and questions go unanswered. Training, support and follow-up after launch are part of the project, not an add-on.
How to start well
- Assess where you are honestly: processes, systems, data and people.
- Agree with leadership on what must change and why, with measurable goals.
- Draw a roadmap of small phases that each deliver value.
- Set governance: who decides, who delivers, when you review.
- Plan training and post-launch support from the start.
These steps are what our digital transformation practice works through with organizations, and it usually begins with a free assessment session.