The document is not the system
If someone reads the SOP and still has to ask the founder what happens next, the team did not receive a working path. They received a file.
A usable instruction shows where the current version lives, what starts the work, who owns the next decision, what happens when the normal path breaks, where the handoff occurs, and how the team knows the result is complete.
Four lessons from the episode
The SOP failed, not the employee
When a capable person cannot use the instructions without returning to the founder, check whether the SOP transferred the decision clearly enough before blaming the person.
Write for the exception
The easy path is rarely where the founder becomes the bottleneck. Useful instructions explain what happens when information is missing, a payment fails, ownership changes, or the normal path breaks.
AI can find the wrong answer faster
AI can organize files and surface instructions. It cannot decide which of five conflicting versions is the current company standard unless a person has made that decision visible.
The founder should be the last stop
The owner may still handle the judgment call that belongs with them. The problem is making the owner the first stop, the search bar, and the backup for ordinary work.
The founder should be the absolute last person anyone ever has to go to. Not the first. Not the backup.Casey Zephirin, Episode 7
Can the instruction answer six questions?
- What starts the work?
- Who owns the next decision?
- What happens when the normal path breaks?
- Where does the work hand off?
- Which version is current?
- How does the team know the result is complete?
What to fix first
Choose the instruction that creates the most repeat questions. Mark the missing trigger, owner, exception, handoff, current version, or completion check. Fix that gap before adding more software or asking AI to search the same unclear material.