What Undocumented Process actually looks like
Every time someone new joins, work slows down for 6 weeks. When someone leaves, work breaks. When someone is out sick, the same tasks get done three slightly different ways depending on who covered. You have a team that is good at their jobs, but the jobs live in their heads. That is fine until it is not.
The tell that you are in an Undocumented Process pattern: you cannot answer the question 'how do we do X' without asking whoever usually does X. And when you do ask, you get three different answers depending on who you ask.
Why this is worth fixing before you add AI
Every AI or automation tool needs to be told what to do. If the input is a fuzzy 'well, usually we...' answer, the output will be a fuzzy result. Teams that add AI on top of undocumented processes end up with AI that produces inconsistent output, and they blame the AI. The AI is doing what it was told; nobody told it clearly.
Documentation done right is not a compliance exercise. It is the specification that lets a human, an automation, or an AI tool all execute the same work the same way. It also becomes the training material for the next hire, which is the reason it usually pays for itself inside 90 days on hiring alone.
What the 90-day rebuild looks like
Day 1 to 21: capture what exists. Not what should exist. What does. Pick the 5 highest-volume processes (intake, onboarding, whatever runs most days) and have the person doing them narrate the process while you write. Include the exceptions. Include the workarounds. Do not clean it up.
Day 22 to 60: turn the captures into SOPs. Structure: what triggers this process, who owns it, step-by-step, decision points with rules, what a successful completion looks like, what happens when it fails. Ideally 1 page per SOP, in a shared drive everyone can search. Not a 40-page manual nobody reads.
Day 61 to 90: use them. New hires read them. Existing team is asked to follow them. Gaps get noted and the SOPs improve. Once the SOPs are stable, they become the source of truth for adding automation or AI on top. That is when the compounding starts.
One investment firm had 4 analysts doing morning research each their own way. The daily TLDR they produced went to different investors and read differently depending on who wrote it. We spent 3 weeks writing one SOP with them, then built the automation on top. Now the TLDR looks the same regardless of who is on shift, and building it takes 30 minutes instead of 90.
If you want to walk your top 5 processes with someone who has documented them for a hundred teams, book a working call. First one is diagnostic, no pitch.
Book a call