You've Outgrown Excel: The Signs, and the Path to a Real System

A spreadsheet becomes a business risk at the point where nobody can answer a simple question without finding the right file, the right person, and the right sequence of instructions. The answer is not to ban Excel. It is to move the operational process that now needs shared control into a real system.

Owners often notice the problem late. The file still opens. The totals still look plausible. Staff have learned workarounds and the person who built the formulas is still available, most days. Then a customer disputes an invoice, a manager asks for a branch comparison, or the finance lead takes leave, and the business discovers that the spreadsheet was carrying far more than numbers.

What are the signs that Excel has become the risk?

Look for patterns in the work, not the number of rows in a workbook. Five signs matter most.

1. There are several versions of the same truth. A file arrives by email, a copy sits on a laptop, another version is in a WhatsApp group, and nobody is certain which one fed the last report. Cloud co-authoring can reduce this problem, but Microsoft’s own guidance still depends on supported file formats, cloud storage, AutoSave, version history, and users reopening the latest version when prompted. That is a controlled collaboration setup, not permission to treat every workbook as a system of record.
2. One person is the translation layer. If only one member of staff understands the tabs, hidden rows, macros, or manual adjustments, the process has a key-person dependency. The risk is not only absence. It is that a business rule lives in memory rather than in a visible workflow.
3. Numbers stop reconciling cleanly. Sales do not match the cash received. Stock in one workbook does not match stock in another. The monthly total changes when someone refreshes a file. A spreadsheet can calculate correctly and still produce an unreliable business process when inputs, timing, and ownership are unclear.
4. Manual consolidation consumes the reporting week. Staff export files, rename columns, copy values, remove duplicates, repair formats, and rebuild the same report every month. That time is often described as “just admin”. It is a recurring operating cost, and it creates several opportunities for a number to change without a trace.
5. The workbook is too important to test casually. Ray Panko’s University of Hawai‘i research, cited by ICAEW, is often summarised as finding mistakes in as many as 90% of spreadsheets examined. The figure is a warning about error exposure, not a claim that every workbook is wrong. If a model decides pricing, stock orders, payroll, cash forecasts, or regulatory reporting, it deserves review, documentation, access control, and a recovery plan.

When is the tipping point serious enough to act?

Use four tests. If a process passes three, stop treating the problem as a spreadsheet tidy-up.

• Decision test: does a manager, lender, customer, regulator, or supplier rely on the output?
• Shared-work test: do several people enter, edit, approve, or interpret the data?
• Change test: do prices, products, branches, currencies, permissions, or reporting rules change often?
• Recovery test: could the team rebuild the process if the file were corrupted or its author left tomorrow?

This is why a small organisation can need a system before a large one. A five-person distributor with daily stock movements may have a higher control burden than a twenty-person consultancy that uses a workbook once a quarter. Complexity is measured by the decisions and handoffs around the file, not by headcount alone.

What should you migrate first?

Do not start by listing every spreadsheet in the company and promising to replace them all. That creates a technology project with no first result. Start with one workflow that is frequent, shared, costly to correct, and easy to measure.

A practical first candidate might be sales and invoicing, purchasing and stock, job tracking, debtor follow-up, or management reporting. The right choice depends on where the current workbook creates the most rework. A useful selection score is:

Keep Excel in the picture where it is still good at analysis. The new system should own transactions, permissions, approvals, and the official report. Excel can receive a controlled export for a one-off scenario or a board analysis. That boundary gives people flexibility without letting a personal workbook quietly become the official ledger again.

What is a calm, phased migration path?

1. Map the current process before choosing the tool

Follow one transaction from start to finish. Who enters it? What evidence is attached? Who checks it? Which formula changes it? Where is the final approval? Which report uses it? Write the answers down. You will find that the workbook is often hiding three separate needs: a data register, a workflow, and a report.

2. Stabilise the rules and the minimum data set

Agree names, codes, units, dates, currencies, approval roles, and the definition of each key total. Do not attempt to clean ten years of every record before anyone sees a working system. Bring across the active master data and the opening balances or records needed for the first controlled period. Keep the old archive read-only while the new process settles.

3. Build the first workflow around control

A real system should make the important path visible: who can enter, who can approve, what changed, when it changed, and which report is current. It should also provide a clean export. A system that traps your information is not a solution; it is a new dependency.

4. Run a short parallel period

Run the new workflow alongside the workbook long enough to compare real transactions. Reconcile totals daily or weekly, depending on the process. Record each difference, decide whether it comes from data, timing, a rule, or user behaviour, and fix the cause rather than editing the output until it matches.

5. Train by role, then retire old steps

Do not give every user the same two-hour demonstration. A cashier, storekeeper, supervisor, accountant, and owner need different tasks and different permissions. Use the team’s real transactions. When the new process has passed reconciliation, remove the old data-entry steps. Keeping both systems open forever creates two competing truths.

How do you bring staff with you?

Staff resistance is often a sensible response to a poor migration. People worry that a new system will expose mistakes, slow down work, remove a useful shortcut, or create extra reporting. Listen for the specific fear, then deal with it in the design.

Give the team three things early: a clear reason for the change, a visible decision about what the system will and will not control, and a named person who can resolve questions. Let experienced users test the workflow before it is fixed. Keep the first release small enough to correct without blame.

The strongest adoption message is concrete: “You will stop copying this report every Friday,” “you will see the approval status without calling finance,” or “you will not have to re-enter the same customer details in three files.” A system earns trust when it removes a repeated burden.

What does success look like after the migration?

Measure the operating change, not the number of screens delivered. Within the first one or two reporting cycles, ask:

• Can two authorised users produce the same report from the same source?
• How long does reconciliation take now?
• How many manual handoffs disappeared?
• Can management see who changed a record and why?
• Can the business export its data in a usable format?
• What still depends on one person or an undocumented workaround?

If the answers are not improving, do not add more modules. Fix the first workflow. The right system is the one the team can run, check, and recover, not the one with the longest feature list.

From a failing spreadsheet to a stronger operating system

Excel usually does not fail in one dramatic moment. It becomes the place where version history, business rules, approvals, and institutional memory quietly accumulate. That is why a migration should begin before the workbook breaks in public.

Keep Excel for the work it does well. Move the process that needs shared control. Start with one workflow, prove the numbers, train the people who use it, and expand only after the first change is stable. If you want help deciding which process to move first, book a consultation or review the approach to business systems for East African organisations.