WIKI SLATEPrecision to Vision
← LibraryBuilding Business Processes — SOPs for a Small CompanyBusiness · Business Expansion← PrevNext →
Business · Business Expansion · WIKI SLATE

Building Business Processes — SOPs for a Small Company

If your business can't run without you in the room, it's personality-oriented — and it can't scale. The goal is a process-oriented business that keeps growing whether you're at a resort or away on a personal break. The bridge between the two is Standard Operating Procedures (SOPs) across every department.

SOPsProcess > personalityRACII·We·You DoScale-up
1

Executive Summary

process beats presence

Every business is either personality-oriented — quality collapses the moment the owner is absent — or process-oriented, where documented procedures run the business and customers know the brand, not the founder. SOPs convert the first into the second, unlocking fast scale-up (a J-curve), efficiency, consistent quality, uniform performance, and far less miscommunication. Keep strategy with you as the owner, but write SOPs for execution so the work runs and automates. Documented manuals also remove the knowledge-loss risk of expertise trapped in one employee's head, and let a new hire be productive in about a week. Build SOPs in five steps, prevent failures with a RACI matrix, and train with I Do, We Do, You Do.

The owner's rule

SOP the execution, keep the strategy

Don't write SOPs for strategy at the start — that stays with you. Document the repetitive, frequent execution so the business runs without you.

  • Manuals bring repeatability.
  • SOPs enable performance management.
  • RACI prevents failures.
2

Visual Knowledge Map — the transformation

personality → process
Personality-oriented
  • Owner must be present
  • Quality drops in their absence
  • Can't run without them
  • Knowledge lives in one head
  • Hard to scale

SOPs
Process-oriented
  • Runs without the owner
  • Consistent, uniform quality
  • Documented in manuals
  • Customers know the brand
  • Scales fast
1

Scale-up

Copy SOPs & manuals to new branches → a J-curve.

2

Efficiency

Tighter, faster business processes.

3

Quality

Consistent quality parameters.

4

Uniformity

The same outcome, every time.

5

Less miscommunication

Fewer mistakes and failures.

3

Core Concepts

key definitions
Definition

SOP

A standard operating procedure — the documented way to perform a process.

Type

Personality-oriented

A business dependent on a specific person to function.

Type

Process-oriented

A business run by documented processes, not by one person.

Concept

Process boundary

The start point (A) and end point (B) that frame a process.

Concept

Best-practice capture

Documenting how your best performer does the work.

Concept

Knowledge-loss risk

Expertise trapped in one head, lost when they leave.

Concept

Repeatability

The same result produced reliably from a written manual.

Concept

Performance management

Comparing output to the SOP to spot high, low and no performers.

4

Frameworks & Models

automation, knowledge, RACI, training
Model 1

Path to automation

List repetitive / frequent activities Build execution SOPs Performance management High / low / no performers
Once an expected outcome is defined by the SOP, you can compare each employee's performance against it.
Model 2

Beating knowledge-loss risk

Expertise in one head Written manual Repeatability + cheap training New hire ready in ~1 week
Hand the manual to a new hire, then assess them; if they score low, re-explain and re-test until ready.
Model 3 · the RACI matrix
LetterRoleWho
RResponsiblePerforms the activity
AAccountableEnsures it's done properly
CConsultedThe super-specialist who helps
IInformedThe head of the branch
Build the RACI matrix before problems occur — broken processes, quality issues, a wrong product reaching the market.
Model 4 · training

I Do, We Do, You Do

I Do

You perform the process while the employee watches and learns.

We Do

You perform it together with the employee.

You Do

The employee performs it while you supervise.

RACI + I·We·You Do together build a high-performance team.
5

Process Flow — five steps to develop an SOP

problem to RACI
1

Identify the problem

The department in frequent crisis; set a goal.

2

Build the boundary

Define start (A) and end (B) of the process.

3

Brainstorm activities

List & sequence steps; capture best practice; set manpower.

4

Put it in a flowchart

Process role · flowchart · integrated review.

5

Apply RACI

Kill potential problems in advance.

Worked example · process boundary

Define A → B, then fill the middle

A · Startbuy raw materials Prepare & cookbest performer's method Assemble & serve B · Endcustomer consumes it
For a food item: A is purchasing the ingredients, B is the customer eating it; observe the person who makes it best — ingredient amounts, cooking times — and write that exact sequence as the SOP.
6

Relationship Diagram

