Ben Hollebon

Fix what exists before you build something new

A case for repairing what already exists before commissioning something new, and why repair is harder to see and harder to fund than a fresh build.

Brown and white brick wall

One of the first pieces of work I did in a large federated organisation was an audit of its public directory. That’s the page that tells someone where their nearest branch is and how to get in touch with it. About 30% of its website links no longer worked.

Nobody had decided to let them rot. Each branch had made its own choice about its own website, or made no choice at all, and the broken links piled up over years, unnoticed, because nobody had the job of noticing them. There are thousands of those branches, each legally its own thing. The centre can’t instruct them. What holds the organisation together is a shared sense of belonging.

When something breaks in a long-running organisation, the reflex is to commission a new platform or tool. I think that reflex is usually wrong. It’s better to look hard at what’s already there and fix it first, even though that kind of work rarely gets funded and never gets a launch date.

We didn’t build anything new to fix the directory. We spent a few weeks correcting the data: checking every link, updating the ones that had moved and removing the ones that pointed nowhere. There was nothing to demo in a board meeting. But a lot more people looking for their nearest branch could now find it and get in touch. Across the organisation, the share of branches with a working web presence went from 58% to 76%.

I’m no better at resisting the new thing than the organisations I’m about to describe. On a personal software project, with no board and no politics involved at all, it was easier to add a new feature than to go back and write tests for what already existed. Checking that the basics were in place lost out too. There was no sponsor to impress and no launch to schedule, so what a board can see can’t be the whole explanation for why the new thing wins.

Why repair loses the argument

Building something new is visible. It has a name and a launch date, and you can point at it and say: we did that. Fixing what already exists has none of that. Nobody watching from a distance notices when a broken link starts working again.

I think this is why organisations that have been running for decades, the ones with the most to fix, keep funding new builds ahead of repair. A board that approves a new platform can see, in outline, what it bought. Asked to fund months of fixing something that should already work, the same board can’t see anything bought at all. From where they sit it looks like nothing is happening.

The people who run these systems day to day can describe exactly what’s wrong, because they work round it every week. By the time the problem reaches the people who allocate money, it has become something vaguer, like a sense that the system isn’t fit for purpose. That usually gets answered with a new one.

What federation does to this problem

Federation makes this worse. In an ordinary hierarchy, someone can at least be told to go and fix the directory. In ours, every branch would have had to decide to check its own page.

It also makes repair harder to sell. A new platform is one of the few things every part of a federation can be shown at the same time. A repair is a long run of small corrections, each one visible only to the branch it happened in. There was no launch event for the directory.

Sometimes a new build is the right call, because the existing system can’t do the job. But before commissioning anything new, it’s worth asking a duller question first: is what we already have beyond repair, or has nobody been asked to fix it yet? In my experience it’s usually the second.

How do you make that case to a sponsor whose whole idea of progress is a new launch, when you’re recommending months of fixing what’s already there? I don’t have a good answer. Every version of the argument I’ve tried only works once the fixing is done and there’s a number to point at.

Ben

Photograph by SJ Objio.