The Oral Tradition Is Not a System

When organizational knowledge lives in people instead of systems, the cost stays hidden until something breaks. 

A surprising number of organizations are still running on the oral tradition of our ancestors. 

Processes are not documented in one reliable place. They are passed from person to person, explained in fragments, adjusted on the fly, and remembered just well enough to get through the next deadline. If someone needs to know how something works, they ask the person who has been there the longest. Or the one who always seems to know. Or the one who is competent enough to be quietly punished for it. 

This is not rare. It is normal. Too normal. 

It is also not because businesses have decided standard operating procedures are outdated. SOPs are not “out.” Most organizations are just moving too fast, running too lean, and postponing documentation until later. 

Later is doing a lot of work. 

The logic usually sounds reasonable. We will document this once the process settles down. Once we finish implementing the new system. Once the next hire starts. Once we get through this grant cycle. Once things calm down a little. 

Things do not calm down a little. 

So the organization keeps going the way many organizations do: on memory, habit, Slack threads, inbox archaeology, verbal handoffs, and whatever Susan knows. 

From the outside, this can look functional. The report gets submitted. The invoice goes out. The client gets onboarded. The board packet appears. A leader looks around and thinks, We have a process for that. 

But often, what they really have is a person for that. 

That distinction matters. 

When a recurring task depends on one person remembering the order of steps, the timing, the judgment calls, the file locations, the exceptions, and the tiny cautions that keep things from going sideways, the organization does not have a system. It has a human workaround with excellent attendance. 

The problem is that this arrangement hides its own risk. 

As long as the knowledgeable person is still there, everything appears to work. They answer questions. They catch mistakes. They remember what happened last time. They know which version is the real final. They know that one approval has to happen before another, and that the vendor form cannot be submitted until finance updates the tax file, and that the report looks complete but is missing the number the funder actually cares about. 

Their competence masks the fragility. 

So the organization mistakes heroics for stability. Then Susan leaves. 

Now everyone has to reconstruct what Susan knew. Not just the steps, but the sequence. Not just the sequence, but the reasoning. Not just the reasoning, but the timing, the dependencies, the exceptions, and the little “do not forget this or the whole thing will go sideways” notes that lived only in Susan’s head. 

That reconstruction is expensive every time. 

A deadline gets missed because no one knew one step had to happen two weeks earlier. A donor acknowledgment goes out late. A proposal gets built from the wrong numbers. A staff handoff is incomplete. A compliance task slips. A client experience gets clunky. A website update stalls because nobody knows who owns it or how it gets approved. 

None of this may look dramatic on its own. That is part of the problem. 

The damage often shows up first as friction, delay, inconsistency, and unnecessary stress. The crisis comes later. By then, the organization is paying interest on a debt it did not realize it was carrying. 

This is why SOPs still matter. 

Not because organizations need more bureaucracy. Because they need continuity. 

A good SOP is not a dusty binder full of lifeless instructions written for appearance’s sake. It is a practical tool that captures how recurring work gets done so the organization does not have to reinvent it every time, re-explain it every time, or rescue it through heroics every time. 

It gives knowledge a place to live other than someone’s memory. 

That does not mean documenting every twitch of organizational life. It means documenting the recurring work that carries risk, requires coordination, affects other people, or tends to get messy when only one person understands it. 

And the old image of SOPs is part of the problem. People hear “standard operating procedure” and picture bloated manuals, stiff language, and a level of procedural theater usually reserved for corporations with seventeen approvals for a stapler. 

That is not the goal. 

The useful version is lighter than that. 

A modern SOP might be short. Searchable. Easy to update. Connected to templates, screenshots, file locations, and decision rules. It might live in a shared drive, a knowledge base, or the platform where the work already happens. It does not need to be impressive. It needs to be findable, usable, and current enough that people trust it. 

That is not red tape. That is organizational memory. 

And in any organization that wants to grow, delegate, survive turnover, or stop making the same avoidable mistakes, organizational memory is not optional. It is infrastructure. 

If a process only works because one person knows how to make it work, that is not resilience. It is borrowed time. 

Eventually, the invoice arrives.