Fix It Twice: Fix the Symptom, Then Fix the System That Produced It

The Framework

Fix It Twice from Allan Dib's Lean Marketing prescribes a two-step response to every problem: (1) Fix the immediate symptom so the customer or operation is unblocked, then (2) Fix the systemic root cause — the process, training, or check that failed — so the problem never recurs. Most businesses stop at step 1, which means they fix the same problems repeatedly. Fix It Twice ensures each problem is solved permanently.

The Two Fixes

Fix 1: The Immediate Symptom. The customer's email went to spam. The order shipped to the wrong address. The invoice had incorrect pricing. The landing page link was broken. Fix 1 addresses the specific instance: redeliver the email, reship the order, correct the invoice, fix the link. This fix is necessary and urgent — the customer is waiting.

Fix 1 is what most businesses treat as the complete solution. Problem reported, problem fixed, move on. But every instance-level fix is a band-aid — it treats the effect without addressing the cause. The same problem will recur next week, next month, with a different customer, requiring another instance-level fix. Over time, the accumulation of recurring problems consumes increasing operational bandwidth.

Fix 2: The Systemic Root Cause. Why did the email go to spam? Because the sending domain isn't authenticated — fix the SPF/DKIM records. Why did the order ship wrong? Because the address field in the CRM accepts unvalidated input — add address verification. Why was the invoice incorrect? Because pricing changes aren't automatically synced between the quoting system and billing system — build the integration. Why was the link broken? Because there's no link-checking step in the content publishing process — add a QA checklist.

Fix 2 asks "why did the system allow this to happen?" rather than "what went wrong this time?" The answer is always one of three things: a missing process (no checklist existed), inadequate training (the person didn't know the correct procedure), or a missing check (no verification step caught the error before it reached the customer).

Connection to Toyota's Five Whys

Dib explicitly connects Fix It Twice to the Five Whys methodology: the first fix addresses Why #1 (what happened), while the second fix requires asking Why #2 through Why #5 to reach the root cause. The shipping error (Why #1) happened because the address wasn't validated (Why #2) because the CRM doesn't require validation (Why #3) because the CRM setup prioritized speed over accuracy (Why #4) because nobody had experienced the cost of address errors yet (Why #5). Fix 2 addresses Why #3 (add validation) to prevent all future instances.

Why Fix 2 Is the Higher-Leverage Investment

Every Fix 2 eliminates a category of problems permanently. If your business handles 100 customer issues per month and each Fix 2 eliminates one recurring issue type, after 12 months you've eliminated 12 categories of problems. If each category produced 3 instances per month, you've eliminated 36 monthly issues — a 36% reduction in operational burden that frees capacity for growth work rather than repair work.

The compound effect accelerates: fewer problems means more time for Fix 2 work, which means faster elimination of remaining problem categories. The business gets operationally cleaner over time in a virtuous cycle that Dib's kaizen philosophy (continuous improvement) depends on.

Cross-Library Connections

Wickman's Process Component from EOS (referenced in The EOS Life) requires documented processes for every core function. Fix It Twice identifies the moments when those processes need updating: every customer problem is a signal that a process is missing, incomplete, or broken.

Hormozi's 3Ds Training Model from $100M Leads connects to Fix 2's training dimension: when the root cause is "the person didn't know the correct procedure," the fix is Document (update the checklist), Demonstrate (retrain), and Duplicate (verify the trainee can execute correctly).

Fisher's Brainstorming Protocol from Getting to Yes applies to Fix 2 sessions: separate inventing (brainstorming root causes and potential solutions) from deciding (selecting the best systemic fix). Creative problem-solving for Fix 2 benefits from the same structured approach Fisher prescribes for negotiation challenges.

Implementation

Create a Fix It Twice log. Every customer problem gets two columns: Fix 1 (what we did immediately) and Fix 2 (what systemic change we made to prevent recurrence).

If Fix 2 is blank, the job isn't done. The symptom may be resolved, but the system is still broken. Schedule Fix 2 work within 48 hours of every Fix 1.

Categorize Fix 2 causes as Process (missing checklist), Training (knowledge gap), or Check (missing verification). This categorization reveals your most common failure mode.

Review the log monthly. Are problem categories declining? If the same categories keep appearing, your Fix 2 solutions aren't actually fixing the root cause.

Celebrate Fix 2 wins. When a problem category drops to zero recurrence, acknowledge the systemic improvement. The team needs to see that Fix 2 work produces permanent results.

📚 From Lean Marketing by Allan Dib — Get the book