← Writing

Systems Thinking for Founders: Why Your Best Fixes Keep Backfiring

JB Ong

You solved the problem. Support tickets were piling up, so you hired two more reps. Two months later tickets are worse, not better — because faster responses trained customers to open a ticket instead of reading the docs, and now the docs are more neglected than ever.

You didn’t fail. You just treated a system like a to-do list. In a to-do list, you fix a thing and it stays fixed. In a system, every fix pushes on something else — and the something else pushes back, usually right where you can’t see it.

Systems thinking is the founder skill of seeing those hidden connections before they bite you. Not a framework to memorize — a way of looking that makes second-order effects visible while you can still do something about them.

Want the plain-English foundation first? Start with What Is Systems Thinking? A Founder’s Guide, then come back here.

The trap: a company is a system pretending to be a to-do list

Early on, a startup feels like a list. Ship the feature. Close the deal. Hire the role. Cross it off. The wins are legible and the cause-and-effect is short: you do X, X happens.

Then it stops working like that. You cut prices to win deals — and attract customers who churn and complain. You add a process to fix quality — and slow the team down so much that quality drops from sheer backlog. You raise a big round to move faster — and the extra headcount adds so much coordination cost that you move slower.

None of these are mistakes in isolation. They’re what happens when you pull one lever in a machine where every lever is connected to three others. The list-brain says “problem → fix → done.” The system is running “input → ripple → delayed reaction → new problem.” Founders who keep getting surprised aren’t careless. They’re reading a system with a list-shaped map.

Three shifts that turn the map right-side up

1. From events to patterns

The list view: “Our best engineer just quit. Let’s backfill.”

The system view: “That’s the third senior person in six months. What keeps producing this?” A single departure is an event. Three in a row is a pattern, and patterns come from structure — comp bands, who gets the interesting work, how decisions actually get made. Backfill the seat and you’ll be hiring again by fall. Fix the structure generating the exits and the pattern stops.

The move: when something bad happens, don’t ask “how do I fix this one?” Ask “how many times has some version of this happened, and what keeps producing it?“

2. From faster to feedback

The list view: “Growth is slow. Push harder on the top of the funnel.”

The system view: “What loop is this feeding into?” Every business runs on feedback loops — reinforcing ones that compound (happy users refer friends who become happy users) and balancing ones that push back (more users → more load → worse experience → fewer users). Pour effort into a balancing loop and it quietly eats your gains. Find the reinforcing loop and a small push compounds on its own.

The move: before you push harder, ask whether you’re feeding a loop that grows on its own or one that fights back the moment you let go.

3. From symptoms to leverage

The list view: “Everything’s on fire. Triage the loudest fire.”

The system view: “The loud problem is usually a symptom generated somewhere quiet.” The place that’s shouting is rarely the place to push. Real leverage — the number the company steers by, the one bottleneck everything waits on, the default nobody chose — sits somewhere unglamorous and untouched. A small change there travels further than a heroic push on the symptom.

The move: find the one change that makes ten other problems re-solve themselves, instead of solving all ten by hand. (This one runs deep — Leverage Points for Founders unpacks exactly where leverage hides.)

Why this matters more the bigger you get

At ten people, you can hold the whole system in your head. You feel the ripples because you’re standing in all of them. At fifty, the loops get long enough that cause and effect drift apart — the pricing decision you make in January shows up as a churn spike in June, far enough away that nobody connects them.

That gap is where good companies quietly go sideways. Not from one bad call, but from a hundred reasonable list-brain fixes, each of which pushed a ripple into a part of the system nobody was watching. Systems thinking is what closes the gap: it lets you trace the ripple forward before you ship, and trace a surprise backward to the structure that caused it.

Why this is a practice, not a one-time insight

You won’t see every connection. The first read is almost always the list-shaped one — fix the ticket, backfill the seat, push the funnel. The systems read only gets obvious once you’ve made the list-brain mistake enough times to feel the ripple coming.

That’s the whole idea behind what we build at Gaia Gauge: small, repeatable ways to keep a systems lens on without it feeling academic. If this way of seeing is useful, here are three low-friction ways to keep the muscle warm:

The next time a fix backfires, don’t reach for a bigger fix. Ask what the system was actually reacting to. That question — asked often enough to become a reflex — is systems thinking.