What a thousand businesses taught us
Across the portfolio, the industries have almost nothing in common — a school and a foundry share no vocabulary. The failure patterns, though, repeat with a consistency that is almost funny once you have seen it enough times.
2 min readOadbox
The parallel register is the leading indicator
Whenever an implementation is quietly failing, somebody is maintaining a spreadsheet or a notebook alongside the system. It always precedes the complaint, often by months.
We now ask about it directly at every review, without judgement, because the register is a precise map of where the software is inadequate. The teams that admit to it get better software; the ones that hide it get a rollout that unwinds later.
Adoption follows the fastest path, not the mandated one
No amount of policy makes people use a slower tool. Every successful rollout we have run succeeded because the new way was faster for the person doing the work, on the day, measured in seconds.
Every failed one had a memo.
The finance team decides, eventually
Software may be championed by operations and chosen by a founder, but it survives or dies on whether month-end works. If the books do not close cleanly, finance will build a workaround, and the workaround becomes the system of record.
Getting the accounting right — reconciliations, opening balances, document numbering, the audit trail — is not a back-office concern. It is the thing that determines whether the implementation is still alive in year two.
Nobody reads the training material
Manuals, recorded sessions and help articles are consumed by a small fraction of users, mostly administrators. Everyone else learns from the person sitting next to them, which means the quality of the first ten users determines the quality of the next hundred.
We now spend disproportionate effort on those first ten. It is a better investment than any amount of documentation, and it is the closest thing to a reliable rollout technique we have found.
- Train the people the others will ask, not the whole room.
- Be present for the first real transaction, not for a simulation.
- Fix the first five complaints immediately, whatever else is planned.
- Then get out of the way — a rollout that needs you present has not landed.
Written by the Oadbox team. Something here not match how it works in your business? We would genuinely like to hear it — connect@oadbox.com.