Geyto Research · Juan Ferreiro · Essay · · 2 min read

Workarounds are evidence

The parallel spreadsheet is not only a discipline problem. It is also information about what the change has not yet solved, worth reading before banning it.

Every implementation leaves traces. A spreadsheet someone keeps filling in "just in case". A notebook where orders are written down before they are entered. A message group where people sort out what the system won't let them sort out.

One reaction to those traces is to want them gone. They are read as resistance, lack of discipline or habit. Sometimes they are. But treating them only that way loses something valuable: a workaround is an answer. Someone found that the work asked for something the new way of doing it did not provide, and solved it with what was at hand.

What a workaround says

A workaround does not prove that people don't want to change, and it does not point to a single cause on its own. It is a signal to investigate, and it can say something more precise:

  • that there is a step the system doesn't cover, or covers at a moment that doesn't help;
  • that a piece of information that used to be visible is now hidden;
  • that a decision one person used to make no longer has a clear owner;
  • that the support that existed during the launch is no longer there.

Each of those readings points somewhere different. Some call for adjusting the initiative: its sequence, its configuration, what it asks for first. Others call for building capacity where the work happens: judgement, coordination, a moment to practise.

Look before you ban

Banning a workaround without understanding it can simply move it. The spreadsheet leaves the shared folder and lands on someone's desktop. The problem is still there, but no one can see it.

Looking at the workaround with curiosity changes the conversation. Instead of asking why don't they use the system, the question becomes what did they need that the system didn't give them. That question has concrete answers, and someone on the team may already know them.

A simple way to start

List the workarounds everyone knows about. For each one, note what it solves, who keeps it going and since when. Then separate the ones that point to something the initiative can adjust from the ones that point to missing capacity.

It isn't a full diagnosis. It is a way of taking seriously what the work is already saying.

Geyto Research publishes essays, evidence reviews, market notes and framework notes on what happens after go-live. If you are working on a change that has gone live but hasn't yet landed, we would like to hear about it.

Share