When everything needs improving, sequencing matters more than ambition. Start with the process that hurts most, not the one easiest to automate.
Digital transformation has become a phrase that can mean anything, which makes it easy to sell and hard to evaluate. In practice it means one thing: work your people do repeatedly by hand is done by a system instead, and the information you need is available without someone assembling it.
Start where it hurts, not where it is easy
The instinct is to begin with whatever is simplest to automate. The better choice is the process causing the most pain, even though it is a harder first project.
The reason is momentum. A visible result carries a programme through its difficult middle, and automating something nobody complained about produces no advocate when the next phase needs approval.
Data quality comes before automation
Integrating systems before cleaning the data underneath simply distributes bad data faster and more authoritatively. If the same customer exists three times, automation propagates all three.
Assess data quality first. Frequently the honest first recommendation is a cleanup project rather than a transformation one, and the automation becomes viable afterwards.
The processes worth fixing first
Anything requiring the same information to be typed into two systems
Any month-end task that takes days and produces a number people argue about
Any question a customer asks that takes three phone calls to answer
Anything only one person knows how to do
That last one is a risk as much as an inefficiency, and it is the category owners most often overlook.
What to leave alone
Not every informal process is a problem. Small businesses run on judgement and relationships that no system captures, and formalising those can remove the thing that made the business work.
A good consultant will tell you which processes to leave alone. Being told everything needs a system is a signal about the adviser rather than about your business.
Adoption decides the outcome
A system nobody uses is worse than the spreadsheet it replaced, because now there are two sources of truth. Training on real tasks, not abstractions, and keeping the old process available in parallel until the new one has genuinely taken hold, is what prevents that.
The moment people stop asking for the old system is the moment the project succeeded. Until then it has not.
Be honest about the disruption
Any change of this kind is disruptive before it is beneficial. There is a period where the old way felt faster because it was familiar, and pretending otherwise sets expectations that guarantee disappointment.
For help sequencing this against your actual processes, see our digital transformation service.
Start where it hurts, not where the brochure starts. Our digital transformation page covers how that assessment runs, and IT consulting is the shorter engagement if you want a second opinion before committing to a programme.