Most process documentation fails for one reason: it records the steps of a job and leaves every real decision with the person who wrote it. A decision-first SOP reverses that order. You write the decisions down first — who may make them, how far they can go, and when the call comes back to you — and only then write the steps. The steps get shorter as a result, because most of the length in an ordinary SOP is the author quietly describing every judgment call they intend to keep making themselves.
Key takeaways
- Process documentation that only lists steps still routes every judgment call back to whoever wrote it.
- A decision-first SOP begins with rows reading decision | who may decide | limit | escalate when, and the step list sits underneath those rows.
- In a hiring SOP, three rows cover most of the stalls: salary above the posted range, skipping a phone screen for a referral, and making an offer before references clear.
- Once decision rights are settled, the steps shrink, because they stop being a place to hide uncertainty.
Process documentation, two ways
The standard format is two columns: step and owner. Post the job — recruiter. Screen resumes — hiring manager. Schedule interviews — coordinator. Debrief — committee. Check references — recruiter. Make the offer — founder.
Nothing there is wrong. It is incomplete in the exact place where work stops. Every line has an unstated question behind it. Can we go above the posted range for someone strong? Does a referral have to sit through a phone screen? Can we move on a candidate before the reference check comes back? The document doesn't say, so the committee does the only safe thing available to it: it asks you. The SOP that was supposed to run without you becomes a queue with your name on it.
That is the whole difference. A two-column SOP documents motion. A decision-first SOP documents authority.
The decision-first SOP, step by step
1. Name the decisions that stall the work. Not every decision in the process — the three to five that reliably produce a message to you. Walk through the last few times the process got stuck. What was the question someone brought you? That question is a missing row.
2. Write each one as a row. Four fields: decision | who may decide | limit | escalate when. No paragraphs, no philosophy. If you want a filled-in example to look at before you start, the free SOP template has a 'fill with an example' button that shows exactly how a finished row reads.
3. Put a real boundary in the limit column. 'Up to 10% over the posted range' is a limit. 'Reasonable discretion' is not a limit — it is a decision you haven't made yet, handed to someone else.
4. Write the escalation as an event, not a mood. 'Above 10%' is an event. 'When it feels like a lot' is a mood, and a mood will always come back to you to be interpreted.
5. Write the steps last, and keep them short. With the rows done, the steps stop asking questions and start naming actions. This is the order most people get backwards.
Side by side: a hiring-committee SOP
Here are the same three decisions, written as rows instead of left as silence.
| Decision | Who may decide | Limit | Escalate when |
|---|---|---|---|
| Approve a salary above the posted range | Hiring manager | Up to 10% over the posted range | The number needed is above that limit |
| Skip a phone screen for a referral | Any interviewer | Their own interview slot only | The referral would skip the full loop |
| Make an offer before the reference check clears | Founder only | One offer, one candidate | Always — this one stays escalated |
Now read the step list that sits under those rows:
- Post the role. The hiring manager approves the range; the recruiter posts it.
- Screen resumes and referrals. Any interviewer may waive the phone screen for a referral and note it in the tracker.
- Interview and debrief. The committee decides who advances.
- Make the offer. The hiring manager may go up to 10% over the posted range; above that, it comes to you.
The same process, with fewer words and no waiting. Notice what vanished: the 'check with the founder' line, the hedge about salary, the paragraph explaining that referrals are a special case. Those weren't steps. They were unresolved decisions wearing a step's clothing.
Why the steps get shorter once decision rights are settled
A step list written before the decisions is padded. It contains duplicate approvals, 'if unclear, ask' lines, and vague verbs like 'coordinate' that hide a judgment call. Once you have written the row, the step can simply say what happens and who does it, because the ambiguity has moved to a column designed to hold it.
There is a second effect. When the limit is explicit, people stop asking permission for things that are already inside their authority. The hiring manager who knows they can go 10% over doesn't send the email. The interviewer who knows they can waive a phone screen doesn't book a call to check.
The mistake almost everyone makes
Writing the decision section as principles instead of rows. 'Use good judgment on compensation.' 'Be sensible with referrals.' Principles read well in a document and change nothing in the moment, because the person still has to guess where the boundary is and still has to ask you to confirm it.
The second version of the mistake is starting with the steps and trying to bolt the decisions on afterward. You end up reverse-engineering your own intent from a list of tasks, and you miss the decisions that never made it into the steps because they were never written down anywhere at all.
After the first month, revisit the limits, not the steps
Once the SOP is live, the interesting signal is which rows keep triggering escalations. If one decision escalates every time, either the limit is set too tight for the work that actually exists, or the row is assigned to someone without the context to use it. Change the limit or change the owner. Rewriting the steps almost never fixes a stall, because the stall was never in the steps.
You can build your own version of this in one sitting. The free template at tools.exiuss.com/sop-template walks you through the decision rows first, then the steps, and you finish with a clear, ready-to-use SOP in about fifteen minutes — drafted entirely from your own inputs.
Quick checklist
- List the three to five decisions where work stops and waits for you.
- Write each one as a row: decision | who may decide | limit | escalate when.
- Replace every vague limit with a number or a condition.
- Write each escalation trigger as an event, not a feeling.
- Rewrite the steps after the rows are done, and delete every 'check with'.
- Run one live case through it and fix the row that failed.
