← All Field Notes

Field Note 001

The Workaround Trap

When a workaround keeps the work moving, it can also hide the weakness that made the workaround necessary.

The fix that becomes the system

Every organization has workarounds. A spreadsheet built because the system cannot produce the right report. A side conversation that happens because the formal handoff is unreliable. One experienced employee who knows how to resolve the exceptions nobody documented.

At first, these are acts of competence. Someone notices a gap and keeps the work moving. The trouble begins when that temporary response becomes the normal way the organization operates.

What the workaround hides

A successful workaround reduces the immediate pressure to address its cause. The report arrives. The customer gets an answer. The deadline is met. From the outside, the system appears to work.

But the cost has not disappeared. It has moved into someone’s attention, memory, relationships, or extra hours. The organization starts depending on invisible labor while losing sight of the weakness that made that labor necessary.

Over time, the workaround creates a trap:

  • The more reliable the workaround becomes, the less urgent the underlying problem appears.
  • The more the organization depends on it, the riskier it feels to change.
  • The person carrying it becomes indispensable—and overloaded.
  • New tools are layered onto the workaround instead of repairing the work.

A better question

When you find a workaround, do not begin by asking how to automate it. Ask: What condition makes this workaround necessary?

That question shifts attention from the person’s improvised solution to the system around the work. It may reveal unclear ownership, missing information, a poorly designed handoff, conflicting measures, or a tool that does not fit the job.

The workaround is not the failure. It is evidence. Treat it as a field observation—then use it to make the organization more capable.

A move to make

Choose one recurring workaround your team relies on. Trace it backward. What problem was it created to solve? What would need to be true for the workaround to become unnecessary?

Do not remove the workaround before the system can carry the work. Strengthen the system first.

What workarounds has your organization learned to live with?

Start a conversation