10 min read
In many asset-heavy organizations, the most important operational workflow does not live in the ERP. It lives in Excel.
Sometimes it is supported by emails, SharePoint folders, PDF instructions, local databases, paper printouts, and the memory of experienced people. The ERP may hold the asset record. The document system may hold the manual. The email thread may hold the approval. The spreadsheet may hold the task list. And the person who has worked there for 25 years may know why the official process does not quite work in practice.
That is the reality in many complex asset organizations. Excel still runs critical operations not because teams are careless, but because it solves a real problem. It gives people a flexible way to manage work when the official systems are too rigid, too slow, too difficult to use, or too far removed from how operations actually happen.
The problem is not that Excel exists. The problem is that organizations gradually ask spreadsheets to do work they were never designed to govern.
Excel can support analysis. It can help with planning. It can organize information. But Excel is not a maintenance execution system. It is not an audit trail. It is not a role-based workflow engine. It is not a reliable handover process. And it cannot provide operational visibility if the real work is scattered across files, inboxes, folders, and individual memory.
Read more: The Reality of Operational Workflows in Complex Asset Organizations
Excel persists because it works where official systems do not
There is a reason Excel survives in complex operations. It is familiar. It is already installed. It does not require a long implementation process. A planner can create a tracker in an afternoon. A maintainer can add a column. A project manager can filter by owner, asset, date, or status. A team can adapt it faster than they can request a change to an enterprise system.
In complex asset environments, workflows often change because the work itself changes. A deployment is adjusted. A maintenance task reveals an unexpected issue. A document is missing. A part is delayed. A customer asks for a different reporting format. A security requirement changes who can see what. Excel gives teams a way to respond without waiting for a formal system change.
This is why spreadsheet-based workflows are not just a “bad habit.” They are usually a symptom of a deeper workflow gap.
Enterprise systems are often designed around administration: resources, costs, procurement, inventory, compliance, and records. Those functions are important, but the daily execution of work is different. It involves ownership, timing, exceptions, handovers, approvals, evidence, and communication between people who may not sit in the same department or even the same organization.
When those execution needs are not supported well, teams build their own layer. And that layer is often Excel.
The problem is not tracking work, but rather governing it
A spreadsheet can track work. It can list assets, actions, owners, due dates, and comments. But tracking work is not the same as governing work.
A governed workflow controls how work moves. It defines who owns each step. It limits who can edit sensitive information. It shows what has changed. It captures evidence. It escalates overdue tasks. It preserves context during handovers. It keeps the organization aligned around one current version of reality.
Excel does not do that reliably.
It can show that a task exists, but not always whether the right person owns it. It can show that a task is marked complete, but not always who validated it. It can contain important evidence, but not always in a controlled or searchable way. It can be shared across a team, but it can also be copied, overwritten, emailed, downloaded, or edited without the level of control required for critical operations.
This is where spreadsheet based workflows risks start to appear.
At first, the spreadsheet is a useful workaround. Over time, it becomes the unofficial system of execution. Eventually, it becomes critical infrastructure without the controls normally expected from critical infrastructure.
The hidden risks of spreadsheet-based operations
The risk of Excel is not only that someone might enter the wrong number. The larger risk is that Excel makes operational control look stronger than it really is. A spreadsheet gives the appearance of structure: rows, columns, filters, comments, dates, and color codes. To the people using it every day, it can feel manageable. It may even feel safer than a new system because the team understands it and controls it directly. But that sense of control can be misleading.
1. Ownership becomes unclear
A spreadsheet can show that a task exists, but it does not always make ownership clear. A name in a column is not the same as a controlled assignment. People may not know they are responsible, tasks may not trigger reminders, and overdue work may only be noticed when someone manually checks the file.
In critical operations, this creates a quiet accountability problem. Work can appear assigned without being actively owned.
2. Changes are hard to trust
Spreadsheet workflows often depend on people editing the same shared file, sending local copies, or updating information after the fact. That makes it difficult to know which version is correct, who changed what, and whether the latest update reflects reality.
For maintenance, deployment, and asset workflows, this matters. If teams cannot trust the status, the evidence, or the version history, they spend time verifying the workflow instead of executing it.
3. Knowledge stays fragmented
Excel often holds part of the picture, but not the whole workflow. The task list may be in one file, the approval in an email, the document in SharePoint, and the exception in someone’s memory.
That creates a knowledge problem. The organization may technically “have” the information, but if it cannot access, connect, and act on it when needed, that information is not operational knowledge. This mirrors what military writers describe as an “unknown known” problem: the organization may possess relevant knowledge, but fail to recognize, access, or use it when it matters.
A spreadsheet full of information is not the same as a controlled workflow.
For a deeper look at these risks, read: The Hidden Risks of Spreadsheet-Based Workflows
Why replacing Excel is harder than it sounds
Replacing Excel is rarely as simple as telling people to stop using it.
Teams do not rely on spreadsheets because they enjoy manual work. They rely on them because the alternative often feels worse. The official system may be too complex. The ERP may be too far from the workflow. A new tool may require training, approvals, integrations, security reviews, and change management. In the short term, Excel feels faster.
This is especially true in defense, aerospace, manufacturing, and other complex asset environments where change is slow for good reasons. Security, compliance, data access, procurement and system reliability matters. Nobody wants to introduce a tool that creates new risk.
Defense economics offers a useful lens here. In The Case for Markets in Defence, Keith Hartley explains that transaction costs shape whether organizations handle activities internally or use outside solutions. These costs include searching for suppliers, negotiating contracts, and policing or enforcing agreements. High transaction costs can prevent better alternatives from being adopted, even when the existing setup is inefficient.
The same logic applies to operational software change.
Moving away from Excel introduces visible costs: procurement, implementation, migration, integration, validation, training, and adoption. Staying with Excel often hides the costs inside daily work: manual updates, repeated checks, missed tasks, weak traceability, poor visibility, and lost knowledge.
That is why Excel persists. The cost of change is obvious. The cost of staying the same is distributed across the operation.
This also explains why “just replace Excel” is the wrong message. Teams need a better operational workflow, not just a new interface. If the replacement does not make the real work easier, people will keep using the spreadsheet.
What good looks like instead
The goal is not to eliminate every spreadsheet.
Excel still has a place. It is useful for analysis, calculations, scenario planning, exports, temporary models, and one-off work. The problem begins when Excel becomes the operating layer for recurring, critical, multi-user workflows.
For asset-heavy organizations, a better model is structured execution.
Structured execution means the workflow itself becomes controlled. Tasks are assigned to the right roles. Access is based on responsibility. Changes are logged. Evidence is captured as part of the work. Templates make recurring processes consistent. Status is visible without asking someone to send an updated file. Handovers preserve context. The system supports the way maintainers, planners, fitters, operators, and support teams actually work.
This does not require replacing every existing enterprise system. In many organizations, ERP, PLM, MES, CMMS, and document systems still have important roles. They may remain the systems of record for financials, parts, assets, engineering data, or compliance documentation. The missing layer is often the system of execution: the place where work is planned, assigned, performed, validated, and made visible. Learn more in our article From Fragmented Systems to Unified Workflows
That is where Excel often sits today. The better approach is to replace uncontrolled spreadsheet execution with structured digital workflows that work with existing systems. The ERP can remain the system of record. The operational workflow can become the system of execution.
The Excel risk test
A simple way to test whether Excel has become a risk is to ask what would happen if the spreadsheet disappeared tomorrow.
Would the organization still know who owns each task? Would it know what is overdue? Would it know which asset is affected? Would it know what evidence has been captured? Would it know who approved the work? Would it know which version is correct? Would it know what changed since the last handover? Would it know what needs escalation?
If the answer is no, the spreadsheet is no longer just a tracker. It has become an uncontrolled operational system.
And if that spreadsheet supports critical assets, maintenance workflows, deployment planning, quality validation, or customer obligations, the organization is carrying more risk than it may realize.
Operational visibility cannot be created after the fact
One of the most common consequences of spreadsheet-based operations is weak visibility.
Leaders may receive reports. They may see exported summaries. They may review status meetings. But those views are often assembled after the work has already happened. Someone has to collect updates, clean the file, verify the numbers, and explain the exceptions.
That is not operational visibility. It is operational reconstruction.
Real visibility comes from the workflow itself. When tasks, owners, evidence, approvals, asset status, and exceptions are captured as work happens, leaders can see what is moving, what is blocked, what is overdue, and where risk is building.
This is particularly important in maintenance and sustainment. If data is inconsistent, delayed, or scattered across manual records, it becomes difficult to improve planning, reduce downtime, or move toward predictive maintenance. You cannot build reliable operational insight on top of fragmented execution. Learn to master operational visibility in this post.
Moving beyond Excel without disrupting the operation
The best replacement for Excel is not the most advanced system. It is the system people will actually use. That means it must be easier than the workaround. It must reflect the real workflow. It must reduce manual effort, not add another administrative burden. It must support the people doing the work, not only the people reviewing the reports.
A practical approach usually starts with the workflows where Excel is already carrying too much responsibility. That might be maintenance planning, deployment readiness, assembly task execution, quality validation, issue tracking, or OEM (Original Equipment Manufacturer)-operator collaboration.
From there, the goal is to structure the work without overcomplicating it.
Define the recurring workflow. Clarify roles and ownership. Identify where approvals, evidence, and handovers happen. Decide what needs to integrate with existing systems. Build templates where work repeats. Make status visible by default. Give frontline users an interface that makes their job easier.
That is how organizations move away from spreadsheet dependency without creating a new adoption problem. The objective is not digital transformation for its own sake. It is better execution.
Conclusion: Excel solved a real problem, but it cannot solve the next one
Excel still runs critical operations because it filled a gap. It gave teams flexibility where formal systems were too rigid. It helped people coordinate when no system matched the real workflow. It allowed operations to keep moving despite fragmented tools, slow change processes, and enterprise systems built more for administration than execution.
That is why Excel deserves a fair assessment. It is not useless. It is often the reason work continued despite imperfect systems.
But as operations become more complex, the limits become harder to ignore. A spreadsheet can track work, but it cannot reliably govern work. It can hold information, but it cannot ensure knowledge is accessible, trusted, and reusable. It can support a team, but it cannot provide the control, traceability, and visibility required for critical asset operations at scale.
The next step is not more spreadsheets. And it is not necessarily replacing the ERP. The next step is making operational work visible, structured, secure, and executable.
That is how complex asset organizations move from fragmented workarounds to workflows that can actually support readiness, reliability, and long-term lifecycle performance.
FAQ
Companies still use Excel because it is familiar, flexible, fast to adapt, and easier to modify than many enterprise systems. It often fills the gap between official systems and real operational work.
The main risks are weak ownership, limited access control, poor auditability, manual handovers, version confusion, missing reminders, and knowledge loss. These risks increase when spreadsheets are used to manage critical assets, maintenance work, approvals, or operational readiness.
No. Excel can be useful for analysis, planning, and lightweight tracking. It becomes a problem when it is used to govern critical asset workflows, maintenance execution, evidence capture, approvals, and accountability.
Maintenance teams should replace Excel when work involves multiple users, recurring tasks, asset history, approvals, security requirements, handovers, evidence capture, audit trails, or readiness reporting.
No. In complex asset organizations, ERP often remains the system of record. The better approach is usually to add a structured execution layer that connects enterprise systems with the real operational workflow.