When Nobody Knows the Process

Documentation Deficit

Documentation Deficit is the disease that hides behind almost every accountability complaint in a fast-growing business. Founders read the symptom as 'people are not owning their work.' The actual cause is that the work itself has never been written down. Without a documented process, there is nothing to own, nothing to audit, and nothing to improve.

The symptoms are familiar inside any scale-up that grew faster than its documentation:

Process knowledge lives in people, not systems. Every handover is an interview. Every new joiner re-learns the workflow from scratch. When someone leaves, a chunk of how-the-business-runs leaves with them.

Inconsistent execution across teams. Two people doing the same job do it two different ways. There is no single source of truth, so quality varies by who happens to be on the task that day.

Accountability ambiguity. When a step breaks, the conversation is about who should have done it — not whether it was ever a defined responsibility. Blame moves faster than learning.

Onboarding is shadowing, not training. New team members are paired with a senior person and told to 'pick it up.' Time-to-productivity is measured in months because there is no codified path.

Improvement is invisible. You cannot improve a process you have not mapped. Without baseline flowcharts, every 'fix' is local, undocumented, and reversible the moment the person who built it moves on.

The business runs on tribal knowledge. That works at 30 people. It is structurally unstable at 300.

Why 'Train Harder' Was Never Going to Fix It

A conventional ops response would have been to run more training, add more managers, or introduce a performance management framework. None of those would have addressed the root: there was no underlying artifact to manage against.

Three structural diseases were active simultaneously:

1. Documentation Deficit. Core processes — receiving, putaway, picking, dispatch, returns, vendor onboarding, exception handling — existed only as practiced behaviour. There was no flowchart, no SOP, no swimlane that defined the work.

1. Role Clarity Deficit. Without process artifacts, role boundaries were inferred, not defined. The same work had multiple soft owners, and the gaps between them had none. RACI was a deck, not a working document.

1. Process Drift. Even where process intent existed, execution had drifted from it over time. Each team had silently localised the workflow. There was no mechanism to catch the drift, because there was no baseline to drift from.

These three diseases reinforce each other. You cannot assign clear accountability without documented work. You cannot prevent drift without a documented baseline. And you cannot document anything until someone walks the value stream end-to-end.

An undocumented process is not a process. It is a habit. Habits do not scale, do not audit, and do not survive the people who built them.