SOPs to growth
SOPs & manuals Process-oriented business Scalable + consistent + low knowledge-loss Fast, repeatable growth
The owner's place: strategy stays with you; execution lives in SOPs. That split is what lets the business grow without your constant presence.
7

Dependencies & Interactions

what depends on what

Fast scale-up depends on SOPs & manuals you can copy to new branches.

Consistent quality depends on standardised procedures.

Low knowledge-loss depends on written manuals, not one expert's memory.

Cheap, fast onboarding depends on a ready manual + assessment.

Performance management depends on SOP-defined expected outcomes.

A high-performance team depends on RACI + I·We·You Do.

8

Key Takeaways

remember these
  • Aim for process-oriented, not personality-oriented.
  • SOPs are the bridge — document every department.
  • SOP the execution; keep the strategy as the owner.
  • Copy SOPs to new branches for fast scale-up.
  • Write down expert knowledge to kill knowledge-loss risk.
  • Manuals cut training cost — new hires ready in ~1 week.
  • Define A→B, capture best practice, then flowchart it.
  • Use RACI + I·We·You Do for a high-performance team.
9

Revision Sheet

layered recall
60 seccore idea
  • Turn personality-oriented into process-oriented via SOPs.
  • SOP the execution; keep strategy with the owner.
  • Build in 5 steps; add RACI and I·We·You Do.
5 minthe detail
  • Benefits: scale-up (J-curve), efficiency, quality, uniformity, less miscommunication.
  • Knowledge loss: write the expert's method into a manual → repeatability + cheap, ~1-week onboarding.
  • 5 steps: identify problem/goal → boundary A→B → brainstorm & sequence best practice → flowchart (role, flow, integrated review) → RACI.
  • RACI: Responsible, Accountable, Consulted (specialist), Informed (branch head); train with I Do / We Do / You Do.
10

Quick Reference Table

step → what to do
Developing an SOP in five steps
#StepWhat to doOutput
1Identify the problemFind the department in frequent crisis; set a goalDirection & a target
2Build the boundaryFix the start (A) and end (B) pointsA defined process scope
3Brainstorm activitiesList, sequence, capture best practice, set manpowerThe full activity sequence
4Flowchart itProcess role, flowchart, integrated reviewA reviewed, role-mapped flow
5Apply RACIAssign R, A, C, I to prevent failuresProblems killed in advance
11

Frequently Asked Questions

common doubts

What's the difference between a personality- and process-oriented business?

A personality-oriented business depends on a specific person — quality drops when they're away. A process-oriented business runs on documented procedures, so it operates without the owner present.

What is an SOP and why does it matter?

A standard operating procedure is the documented way to perform a process. SOPs deliver fast scale-up, efficiency, consistent quality, uniform performance and less miscommunication.

Should I write SOPs for strategy too?

Not at the start. Keep strategy with you as the owner and write SOPs for execution — the repetitive, frequent activities — so the business runs and automates.

How do SOPs reduce knowledge-loss risk?

They move an expert's knowledge out of their head and into a written manual, bringing repeatability. When the expert leaves, the manual remains, and a new hire can be ready in about a week.

What is the RACI matrix for?

To prevent failures before they happen by assigning each activity a Responsible person, an Accountable owner, a Consulted specialist, and an Informed branch head.

What is the I Do, We Do, You Do model?

A training progression: you perform the process first, then do it together with the employee, then supervise as they do it themselves — building a high-performance team.

12

Memory Hooks

make it stick
Brand > founder
The goal

Customers should know the brand, not you.

SOP the doing
Owner's rule

Document execution; keep strategy.

A → B, fill the middle
Boundary

Fix start and end, then the steps.

I → We → You
Training

Show, share, then supervise.

13

Practical Applications

putting it to work
Diagnose

Find the weak department

Spot where you face frequent crises in quality, productivity, output, accounting or sales, and set a goal for it.

Scope

Draw the boundary

Decide the first and final step of the process, the look and feel of the output, and the inputs needed in between.

Capture

Document best practice

Observe your best performer, record their exact sequence and quantities, and write it up as the SOP.

Map

Flowchart & review

Assign each person's role, sequence the tasks into a flowchart, and run an integrated review of who does how much.

De-risk

Set the RACI

Name the Responsible, Accountable, Consulted and Informed people up front to prevent quality and process failures.

Train

Run I·We·You Do

Demonstrate the process, do it together, then supervise — and hand over the manual with an assessment for new hires.