How to process map your small business and build lasting systems

Executive overview

Most small business owners carry critical processes entirely in their heads. Process mapping — drawing a simple flowchart of what actually happens — is the first step to getting those processes out and making them delegatable.

Start with the area that is both most valuable and most painful. Map the actions, not the actors or tools. Once the map exists, a five-step framework (what, why, who, when, how) turns it into a fully owned, continuously improving system.

The core insight: define what happens before you define who does it or how.

The four process mapping symbols

1. Box — an action or observable step
2. Diamond — a decision point with mutually exclusive paths
3. Arrow — direction of flow between steps
4. Double-bordered rectangle — a predefined sub-process (a "folder" you can zoom into later)

Choosing what to map

• Pick an area that is both high-value and currently painful to delegate
• Define a clear start point and stop point before you begin
• Keep scope tight — one service or function at a time
• Name the map (e.g. "sales to onboarding") so you can reference it later

How to build the map

• Write the start step, then keep asking: "What happens next?"
• Label each box as a discrete, delegatable action — roughly one work session (20–90 min)
• Avoid step-by-step sub-actions (e.g. "attend the call", not "say hi, establish rapport, ask questions")
• At decision points, label every path; paths must be mutually exclusive
• Follow the preferred (yes) path straight across; route deviations downward
• Only include delays if they require active effort
• When you finish, check: does every path connect to the endpoint? Are all diamond paths labelled? Is anything missing?

Turning the map into a system: the what–why–who–when–how framework

1. What — the process map itself; defines every action in the flow
2. Why — the reason each step matters and how it supports the business
3. Who — the person responsible for owning and performing the what
4. When — the trigger or interval (event-based, daily, weekly, annual)
5. How — SOPs, templates, playbooks; created by the who, not the business owner

Handing off ownership

• Once the who is assigned, they own the how and the when — not you
• If the who is junior, brief them verbally; they write the instructions themselves
• If the who is experienced, hand off the map and step back
• If no one knows how, bring in external resources; the who still owns the output
• Feed errors and feedback back into the cycle — the who updates their own instructions

The continuous improvement loop

• Catch an error → give the who the information → they update the SOP
• The system improves without the owner re-entering the process
• Metrics and activity should be visible in one place so the loop is observable