How I Shield 5 Hours a Week for Strategic Thinking (Running a Team of 12)

productivity-time · Productivity & Time Management

Last quarter, I hit a wall. I was running a team of 12, and my calendar looked like a game of Tetris—back-to-back meetings, Slack pings every four minutes, and a growing list of fires to put out. I remember one Thursday: I had six 30-minute calls, two “quick syncs” that ran over, and by 4 PM, I hadn’t touched the strategic project that was due in two weeks. That night, I realized I hadn’t had a single uninterrupted hour to think about where we were headed in over a month. The cost wasn’t just my sanity—it was the team’s direction. So I built a system to shield 5 hours a week for strategic thinking. Here’s exactly how I did it, and how you can too.

The Real Cost of Reactive Mode (And Why I Changed)

I used to pride myself on being available. Every Slack message got an answer within minutes. Every meeting invitation got a yes. But after a few months of this, I noticed something: my decisions were getting shallower. I was approving things without really thinking them through. The team started spinning on small issues because I hadn’t set clear priorities. And worse, I felt like I was just keeping the wheels on, not steering the bus.

The turning point came during a quarterly review. My boss asked me what our biggest opportunity was for the next quarter, and I froze. I had a dozen operational answers—fix this process, hire that person—but no strategic vision. I spent the next weekend mapping out my average week: 35 hours of meetings, 5 hours of reactive email, and zero hours of deliberate, uninterrupted thinking. That’s when I knew something had to change.

My Three-Part System to Block Strategic Time Without Guilt

I didn’t want to just carve out time and hope it stuck. I needed a system that felt natural, not forced. After testing a few approaches, I landed on three components that work together. They’re small, but combined, they protect my thinking time like a force field.

Part 1: The 90-Minute ‘No-Meeting’ Morning Window

Every weekday, from 8:30 to 10:00 AM, my calendar is blocked with a recurring event called “Strategy Focus.” No meetings, no calls, no Slack. I set my status to “Do Not Disturb” and close out of email. The first time I tried this, I felt guilty—like I was hiding from my team. But I communicated it clearly: “I’m working on our biggest challenges. If there’s a true emergency, text me with the subject line ‘URGENT: [one-line description].’” In 18 months, that’s happened exactly three times. The rest can wait 90 minutes.

I also learned to protect the start of this block. I used to check Slack first thing, which often pulled me into a reactive spiral. Now, I don’t open any communication tools until after 10 AM. That first hour of the day is for my brain, not for everyone else’s agenda.

Part 2: A Shared ‘Thinking Time’ Calendar Rule (With a Simple Exception)

