Susan is the integration

A typical business runs on email, WhatsApp, a few spreadsheets, an accounting system and a shared drive. None of those systems talk to each other. Susan does.

What Susan actually does all day

The org chart says admin. The actual job: a request arrives by email or WhatsApp, and Susan carries it across every system it touches until the business has done what it promised.

She knows this customer’s deliveries go to the second address, not the one on file. She checks stock the way only she knows to, because the spreadsheet runs a day behind the warehouse. She updates two systems in the right order, because backwards creates a duplicate. None of it is written down. The procedure exists in exactly one place: Susan.

• the fieldsWhich ones matter, which ones lie.
• the exceptionsWho bypasses the rules, and who must not.
• the approvalsWhat she decides herself, what needs the boss.
• the smell testThe half-second pause when a request looks wrong.

Why nobody notices until she’s gone

While Susan is at her desk, all of this looks like “things working.” Then she takes two weeks off.

Someone else answers the email and ships to the address on file. Nothing errors. The mistake surfaces a week later as an angry phone call.

Resignation is the same event with no end date. The business doesn’t lose an employee — it loses the only working copy of its own operating procedures. The replacement inherits the logins, not the twelve years of exceptions.

The standard fixes, and why they fail

• hire a backupTwo people now hold slightly different versions, and they drift. You haven’t documented the knowledge; you’ve forked it.
• write the sopsThe binder captures the routine 80%. The exceptions — the actual job — never make it in.
• diy automationAutomates the happy path. Susan’s value was knowing when not to fire.

All three copy the tasks. The job was judgment applied to procedures.

What encoding Susan actually takes

Not “update the delivery date” — “update the delivery date, unless it’s one of these customers, unless stock says otherwise, and never without telling the warehouse.” Procedures, with their exceptions.

And her half-second pause. Executing is one of four things a request can deserve:

• executeswhen conditions are right
• clarifieswhen the request is unclear — queried, not guessed
• declineswhen the request is valid but creates a problem nobody can see yet
• escalateswhen a human should weigh in — with the context, not just the alarm

A system that always says yes is a fast intern. Susan says no several times a week, and every one of those no’s is money.

If a specific person came to mind while reading this, their workload is a map of your most valuable workflows. Start with the one they’d most gladly hand over.