Most software doesn’t fail in one dramatic moment. It drifts. The people who built it move on, the reasons behind its quirks fade, and the documentation — if it ever existed — stops matching reality. One day you realise the system running a good part of your business still works perfectly well, but nobody can quite explain how.
That’s a black box: inputs go in, results come out, and the part in the middle has gone dark. It isn’t a crisis — which is exactly why it’s easy to miss. The trouble only shows up the day you need to change something, prove something, or fix something, and the lights won’t come back on.
Here are three signs it’s already happening.
Nobody can tell you why it does what it does. You ask a reasonable question — why it calculates a figure that way, why a step happens in that order — and the honest answer is a shrug. “It’s always done that.” The system still behaves correctly, but the reasoning behind it has left the building. The logic lives only in the code now, and the code isn’t talking.
Changing anything has become a held breath. An adjustment that should take an afternoon turns into a fortnight of caution, or quietly never happens. People would rather build a workaround — another spreadsheet, a manual re-keying step, a “just do it by hand for now” — than touch the system itself. When the cost of change climbs that high, it’s usually because no one is confident what a change might break.
One person is the system’s memory — or worse, no one is. There’s a single person who knows how it works, and the business holds its breath when they’re on leave. Or that person has already moved on, and the honest answer is that nobody knows. Either way, the understanding your business depends on sits in one head, or even none — not anywhere you can rely on.
None of this means you’ve done something wrong. Black boxes form in well-run businesses precisely because the software kept working and never asked for attention, so attention went where it was needed instead. The catch is that the risk compounds quietly, and tends to present its bill at the worst possible moment: an audit, a key departure, a change you can no longer put off.
The reassuring part is that a black box can be opened. The first job isn’t to rebuild anything — it’s to get the system understood again: what it does, why it does it, and what the business genuinely depends on. Once that’s back in the light, you can make calm, informed decisions rather than nervous ones.
If that’s quietly where you’ve ended up, it’s exactly the work a Discovery & Roadmap is built for — turning the black box back into something you can see into, and act on with confidence.