The way your team does work is costing you more than you think

Every organization has two operating systems running at the same time: the one on the org chart, and the one people actually use to get work done. The gap between those two is where friction lives — and most of the time, it's invisible to leadership.

When I walk into a new team, I'm not looking at the process diagrams. I'm watching what people do at 3pm on a Tuesday. Where do they look first when they need a number? Which Slack channel do they DM when the official form is broken? Which spreadsheet gets opened more than the dashboard?

The answers tell you what the team actually runs on. Not what leadership thinks the team runs on. Not what the wiki says. What it actually runs on.

The first thing I look for

The first sign of shadow workflow is always the same: a tool being used for something it was never designed to do. Email becomes a queue. Slack becomes a database. A spreadsheet becomes the source of truth that two other systems pretend to be.

None of this is malicious. It's adaptation. People are doing the best they can with what's in front of them. The shadow OS exists because the official one didn't work — or worked, but slowly, or worked, but required permission they didn't have.

If you want to fix it, the worst thing you can do is take away the spreadsheet. The spreadsheet is a symptom, not the problem. Take it away and you've just made the team's day harder without addressing the friction underneath.

Three places shadow ops accumulate

Once you start looking, you see them everywhere. Three patterns show up in every organization I've watched up close, regardless of size or industry. The names change. The shape doesn't.

1. Email becomes the queue

   When the ticketing system is too slow, too rigid, or too political, email picks up the slack. Now you have a parallel queue with no SLA, no visibility, no analytics — and one person who knows where everything is.

2. Slack becomes the database

   Decisions get made in DMs. Files get pasted into channels. Six months later, nobody can find anything, but everyone agrees the meeting happened. The database with no schema, indexed by memory.

3. Spreadsheets become the source of truth

   The dashboard is wrong. Everyone knows it's wrong. The real numbers live in a spreadsheet someone updates manually each morning. The dashboard exists for the meeting. The spreadsheet exists for the work.

The cost of doing nothing

Friction is the most expensive line item nobody puts on the budget. It doesn't show up in spend. It shows up in time, in attention, in the small daily resignation of "this is just how it is." Multiplied across a team of fifty, across a year, that's a real number — but no one is measuring it, so no one acts on it.

The teams I've seen take this seriously do one thing first: they make the shadow visible. Not to punish anyone. To see what the team actually needs.

What good looks like

Good doesn't mean eliminating the shadow workflows. Good means catching up to them — building systems that match what people are already doing, instead of fighting them. The spreadsheet becomes a real tool. The Slack channel becomes a documented process. The shadow queue becomes the queue.

The work is the same. The official systems just stop being a fiction.