The SOP That Actually Gets Followed
Write an SOP from a messy process
write an sop from a messy processcross-industrytool-agnosticoperationssopprocessonboardingbeginner
Entry PT-0115 · full text · stolen 0 timesReceived
Turn this messy description of a recurring process into a one-page SOP a new hire could run without asking me anything: [DESCRIBE THE PROCESS - who does what, tools involved, how often, where it breaks]. Structure it as: purpose in one sentence, trigger (what kicks it off), steps as numbered verbs with the owner and tool for each, the two most common failure points and what to do instead, and a definition of done. Cut any step that does not change the outcome and tell me which ones you cut.
Inputs needed
- ■Process description, tools involved, who runs it
What good output looks like
A new hire runs it end to end with zero questions; every step has an owner and a tool; definition of done is checkable
The stream (0)
Reading the room…