SOPs and an operations manual
Which job only works when one person is in?
Every company has a few jobs only one person knows how to do, and a few that go wrong the same way every month. What if you wrote those down first? One job, one page, in the words of the person who does it.
Book a free 20-minute callQuestions I would ask
- When the person who knows is away, does the job wait, or get done differently?
- Do your policies live in an inbox?
- Do changes reach customers before the team has been told?
Would a manual nobody opens fix any of this? I doubt it. So I write short procedures that match the real job, with the person doing the work, and test them on someone who has never done it.
What you get
- Each procedure written with the person who does the job, then tested by someone who does not.
- One place to keep them, organized so a new hire can find their way, with one owner each and a version log.
- A simple rhythm for keeping them current, owned by someone on your team.
How it ends: Your team owns the manual and keeps it up to date.
It starts with the Read
Before anything is built, a written reading of how your company runs. Sometimes it points somewhere else, and it says so. If the report doesn't show you something you didn't already know, tell me and I refund it.
Scope and price are set together on a free 20-minute call.
Book a free 20-minute callHow it starts
Find your stage
A few questions, then the free guide for a company your size. Yours to use, whatever you do next.
A free 20-minute call
You tell me what is going on, and I ask questions. No pitch.
The Read
A written reading of your company and where to start. If nothing is worth doing, or you are not a fit yet, it says so.
Yours to take
A free template
Not ready yet. When there is one worth giving away, it goes here, free.
Related writing
Nothing here yet. See what I have written so far.
Related
Want to talk it through?
Twenty minutes, free. You tell me what is going on and I ask questions. If I am not the right help, I will say so.