Volume 31, Chapter 6
The Business Judgment Index
Definition
For years, "should we dismiss this difficult client?" got decided differently every single time it came up at MANIAC MINDZ, sometimes tolerated indefinitely out of guilt, sometimes ended abruptly out of frustration. Same question, no consistent answer, and an emotional toll every time. The problem was never the client. It was the absence of a written threshold.
is a map, not a new lesson. Across Chapters 1–5 and every other volume, this manual answers dozens of "how do I know when...?" questions. This chapter collects them in one place, points to where each is already answered, and gives a direct answer to the handful that weren't covered anywhere else.
Why does a recurring decision get exhausting when it has no written threshold? Because without one, every occurrence gets re-argued from scratch, and whichever emotion is loudest that day, guilt, frustration, fatigue, quietly casts the deciding vote. A written threshold takes the decision out of any single emotional moment and settles it once, calmly, for every time it recurs.
A business owner shouldn't have to remember which volume answered which timing question; this index sorts every one of them, growth, staff, finance, customers, production, into a single table, so "how do I know when...?" always has a specific, findable answer.
Growth
| Question | Answer |
|---|---|
| When should we open a second branch? | Once the current location's systems are fully documented and can run without daily owner presence, see Volume 26's scaling stages; opening before that just duplicates an undocumented, owner-dependent operation. |
| When should we buy instead of rent? | Chapter 5 |
| When should we stop accepting custom work? | When custom orders consistently fall below the lowest price worth accepting or the quality standard can't realistically be met on the timeline offered, a full Volume 19 project plan should exist before accepting, not after. |
| When should we raise prices? | When Chapter 2's break-even and target math shows rising costs eating into profit, or when Volume 08's competitive analysis confirms the price no longer reflects the value delivered, never simply "because it's been a while." |
| When should we discontinue a product? | Chapter 5 |
| When should we buy another machine? | Volume 07's depreciation math plus Chapter 5's buy-vs-rent test |
| When should we hire a manager? | Volume 26, Chapter 2: When to Introduce Middle Management |
Staff
| Question | Answer |
|---|---|
| When should an apprentice become a tailor? | Once they've completed Volume 06's full training rhythm, observed, co-done, solo-supervised, and solo-verified against the standard, not simply "enough time has passed." |
| When should someone receive a raise? | Tied to consistent performance against their role's key performance measures (KPIs), reviewed at the same rhythm as Volume 06's formal reviews, not an on-the-spot reaction to a single conversation. |
| When should someone be promoted? | Volume 06, Chapter 8 + Promotion Letter |
| When should someone be dismissed? | After Volume 06's warning process has been followed, a specific issue named, a documented chance to correct it, and no improvement within the agreed timeframe. Dismissal without that documented record is both unfair and legally risky. |
| When should we replace instead of retrain? | When the gap is about fit (values, reliability, honesty) rather than skill. Skill gaps are usually worth retraining against Volume 23's documented systems; fit gaps rarely improve with more training. |
Finance
| Question | Answer |
|---|---|
| How much cash should always remain in the bank? | Volume 07, Chapter 14: The Emergency Fund |
| How much profit should be reinvested? | Volume 07, Chapter 12: Profit Distribution, Dividends, and Owner's Drawings |
| How much can the owner safely withdraw? | Volume 07, Chapter 12, only from confirmed profit, never from capital still needed by the business |
| When should we borrow money? | Volume 03, Chapter 5: Loans and Debt Financing |
| When should we reject an investment offer? | Volume 03, Chapter 9: Questions Every Founder Must Ask + Investor Due Diligence Checklist |
Customers
| Question | Answer |
|---|---|
| When should we refuse a customer? | When the request would require breaking a core value or quality standard to fulfil. A real value only exists once it's cost you a customer you could have kept. |
| When should we offer a refund? | Volume 15, Chapter 2: Complaints, Returns, and Refunds |
| When should we remake a garment? | Volume 14, Chapter 3: Defects, Rejections, and Rework |
| When should we dismiss a difficult client? | When the relationship consistently costs more, in staff time, morale, or waste, than the revenue it brings in; recall Chapter 3's rule that the goal is spending (and earning) wisely, not chasing as much business as possible no matter the cost. |
| When should we give a discount? | Volume 15, Chapter 3: Loyalty, VIP Customers, and Discount Policy |
Production
| Question | Answer |
|---|---|
| When should we create a new pattern? | Volume 05, Chapter 2: When Should a New Pattern Be Created? |
| When should we archive a pattern? | Volume 05, Chapter 6: Retiring and Archiving Patterns |
| When should we replace a machine? | Volume 07's depreciation math plus Chapter 5's buy-vs-rent test |
| When should we outsource work? | Chapter 5 |
| When should we increase stock levels? | Volume 13, Chapter 2: Stock Counts and Reorder Levels |
Every "when should we...?" question deserves a specific, checkable answer, not a feeling. If a question in your own business isn't in this table, the same discipline still applies: find the actual threshold, write it down, and stop deciding it fresh every time.
Example Story: The Question That Finally Had an Answer
Here's the full version of the difficult-client story from the start of this chapter.
For years, "should we dismiss this difficult client?" had been decided differently every time it came up at MANIAC MINDZ, sometimes tolerated indefinitely out of guilt, sometimes ended abruptly out of frustration, with no consistent standard either way.
The exhaustion had never come from the decision itself. It came from making it fresh every time. Applying a specific, written threshold, "does this relationship cost more in staff time and morale than it brings in revenue?", turned an inconsistent, draining question into a calm decision that could be clearly justified, applied the same way every time it came up again.
Quiz Yourself
Practice Exercise
Pick one "when should we...?" question your business currently answers inconsistently. Find it in this index, or write your own specific threshold for it today.
Quick Summary
Quick Summary
- Every recurring "when should we...?" question deserves a specific, written threshold, not a fresh, inconsistent judgment call each time.
- Most of these questions are already answered elsewhere in the manual; this chapter is the map.
- The handful not covered elsewhere, dismissal, replace-vs-retrain, refusing or dismissing a customer, now have a direct, clear answer here.
- Volume 31 complete. The Business Operating Manual (Volumes 00–31) is now complete.