Operations 101 Textbook
Turn a business that lives in your head into one that lives on paper and runs itself. Five Rs. Build them in order. The chaos disappears.
Five Rs. Build in order. The business runs without you inside it.
Everything in the Textbook
The five components every operating business needs. Miss one, the machine breaks. Build all five in the order below and the chaos stops.
CHAPTER 1The 15-Minute Quick Win
Before you read anything else in this book, do this one exercise. It will change how you read the rest.
Take a piece of paper. Draw a box for every role in your business. Not people. Roles. Sales. Delivery. Operations. Owner. Under each box, write the one outcome that role is accountable for. Not tasks. Outcomes.
If you are solo, you wear all 4 hats. That is fine. Specify WHICH hat you are wearing for each decision. If you have 2 to 3 people, still wear multiple, but name it. At 5+, at least 2 of the 4 should be separate people (even part-time).
Now look at the picture. Every box that has no name under it is a decision that will land on you today. Every outcome nobody owns is a problem nobody will solve. Fix Roles first. Everything else is downstream of who owns what.
CHAPTER 2Why You're the Bottleneck
If you are reading this, one of these is true:
- Every decision has to run through you and nothing moves without your input.
- You have hired people but they still bring you problems instead of solutions.
- When you take a day off, things break.
- You have tried to write SOPs before but never finished them.
- Your team asks the same questions over and over.
- You know you need "systems" but do not know where to start.
- Your business runs on emergencies, not rhythm.
All seven have the same root cause: the business lives in your head.
The business that lives in your head has a hard cap. You can only work so many hours, hold so many details, and make so many decisions before quality drops. Every business owner hits that cap. Most hit it before revenue hits $500K/year.
It doesn't have to be that way. The businesses that break through the cap all do the same thing. They move what is in the owner's head into a repeatable operating system. Not "documentation." Not "SOPs." An operating system with roles, rules, rhythms, reports, and reviews. Gino Wickman's Traction (2007, revised 2011) is one version of this idea. This book is another, built for owner-operators without a leadership team to lean on.
The chaos is not chaos. It is the absence of rhythm. Fix the rhythm, the chaos disappears.
CHAPTER 3The 5-R Operating System
Every business has (or lacks) five ops components. Missing any one of them and the machine breaks in a predictable way.
R1: ROLES. Who owns what. Clarity on decisions, work, and reporting.
R2: RULES. How work gets done. SOPs, playbooks, standards. The "how" that lives on paper.
R3: RHYTHMS. When things happen. Weekly ops, monthly review, quarterly plan, annual review.
R4: REPORTS. What we measure. The scoreboard everyone sees weekly.
R5: REVIEWS. How we improve. Retrospectives, corrections, adjustments.
What happens when each one is missing
- No Roles: everyone assumes it is someone else's job.
- No Rules: same problem solved differently every time.
- No Rhythms: nothing happens until you push it.
- No Reports: no shared view of reality, decisions made on gut.
- No Reviews: same mistakes repeat forever.
Present all five: the business becomes a machine you tune, not a fire you fight. Build them in R1 to R5 order. You cannot write Rules without knowing who owns them. Rules alone do not run themselves without Rhythms. Rhythms need Reports to measure. Reports need Reviews to convert into change.
CHAPTER 4Sample Template: The 3-Layer SOP
Most owners try to build Rules first and give up. Because they try to write down EVERYTHING. Never do that. Write down what breaks the most.
Every SOP should have three sections. No more, no less. A 3-layer SOP takes 15 minutes to write and can be followed by a new hire in week 1.
Why this works: the bad SOPs are 8-page Word docs with introductions, background context, alternative approaches, and appendices. Nobody reads those. Nobody follows those. The 3-layer version is short enough to actually get used.
The first 5 SOPs to write, in order: New Client Onboarding, Weekly Ops Meeting, Payroll, New Hire Onboarding, Customer Complaint. These 5 handle 60-70% of your recurring ops decisions. Everything else can wait until it breaks.
CHAPTER 5AI Prompt Pack (Preview)
The full book ships with 10 copy-paste AI prompts. Paste into ChatGPT or Claude, replace the brackets, iterate. Here are 5 you get.
CHAPTER 6The 5 Ops Metrics That Matter
Not marketing metrics. Not sales metrics. Ops metrics. Track these 5 monthly. They tell you if the operating system is working.
The rule: On-Time Delivery under 80% is a major ops problem. Rework above 10% is a SOP or training gap. Complaint rate above 10 per 100 is systemic. Team utilization above 85% is burnout risk. Owner Focus under 60% means you are still the bottleneck. Fix the one that is red first, in that order.
CHAPTER 73 Common Mistakes That Stall Owners
The full book lists 10. These 3 stall more owners than the other 7 combined.
Mistake 1: No org chart. Everyone assumes it is someone else's job. Nothing has an owner. Every decision becomes a meeting. Fix: draw the current org chart today. Then draw the 12-month org chart. The gap is your hiring roadmap.
Mistake 2: Writing SOPs for everything. 100 SOPs nobody reads. The trap is trying to document the whole business at once. Fix: write only the 5 SOPs that handle 60-70% of recurring decisions. New Client Onboarding first. Everything else waits until it breaks.
Mistake 3: No weekly ops meeting. Every problem is an emergency. Every decision is fresh. Every meeting is called last-minute. Fix: put a 45-minute weekly ops meeting on the calendar as recurring. Do not accept meetings on top of it. Do not skip it. The rhythm is the whole point.
The One Thing To Do Today
Before you close this file, do this ONE thing:
Get a piece of paper. Draw a box for every role in your business (not every person, every role). Under each, write the ONE outcome that role owns. Now put a name in each box. Any box with no name is a decision that will land on you today. Fix that box first.
If Roles are clear but no SOPs exist, write your first 3-Layer SOP this week. Start with New Client Onboarding. If SOPs exist but no weekly rhythm, put a 45-minute weekly ops meeting on the calendar for next Monday. There is a next action for every state. Pick yours.
Go do it. Come back for the rest.
Ready to install the operating system?
You just read the framework. You have the 4-role diagnostic. You have the 3-Layer SOP template. If you want the full 90-day ops build, all 12 templates, the 10 AI prompts, and the 5-R sequence with worked examples, the book is $47 and lands in your inbox instantly.
Get The Textbook For $47 →Instant delivery. Lifetime updates. 30-day money-back guarantee.
