Every business we work with has two systems running side by side. There's the official software, the stuff that got signed off, budgeted and rolled out properly, and then there's the spreadsheet nobody remembers commissioning, the one that somehow ended up running half the operation anyway.

There's actually a name for this

The sociologist Diane Vaughan coined a term while studying something far more serious than office spreadsheets: the Challenger space shuttle disaster. She called it the normalisation of deviance, where small departures from how things are meant to work become normal simply because nothing's gone wrong yet.

The same idea applies neatly to everyday data workflows, and it's an uncomfortably good fit. A quick fix works once, then twice, then becomes the way everyone does it, without anyone really deciding it should. It just sticks, until the day it doesn't.

The spreadsheet isn't actually the villain here

There's nothing wrong with a spreadsheet. It does what it was built to do, perfectly well. The problem starts when it becomes the system of record for something important without anyone ever actually deciding that's what it should be.

Formula errors can sit there for months without anyone noticing, and often the only person who understands how the whole thing works is the only one who knows why a particular calculation is even there. Then there's the version control problem: once a file has been emailed around and changed by three different teams, knowing which one is actually correct can become a job in itself. None of this means your spreadsheet is bad. It just means it's been asked to do a job it was never really designed for.

"The business logic doesn't need to change just because the software does. The only real difference is that none of it depends on one file, one formula or one person's memory anymore."

Where commissioned software actually comes in

This is roughly what commissioned software is for: not forcing a team onto something off the shelf that doesn't quite fit, but taking the logic that's already working and giving it somewhere sturdier to live. We do this a lot: pricing rules, reconciliation steps, calculations and workflows that ended up trapped inside a spreadsheet, built into something the whole team can use without crossing their fingers.

The best time to look is before it breaks

You don't have to wait for your system to collapse before calling us (we'd actually prefer it if you didn't). Get in touch, and we'll have a look at what's actually holding your process together, what you'd like to keep as is, and talk you through what moving it somewhere sturdier would involve.