The system went live in April. The spreadsheet is still open.
When a team keeps a parallel file after go-live, it is rarely defiance, and it is usually telling you something the implementation plan never asked about.
Articles on technology.
When a team keeps a parallel file after go-live, it is rarely defiance, and it is usually telling you something the implementation plan never asked about.
Shadow spreadsheets are rarely indiscipline. They are a precise map of what the implementation failed to capture, and reading that…
Eighteen months after go-live, the real answer still lives in a workbook on someone's desktop. That isn't a discipline problem,…
A workaround that survives go-live is not an adoption problem. It is the most honest requirements document your implementation never…
Requirements lists are written by memory, and memory is biased toward the painful exception: which is how the rare case…
Systems investments are justified on the hours they will remove. The hours rarely leave, and the spreadsheet that outlived the…
Software projects get judged on licence cost and go-live dates. The decision that actually matters gets made months earlier, usually…
Connecting two systems has a price. Not connecting them has a price too. It just arrives as a hire rather…
Six months after go-live, someone is still updating the old workbook every Tuesday. That isn't resistance to change. It's a…
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.