All notes

The System That Needs a Translator Is Already Broken

If your system requires a translator to function, the system is the problem.

Not the users. Not the training materials. The system.

There’s a pattern in professional tools where complexity gets normalized over time. The people who built it learned the quirks. The people who inherited it learned the workarounds. Eventually, knowing how to navigate the dysfunction becomes a skill in itself — and that skill gets mistaken for expertise.

It isn’t.

Real expertise is understanding why a process exists, what outcome it produces, and how to improve it. Memorizing which buttons to click in which order to avoid a crash is just damage control with good posture.

Scott Andrew Alpaugh has seen this in supply chain, in operations, in software: the moment a team starts hiring for “experience with our system” instead of “good judgment,” they’ve outsourced their thinking to the tool’s failure modes.

The test is simple. Hand your process to someone competent but unfamiliar. Watch where they hesitate. Every hesitation is a question your system should have answered before they got there.

Good tools reduce hesitation. Bad tools manufacture dependency.

If the only people who can run your operation efficiently are the ones who’ve survived learning it, you don’t have a trained team. You have a hostage situation with a good benefits package.

Fix the system. Document what it should do, not just how it currently behaves. Then close the gap.