The first SOP I ever wrote was beautiful. Clear steps. Proper formatting. Color-coded sections. I put it in the shared folder and waited for the team to thank me. Three weeks later someone asked if we had a process for that thing. Nobody had opened the document. The process I documented had changed two weeks earlier and I had not updated it. The SOP was fiction. This cycle repeated across every team I worked with. Write a process. File it somewhere. Forget it exists. Repeat when something breaks. After watching this fail enough times I stopped writing SOPs the way everyone tells you to. Here is what actually worked. Rule 1: Fill the template with the person who does the work Do not write processes alone at your desk. Sit with the person doing the job. Capture what actually happens — not what should happen. The gap between the official process and the real process is where things break. A template that takes 20 minutes to fill gets used. A manual that takes a weekend to write gets ignored.…