Every company has them. The Excel spreadsheet that runs the warehouse. The personal Gmail account that handles vendor approvals. The Slack channel that replaced the ticketing system three years ago and nobody told IT.
We call them shadow systems. Not because they're sinister — but because they operate outside the official tooling, invisible to leadership, undocumented, and load-bearing. They are the duct tape holding operations together when the "real" systems fail.
They're not bugs. They're signals.
The instinct from IT leadership is to shut them down. Mandate the official tools. Enforce compliance. This is exactly the wrong response.
Shadow systems exist because the official tools failed the people using them. Every rogue spreadsheet is evidence of a broken workflow. Every personal email forwarding chain is a process that the enterprise system couldn't accommodate. Killing the workaround without fixing the root cause just pushes the pain deeper underground.
"I know I'm not supposed to use this spreadsheet. But the ERP takes 14 clicks to do what I can do in one formula."
That's a direct quote from a warehouse supervisor at a mid-market logistics company. Fourteen clicks. We timed it. The ERP's inventory adjustment flow took 14 clicks across 3 screens. His spreadsheet did the same calculation with a single VLOOKUP and a copy-paste. Of course he used the spreadsheet.
What we actually find
In a typical discovery engagement with a 50-200 person company, we find between 8 and 15 shadow systems. The most common patterns:
The spreadsheet that runs everything. There's always one. Usually maintained by one person who's been there for years. It has macros. It has conditional formatting that tells a story. It has tabs named after months. If that person gets hit by a bus, a critical business process stops functioning.
The email-based approval chain. Someone decided years ago that approvals should go through email. Now there's a 12-step forwarding chain involving people who don't even work there anymore. Nobody knows the full chain. Approvals take 3-5 days for what should take 3 minutes.
The Slack channel that replaced the tool. A team tried the official project management tool, found it cumbersome, and moved everything to a Slack channel. Now all project context, decisions, and file sharing happens in an ephemeral chat stream with no search, no assignment tracking, and no audit trail.
The personal account bridge. When the official integration between two systems doesn't work (or doesn't exist), someone creates a bridge using their personal account. Personal Gmail forwarding vendor POs. Personal Dropbox syncing files between departments. The company's data flowing through infrastructure they don't own or control.
The cost is always bigger than expected
When we aggregate shadow system usage across interview subjects and cost it at loaded salary rates, the number is consistently surprising. A 100-person company typically burns 2,000-4,000 hours per year maintaining workarounds that exist because official tools don't work for the people using them.
At a loaded cost of $45-65/hour for mid-level employees, that's $90K-260K annually in labor that produces no value — it just maintains the status quo. And that doesn't account for the error rates, the institutional risk of single-person dependencies, or the morale cost of making smart people do dumb work every day.
What to do about it
Don't kill the shadow systems. Map them. Every one is telling you where automation will deliver the highest payback. The warehouse supervisor's spreadsheet is a specification for an inventory adjustment API. The email approval chain is a workflow engine waiting to be built. The Slack channel is a project management tool that needs search, assignment, and persistence.
The fix isn't "make everyone use the official tools." The fix is "make the official tools work the way people actually work." And the fastest way to learn how people actually work is to ask them — then listen to where they built something better out of duct tape and frustration.
That's what discovery is for.