data.day
risk-management / documentation / process-design

The Day the Intern Became the System

We rely on 'Dave' to fix the data. This is not a process. This is a liability. When knowledge lives in one head, the business is fragile.

Ingrid Pipeline Ingrid Pipeline

The Flu Virus vs. The Enterprise

It was a Tuesday. The concrete trucks were queuing at the gate. The drivers needed the QR codes to enter. The codes were not working. The site foreman called the office. “Get the codes.”

The Operations Director looked around the open-plan office. He looked at the empty chair. “Where is the intern?” he asked. “He has the flu,” someone said. “He is out for the week.”

Silence. Nobody else knew how to generate the QR codes. The intern ran a manual script on his laptop. The password was on a sticky note in his pocket. The trucks waited. The concrete began to cure in the drums. We lost $15,000 of material because a 22-year-old had a fever.

The Fragile Link: The Single Point of Failure

We talk about server redundancy. We rarely talk about cognitive redundancy. In many companies, the “System” is just a person who remembers which button to click. This is Fragile.

It is lazy management. We let processes accrete around helpful people.

  • “Just send it to Mike.”
  • “Mike handles that.”
  • “Mike knows the trick.”

Mike becomes a bottleneck. Mike becomes stressed. And when Mike leaves, the knowledge leaves with him. This is not an asset. This is an undocumented liability.

The Sturdy Fix: Externalize the Logic

We need to pull the logic out of the brain and put it into the tool. The rule is simple: If a process requires a specific human, it is broken.

We fixed the QR code problem.

  1. Map it: We asked the intern (when he returned) to write down the steps.
  2. Script it: We turned his manual clicks into a button on the dashboard.
  3. Test it: We unplugged the intern’s laptop and asked the Director to push the button.

It worked. Now, the intern is working on safety analysis. He is adding value. He is not just a cog in a broken machine.

Respect the Process

Do not praise the “Hero” who stays late to fix the data manually. The Hero is hiding the flaw in the plumbing. Fix the plumbing. Make the system boring. Make it reliable. Make it so the work flows even when the office is empty.

FAQs

But Sarah does it faster than the software.

She does it faster today. She does it slower when she is tired. And she does it zero times when she is on holiday.

How do we extract the knowledge?

Sit with her. Watch her screen. Record the steps. If it takes more than 5 steps, automate it.

Is this about firing Sarah?

No. It is about freeing Sarah. She should be solving problems, not acting as a human router for CSV files.