Building Management Systems

Documenting What's Actually in Your Head

Getting your core processes out of your head and into something someone else could follow

Delegation Without Losing Control

The difference between delegating tasks and delegating decisions — and how to do each safely

Hiring for a Role, Not a Person

Building roles that outlast whoever currently fills them

The Weekly Rhythm That Keeps Things Running

Meetings, reporting, and check-ins that surface problems early instead of at crisis point

Module 1: Documenting What's Actually in Your Head

Almost every small business runs the same way at first: the founder knows how everything works, and everyone else asks the founder when something isn't obvious. This is fine at first — and it's exactly what quietly caps how big the business can grow, and how much time the founder ever gets back.

The fix isn't a big, formal operations manual written all at once. It's capturing the handful of processes that actually repeat, in a form someone else could follow without you standing next to them.

Start with what repeats, not what's important

The instinct is to document the "big" strategic things first. Don't. Start with whatever happens over and over, the same way, regardless of how small it seems — onboarding a new client, fulfilling a standard order, responding to a common complaint. These are the processes that, once written down, immediately free up real time, because they're the ones someone is currently asking you about weekly.

A process document doesn't need to be elaborate

For each process, capture just four things:

Trigger. What starts this process? (e.g. "a new order comes in")
Steps. The actual sequence, in plain numbered steps — write it the way you'd explain it out loud to a new hire
Who's responsible. Even if it's just you for now, name the role, not just "me" — this makes it easy to hand off later without rewriting anything
What "done" looks like. How do you know this process completed correctly?

A useful test If a competent new hire, with no prior context, couldn't follow your written process and get a reasonable result — it's not documented yet, no matter how clear it feels in your own head.

Try this this week

Document one process, start to finish

Pick the one process you get asked about most often by staff, clients, or yourself
Write it out using the four elements above — trigger, steps, responsible role, definition of done
Hand it to someone else in the business (or even a friend unfamiliar with the work) and watch them try to follow it without your help
Fix whatever confused them — that's usually the gap between what's in your head and what's actually on the page

Before moving to Module 2

At least one process fully documented using the four-part structure
Tested by someone other than you, following only the written version
A short list started of the next 3–5 processes worth documenting next

Want this built out for your actual business?

HZ MGT works directly with Enterprise clients to document real processes, build out delegation structures, and set up the management rhythm that lets a business run without the founder in every room.

Talk to HZ MGT →