Problem
Every business we meet has a spreadsheet that started as a simple list and quietly became the system of record. Orders, approvals, tracking and reporting all flow through one file, usually shared by email or a sync folder.
Root Cause
The spreadsheet is not the problem — it is the symptom of an unmade model. The business has real objects (orders, assignments, approvals, statuses) that were never modelled as data. The spreadsheet was the fastest way to hold them without deciding what they really are.
Architecture
A real system replaces the file with connected records: each object gets a type, each status becomes a defined state, each user gets a role, and each action leaves an audit trail. The workflow that used to live in colour-coded cells becomes enforced logic.
Solution
The transition is done by mapping the columns first. Every column is a field, every colour highlight is a status, every merged cell is a relationship waiting to be expressed. The model builds itself once the workflow is actually understood.
Implementation
We import the live records, roll out one workflow at a time, and keep the spreadsheet as a temporary view until the team trusts the system. Nobody is asked to learn a new world overnight.
Trade-offs
You lose the spreadsheet's instant flexibility: adding a column now means a deliberate change. In exchange you gain concurrency, permissions, enforcement and reporting that actually reflects reality.
Verification
The system is verified by the reports it produces: if management can answer 'what is the current state of every order' without asking anyone, the system is working.
Lessons
Do not buy software to replace the spreadsheet. Understand the workflow first — the software decision becomes obvious afterwards. That is the whole method in one paragraph.
Galaxy DigiLabs · Engineering Notes
All Notes →