Operations
When should a spreadsheet become software?
Direct answer
Keep the spreadsheet when one person owns one list and the cost of a mistake is small. Replace it when several people edit the same records, the list is the only place the truth lives, or you need to know who changed what. The replacement should be the list the team already keeps, with an owner and a history, not a platform that asks them to learn a new theory of their job.
A spreadsheet is a good tool until it becomes shared infrastructure
One planner, one register, a file that is saved with today's date and trusted by the person who made it: that is what a spreadsheet is for. It is fast, it is flexible, and it does not require a project. Many firms should stay there longer than a software company will tell them.
The change happens quietly. A second person needs the file. Then a third keeps a copy. Then someone emails “final_v7” and the office has two truths. At that point the spreadsheet has not failed as a spreadsheet. It has been asked to be a multi-user system, which it is not.
The signs that the list has outgrown the file
People are afraid to sort or filter because they might damage someone else's work. History matters — which revision was issued, what the client had already sent, who changed the fee — and the only history is an old email. The same entity appears under three spellings, and a report depends on which spelling was used this week.
A further sign: the file is the system of record for something the firm would be embarrassed to lose, and it lives on one laptop. That is an operational risk, not a style preference. Backups of a contradictory file do not fix the contradiction.
Replace the list, not the whole company
The first software version is that list, with one row meaning one thing the team already agrees on: a drawing, an engagement for a period, a learner in a batch, a job on the floor. Statuses are the words the team uses. Editing is permissioned. The previous value is still visible.
Leave the neighbouring spreadsheets alone until this one is a habit. A programme that replaces eight files at once asks the team to change every habit in the same month. They will keep the files, and the new system will be the ninth.
When not to replace it
Do not replace a spreadsheet that is a personal working note, a one-off analysis, or a list whose shape changes every week because the work itself has not settled. Software will freeze a shape that is still a draft. Wait until the columns have been stable long enough that people complain about the file rather than about the columns.
If the pain is that two products do not talk, the answer may be a connection between them rather than a new home for the data. That choice is the subject of the guide on integrating tools.