Your organisation has documented processes. They exist in wikis, handbooks, and shared drives. Someone invested real time in writing them.

Nobody follows them - not fully, not consistently, and probably not in the way you think.

The usual diagnosis is a people problem: discipline, training, culture. So the usual response is more enforcement. It rarely works, because the diagnosis is wrong.

The real problem is a design problem. Documented process describes how work should happen in ideal conditions. Actual work doesn't happen in ideal conditions. The gap between what you documented and what people actually do is where productivity disappears and frustration accumulates.

---

Two Process Systems

Every organisation runs two process systems simultaneously. The first is the documented system - the official version, the approved workflow, the thing that satisfies audit requirements. The second is the actual system - what people really do when they need to get work done under real conditions.

Most governance sits on top of system one. Most work runs on system two. When those two systems diverge significantly, you get friction: slow execution, inconsistent quality, new employees who can't get up to speed, and experienced employees who stop pretending to follow documented process.

The right question isn't "how do we get people back to system one?" It's: why did system two emerge, and what does it tell us about what's broken?

---

The Five Process Failures

Process problems have structural causes underneath them. There are five patterns that appear repeatedly across organisations.

1. The Designed vs Actual Gap. Process is designed for the happy path - clean inputs, expected dependencies, no surprises. Real work involves exceptions, late information, and shifting priorities. Documented process addresses perhaps half of what people actually encounter. For the rest, they adapt. The gap between designed and actual process isn't a compliance failure. It's a design failure.
2. Compliance Theater. Some process exists to satisfy external requirements, not to help people work. People understand this, even when it's never stated. So they follow the process when observation is likely, and do something more efficient when it isn't. This creates two cultures: what you claim to do, and what actually happens. Leadership operates on a picture of the organisation that doesn't match reality.
3. The Rigidity Trap. Rigid process handles the common case. But a significant portion of real work involves exceptions that don't fit the standard workflow. Rigid process forces a choice: follow process and handle the exception badly, or break process and handle it well. Most people choose to handle it well. Which is why senior employees don't follow documented process the same way junior employees do - they've learned, through experience, where the process breaks.
4. The Checklist Illusion. Following every step of a process is not the same as achieving the outcome the process was designed to produce. A code review can be followed exactly and still ship a vulnerability. An onboarding process can be completed in full and still leave a customer confused. Process compliance is a measure of effort. Process effectiveness - whether the process achieved what it was supposed to achieve - is what matters.
5. The Invisible Workaround. The real process no longer exists in any documentation. It lives in Slack threads and tribal knowledge. The invisible workaround is often the best process in the organisation - the thing that actually works. But because it's invisible, it's fragile. It doesn't survive turnover. It can't be improved deliberately because nobody can see it.

---

What Leaders Don't See

Process failures are particularly hard to diagnose from a leadership position. Documentation bias creates a false sense of confidence - if it's written down, it must be happening. Observation effect means people follow process more carefully when they're being watched. And reported compliance rates describe what people say they do, not what they actually do.

The fastest way to close this gap is simple and underused: spend time watching people execute work in real time. Not in a review meeting - actually following along as someone works through a real task, noting every deviation from documented process.

Do this with several people across different roles. You will see your actual organisational process within days.

---

Designing Process from Reality

Process redesign usually fails because it starts from theory instead of observation. The theoretically optimal process doesn't account for the actual constraints people work under. A more effective approach:

Shadow the work. Watch people execute in real time. Document what actually happens - not what you expected. Note every skip, every shortcut, every exception handled.

Ask why at every deviation. The answers are diagnostics. They point directly to where the original process was designed wrong.

Redesign from actual practice. Formalise the shortcuts that work, remove steps that create no value, make exception-handling explicit.

Draw the line between non-negotiable and flexible. Some steps can't vary - safety, compliance, risk. Others can be handled differently as long as the outcome is achieved. Being explicit about which is which lets people operate flexibly within real boundaries.

Process designed from actual practice gets followed. Not because people are forced to - because it reflects how the work happens.

---