> Source: https://brendanlevin.com/insights/how-to-stop-firefighting-in-your-business/
> If you are constantly putting out fires as a business owner, the problem is not the fires. It is that the same fires keep coming back because nobody owns the cause. Here is a concrete method to stop the cycle.

For founders, owners, and operators

# I Spend My Whole Day Firefighting. How Do I Get Out of It?

By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.

Most firefighting is the same fires recurring because nobody owns the cause. Build a two-week fire log: what broke, who noticed, who fixed it, have we seen it before. Then apply the **second-time rule**: any problem that appears twice gets a named owner and a standing fix reviewed in your weekly rhythm. The fires stop when ownership is permanent, not when you are faster.

Key takeaways

-   Most fires are not emergencies. They are recurring failures with no named owner.
-   The two-week fire log reveals the pattern. Most founders are surprised how few distinct problems there actually are.
-   The second-time rule converts a recurring fire into a managed process: named owner, standing fix, weekly review.
-   When you are the best firefighter in the building, the building keeps catching fire. Your speed is the problem, not the solution.

## Why the fires keep coming back

Every business has true emergencies. A key client goes dark. A supplier fails without warning. A critical hire quits on a Friday. These are one-off events, and they will always exist. You deal with them and move on.

The firefighting that consumes a founder's day is almost never that. It is the same client-onboarding breakdown for the third time. The same invoice dispute. The same scheduling clash that somehow nobody resolves without you. These are not emergencies. They are recurring failures with no named owner.

The reason they keep recurring is structural: when you are available to fix things, nobody needs to prevent them. Your speed at solving the problem is the mechanism that guarantees the problem will return. [Why your team does not take ownership](/insights/why-doesnt-my-team-take-ownership/) is almost always a question about structure, not attitude.

## The two-week fire log: the artifact that shows you what is actually happening

Before you can fix the cycle, you need to see the pattern. For two weeks, every time a fire lands on you, log four things in a simple shared document or spreadsheet: what broke, who first noticed it, who actually resolved it, and whether you have seen this before. That is the whole log. Nothing elaborate.

What the log typically shows by week two surprises most founders. Illustratively, you might expect fifteen to twenty distinct fires in a fortnight and find that eight or nine of them are the same four or five problems repeating. The clients-not-invoiced-on-time fire. The scope-not-confirmed-before-work-starts fire. The same system access problem every new hire triggers. The names change. The failure mode does not.

The log also shows you something uncomfortable: in the vast majority of resolutions, the fixer column has your name in it. That is not a coincidence. It is the system working exactly as it is currently designed.

## The second-time rule

Once the log is running, apply one rule without exception. Any problem that appears in the log for a second time gets two things assigned before the week is out: a named owner (a specific person, not a role or a team) and a standing fix (a written process, a checklist, a decision rule, whatever prevents recurrence). That fix goes onto the agenda of your [weekly team meeting](/insights/how-to-run-a-weekly-team-meeting/) and stays there until the problem stops appearing in the log.

The rule does not require perfection on the first attempt at a fix. It requires that someone other than you owns the problem permanently. If the fix fails, the owner refines it. You are not the backstop.

This is where decision rights become relevant, though only once: part of the standing fix sometimes includes a threshold below which the owner acts without involving you. The point is not the number itself. The point is that the owner knows they have the authority and is expected to use it.

## How to tell a true emergency from a recurring fire

A genuine one-off emergency has two qualities: it has not happened before in a materially similar form, and there is no plausible process that would have caught it. If both are true, handle it and move on. Do not build a process around an event that has a near-zero chance of repeating in the same shape.

If either quality is missing, it is a recurring fire wearing an emergency costume. The client who threatens to leave because of a problem you have quietly patched twice before is not an emergency. It is a fire the log already flagged.

The honest test when a fire lands: check the log first. If you have seen it before, the correct response is not to fix it faster. It is to activate the second-time rule immediately, hand it to the named owner or appoint one, and step back.

## Why being the best firefighter in the building keeps the fires coming

Founders who are fast, capable problem-solvers often build businesses that are structurally dependent on exactly that. The team learns, correctly, that the fastest path to resolution is to escalate to the founder. [When every decision routes back to you](/insights/decisions-route-back-to-me/), the business is not broken. It is working as designed, and you are the design.

