Product Discovery
Recognize when spreadsheets need stronger operating controls
A spreadsheet does not need replacement simply because it is important. Evaluate editing rights, rule ownership, reconciliation, and recovery to decide whether stronger controls or a dedicated application are justified.
The warning sign is not the number of rows in a workbook. It is the gap between the consequences of an error and the controls around daily use. A small sheet can drive a critical decision. A large analytical workbook may remain appropriate when trained users review its outputs before action.
Inspect how the file becomes operational truth
Trace one record from its source to the decision it affects. Ask which copy is authoritative, who can change formulas, and how corrections reach downstream users. Observe the process rather than accepting a claim that everyone uses the same file.
GOV.UK discovery guidance includes existing processes, systems, and legacy technology among constraints to investigate.[1] Apply that approach before assuming a new application is necessary. The immediate problem may be ambiguous ownership or an uncontrolled handoff rather than spreadsheet software itself.
Look for control gaps with business consequences
Identify whether staff can distinguish approved records from drafts and detect changes after review. Check how imports, manual edits, and formula changes affect outputs. Ask the process owner to describe a failed run and demonstrate how the team would recover.
Access needs deserve a separate decision. OWASP recommends assigning only the privileges needed for a person’s job.[6] That principle can guide requirements for a replacement. Do not assume a shared workbook offers the required separation merely because some cells are visually protected.
Hypothetical example: a promotional allocation sheet
A hypothetical retailer allocates promotional stock in a shared workbook. Branch staff change quantities while a coordinator exports orders. The issue is not calculation speed. It is uncertainty about which allocation received approval and whether later edits entered the export.
The team first tries a controlled submission window, a named approver, and an identifiable approved snapshot. If these steps cannot meet operational needs, the application brief can specify approval states and export boundaries. No improvement percentage is assumed before the trial produces evidence.
Use a control-first decision checklist
Evaluate the workbook and its surrounding process together. A replacement should close demonstrated gaps, not just provide a more polished interface.
- Name the authoritative copy and the person responsible for its rules.
- Separate data entry, formula maintenance, and business approval responsibilities.
- Reconcile outputs against a known input sample before operational use.
- Demonstrate recovery from a mistaken edit or unavailable file.
- Define the conditions that make manual controls impractical.
Choose the smallest workable intervention
Stronger review and ownership may be enough when the process is infrequent and mistakes are detectable before action. A dedicated application becomes more compelling when the workflow needs enforced states, granular permissions, or coordination that manual controls cannot sustain.
An application still needs data definitions, exception handling, support, and an owner. Migration also introduces training and reconciliation work. Compare those costs with the observed control problem, then decide whether to improve the workbook, introduce a supporting tool, or replace the workflow.
