4 min readJun 20, 2026

By Jonas AnderssonCo-founderJun 20, 2026

4 min readJun 20, 2026

Field note

When spreadsheets stop working

A spreadsheet is often the right first tool. It is flexible, fast, and easy to change. The problem starts when the spreadsheet stops supporting the workflow and quietly becomes the workflow.

That is usually when teams start exporting the same data to different places, arguing about the source of truth, and relying on memory to keep the operation moving.

Red flags

The signs are usually practical, not dramatic.

You do not need a grand digital transformation warning sign. You need to notice when the same small workarounds keep appearing every week.

Data is exported to three places

Reports, CRM updates, and delivery notes all depend on slightly different copies of the truth.

Follow-up happens if someone remembers

The sheet tracks the fact that something should happen, but not enough to make it happen reliably.

Nobody trusts the current version

People ask which tab, which export, or which person has the latest answer.

In this articleTap to open the section map

Overview
Red flags
The real issue
Better question
Audit checklist

The real issue

A spreadsheet breaks when it has to behave like a system.

The moment it needs ownership, alerts, history, permissions, intake rules, or reliable handoffs, it is no longer just a spreadsheet. It is doing system work without system support.

That is the moment to stop asking the sheet to become smarter and start asking what surrounding workflow it is trying to replace.

The fix often starts outside the file: who creates the record, who updates it, and what should happen when the next step is overdue.

There is no clear owner for the next step.

Updates are copied instead of synced.

Important context lives in comments, messages, or memory.

Reporting takes cleanup before anyone believes it.

Better question

The spreadsheet is not the problem. The problem is being asked to control work it cannot.

A spreadsheet can hold a list. It cannot reliably enforce ownership, protect context, route exceptions, or tell the team when a workflow has drifted away from the truth.

CRM vs Spreadsheet: When to Move On ->

Audit checklist

A useful audit starts with four questions.

01
Where does data enter?
List the forms, tools, people, imports, and manual updates that create the first version of the record.
02
Where does it get copied?
Find every export, duplicated tab, manual report, and second system that depends on the same information.
03
Where does ownership disappear?
Mark the handoffs where nobody can quickly say who owns the next step.
04
Where does trust fail?
Find the reports or views people check twice because they do not quite believe the data.

Where does data enter?
List the forms, tools, people, imports, and manual updates that create the first version of the record.
Where does it get copied?
Find every export, duplicated tab, manual report, and second system that depends on the same information.
Where does ownership disappear?
Mark the handoffs where nobody can quickly say who owns the next step.
Where does trust fail?
Find the reports or views people check twice because they do not quite believe the data.

Key takeaways

Spreadsheets become liabilities when they stop supporting the workflow and quietly become the workflow.
The clearest signs: two people overwrite each other, history lives in email, multiple versions exist.
The decision is not about row count. It is about what the data needs to do.

If you only remember one thing

A spreadsheet is often the right first tool. The problem starts when it stops supporting the workflow and becomes it.

Data & Visibility Spreadsheets Source of truth

Continue the thinking

Part of this guide

Data Visibility for Commercial Teams: The Complete GuidePrincipleA derived path to the complete guide for this systems problem.15 min

CRM vs Spreadsheet: When to Move OnPrincipleExplores a neighboring systems problem from a different operational angle.5 min

What Is a Single Source of Truth in Operations?DefinitionExplores a neighboring systems problem from a different operational angle.5 min

Sources

References behind this piece

Government Data Quality Framework: guidance
Government Digital Service

Written by

Jonas Andersson

Co-founder, Mannvit Labs

Co-founder of Mannvit Labs, leading systems, data, automation, and technical delivery. He spent four years before this running e-commerce for a Swedish retailer, from SEO to campaigns.

He builds the internal tools and data workflows these guides come out of. See the builds.

Commercial data & reporting
CRM data quality
Process optimization

Connect on LinkedIn More from Jonas

Data & Visibility

Spreadsheets Source of truth

By Jonas Andersson

4 min readJun 20, 2026

By Jonas AnderssonCo-founderJun 20, 2026

4 min readJun 20, 2026

Field note

When spreadsheets stop working

A spreadsheet is often the right first tool. It is flexible, fast, and easy to change. The problem starts when the spreadsheet stops supporting the workflow and quietly becomes the workflow.

That is usually when teams start exporting the same data to different places, arguing about the source of truth, and relying on memory to keep the operation moving.

Red flags