I knew I couldn’t be the only one with protected time. So I introduced a team-wide rule: every person on my team can block up to two 90-minute windows per week for deep work, and no one is expected to respond to messages during those blocks. We call it “Focus Time” on the calendar, and it’s visible to everyone. The exception? If something is truly critical—like a production outage or a client escalation—we use a dedicated Slack channel (#urgent-pings) to flag it. Otherwise, we respect the block.

This rule did something unexpected: it made strategic thinking a shared value, not a personal luxury. My team started using their own focus blocks for planning, and the overall quality of our work improved. Plus, it took the pressure off me to be the only one modeling this behavior.

Part 3: A Weekly ‘Decision Dump’ That Frees My Headspace

Even with the morning windows, my brain was still cluttered with operational noise. Every decision—from approving a PTO request to choosing a vendor—lived in my head until I acted on it. That’s where the “Decision Dump” comes in.

Every Friday at 3 PM, I spend 30 minutes writing down every pending decision I’m holding. I categorize them: “Decide now,” “Delegate,” or “Defer to next week.” I then tackle the “Decide now” items in 5 minutes each, and for the “Delegate” items, I assign them to a team member with clear criteria. This ritual clears my mental cache, so when Monday’s strategy block rolls around, I’m not still chewing on last week’s operational crumbs. It also forced me to get better at delegation—I can’t offload decisions if I don’t trust my team to make them.

What I Actually Do During Those 5 Hours (And What I Don’t)

People often ask me, “What does strategic thinking even look like?” Here’s the truth: it’s not glamorous. I pick one high-leverage question per week and spend the full 5 hours on it. For example, last month I asked: “What’s our biggest bottleneck for the next quarter, and how do we remove it?” I spent two mornings mapping out dependencies, one morning interviewing three team members, and the final morning drafting a proposal. That proposal saved us an estimated 20 hours of wasted effort the following month.

What I don’t do: check email, browse industry news, or work on operational tasks. I also avoid multitasking between ideas. If I start a new question midweek, I note it down for next week and stay focused. This discipline was hard at first—my brain wanted the dopamine hit of a quick reply—but after a few weeks, it became a habit.

A concrete example: When we were deciding on a new project management tool, I used my strategy time to create a decision matrix. I listed criteria (cost, integration, team ease-of-use), scored each option, and presented it to the team. The whole process took 4 hours over two weeks. Before the system, I would have made a gut call in 15 minutes and regretted it later.

How to Adapt This System for Your Team Size and Culture

I know what you’re thinking: “This works for you, but my team is different.” And you’re right—context matters. Here are a few ways I’ve seen this system work in different settings:

Smaller teams (3-5 people): You might only need 2-3 hours a week. Start with one 90-minute block on Tuesday and Thursday mornings. The shared calendar rule still applies, but you can be more flexible with the exception.
Remote teams across time zones: Shift your protected window to overlap with the most common time zone’s morning. Use an asynchronous decision dump (a shared Google Doc) instead of a live meeting. I’ve done this with a team spanning five time zones, and it worked.
High-demand cultures (e.g., startup or client-facing): Frame your protected time as “experimentation” to improve outcomes. Start with just 60 minutes twice a week, and after a month, share a measurable win—like a new process that saved the team 3 hours. That builds buy-in.

Common Objections (And How I Overcame Each One)

I had plenty of doubts when I started. Here’s how I addressed them:

“I’ll look unavailable or unresponsive.” I set expectations early: “I’m working on our biggest priorities during these blocks. For urgent stuff, use the #urgent-pings channel.” After two weeks, my team actually appreciated the predictability—they knew when I’d be responsive.
“I’ll miss something urgent.” The 5-minute text rule covers true emergencies. In practice, 95% of what felt urgent could wait 90 minutes. I also check messages right after my block ends.
“My team will resent me for being unavailable.” They did at first. But I modeled the same respect for their focus blocks, and within two weeks, they started protecting their own time too. One team member even said, “I finally feel like I can think.”

Frequently Asked Questions

What if a real emergency happens during my protected time?

I keep a 5-minute phone rule for true emergencies (e.g., server down), but I gate it by asking the team to text first with a clear subject line. 95% of ‘urgent’ things can wait 90 minutes.

My team of 12 is remote and scattered across time zones. Does this still work?

Yes, but you need an asynchronous version. I shift my protected window to overlap with the most common time zone’s morning and use a shared doc for the decision dump instead of a live meeting.

Won’t my team feel like I’m ignoring them during that block?

They will at first, but I set clear expectations and model the same respect for their own focus blocks. After 2 weeks, they actually appreciated the predictability and started protecting their own time.

How do you choose what to work on during those 5 hours?

I pick one high-leverage strategic question per week (e.g., ‘What’s our biggest bottleneck next quarter?’) and spend the full block on it. I don’t multitask between ideas.

What if my boss doesn’t support me having protected time?

Start with just 60 minutes twice a week and frame it as experimentation to improve team outcomes. Share a measurable win (e.g., a new process that saved 3 hours) to build buy-in gradually.

Your takeaway: Shielding strategic time isn’t about being selfish—it’s about leading better. Start with one 90-minute block this week, communicate it clearly, and see what happens. Worth bookmarking before your next quarterly review.