Turn a task only you know how to do into a written SOP someone else can run correctly the first time, then roll it out and keep it current.
A task that only one person knows how to do stops whenever that person is away.
The cost rarely shows up on a statement. It shows up as waiting, as the same question answered for the tenth time, and as a new hire with nothing to read but your attention. Written procedures fix this one task at a time, provided they cover the right task, hold the steps people actually take, and get used once they exist.
You pick the first process by scoring impact against effort, set its scope and owner, record one real run, and turn the recording into short steps with the irreversible step last. Then you test it on someone who has never done the task, roll it out where the work happens, and set a review rhythm that keeps it true when your tools change.
You walk away with one tested SOP for a task you do today, and a method for writing the next one each month.
Founders: want to hand off recurring work without answering the same questions every week.
Operators: need procedures a new hire can follow correctly in their first week.
Team leads: want the same result whoever on the team does the task.
