Replacing the tracking spreadsheet, one workflow at a time

The spreadsheet is one of the most successful pieces of software ever built, which is exactly why it ends up running things it was never meant to run. It starts as a quick way to track a handful of issues. A few months later it has twelve tabs, colour-coded by a convention only one person remembers, emailed around in versions nobody can reconcile.

Spreadsheets are brilliant for analysis and miserable for accountability. They don't know who changed what, they can't chase an overdue item, and the moment two people open the "master" copy you have two masters. The question isn't whether to move off them — it's how to do it without halting the work already in flight.

Where the spreadsheet quietly fails

A tracker has one job: make sure nothing falls through the cracks. Spreadsheets fail at it in specific, repeatable ways — no audit trail, no enforced ownership, no automatic reminders, no reporting that isn't a manual copy-and-paste. Each gap is survivable alone; together they mean items age silently and status is always somebody's best guess.

And the failure scales with success. The more the team leans on the sheet, the more expensive its blind spots become.

A spreadsheet records that work exists. A system makes sure it moves.

— On outgrowing the grid

Migrate by workflow, not big bang

The mistake is trying to replace everything at once. The smoother path moves one workflow at a time, starting with the one that hurts most:

• Pick the highest-friction process first. The tracker that's most chased, most argued over, most often overdue — that's where a system pays for itself fastest.
• Model it as it really runs. Capture the fields, stages and owners people already use informally, rather than an idealized version nobody follows.
• Run in parallel, briefly. Keep the sheet alive just long enough for the team to trust the new system before it's retired.
• Turn on automation last. Add routing, reminders and escalation once the workflow itself is settled — not while it's still moving.

What you get back

When a workflow moves into a real system you gain the one thing a spreadsheet can never offer: a single, current, accountable view of who owns what and what's overdue — built without a six-month project. Do it one workflow at a time, and the spreadsheet retires itself, quietly, as the team simply stops reaching for it.