How to Make Time for Strategic Thinking When the Week Goes to Firefighting

Friday, 2 to 4, is blocked for thinking. It's been blocked since January. Most weeks it goes to a vendor question, a staffing gap at one location, and a spreadsheet that has to go out before Monday. By 3:30 you're answering email about next week's version of the same three things.

You schedule time for strategic thinking and end up fighting fires instead. Almost every leader of a growing business or nonprofit knows that week. It doesn't mean anyone is doing their job badly. Usually the team is working hard and the calendar block is losing a fair fight.

Why does strategic thinking time keep losing to firefighting?

Urgent always beats important, until you build systems that protect your thinking time. The reason is mostly structural.

When teams work in separate lanes, a lot of ordinary work needs someone who can see across all of them. Scheduling needs to know what finance approved. Programs need to know what facilities can support this month. The development director needs a number the finance manager has. Each person is doing their part well. The connection between the parts has no owner, so it routes to the one person who can see everything. In most organizations, that's the leader.

So the leader becomes the coordination point. It rarely has anything to do with wanting control. That's just where the information meets. Each of those small relays is reasonable on its own, and together they eat the week.

A calendar block can't fix that by itself. The work that shows up during it is real, and it does need to get handled somewhere.

Strategic thinking vs operational thinking: what the difference looks like in a week

Operational thinking asks what has to happen today so this works. Strategic thinking asks what this should look like a year from now, and what you'd stop doing to get there. Both matter. The trouble is that operational questions arrive on their own and strategic ones never do. Nobody emails you to ask whether the second location should exist.

The leaders who get real thinking time usually don't find it. They set up the operation so fewer things need them in the middle. Connected operations and clear boundaries do most of that work.

How do you stop firefighting at work?

Mostly by making the recurring fires someone else's normal job, and giving them the information to handle it. Some places to look:

• The relay messages. Count how often in a week you pass information from one person to another. Each one is a connection between two teams that currently runs through you. Give those two people a direct line and one shared place the information lives.
• The "just checking" approvals. Some sign-offs protect the organization. Others exist because at some point it felt safer to ask. Sort them. Write down a dollar or risk line below which the team decides.
• The same question every month. If you answer "where are we on this" on a schedule, the answer can be built to show up on a schedule, without you assembling it.
• Meetings that exist to sync. A standing meeting whose main job is getting everyone on the same facts usually means the facts don't live anywhere shared yet.
• Exceptions with no rule. When something goes sideways and there's no stated way to handle it, it lands on your desk. A paragraph on how you'd handle the common ones moves most of them off it.
• Your own "I'll just do it." Every leader has a few. They're fast in the moment, and they quietly teach the team that the work belongs to you.

Some of this is technology. Connecting two systems so a number stops traveling by email is a real fix, and sometimes automation, or AI, is a reasonable way to pull a recurring update together. Most of it, though, is decision rights and a shared place for the facts. That part costs very little, and it's where the hours actually come back.

Protecting the time once you have it

Once fewer fires need you, the block has a chance. Put it where your week is quietest, which for a lot of leaders is early, before the inbox wakes up. Tell the team what it's for and what counts as a real interruption, so they aren't left guessing. And walk in with one question, written down the day before. A block with no question in it fills with email.

Strategic thinking is part of the job. It's the part that decides whether next year's organization is easier to run than this one.

A first step you can take this month

Open the last two weeks of your calendar and messages. Mark every time you were the go-between for two other people or two teams: passing along a number, confirming a schedule, answering something one of them could have asked the other directly.

Pick the pair that shows up most. Sit down with both of them for twenty minutes. Agree where that information will live, who keeps it current, and the one situation where they should still bring it to you. Then leave it with them for two weeks and see what comes back.

That's one relay. Most leaders find five or six once they start counting. Take them one at a time.

If you'd like a hand mapping where the week goes and building the connections that give it back, that's work we do alongside leadership teams, and we stay with it as the organization changes. You'll find more at 2n2solutions.com.