Gall’s Law: Grow What Works, Then Add Complexity (with AI)
Build a habit that survives your worst day, then grow it with AI.
TL;DR
Gall’s Law is the pattern that complex things that work usually started as simple things that worked.
Most personal systems fail because they depend on too many things going right, every day.
The practical loop is Minimum → Run → Learn → Upgrade (or Quit).
AI helps by shrinking your plan, spotting fragile dependencies, and proposing one safe upgrade at a time.
After reading, you will have three copy paste prompts to turn any messy goal into a small working routine.
In five minutes, you can turn “I need a full system” into a loop you will actually keep.
1) Why big plans feel good (and why they die)
You decide you will finally fix it.
Health. Focus. Home. Relationships. Pick your arena.
You do what smart people do. You think.
You research, compare options, and design a complete plan. You add rules so you will not fail. You collect tools so it feels serious.
For a moment, it feels great. Your brain relaxes. You have a map.
Then real life shows up.
A bad night of sleep. A busy day. One missed day.
And the plan needs momentum.
So one missed day becomes two. The plan starts to feel heavy. You stop using it.
Then the story becomes, “I just lack discipline.”
Most of the time, the system was simply too demanding. It needed your best self too often.
This is a way to change that does not depend on motivation. It depends on design.
I know this trap well. I tend to overthink. I used to believe I could think a problem to completion and then execute cleanly. What changed things was a bit of indifference. I started with a small imperfect version and let reality teach me what to improve next.
This week’s move is simple:
Build the smallest loop that survives your worst day.
How AI helps
AI gives you speed and clarity:
It shrinks your plan into a minimum you can keep.
It shows what your plan depends on.
It helps you upgrade without restarting.
Key takeaway: A plan that requires perfect days will not survive normal life.
2) Gall’s Law in plain language (and why it works)
Gall’s Law is a simple pattern.
If you want something complex that works in real life, it usually started as something simple that worked.
This is about building something that survives contact with normal days.
The hidden problem
Most full systems fail because they depend on too many things going right at the same time.
Your plan quietly depends on sleep, mood, time, prep, motivation, and a clean week.
When any one of those breaks, the whole thing breaks.
A simple start cuts the dependency chain.
It gives you one small loop you can keep running long enough to learn.
The fitness example
People chase the perfect plan, the perfect program, the perfect gear.
A better start is one exercise.
Day 1: 1 rep.
Days 2 to 3: 2 reps.
Days 4 to 6: 3 reps.
You are keeping the loop alive.
Technique improves because you repeat it.
Strength improves because the load grows slowly.
Habit forms because the entry cost stays tiny.
The practical move
Gall’s Law gives you three options when you want change:
Start with a minimum loop
Run it until reality shows friction
Upgrade one thing at a time
If the loop never produces a signal, stop and choose a different loop.
If you liked our Occam’s Razor and Via Negativa articles, this is the same instinct in action: simplify, remove friction, then grow what earns its place.
Quick source note: this principle is commonly attributed to John Gall’s Systemantics (1970s).
Key takeaway: Start small. Keep it alive. Let reality choose the complexity.
Now we turn the model into a five minute protocol you can run on demand.
3) Prompts: use AI to run Minimum → Run → Learn → Upgrade
Gall’s Law is easy to agree with and easy to ignore.
So the goal is speed. You want a small loop you can run in minutes, right when you feel the urge to design a full system.
Pick the prompt that matches your stage. Do not run all of them.
If you only do one, do 3.1.
3.1 Shrink prompt: define the Minimum Working Version (Minimum)
Use this when your goal feels big and your brain wants a complete plan.
You will know it worked if you can do the minimum on a bad day and you still did it.
Help me apply Gall’s Law.
Return the answer in three blocks:
A) Minimum Working Version (under 2 minutes)
B) Success signal (one simple signal the loop is alive)
C) Anti creep (top 3 things to NOT add yet)
Then:
1) Make the minimum doable on my worst day.
2) Write the one sentence rule I will follow for 7 days.
INPUT:
Goal + constraints (time, energy, schedule, injuries, budget, preferences):
[PASTE HERE]
3.2 Diagnostic prompt: find the fragile dependencies (Learn)
Use this when you already have a plan, but it keeps collapsing for reasons you cannot name.
You will know it worked if you can name the top 3 breakpoints and one subtraction you will try today.
Audit my routine for fragility.
Return the answer as a short checklist with four sections:
1) Top 3 must go right dependencies
2) One way to weaken each dependency
3) The smallest change I can apply today
4) A fallback minimum mode for bad days
INPUT:
Routine + where it breaks (what happens, what I skip, what day it tends to fail):
[PASTE HERE]
3.3 Decision prompt: upgrade without restarting (Upgrade or Quit)
Use this when the loop is alive and you want better results without breaking consistency.
You will know it worked if you have one upgrade, one stop rule, and minimum mode stays alive.
Help me evolve a working loop without restarting it.
Return answers in five parts:
1) What reality taught me (constraints, friction, failure points)
2) ONE reversible upgrade for the next 14 days
3) One metric (what "better" means)
4) One stop rule and one fallback (minimum mode stays alive)
5) Decision: keep, upgrade, downgrade, or quit
Then write the next 14 days rule in one sentence.
INPUT:
Current loop + last 7–14 days (what I did, what I missed, what felt hard, any results):
[PASTE HERE]
Prompts are the tactic. The next section is the operating system.
4) Principles and traps
This is not a motivation problem. It is a design problem.
Principles
Keep the loop alive.
Your minimum is sacred.Fewer dependencies win.
Build something that does not require perfect days.One change at a time.
Change one thing, learn one thing.Prefer reversible upgrades.
Improve without breaking what already works.
Notes that help:
Let reality choose the complexity.
Use AI to subtract steps and decisions.
Traps
High stakes blindness.
Iterating casually when the downside is meaningful or irreversible.System cosplay.
Tools, templates, gear, research. It feels like progress. Nothing runs.Restart addiction.
Missing once turns into “start over Monday.”Complexity creep.
Every improvement adds a step until the whole thing collapses.Premature optimization.
Solving problems you do not have yet.AI theater.
Beautiful plans that you do not execute.
5) Closing: the practical payoff
You do not need a perfect system.
You need a loop that survives real life.
The next time you feel the urge to design the complete plan, run the loop:
Minimum → Run → Learn → Upgrade (or Quit)
Minimum: What is the smallest version I will actually do.
Run: Can I keep it alive for seven days.
Learn: What broke, and what does that reveal.
Upgrade: What one reversible change improves it.
Quit: If there is no signal, stop and pick a different loop.
If you want more pieces like this, subscribe on Substack. One mental model per week, with prompts you can use immediately.
If you want, paste the goal you are overbuilding right now in the comments and I will help you find the Minimum Working Version.