5 Comments
User's avatar
Scenarica's avatar

The Delegability Test at the end is the part that makes this actually useful rather than just another document generator. Most SOPs fail not because the steps are wrong but because the person writing them can't see their own assumptions. They skip the step that feels obvious to them and that's the exact step the new person gets stuck on.

Having the skill audit itself for zero-context executability solves the problem that makes SOPs fail in the first place. The document isn't done when you've written every step. It's done when someone who has never spoken to you can finish the process without asking a single question. That's a different standard from what most people write to, and it's the right one.

Keima Dee's avatar

Thanks for the screenshots and step-by-step process!

Beth Chodak's avatar

This is so helpful. I could have used this at my last job. We were good about documenting processes, but it was such a time suck.

Fabrice Talbot's avatar

Another brilliant skill!

I already create SOPs and it's sometimes hard to keep them up to date as your process evolve, especially when you automate in pieces, test, and expand.

I do daily standups and weekly checkins but it's hard to capture process updates often stuck in a session that I archived.

Any advice on how to avoid stale SOPs and keep them always up to date?

Sunita | Business Alchemist's avatar

I love this. I need to delegate now and I am avoiding because I am not the best at it. This will help me.