None of them needs heroics
They need decisions made once and written down.
Volume 02, Chapter 4
Systems Thinking Across Industries
If a task has happened twice and will happen again, write it down before the third time.
Decision rule
The six-question method is not only for tailoring or factory work. It works for any recurring activity in any business.
Strong systems share four traits: written decisions, pre-decided failure plans, checkable measures, and less dependence on one person. Every breakdown should make the document clearer.
Happened twiceWill happen again. It should already be on paper.
Decided on a calm dayEvery "if it fails" answer, arranged before the crisis.
Checkable by someone elseA signed checklist, a percentage, a count, never "done properly."
Systems improve after failures
Every breakdown should lead to a clearer step, rule, or check in the document.
No exceptions, even under pressure
A rush job is exactly when a 5,000-copy typo is most likely.
Years of records become an advantage
A business that improves its SOPs for years becomes harder to copy.
1
Why This Chapter Exists
The previous chapters taught the method on a sewing machine and a measurement card. The danger is walking away thinking systems are only for tailoring or factory work.
They are not. The same six questions work for any recurring activity in any business, including activities that do not look like "operations" at all, like welcoming a new employee or deciding on a discount.
Memory Trick
If it has happened twice and will happen again, write it down before the third time. That is how a repeated task starts becoming a system.
2
One Method, Eight Businesses
MANIAC MINDZ
SystemFabric reordering.
Why · Who · WhenRunning out mid-order kills deadlines · Storekeeper · any type drops below 5 rolls.
City Kitchen
SystemClosing the kitchen.
Why · Who · WhenFood safety + tomorrow's fast start · Shift Supervisor · every close, 9:30 p.m.
Golden Crust Bakery
SystemDaily production quantity.
Why · Who · WhenToo little = lost sales, too much = waste · Head Baker · 8 p.m., for next morning.
Rapid Auto Works
SystemJob intake.
Why · Who · WhenVerbal promises cause disputes · Service Advisor · every vehicle, before work.
Nimbus Labs
SystemSupport tickets.
Why · Who · WhenSlow answers cancel subscriptions · Support Lead · continuous, every ticket.
Green Fields Farm
SystemDry-season irrigation.
Why · Who · WhenTwo missed days can cost a bed of vegetables · Farm Supervisor · daily 6 a.m.
Precision Print & Press
SystemPre-print proof approval.
Why · Who · WhenA typo printed 5,000 times is a total loss · Studio Manager · every job, before plates.
Bright Path Academy
SystemNew teacher onboarding.
Why · Who · WhenA lost first week teaches bad habits that last years · Head of Studies · first 5 school days.
Each card below answers the same six questions as the sewing-machine system in Chapter 2, just compressed to one line per answer:
MANIAC MINDZ
Fabric Reordering
Why
Running out mid-order kills deadlines.
Who & When
Storekeeper · any fabric type drops below 5 rolls.
How
Reorder card at the shelf (approved suppliers list, quantities).
Measured
Zero "out of fabric" work stoppages per month.
If It Fails
Emergency purchase rule, then log which fabric ran out and why.
City Kitchen
Closing the Kitchen
Why
Food safety, plus a fast, clean start tomorrow.
Who & When
Shift Supervisor · every close, 9:30 p.m.
How
12-point checklist by the door (gas off, fridges at temperature, surfaces, floors, locks).
Measured
Signed checklist nightly; zero morning surprises.
If It Fails
Any unchecked point sends the supervisor back; repeated misses trigger retraining.
Golden Crust Bakery
Daily Production Quantity
Why
Too little means lost sales; too much means waste.
Who & When
Head Baker · 8 p.m., for the next morning.
How
Yesterday's sales sheet plus weather/holiday notes feed a quantity table.
Measured
Unsold bread stays under 5% of the batch.
If It Fails
More than 10% unsold two days running means the owner reviews the quantity table itself.
Rapid Auto Works
Job Intake
Why
Verbal promises cause disputes and unpaid extras.
Who & When
Service Advisor · every vehicle, before any work.
How
Intake form: the fault in the customer's own words, visible damage photographed, estimate signed.
Measured
Zero "I never agreed to that" disputes.
If It Fails
Any dispute sends the owner back to that intake form, and the missing line gets added.
Nimbus Labs
Customer Support Tickets
Why
Slow answers cancel subscriptions.
Who & When
Support Lead · continuous, every ticket.
How
Reply templates plus escalation rules ("bug affecting money reaches a developer within 1 hour").
Measured
First reply under 4 working hours, for 95% of tickets.
If It Fails
A breached ticket auto-flags to the founder daily.
Green Fields Farm
Irrigation in Dry Season
Why
Two missed days can cost a whole bed of vegetables.
Who & When
Farm Supervisor · daily 6 a.m., November–March.
How
Pump start card plus bed rotation chart.
Measured
Soil moisture passes a random weekly spot-check.
If It Fails
A pump failure activates a borrowed-pump agreement with a neighboring farm, arranged before the season, that's Q6 thinking in advance.
Precision Print & Press
Pre-Print Proof Approval
Why
A typo printed 5,000 times is a total loss.
Who & When
Studio Manager · every job, before plates are made.
How
The customer signs a physical proof. No signature, no print, no exceptions, including rush jobs.
Measured
Fewer than 1 reprint-at-our-cost per quarter.
If It Fails
Any reprint triggers one question: was the rule bypassed, and who authorized it?
Bright Path Academy
New Teacher Onboarding
Why
A lost first week teaches bad habits that last years.
Who & When
Head of Studies · every hire, first 5 school days.
How
A day-by-day plan: observe, co-teach, teach observed, feedback.
Measured
The new teacher passes the classroom checklist by day 10.
If It Fails
One extra week with a named mentor; a second failure triggers a probation review.
3
What These Eight Rows Have in Common
- None of them needs heroics. They need decisions made once and written down.
- Every "If it fails" was decided on a calm day. The borrowed-pump agreement exists before the pump dies.
- Every measure is checkable by someone outside the process. Signed checklist, percentage, count, never "done properly."
- Each one reduces dependence on one person's memory. That is Chapter 1's core argument, shown in eight more examples.
Did You Know?
Notice how many rows end with "…and log it / review the form / add the missing line." Strong systems improve after failures: every breakdown should make the document clearer so the same problem is less likely to happen again.
4
Quiz Yourself
Quiz 1
What's the "happened twice" rule?
If a task has happened twice and will happen again, it should be systemized. By the third occurrence it should run on paper, not memory.
Quiz 2
The farm's backup-pump agreement demonstrates which of the six questions, and why is its timing the point?
Q6 (what happens if it fails), the point is that the response was arranged before the failure, on a calm day, not improvised during the emergency.
Quiz 3
Why does the print shop allow no exceptions for rush jobs?
Rush jobs are exactly when a 5,000-copy typo is most likely. Allowing exceptions would remove the protection when it is needed most.
5
Practice Exercise: Your Business in Eight Rows
Write your own version of Section 2, eight one-line systems for your business:
- List the eight recurring activities where failure hurts most (mix operations, money, and people tasks).
- For each, write the six answers in one compressed line, exactly like the rows above.
- Any line where you can't name the owner or the trigger is not criticism. It is your build queue, in priority order.
- Build one per week for eight weeks using Chapter 3's seven steps. In two months, the Two-Week Test reads very differently.
6
Quick Summary
Quick Summary
- The six-question method can systemize anything recurring: production, money, people, safety, or sales.
- Strong systems share four traits: written decisions, pre-decided failure plans, checkable measures, and less dependence on one person.
- The best systems improve after failures: every breakdown becomes a clearer step, rule, or check in the document.
- Rule of thumb: happened twice + will happen again = write it down.
Related Topics