·4 min read·Nasir Hussain
Why your last software rollout failed (and it was not the software)
Most failed rollouts we are called in to rescue were not technical failures. They were sequencing failures.
Engineering
Every rescue project we take over has the same shape: the software mostly worked, and nobody used it.
The pattern is almost always that everything launched at once. Staff were asked to learn six new screens in one week while still doing their actual job, so they quietly went back to the register.
Roll out one module per month instead. Slower on paper, dramatically faster in practice, because each module is genuinely adopted before the next one lands.