When a company hits a rough patch — missed deadlines, duplicated work, decisions made twice — the instinct is to document. Write the process. Make it official. Ensure everyone knows what to do.
Six months later, the process document sits untouched in Notion. The chaos continues.
Why documentation fails
Documentation fails for a predictable reason: it describes what should happen, not what does happen. The gap between those two things is where operational problems actually live.
A process document can’t tell you that your team ignores Step 3 because the tool it references doesn’t work properly. It can’t capture the workaround everyone uses on Thursdays when the usual contact is out. It doesn’t know that the approval flow takes four days because one person is the bottleneck and nobody has said it out loud yet.
Good operations isn’t about having the right documents. It’s about understanding the actual system and knowing where it’s fragile.
What works instead
Three questions cut through more than most audits:
Where does work stall? Not where it should stall — where it actually stalls. Ask the people doing the work, not the people who designed the process.
What gets decided twice? Duplicated decisions are almost always a sign of unclear ownership. The fix is rarely a new process — it’s a conversation that hasn’t happened yet.
What does everyone know but nobody says? Every organisation has operational truths that live in heads, not documents. The Thursday workaround. The approval that always takes longer. The dependency nobody wants to admit. Surface these first.
The AI angle
This is where AI tools genuinely help — not by generating more process documentation, but by making the real system visible. You can now analyse support tickets, meeting notes, and project histories at scale to find where things actually break down. Pattern recognition that used to take weeks of interviews can happen in hours.
But the insight still needs a human to act on it. Someone who can say: here’s what the data shows, here’s what it means for how we work, and here’s what we’re going to change.
More documentation won’t get you there. Understanding the gap between your written process and your real one is where the work actually starts.
