Twenty-Three Tabs and a Free Account: Auditing the Workflow Nobody Signed Off

There's a moment in most workflow reviews where someone opens their laptop to "just check something" and the room goes a bit quiet. Forty-one tabs. A free-tier kanban nobody mentioned. A spreadsheet called FINAL_v3_real.xlsx living in a personal OneDrive. A Chrome extension that scrapes a supplier portal because the portal has no export button.

None of it is on the diagram. All of it is load-bearing.

Call it the shadow workflow: the unsanctioned layer of tabs, plug-ins, free accounts and copy-paste bridges that people built because the official process didn't quite fit the job. It isn't sabotage. It's usually the most pragmatic thing in the building. But it's also invisible until it breaks, someone leaves, or a client asks a perfectly reasonable question about where their data is sitting.

Why start with the browser and not the software register

Most organisations audit tools by pulling a list of licence payments. That tells you what the finance team knows about. It tells you almost nothing about how work actually moves, because the interesting stuff is frequently free, freemium, or on someone's personal card for £8 a month.

The browser is the honest artefact. It shows the route a task actually takes — the portal, the converter, the PDF fiddler, the AI summariser that someone pasted a contract into at 4:50pm on a Friday. If your official process is the A-road and the shadow workflow is a series of farm tracks, the tabs are the map.

So the audit starts there. Not with a network scan, not with a stern email about shadow IT, and definitely not with a slide titled Tool Rationalisation Programme.

Three questions, and no blame

The framing matters more than the method. If people think the exercise ends with someone's free account being cancelled and a mild telling-off, they'll hide the tabs and you'll learn nothing. You'll get a tidy report and a workflow that keeps running exactly as before, just further underground.

Instead, ask three questions of every tool you find:

What would stop if this vanished tomorrow? This separates genuine dependencies from abandoned experiments. Half the tabs will be things someone opened once in March and never closed. Those don't need a policy, they need a tab cull.

Who else depends on it, and do they know? A tool used by one person is a quirk. A tool used by nine people across three teams is infrastructure with no owner, and that's the category that needs attention.

What data passes through it, and where does it land? Keep this light. You're not running a full data protection impact assessment over a team's lunch-order spreadsheet. You're spotting the cases where customer details, staff records or commercially sensitive material are leaving the building via something with a terms-of-service page nobody read.

That third question is the one that eventually drags in the information governance crowd, and it should — but bring them in late, once you've got a real picture. A compliance-led audit from day one gets you a clean spreadsheet and a team that has learned to use their phones instead.

Running the walkthrough in practice

The most useful format we've seen is short and slightly awkward: twenty minutes, screen shared, with the person who does the job narrating a single piece of real work from start to finish. Not a demonstration of the ideal process — an honest run at a genuine task.

Ask them to open everything they'd normally open. Then watch where the time goes. The moment someone says "and then I just…" is usually where the interesting tool lives. "And then I just paste it into this thing." "And then I just drag it across." "And then I just re-type it because the export's rubbish."

Capture three columns as you go: the step, the tool it happens in, and the workaround (if any). Twenty minutes per person, six to ten people, and you'll have a map that looks nothing like the process documentation and considerably more like reality.

A few practical notes for UK teams:

• Timing. Do it in the quiet stretch before the December shutdown, or in late January when the year's shape is clear. Avoid the week a big deadline lands, because you'll get a performance of the process rather than the process.
• Who to include. Skip the org chart. Ask the person who trains new starters, the one who covers for holidays, and the one everyone quietly asks when something breaks. That last person is almost always sitting on the most workarounds.
• Record it, briefly. A five-minute screen recording per walkthrough beats a long written summary nobody reads. Your future self will thank you when the tool owner leaves.

Adopt, integrate, or retire

Once you've got the map, every shadow tool lands in one of three buckets. Be honest about which is which, and don't let the neatness of the framework push you into decisions the evidence doesn't support.

Adopt means the workaround is genuinely better than the sanctioned route and solves a real problem the official process ignores. Buy it properly, name an owner, put it on the register, give it a login policy. A shadow tool that becomes official stops being a risk and starts being an asset — and you've just learned something about your official process for free.

Integrate means the function is needed but the standalone tool is the problem. That's a connector, an API, or a proper export. It costs a bit of development time and saves an entire class of copy-paste error.

Retire means the tool exists because of a gap that no longer exists, or because someone solved the same problem twice. Retire it gently. If you just switch it off, the person who built it will build it again by Thursday, only quieter.

The trap is treating this as a one-off clean-up. Shadow workflows regrow, because official processes don't keep up with the job. The point of the audit isn't a tidy estate — it's knowing where the farm tracks are before you need to drive down one in a hurry.

The bit everyone skips

Schedule the next one now. Six months out, same format, same three questions, same non-punitive framing. Put it in the calendar as something less alarming than audit — a workflow check-in, a tools review, whatever gets people to turn up without assuming they're in trouble.

The teams that handle change well aren't the ones with no shadow tools. They're the ones who know about theirs, and have decided, deliberately, which ones to keep.