Ask five employees to explain the same process and you’ll get five different answers. Ask leadership why, and you’ll usually hear the same line: we just never got around to writing it down.
That explanation is comfortable. It’s also almost never true.
Nobody Forgot. Somebody Chose.
Organizations don’t drift into having no documentation. They arrive there through a long series of small, reasonable-sounding decisions. Documentation got deprioritized behind a product launch. The person who was supposed to own it left, and nobody replaced the responsibility, only the headcount. Leadership decided speed mattered more than consistency, and every quarter since has quietly confirmed that decision by funding other things instead.
None of this looks like a decision from the inside. It looks like busyness. But the outcome is identical to a decision, because the organization built its systems, its onboarding, and its expectations around the assumption that documentation wasn’t going to happen. That’s not an oversight sitting around waiting to be noticed. That’s a working model of how the business runs.
Informal Process Knowledge Is Serving Somebody
Ask who benefits from process knowledge staying informal, and the answer clarifies fast. The people who hold undocumented knowledge hold leverage. They become indispensable in a very literal sense, because the process doesn’t survive their absence. Some of that is unintentional. Some of it isn’t.
Leadership benefits too, in a way that’s easy to miss. Documentation takes time and budget that could go toward something with a more visible return. Skipping it is cheap in the short term. The cost shows up later, in onboarding time, in inconsistent output, in the quiet panic when someone senior gives notice.
Training Won’t Fix a Decision
This is where most attempts to fix the problem go wrong. Leadership notices the inconsistency, assumes it’s a skills gap, and orders more training. But you can’t train your way out of a documentation vacuum. Training teaches people what to do. It doesn’t create the reference they need six weeks later when they’ve forgotten half of it and there’s nothing to check against.
More training on top of no documentation just produces employees who were taught something once and are now filling in the gaps with guesswork, the same as before, just with slightly more confidence.
Naming the Decision Is the First Move
You can’t fix a decision you haven’t acknowledged was made. The organizations that actually get documentation built are the ones that stop calling it an oversight and start asking a harder question: what were we optimizing for when we let this slide, and are we still willing to pay that price.
Sometimes the honest answer is yes, for now, and that’s a legitimate call for an organization in growth mode with limited hands. But at least it’s a call being made on purpose, one that can be revisited when the cost of not documenting starts outweighing the cost of doing it.
What Changes Once It’s a Decision Instead of an Accident
Once leadership names the tradeoff out loud, the fix stops being abstract. You’re not chasing a vague goal of getting more organized. You’re deciding whether the business can keep absorbing the cost of undocumented process, and if not, which processes get documented first and who’s accountable for it happening.
That’s a project with an owner and a deadline. An oversight is just a feeling everyone shares and nobody acts on.
Diagnose what’s actually driving your process gaps: hermothersdaughter.com/diagnose. Or see how HMD works with organizations through execution, not just strategy: hermothersdaughter.com/work-with-us.