Why Software Rollouts Fail to Deliver ROI: The Behaviour Problem Behind Adoption

30% faster case resolution. 25% less time resolving outages.

That is the promise behind a platform like ServiceNow: faster flow of work, cleaner handoffs, better visibility, fewer delays. 

But many technology rollouts never fully realise these results. The assumption is people will use the new system deliberately and consistently because they were shown how, trained on it, and told it matters.

That is not how behaviour works under real working conditions.

When people are busy, under pressure, switching tasks, and trying to get something out the door, they do not stop and think, What is the correct new workflow here? They revert to what is fastest, most familiar, and most automatic. Research on habit formation makes the same basic point: under time pressure and cognitive strain, automatic, well-practised responses tend to dominate over slower, more reflective ones. 

Take a large company implementing ServiceNow. The goal is straightforward: one place for requests, approvals, case management, onboarding tasks, service access, and workflow tracking. In theory, that should reduce noise, speed up resolution, and make work easier to manage.

But if adoption does not stick, the old system never really dies.

Employees still message someone directly on Teams because it feels quicker. Managers approve things over email because that is what they always do. HR and IT teams keep side spreadsheets because they do not fully trust what is in the platform. Teams create informal shortcuts to get urgent work through. The software is live, but the real workflow is still happening somewhere else.

That is what weak adoption looks like in practice: not dramatic failure, just constant leakage. Small acts of reversion repeated every day until the return gets diluted.

And the real issue is not usually the platform, but how the new behaviour becomes automatic when pressure hits. If the old habit is still easier than the new workflow, the old habit will win. 

This is why many rollouts underperform even after substantial investment. The organisation focuses on implementation, access, communications, and training. These are all necessary, but they do not determine what people do when deadlines are tight and pressure is on.

If people already know how to use the system but their manager doesn’t model the behaviour, allow time for experimentation or leadership has not visibly committed to the new workflow, employees read the signal and hedge. The barrier is not always in the individual. It is in fact often in the environment around them.

If you want your workplace technology to deliver the gains it was bought for, the new workflow has to become easier to trigger, easier to repeat, and harder to bypass than the old one.

That is when a rollout starts to pay back. Not when the platform goes live, but when the old pattern stops being the one people reach for first.