Why it is still in your head

The help desk in your head

Every question your team brings you costs you twice: your time to answer it, and their time waiting for you. Most owners know the feeling without ever having counted it. You cannot take a week off without your phone. A new hire takes months to stop asking. Somebody leaves and takes half of how things work with them.

Most owners respond the same way: write it down. A wiki, a shared drive, a Notion workspace, a folder of SOPs. Then the questions keep coming anyway.

Every question is a step or a decision

A step is "how do I do this?" It has one right way, and it fits in a checklist. A decision is "what should we do here?" It needs your rule, where your line sits, your exceptions and your reason.

SOPs hold steps well. They do not hold decisions, because nobody wrote down the reason behind the rule, or where the line is, or who is allowed to make the call. So the decisions keep coming back to you, and they are most of what you get asked.

Your head was never built to hold all of it

Working memory holds about four things at a time (Nelson Cowan, 2001). Everything else you know sits somewhere you have to remember to look, and it is out of reach when you are on holiday, asleep or busy with something else. Your business runs on far more than four things.

Getting it out of your head does two jobs. It frees your attention for the work only you can do, and it gives everything that can read, your team and now AI, something to work from. AI can draft, sort and answer around the clock, but only from what has been written down. What stays in your head stays out of its reach.

Why the last attempt went quiet

When a wiki dies it fails at one of three points:

• Capture: you never had time to write it. Writing SOPs yourself takes forever, and you are already the bottleneck.
• Upkeep: it went out of date. Nobody owned keeping it true, so people stopped trusting it.
• Use: the team did not look. Asking you was faster than searching.

What this course does about it

This course gets the first part out of your head and into a structure you own. You will count the questions that come to you, see which ones only you can answer, set up a folder of notes built to hold decisions as well as steps, decide what must never go in it, and write your first decision down the way a team member could act on it.

It takes about five working days, because the first job is watching what comes to you. Each lesson takes a few minutes to read and ends with one thing to do.