Observable condition
The workbook started as a useful tracker. Then it gained formulas, tabs, colour codes and lookup tables. Later it became the place where the team decides what happens next. New staff are told not to touch certain columns. One person understands the logic. If the file is unavailable or altered incorrectly, the operation slows down.
At that point the spreadsheet is no longer just a productivity tool. It is carrying operational responsibility.
Realisation
Excel is not automatically the problem. Modern Excel supports co-authoring, version history and tracked changes when files are managed appropriately. The deeper question is whether a file designed for flexible analysis has quietly become the control layer for a business-critical process.
Identification
This is often a shadow-system and workflow-control problem. The spreadsheet has become an informal application because the approved systems do not represent the process well enough, are difficult to adapt, or do not connect the information people need.
Diagnosis
Business-critical spreadsheets commonly emerge when:
- teams need a flexible view that core systems do not provide;
- several systems must be manually reconciled;
- workflow states and approvals have no proper home;
- exceptions are easier to manage in rows than in the formal system;
- people need to change the process faster than technology governance can respond.
The spreadsheet is therefore often a symptom of an unmet operational need. Replacing it without understanding that need simply drives the workaround somewhere else.
Commercial impact
The Commercial Value Wrapper is operational risk, scalability, accuracy and continuity. A critical workbook can concentrate knowledge, logic and control in one file. As volume and collaboration increase, errors become harder to detect, ownership becomes less clear and the cost of manual reconciliation grows.
There is also continuity risk when one employee understands the formulas, data imports or unwritten rules that make the workbook function.
Common misidentification
The simplistic answer is “get rid of Excel.” That is weak diagnosis. Spreadsheets remain excellent tools for analysis, modelling and flexible exploration. The problem is using them as invisible infrastructure without intentionally managing the workflow, ownership and controls that infrastructure requires.
Possibility
A better state keeps spreadsheets where they are useful while moving business-critical records, approvals and workflow states into systems designed to manage them. Teams can still analyse and export data, but the operation no longer depends on one workbook being the authoritative process engine.
Intervention
Do not start by deleting the spreadsheet. Map what it actually does: which records it owns, which calculations matter, which decisions it supports, which systems feed it and what downstream actions depend on it. Then separate analytical use from operational control.
The intervention may be a better workflow, integration, shared database, low-code application, controlled reporting layer or simply stronger ownership and version governance. The right answer depends on why the spreadsheet became critical.
Practical diagnostic questions
- Would work stop if this workbook were unavailable for a day?
- Does it contain the authoritative status of customers, jobs, orders or approvals?
- Do people avoid changing parts of it because only one person understands them?
- Is information manually imported from or exported to core systems?
- Does the file manage work, or merely analyse it?
Bottom line
A business-critical spreadsheet is not proof that spreadsheets are bad. It is a signal that an important process may be operating outside intentional systems architecture. The strongest response is to understand the process first, then decide what belongs in Excel and what no longer should.
Sources and further reading
Related Mellorca reading
- How to Decide Which Software to Remove
- How to Decide What Should Be the System of Record
- What Process Mining Can Reveal That Workshops Cannot