Fractional Operations

Process documentation: getting the business out of people's heads

Knowledge stored in one person's memory is a risk, not an asset.

The symptom. Training a new hire means someone shadows you for three weeks, and the quality of the training depends on how busy that week was.

What this actually is

Documentation is the difference between a business and a collection of people who know things. It is also the single cheapest form of insurance an owner can buy, and the one most often postponed because it is never urgent.

What it includes

• Current-state mapping of how work really flows, which is rarely how anyone believes it flows
• One-page SOPs for quoting, fulfilment, invoicing, purchasing and onboarding
• Checklists, templates and work instructions people actually use
• A living SOP library your team maintains rather than a binder nobody opens

The test

If your best person left on Friday, could someone else do the core of that job on Monday from what is written down?

The mistake to avoid

Documenting the process you wish you had instead of the one you have. A map of an imaginary process helps nobody. Start with what actually happens, including the workarounds, then improve it.

Common questions

How long should an SOP be?

One page. If it runs longer, the process is either too big to be one procedure or it contains explanation that belongs in training rather than in the procedure itself.

Who writes them, you or my team?

Both. Documentation written entirely by an outsider is accurate and ignored. We map and draft, your people correct and own it, which is what makes it survive.

This is one of ten lanes inside a single fractional operations retainer. Most owners need three or four to start. To talk it through, book a readiness call.