Digital Transformation · Actual Adoption
The New System Is Live. Why Is Everyone Still Using the Spreadsheet?
Investigate workarounds as evidence of unmet needs, unclear ownership, and operational friction after a system launch.
In this article
The implementation is complete. Training attendance was strong. The dashboard shows active users. Yet the team still runs the day from a spreadsheet.
It is tempting to call this resistance. Sometimes a familiar habit is part of the explanation. But the spreadsheet may also contain a view, calculation, exception, or coordination function the new system does not provide. Removing it before understanding its job can remove the thing keeping the work moving.
Ask the team to demonstrate the whole task
Watch a real workflow with appropriate privacy safeguards. Ask the employee to begin where the task actually begins and continue until the handoff is complete. Note every export, copy, side message, and manual check.
Do not ask only why they dislike the new system. Ask what the spreadsheet lets them accomplish. A person may not be able to describe a missing requirement abstractly but can show exactly why they open the file at 9 a.m.
Distinguish the causes
The spreadsheet may fill a functional gap, compensate for unreliable data, provide a faster interface, support a permission the user lacks, or preserve an old habit after the need has disappeared. Each explanation calls for a different response.
More training helps when a useful feature exists but is unknown. It does not fix data that arrives too late. A new integration helps when re-entry is the problem. It does not settle a disagreement about who owns the record.
A hypothetical service operation
The new platform records jobs correctly, but supervisors use a spreadsheet to plan tomorrow’s crew assignments. The platform’s standard view is organized by customer; the supervisors need a view by skill, availability, and travel sequence.
The spreadsheet is not proof that the platform has failed. It identifies a planning task that needs a supported solution. The team can then evaluate configuration, reporting, integration, or an explicitly governed companion process.
Decide which system owns each fact
Duplicate records become dangerous when both are edited without a reconciliation rule. Name the authoritative source for the relevant fields and how changes move between systems. Identify who resolves conflicts and how quickly.
A temporary spreadsheet may be acceptable for a defined purpose if access, version control, ownership, and retirement conditions are clear. Calling it temporary without a review date simply gives an unmanaged process a reassuring name.
Fix the work before demanding compliance
Choose one high-value workflow and define what successful adoption means in task terms. For example: an authorized supervisor can make and communicate the next day’s assignments without duplicate entry, while the receiving team sees the current version.
Involve the people doing the work in testing the revised process. Include exceptions, absences, and incomplete information. A demonstration using ideal data can pass while the ordinary workday remains difficult.
A workaround review record
Task served. Users involved. Information copied. Failure prevented. Risk introduced. Missing capability or trust issue. Proposed fix. Owner. Test condition. Date to keep, change, or retire the workaround.
Update the SOP after the workflow works
A standard operating procedure should describe a usable process with clear roles and exception handling. Writing it before resolving the underlying problem can formalize a sequence employees already know will fail.
Once the revised workflow is tested, update training, job aids, and support routes. Explain what has changed and why. Retire obsolete instructions so employees do not receive two official versions of the same task.
Retire the duplicate in a controlled way
Once the revised workflow works, establish when the spreadsheet stops accepting new updates, how necessary records are retained, and where users should go instead. Communicate the change to everyone who receives information from the file, not only its main editor.
Keep a short support period with an owner for exceptions. If a genuine missing requirement appears, address it through the agreed route rather than allowing a second unofficial copy to emerge quietly.
The retirement is successful when the task continues reliably through the intended process. Deleting a file is only an action. It is not evidence that the operational need has been met.
Inspect the columns before replacing the file
Return to the hypothetical crew-planning spreadsheet. Its columns might include customer address, job status, required skill, proposed crew, and a supervisor’s planning note. Those fields do not all play the same role. Some repeat facts already owned by the platform; others support a decision the platform’s current view does not express.
Copied fact
A customer address appears in both places. Identify the authoritative record and what happens when it changes. The planning file should not silently become a competing address book.
Working decision
A proposed crew assignment may remain provisional until a supervisor approves it. Make that state visible so downstream staff do not mistake a draft for tomorrow’s confirmed schedule.
Exception note
A special access constraint may change the plan. Decide who can verify it, where it belongs, and how the crew receives it. Keep unnecessary personal information out of the planning view.
Now test a change after the first schedule is prepared. A job moves, the available crew changes, or an input is incomplete. Follow the information to the person doing the work. Which version do they see? Who is responsible for reconciling the difference? A process that works only before the first exception is not ready to replace the workaround.
The result may be a better platform view, an integration, a supported companion tool, or a simpler procedure. Select the remedy around the task and its ownership. Recreating every spreadsheet column inside the new system can preserve an old problem just as easily as deleting the file can expose a missing capability.
Before retirement, have the actual users complete the ordinary task and one relevant exception using the revised process. Record what they still had to verify elsewhere. That last question often reveals whether the apparent adoption is supported by a hidden second workflow.
Measure completion, rework, and trust
Logins tell you someone entered the system. They do not establish that the work was completed there. Track duplicate entry, reconciliation effort, errors, handoff delays, and the number of tasks completed through the intended process.
Ask employees which information they still verify elsewhere and why. Trust often grows when a system repeatedly gives them information they can act on. An adoption campaign cannot substitute for that experience.
This is where digital transformation advisory becomes operational. The capacity and ownership decisions also belong in executive strategy. The goal is improved work, not the ceremonial disappearance of a spreadsheet.