← All insights

Somebody in your business keeps a spreadsheet that duplicates what your main system already holds. Somebody rings ahead because a notification does not fire reliably. Somebody has memorised which five customers need handling differently, because the customer record has nowhere to put that.

None of them have raised it with you. That is not a loyalty problem or an effort problem. It is entirely predictable, and it happens for three reasons.

One. It stopped registering as a problem

A workaround that has survived two years is no longer experienced as a workaround. It is just how the job is done. Ask someone to list what slows them down and they will not mention it, in the same way you would not list your commute as an obstacle to getting to work. It has been absorbed into the shape of the role.

This is why asking your team what is broken produces so little. They will tell you about the thing that broke last week. The structural stuff has gone quiet.

Two. They raised it once and nothing happened

Most workarounds were reported at some point, usually early, often by the person who first hit the problem. The answer was that it would be looked at. It was not, or it was and the fix was too expensive that quarter, which from the outside looks identical.

People do not stop reporting problems because they have given up on the business. They stop because reporting has stopped producing outcomes, and inventing a workaround produces one immediately.

Three. The workaround has become theirs

This is the awkward one. A person who has built a clever workaround now owns something. They are the one who knows how it runs, and that is a real if unspoken piece of job security in a business where nothing else is written down.

Nobody is being cynical. It is simply that there is no incentive to hand over the one thing that makes you difficult to replace, particularly if handing it over means admitting you have been running a shadow system for eighteen months.

How to actually find them

Asking does not work, for all the reasons above. Watching does.

• Sit with someone doing a real job, start to finish. Not a demonstration and not a description. A live one, with the interruptions included.
• Count the applications they open. Every switch between systems is a place data is being carried by hand. Every switch that goes to a spreadsheet or a personal note file is a workaround.
• Listen for "I just". "I just copy it over here." "I just give her a ring to make sure." "I just keep a list." The word "just" is doing enormous work in those sentences and it almost always marks a compensating behaviour.
• Ask what happens when they are out. If the answer involves a specific person being briefed, or things simply waiting until they return, you have found a process that exists only in someone's head.
• Ask what they would fix with a free afternoon. This gets past the "is this worth mentioning" filter better than asking what is broken, because it invites a preference rather than a complaint.

Then treat them as evidence, not error

This matters more than the finding. If discovering a shadow spreadsheet leads to somebody being told off, you will not be shown the next one, and there is always a next one.

A workaround is not a failure of discipline. It is a piece of design. Somebody identified a gap between what the system offered and what the job required, and closed it themselves, usually on their own time, usually without being asked. The correct response is to ask what gap it was closing, and then close it properly.

Do that once, visibly, and the rest of them surface on their own.