The system replaced the spreadsheet. The spreadsheet came back.
A workaround that survives go-live is not an adoption problem. It is the most honest requirements document your implementation never received.
SBy Steve··5 min read
Some months after a new system goes live, a spreadsheet reappears. Usually on one person’s machine, usually named something like tracker_v4_current, usually maintained quietly by someone competent. The system is still in use. Invoices come out of it, reports come out of it, the licence renews. But the number people actually trust before a Monday meeting is in the spreadsheet. The instinct is to read this as an adoption failure: insufficient training, insufficient discipline, a user who prefers the old way. That reading is comfortable because the remedy is cheap:…
Keep reading for free
Create an account to read the rest.
The whole library is free. No card, no subscription, no trial that
quietly ends. An account simply lets us know who we are writing
for, and opens every article from here on.
Free means free. We will not charge you for
the library, and you can read as much of it as you like.
Important: General information only. Rialto Bridge articles describe patterns and considerations that may apply to a business; they are not financial, legal, tax or accounting advice, and they take no account of your particular circumstances. Consider your own situation and seek advice from a qualified professional before acting.