Spreadsheets as the First Draft of Operational Systems
Part of a short series on how operational systems emerge and how they can be formalised. Looking at how spreadsheets reveal the structure of operational work.
Most operational systems do not begin as software projects.
They begin as spreadsheets.
A team needs to track jobs, shipments, assets, or requests. A spreadsheet is created. Columns are added. Status values appear. Reporting tabs grow around it.
Over time the spreadsheet becomes the place where the operation is understood.
What appears inside the spreadsheet
If you examine a working spreadsheet, a structure becomes visible.
You can usually identify:
- operational entities (jobs, shipments, assets)
- relationships (customer, location, assignment)
- workflow state (status, stage, progress)
These are not just data fields. They describe how the operation actually works.
When the spreadsheet becomes the system
As usage grows, the spreadsheet is no longer just a record.
It becomes:
- the source of reporting
- the way workflow is tracked
- the reference point for decisions
At that point, the spreadsheet is already functioning as a system.
The key insight
The spreadsheet is not the problem.
It is the first place where the structure of the operation becomes visible.
The issue is that this structure remains implicit.
Focusing on how operational structure emerges. Next → Structure Before Software