Why Employees Keep Using Spreadsheets After a New System Launches

Continued spreadsheet use after a software launch is a signal to investigate, not sufficient evidence that employees reject change. A spreadsheet may fill a missing step, provide a familiar checking method, or preserve information staff do not yet trust the new system to hold. Removing it before understanding its purpose can make daily work harder while concealing the actual adoption problem.

Ask what the spreadsheet makes possible

Request a walkthrough of an ordinary task using both the new service and the spreadsheet. Identify where information is copied, calculated, checked, or shared. Ask which outcome would become difficult if the spreadsheet disappeared today. The answer gives management a specific problem to address instead of a general complaint about resistance.

In a hypothetical wholesale business, the new system records orders correctly, but dispatch employees keep a spreadsheet for grouping deliveries by location. Their workaround may reveal an essential planning need missing from the launch. Alternatively, the system may already support grouping, but nobody has shown employees how to use it in their daily routine. Those causes require different responses.

Examine trust in the underlying information

Employees may maintain their own records because they have encountered incorrect stock figures, missing customer details, or unclear update responsibilities. Training cannot resolve a genuine information-quality problem. Investigate examples and establish which record is authoritative, who corrects discrepancies, and how staff can see that corrections have taken effect.

Do not dismiss every concern because the system's calculations are technically correct. A figure can be accurate but misleading if staff misunderstand when it was updated or what it includes. Explain the meaning and timing of important information in the working process. If two sources show different answers, resolve the discrepancy openly rather than instructing employees to trust one without explanation.

Observe the workflow rather than judging preferences

The GOV.UK usability-testing guidance recommends observing actual or likely users completing relevant tasks. For an internal service, this provides a practical way to distinguish a missing capability from an unclear interface or a training gap.

Give employees a realistic task and allow them to attempt it without coaching every step. Note where they hesitate, lose context, or return to the spreadsheet. Include difficult cases, not just the demonstration used at launch. A tool that handles a routine order but cannot support a partial delivery may be forcing the most important work outside the official process.

Discuss findings with the employees involved. An observation is evidence of a difficulty; it does not by itself establish the best solution. A change to guidance, a clearer responsibility, or a focused software improvement may be more useful than rebuilding the spreadsheet inside the application.

Decide which uses should end and which should remain

Some spreadsheet use is legitimate analysis rather than a competing operational record. A manager may export approved figures for a one-off commercial review without undermining the main system. The greater concern is a parallel record that controls orders, customer commitments, or payments without being reconciled.

Classify the uses and agree a transition for the ones that create conflicting information. Assign an owner, identify what must improve, and set a review point. Where a temporary workaround remains necessary, make its purpose and reconciliation responsibility explicit. An undocumented ban may simply drive the same activity out of management's view.

Avoid asking employees to enter identical information indefinitely. Temporary duplication may help a controlled transition, but it needs a purpose and an end condition. Otherwise, staff experience the new system as additional administration rather than a better way to work.

Use Holism to address the actual gap

Holism's human developer can assess the observed workflow and determine how a focused change fits the software. AI supports implementation and iteration, while the Software Product Line foundation offers reusable capabilities and consistent rules. The owner contributes the operational examples and chooses which problems carry the greatest business consequence.

This model helps a business improve the system without making its managers responsible for engineering. It does not replace employee participation or guarantee adoption. The relevant result is that staff can complete the required work accurately and can explain why the official record is dependable.

Retire a workaround when the business can demonstrate that its legitimate purpose is met elsewhere. Spreadsheet use then becomes useful diagnostic evidence during improvement, rather than a contest between management instructions and practical employee needs.