Almost every operations platform we build replaces a spreadsheet, or more often a dozen of them. The spreadsheets are not the enemy. They are flexible, everyone knows how to use them, and they encode years of hard-won knowledge about how the business really works.
What they can't do is enforce a process. Anyone can type anything anywhere, status lives in cell colours, and the rules only exist in the heads of the people who built the sheet.
Write the process down first
Before designing a single screen, we map each workflow as a set of states and the handoffs between them. We pay special attention to the exceptions: the orders that skip a step, the approvals that need a second person, the things someone 'just knows' to check.
- What are the stages a piece of work moves through?
- Who owns it at each stage, and who needs to know when it moves?
- What must be true before it can move forward?
- What happens when something goes wrong?
Structure before automation
It is tempting to automate everything on day one. We add structure first: defined stages, clear owners, due dates. Once the team is working inside that structure and it matches reality, we automate the transitions that are predictable.
Migrate in slices
A big-bang switchover asks the whole team to stop and learn a new system at once. Instead we move one workflow at a time, importing its data and running it in the platform while the rest continues as before. Each slice builds confidence for the next.
The goal isn't to take the spreadsheet away. It's to make the platform so obviously better that nobody opens the spreadsheet again.
The result is a system where every piece of work has a clear owner and status, managers see bottlenecks instead of chasing updates, and the process survives when the person who built the spreadsheet goes on holiday.