← Writing

Patterns Over Firefighting: Stop Reacting to the Same Problem Twice

JB Ong

It’s Monday and something’s on fire. You put it out. Tuesday, something else. By Friday you’ve had a productive, exhausting week and you’d struggle to name one thing that’s permanently better. Next Monday, a fire that looks suspiciously like three weeks ago.

That’s not a busy season. That’s a pattern. And the founders who eventually get their week back aren’t faster at putting out fires — they got good at noticing that the same fire keeps coming back, and asking why before they grab the extinguisher again.

New to this lens? Start with What Is Systems Thinking? A Founder’s Guide — the plain-English foundation this essay builds on.

The trap: every fire looks brand new

Firefighting feels like the job, and it’s seductive because it works. The fire is real, you put it out, you get the hit of having fixed something. Repeat forty times a week and you feel productive — busy, needed, decisive.

The catch: when you treat every problem as a one-off emergency, you never zoom out far enough to notice the ones that rhyme. A single fire is an event. The same fire, three times a quarter, is a pattern — and a pattern is pointing at a structure that keeps producing it. Stay at the event level and you’ll keep paying, in full, for the same fire forever.

The shift is small and it changes everything: stop asking “how do I put this out?” and start asking “how many times have I put this exact thing out?”

Three signs you’re firefighting a pattern, not fixing a problem

1. The recurring fire you’ve stopped noticing is recurring

The pattern: A problem shows up often enough that handling it becomes routine — so routine you file it under “just part of the week” instead of “unsolved.”

Founder version: Every launch, something breaks in the same handoff between design and engineering. You scramble, you patch it, you ship. It’s happened five launches running, but because you always do ship, it never gets promoted from “annoying” to “broken.” The recurrence is the whole signal — and you’ve trained yourself to look past it. A fire you’ve gotten good at fighting is a fire you’ve quietly agreed to keep.

What to watch for: any problem you’ve built a personal workaround for. If you have a routine for handling it, it’s recurring — and recurring means structural.

2. Different fires, same root

The pattern: Several problems that look unrelated on the surface are all downstream of one thing you haven’t named.

Founder version: Support tickets are up, sales calls run long, and onboarding keeps stalling. Three teams, three fires, three separate scrambles. But all three trace back to one thing: nobody can tell, from the outside, who the product is actually for. Fix each fire on its own and you’ll fight all three again next month. Name the shared root — the positioning — and three fires go quiet at once. When unrelated problems keep flaring together, suspect a single cause upstream of all of them.

What to watch for: fires that cluster. If several things break in the same stretch, don’t fix them in parallel — look for the one thing they’re all standing on.

3. The fire that only exists because you keep fighting it

The pattern: Your response to the problem has quietly become part of what keeps the problem alive.

Founder version: Answers live in your head, so people interrupt you constantly. You answer fast — you’re helpful, you’re on it — which teaches everyone that the fastest path to an answer is asking you. So they never write anything down, the dependency deepens, and the interruptions grow. Your firefighting is the fuel. The fix isn’t answering faster; it’s answering in a place others can find later, so the fire stops needing you.

What to watch for: any fire where you’re the reliable extinguisher. If putting it out always routes through you, your involvement may be what keeps it burning.

The move: keep a fire log, read it monthly

You don’t need a framework. You need a memory longer than a week — because the whole trap is that fires feel new when they’re not. One habit closes the gap:

  1. What have I put out more than once this month? List the fires. The repeats are your real work — everything on that list is a pattern wearing an event’s costume.
  2. Which of these share a root? Group the repeats. Fires that flare together usually trace to one unnamed cause upstream.
  3. Where is my response feeding the fire? For each recurring one, ask whether the way you handle it is teaching the system to keep producing it.

Answer those once a month and you’ve done the thing firefighting never lets you do: you looked across time instead of at the flame in front of you.

Why this is a practice, not a trick

Nobody zooms out on the first fire — in the moment it always looks like a one-off, and the pattern only shows up when you’ve got enough distance to see it repeat. Seeing patterns is a muscle: the more often you catch yourself thinking “wait, haven’t I fixed this before?”, the sooner in the cycle you catch it, until you’re spotting the pattern on the second fire instead of the fifth.

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 something catches fire, don’t just reach for the extinguisher. Ask “how many times have I put out this exact fire?” That question is the entire skill.