AS
Aaron SuarezValencia City, PH · remote-first
Universal searchFind your way through the site

Every operation I’ve walked into has the same scene playing somewhere: a capable employee asking a senior person a question they’ve asked before, the senior person answering it again, and a manager somewhere concluding that the team “needs more training.”

So the training happens. A workshop, an updated onboarding deck, maybe a quiz. Three weeks later the questions return — same questions, same desk. The diagnosis gets repeated too: they need more training. Nobody questions the model itself.

Here’s the model’s flaw. Training transfers knowledge into a person, and knowledge stored in a person has three structural problems: it decays, it leaves when they leave, and it bottlenecks at whoever holds the most of it. You can pour into the bucket forever; the bucket was never the issue. The environment around the work gives people nowhere to turn except up — so up they go, again and again, and the seniors spend their days as human search engines.

A system stores the knowledge at the moment of work instead. The definition lives on the field label. The checklist lives inside the workflow. The SOP is linked from the task it governs, not filed in a wiki three clicks and a search away. When the answer is closer than the senior person, people stop asking the senior person — not because they were trained to stop, but because the path of least resistance finally points at the right thing.

That’s the distinction that changes how you build: training optimizes the person; systems optimize the environment. And environments don’t forget, don’t resign, and don’t mind being asked twice.

The deeper win is the one in the title. People under constant correction become passive — they learn that initiative means risk and questions mean looking slow, so they stop doing both. Put the knowledge in the environment and the dynamic inverts: people act, check themselves, and move. The system doesn’t constrain them. It’s the thing that finally sets them free to work without permission.

When you find yourself scheduling the third training on the same topic, that’s the signal. You don’t have a memory problem in your team. You have a placement problem in your system — and placement problems are fixable this week.

The full investigation of this pattern — and what it does to organizations at scale — is Case 08 in Organizational Physics.

↑ top