When Excel becomes the system: five signals it is time to build a workflow

Most teams do not choose Excel because they want to run a business from a spreadsheet. They choose it because it is available, flexible, and fast enough for the first version of a process. The trouble starts when that first version becomes the company’s operating system.

The five signals

1. There is a “master” file nobody is allowed to touch

If one person owns the latest version, the process has a single point of failure. People wait for access, create local copies, and then spend time reconciling which number is correct. That is not a collaboration problem; it is a system design problem.

2. The spreadsheet contains rules that only one person understands

Hidden formulas, colour conventions, protected tabs, and notes in cells are often undocumented business logic. When the person who built them is away, the organisation loses the ability to explain or safely change the process.

3. Approvals happen in another channel

A spreadsheet may record the result, while the real decision happens in LINE, email, or a conversation. This creates a gap between what the system says and what actually happened. An operational workflow should make the request, decision, owner, and timestamp visible together.

4. Reporting requires a weekly ritual

If somebody exports, cleans, copies, and reformats data every week before management can see it, the report is not a report. It is a manual data pipeline. The right first step is usually a focused data model and a small dashboard, not a giant analytics programme.

5. The team has built a shadow process around the file

Watch for inbox folders, checklists, duplicate trackers, screenshots, and reminders that exist only to make the spreadsheet usable. These are valuable clues. They show you the workflow the business needs, including the parts the spreadsheet was never designed to handle.

What to do before you build

• Map one complete case from request to completion, including every handoff.
• Name the decisions and exceptions, not only the happy path.
• Measure delay, rework, duplicate entry, and time spent producing reports.
• Choose the smallest workflow that would remove the most coordination work.
• Keep the spreadsheet as a read-only archive during rollout rather than migrating its confusion wholesale.

The goal is not to make a spreadsheet look like an app. It is to make the work legible, accountable, and easier to complete.

A focused workflow can be the right answer: an approval tool, an inspection app, a scheduling layer, or an internal portal. Start with the operational bottleneck. The technology should follow the process, not become another project to manage.