The log makes this visible. But visibility alone does not fix it. What fixes it is refusing to be the resolver for any fire that appears more than once, and making sure the named owner has the information and authority to do the job without you. [Getting out of the day-to-day](/insights/how-to-get-out-of-the-day-to-day/) starts with this shift, not with hiring.

This is also why the firefighting problem often gets worse as a business grows. More staff means more surface area for the same unowned failure modes to express themselves. [Businesses stall at certain headcounts](/insights/why-businesses-stall-at-10-employees/) for exactly this reason: the founder's personal capacity to absorb fires hits its ceiling.

## What to do with the log after two weeks

By the end of week two you have a ranked list of your most frequent fires. Take the top three by frequency. Assign an owner to each one this week. Write the simplest possible standing fix for each one, even if it is just a one-page checklist. Put all three on the [weekly meeting](/insights/how-to-run-a-weekly-team-meeting/) agenda under a standing item called something plain like 'open fires.'

Each week, the owner reports whether the fire appeared again and what they did. If it appeared, what did the fix miss? Refine it. If it did not appear for three consecutive weeks, it comes off the agenda. You are looking for the list to shrink, not for perfection.

Most founders find that after four to six weeks of this discipline, the volume of fires reaching them drops sharply. Not because the business became simpler, but because ownership became real. [When everything feels urgent](/insights/how-to-prioritize-when-everything-feels-urgent/), the underlying issue is almost always that urgency is the only available signal because nothing has a permanent owner.

If the fires keep coming back because the business still runs through you, the [Momentum Engine](/momentum-engine) is the structured way to change that, in twelve weeks.

[See the Momentum Engine](/momentum-engine)

## Common questions

How do I find time to build the fire log when I am already overwhelmed?

The log takes about three minutes per fire to fill in. You are already spending twenty to sixty minutes resolving each one. The log does not add time to your day. It is a note you write right after the resolution, before you move on. If that still feels impossible, that is itself a signal worth pausing on: the fires are so frequent and so consuming that you cannot afford two minutes of documentation. That is the problem, not a reason to skip the log.

What if the same person keeps being the one who notices the fires but nobody can own the fix?

That is a common pattern and it usually means two things. First, the person who notices is probably closest to the failure point and is the right candidate to own the fix, whether or not they currently have the authority. Second, 'nobody can own it' often means nobody has been explicitly told they own it and given the authority that goes with it. Assign ownership out loud, in writing, in front of the team. Ambiguity defaults to the founder every time.

What if a fire is genuinely too big or too risky for anyone but me to handle?

Some fires legitimately need you in the room: a legal exposure, a major client relationship in genuine crisis, a personnel situation with real liability. Handle those. The question worth asking afterward is whether a better process upstream would have caught the situation earlier, before it reached that severity. Most fires that feel too big for anyone else started small and went unowned for weeks.

Will the fire log work if my team is small, say five or six people?

It works better in smaller teams because the ownership assignments are cleaner. With five or six people, you probably have four or five distinct recurring fires and an obvious owner candidate for each one. The log still matters because it makes the recurrence visible in writing rather than just a feeling. Small teams often under-document because everyone knows everything. That shared knowledge disappears the moment anyone leaves.

How is this different from just telling my team to take more ownership?

Telling a team to take ownership without changing the structure produces one outcome: they try for a week and then the founder resolves something faster, and the old pattern reinstates itself. The fire log and the second-time rule change the structure. The owner is named in a document, the fix is written down, and the review is on a recurring agenda. Ownership without those three things is a request. Ownership with them is a system.

At what point should I think about hiring someone to help with operations instead of building this myself?

The right sequence is structure first, then staffing. If the recurring fires have no named owners and no standing fixes, hiring a senior operator relocates the problem onto them at a higher cost. If they leave, the fires route straight back to you. Build the log, apply the second-time rule, and get three or four major fires under permanent ownership. At that point you can see clearly what operational role, if any, you actually need to fill.

Related: [how to prioritize when everything feels urgent](/insights/how-to-prioritize-when-everything-feels-urgent/) · [how to run a weekly team meeting](/insights/how-to-run-a-weekly-team-meeting/) · [how to get out of the day to day](/insights/how-to-get-out-of-the-day-to-day/) · [why businesses stall at 10 employees](/insights/why-businesses-stall-at-10-employees/) · [decisions route back to me](/insights/decisions-route-back-to-me/) · [why doesnt my team take ownership](/insights/why-doesnt-my-team-take-ownership/) · [more insights](/insights).
