Common Failure Modes (and Fixes)

Failure mode 1: too many goals

The most common failure is imported directly from annual planning: five or six goals, each deserving, collectively impossible. Every goal demands weekly tactics executed every week, so goal count multiplies scored commitments — and the score sags into the 60s by week 3, not from laziness but from arithmetic.

The fix: cut to one to three goals now, mid-cycle if necessary. Demoting a goal to the backlog isn't failure; carrying it to a 55% average is. The selection test from chapter 3 applies: which single outcome would make the quarter a win?

Failure mode 2: tactics that are outcomes

'Sign three clients per week' looks like a tactic but is a result — it depends on other people's decisions, so scoring it measures luck. Outcome-shaped tactics corrupt the whole loop: the score stops reflecting effort, and the system's core promise (execute at 85% and results follow) can't operate.

The fix is mechanical: for each suspect tactic, ask 'can I complete this by my own actions alone?' If not, replace it with the controllable actions upstream of it — the outreach, the calls, the proposals. Chapter 4's Friday test catches these at writing time; this failure mode is what it exists to prevent.

Failure modes 3 and 4: not scoring, and quitting after a bad week

Skipped scoring is the quiet killer. It never announces itself — one busy Friday goes unscored, then two, and by week 6 there's a plan but no system, because the feedback loop is the system. The fix: make scoring the one non-negotiable ritual, ten minutes at a fixed time, and if a week did slip, reconstruct it approximately rather than leaving a gap — an estimated 70% preserves the habit; a blank breaks it.

Bad-week abandonment is the loud killer. A 45% week arrives — illness, a launch, life — and the plan suddenly feels falsified, so it gets shelved. This is the perfectionism trap from the 85% rule at full scale: one datapoint treated as a verdict. The fix is to pre-commit to the recovery protocol: score the bad week honestly, write down the one thing that most caused it, cut next week's tactic volume by a third, and rebuild. A 12-week cycle absorbs two bad weeks with room to spare; what it can't absorb is the week after a bad week going unmeasured.

• Bad-week protocol: score it honestly — no retroactive editing.
• Name the single biggest cause in one written line.
• Cut next week's planned volume ~30% and win the week.
• Restore full volume once you've banked one 85%+ week.

Failure modes 5 and 6: no WAM, and planning as procrastination

Running without a WAM means running on willpower, and willpower has a known depletion curve: strong through week 3, unreliable by week 6. Solo operators are especially exposed. The fix costs fifteen minutes a week: one accountability partner and a standing call, per chapter 8 — or at minimum the written solo WAM with a visible score history.

The last failure mode masquerades as diligence: perpetually refining the plan — re-templating, re-tooling, adjusting goals — because planning delivers the feeling of progress without the exposure of execution. A 12-week plan needs about a day to write. The fix is a hard boundary: planning gets one day, week 1 starts on a named date, and mid-cycle changes are restricted to tactics at the weekly review. If planning keeps reopening, that's the tell — the plan isn't unfinished; it's unstarted.