<aside>
📋 Frequency: Quarterly | Time: 90 min | Trigger: Second week of each quarter
</aside>
Every solo practice accumulates process debt — workarounds that became habits, manual steps that should be automated, and SOPs that no longer match how you actually work. Without a dedicated sprint to surface and fix these, owner dependency deepens quarter over quarter because you're the only one who knows the workarounds. This SOP dedicates one focused session per quarter to resolving the highest-cost bottleneck in your operating cadence.
Prerequisites
- Friction notes collected during the prior quarter — informal is fine: flagged items, sticky notes, messages to yourself, complaints that surfaced during delivery
- Your current SOP library (Notion, folder, or equivalent) accessible and searchable
- 90 minutes of protected time — no client deliverables, no email, no calls scheduled inside this block
Procedure
- Compile all friction notes from the prior quarter into a single list. If you kept no notes, spend 10 minutes free-writing every process that caused delay, rework, or confusion in the last 90 days.
- Run the Process Bottleneck Identifier skill with your full friction list, your active SOP library, and the types of work you delivered last quarter as input. Review the output for a prioritized ranking of bottlenecks by time cost and fixability.
- Select the top-ranked bottleneck. Confirm it's a process problem — not a tool or people problem. If the top item requires a tool change or a conversation rather than a documented procedure, drop to the next item on the list.
- Run the SOP Writer skill with a description of the current broken workflow, the desired outcome, and any constraints as input. Review the draft SOP output for accuracy against how your practice actually operates.
- Edit the draft SOP by walking through each step against the real process. Remove any steps that don't match actual practice. Add any steps the draft missed.
- Publish the new or revised SOP to your library. Document the bottleneck resolved and archive the remaining friction list as candidates for next quarter's sprint.
Expected Outcome
You'll have one documented SOP replacing your highest-cost quarterly bottleneck, a prioritized friction list for future sprints, and an SOP library that reflects how your practice actually runs — not how it ran six months ago.
<aside>
⚠️ Common mistakes:
— Trying to fix three bottlenecks in one sprint. You'll start all three and finish none. One fix, fully implemented and documented, beats three half-built improvements every time.
— Writing the SOP for an idealized process rather than the actual one. SOPs that describe how you wish the process worked don't get followed. Document the real workflow, then improve it — not the other way around.
</aside>