From spreadsheets to systems: knowing when an organisation has outgrown Excel

Excel is not the enemy. It is often the first honest model of a process: columns that reflect real work, calculations that reflect real rules, a file that can be emailed to the person who needs it today. The problem begins when that file becomes the system of record, the workflow engine, the access control and the audit log at the same time.

Signals that the file is now a system

Several people must edit it. There are versions in inboxes. A formula is a business rule that nobody can change safely. Access is ‘whoever has the link’. Reporting requires a person to sit with the file before a meeting. At that point the organisation does not have a spreadsheet problem. It has an operations problem that happens to be stored in a spreadsheet.

Move the process, not the grid

The wrong response is to recreate the spreadsheet in a database, cell for cell. The right response is to extract the objects, rules and handoffs the spreadsheet was carrying, then put those into a system with roles, history and a reporting path. The spreadsheet can remain a working tool. It should not remain the place where the organisation’s memory lives.

Knowing when to move on is a leadership judgement. The cost is not the licence. The cost is the operational risk of a process that cannot be seen, governed or handed over.