The workaround is evidence

Every organisation has a workaround. The tracker updated before the CRM field exists. The approval that happens in email because the workflow cannot model the exception. The export that leaves the system of record because the report is wrong but fast. Leadership calls these habits, shortcuts, or shadow behaviour. Operations calls them Tuesday.

Constrange treats workarounds as evidence, not disobedience. They show where official design does not match reality: where speed conflicts with audit, where definitions split, where the tool was built for a process the organisation no longer runs. Reading workarounds well is one of the fastest ways to see what a transformation must actually carry.

Demonising workarounds produces hiding. Ignoring them produces go-live surprises. The mature move is to ask what pressure created the path — and whether the organisation is willing to remove that pressure or formalise the function the workaround serves.

What counts as a workaround

A workaround is any unofficial path that carries work the official stack was supposed to own. It includes spreadsheets, inboxes, chat channels, verbal handoffs, side integrations, and printed forms. It also includes official tools used unofficially: the CRM field everyone knows is wrong but fills anyway because the alternative is slower.

• Higher velocity than the official change process allows
• Exceptions the workflow engine cannot encode
• Definitions the enterprise never agreed
• Political safety — failure is invisible in the system of record
• Skill concentration — one person maintains the real logic

Why workarounds are rational

Teams do not wake up wanting shadow systems. They wake up with deadlines, clients, auditors, and incentives that reward shipping. When the official path is slow, rigid, or wrong, the unofficial path is rational. It absorbs variance. It preserves relationships. It keeps revenue moving.

Workarounds emerge when official tools are slow, rigid, or misaligned with incentives. They reward local speed. They are maintained because removing them without replacing function would stop revenue or breach trust. The organisation often knows the workaround exists. It prefers not to name it until a migration forces the conversation.

The table explains persistence, not virtue. A workaround is a signal that the official path lost a contest operations could not afford to lose.

Reading workarounds without blame

Discovery fails when it sounds like compliance enforcement on day one. Teams hide what keeps them employed. The better frame is design research: show us how work actually moves when the system is down, when the client is unusual, when the quarter is closing.

Blame produces theatre. Evidence produces design. When leadership names the workaround without punishing the maintainer, teams will show you the load-bearing paths. When leadership treats every unofficial route as disobedience, you will get a cleaner audit story and a less honest map.

1. Follow one high-volume object for a week — order, case, claim, candidate.
2. Ask what people check before they trust the official number.
3. Inventory exports that leave systems of record.
4. Listen for phrases: 'the real one', 'what we use', 'when it matters'.
5. Treat findings as requirements, not violations.

Three responses to evidence

Formalise

Bring the workaround into governance: owner, access control, change log, defined retirement of duplicates. Appropriate when the workaround is load-bearing and honest — when it encodes judgement the official tool cannot replace quickly.

Replace

Fix the official path until it is faster or simpler than the workaround. Requires definition work, integration honesty, and political will. Not a vendor checkbox.

Remove pressure

Sometimes the workaround exists because the organisation asks for impossible speed and perfect audit simultaneously. Collapse approval layers. Agree one definition. Stop measuring conflicting outcomes. Remove the pressure and the workaround may shrink without a fight.

Workarounds and transformation programmes

Programmes that mandate 'no spreadsheets' without replacing function fail quietly. The workaround mutates. It moves to inbox. It moves to chat. It moves to a personal database with a friendlier name.

Programmes that map workarounds early can sequence: formalise the load-bearing path while fixing the join, then narrow official scope until unofficial volume naturally falls. The goal is not purity. The goal is honest load-bearing design.

Patterns we see across sectors

In regulated environments, workarounds often carry judgement the official tool cannot encode: exceptions, overrides, client-specific terms. In high-growth firms, workarounds carry speed: a tracker updated before the CRM field exists. In cost-focused programmes, workarounds carry reconciliation between systems that were never integrated honestly.

The pattern is stable even when the tools differ. Official promises control. Workarounds carry the gap between policy and Tuesday. Naming that gap is the beginning of design.

Sector language changes. The structural move does not: read workarounds as requirements written in behaviour, not in a backlog.

“The workaround is not the enemy of the official system. It is the proof of where the official system failed to carry the work.”Constrange

Discovery without a witch hunt

The best discovery sounds like design research, not audit. Ask teams what they check before they trust the official number. Follow one object for a week. Review incident stories for recurring manual bridges. Treat findings as input to the programme, not as violations to punish on day one.

If discovery requires people to admit what keeps them employed, you will only hear the workarounds they are willing to sacrifice. Read evidence where work already flows.

When leadership misreads the evidence

The common failure is to see a workaround and respond with training. Training does not fix a path that is slower than the deadline. It does not fix a definition split between finance and operations. It does not fix a rule that forbids the official route. Training is appropriate when people do not know the official path. It is theatre when they know it and avoid it on purpose.

The second failure is to see a workaround and respond with a bigger platform. If the pressure that created the path remains — conflicting metrics, approval layers, split definitions — the new platform will grow its own unofficial layer within a quarter. Evidence without triage becomes another migration that deletes infrastructure nobody knew was load-bearing.

The mature response is triage in public: this path is load-bearing and we will formalise it; this path is duplicate and we will retire it; this path exists because policy has not caught up and we will fix policy first. Public triage builds trust. Secret mandates build shadow.

Risks of misreading evidence

Treating workarounds as laziness produces hiding and continuity risk. Treating every workaround as sacred produces sprawl. The discipline is triage: which paths are load-bearing, which are duplicate, which exist only because policy has not caught up with reality?

• Continuity risk when the maintainer leaves
• Quality risk from untested logic
• Compliance risk when auditors find the real path
• Security risk from unmanaged access
• Programme risk when migration deletes infrastructure nobody knew was infrastructure

A ninety-day reading programme

1. Month one: map the top five unofficial paths without blame — names, owners, triggers.
2. Month two: classify each path — formalise, replace, or remove pressure.
3. Month three: execute one move on the highest-risk path; measure reconciliation time or error rate.

Ninety days is enough to show whether leadership will change the official path or only rename the workaround. If unofficial volume grows during the programme, the official path is still losing.

Questions for your next operating review

• Which number do we act on when systems disagree?
• What breaks if the maintainer of the real tracker is unavailable for two weeks?
• Which approval happens only in email?
• What did the last migration assume would stop that did not?
• Which workaround would we formalise if we were honest about load?

If the room cannot answer, the workaround is running the review — not because people are disobedient, but because the official story is incomplete.

Constrange treats workaround discovery as the fastest requirements process most organisations already have — written in behaviour, not in a backlog. Read it before you fund the next platform.

The workaround is not a moral failure. It is evidence that the official path lost a contest operations could not afford to lose. Design from that evidence, or fund the same surprise again.

Read the workaround before you read the roadmap. The roadmap shows what leadership hopes will run. The workaround shows what already does.