The system went live in January. The spreadsheet is still open.
When a team keeps a parallel record after a new system goes live, the problem is rarely training, and banning the file rarely fixes it.
Articles on technology.
When a team keeps a parallel record after a new system goes live, the problem is rarely training, and banning the file rarely fixes it.
When a spreadsheet survives the software that was meant to replace it, the usual reading is poor discipline: the more…
When staff quietly run a parallel spreadsheet alongside a new system, they are not being difficult. They are telling you…
Six months after go-live, the workbook on the shared drive is still the version people trust. That is information about…
A shadow spreadsheet surviving six months after go-live is telling you something specific about the system you bought, and it…
When a new system installs cleanly but never displaces the workaround it was bought to replace, the reason is rarely…
When a shadow spreadsheet outlives a system implementation, it is usually treated as a training failure. It is better read…
When a shadow spreadsheet survives a system implementation, it is rarely defiance: it is usually a diagnosis of the system,…
A shadow spreadsheet surviving a system go-live is rarely defiance. It is usually the most precise requirements document anyone in…
Every implementation leaves a spreadsheet behind. What that file contains is the most honest specification document a business will ever…
Everything here is free to read with an account, and always will be. What it cannot do is tell you which of these applies to your numbers, your market and your constraints. That is the work we do with clients.