How I Actually Time Block a Week Without Burning Out

My calendar looks perfect. For about 6 hours.

I love clean time blocks. Color-coded. Edges aligned to the half hour. A neat little life in 2D.

Reality does not care.

I coach baseball. I build weird web experiences. I write. I have a family. I also like sleeping and not being a wreck by Thursday.

So this is what I actually do. Not the Instagram version of time blocking. The version that gets punched in the face by kids, clients, and Dutch weather, and still mostly works.

The fake perfect week I wanted

When I started taking time blocking seriously, I tried to design the ideal builder-coach-writer week.

On paper, it looked like this:

• 07:00 – 08:30: Deep work (writing)
• 09:00 – 12:00: Dev work (client or product)
• 13:00 – 16:00: Dev work (focus blocks)
• 16:30 – 18:30: Coaching (training or games)
• 20:00 – 21:00: Light admin, planning next day

Sprinkle in lunch, a walk, some mobility, and an enlightened look on my face. Perfect.

That calendar survived about one week. Kind of. Then reality sent some feedback:

• Morning writing often collided with late games or travel the night before.
• Client calls landed right in the middle of "sacred" deep work.
• Rain rescheduled practices. Games moved. Whole evenings disappeared.
• Kids have zero respect for my notion of context switching.

I kept trying to force life into that ideal template. I was exhausted by the second month.

The mental shift: blocks are bets, not promises

The week started working when I changed how I think about blocks.

I used to treat a time block like a contract. "Tuesday 9 to 12 is deep work, non-negotiable." Guess what. Life negotiates.

Now I treat blocks like bets.

• I bet that if nothing explodes, I will use this time for X.
• If something explodes, the block moves or shrinks, but the energy type stays the same.

That energy-type idea is important. I care less about whether I wrote a blog or coded a feature. I care more that I used deep-focus energy for something that deserved it.

This is how I group the week now:

• Deep build time: no meetings, no Slack, high-energy work.
• Shallow work: email, comments, tickets, light coding.
• Coaching time: physical, social, high-output.
• Recovery time: walks, reading, stretching, being offline.

Then I lay blocks for those energy types first. Exact tasks come later.

The real weekly structure I use now

I will walk you through a real pattern I fall back on. This is my baseline. Every Sunday I copy this into the next week, then adapt.

Monday: protect the runway

Monday used to be my "let's catch up" day. Which is a nice way to say "let's scatter my brain." Now I use it to set the runway for the week.

• 07:30 – 08:30: Walk + notes. No laptop. Just a short walk and notes on my phone. I brain dump everything I think I "have" to do.
• 09:00 – 10:00: Weekly planning. Calendar open. Task manager open. I assign work to days. I also block out coaching slots first, because those are fixed.
• 10:00 – 12:00: Deep build block. Usually architecture decisions, prototypes, or anything that needs a fresh brain.
• 13:30 – 15:30: Client or product work. Still deep, but I allow one call if needed.
• Evening: Free or recovery. Never hard commitments if I can avoid it.

Key rule for Monday: I refuse to start the week already behind.

I say no to Monday morning meetings whenever I can. I want the first big block of the week to be me making progress on my work, not reacting to other people.

Tuesday & Wednesday: heavy build days

These are my brutalist days. I front-load as much cognitive load as possible into 48 hours.

• 08:30 – 11:30: Deep work block. Usually coding. Sometimes design and UX flows. I aim for one clear objective per block. Ship a thing. Remove a blocker. Finish a chunk of infrastructure.
• 11:30 – 12:00: Admin sprint. Inbox, messages, quick replies. I run a 25-minute timer and process aggressively.
• 13:30 – 15:30: Second build block. Slightly lighter. Code reviews, refactors, tests, content edits.
• Late afternoon / evening: Coaching. Training sessions, drills, planning lineups.

The reality check part:

• If a game gets rescheduled to midweek, the evening coaching block stretches or moves earlier. I don't fight it. Coaching is not optional.
• If a client insists on a meeting here, I trade. That means I protect a different deep block later and mark it as untouchable.

This is where time blocking breaks for a lot of people. They try to defend every single block equally. I do not. I defend two deep blocks per week like my life depends on it. The others are flexible.

Thursday: context switch and writing

By Thursday my brain is a bit fried from heavy build work and coaching. I lean into that instead of pretending I am still fresh.

• 08:30 – 10:00: Writing block. Blog posts like this, docs, outlines, marketing copy. I treat it like coding. One small outcome.
• 10:00 – 12:00: Shallow work. Tickets, comments, light UI tweaks, bug triage.
• 14:00 – 16:00: Second writing or creative block. Sometimes I script a small interactive demo. Sometimes I just freewrite about something I shipped.
• Evening: Games or training if scheduled. If not, family and recovery.

I stopped trying to write in the "perfect" conditions. My reality is that by Thursday I have a lot of context in my head. That is perfect material for writing as long as I do not aim for poetry, just clarity.

I also noticed something specific. If I push another heavy coding block on Thursday afternoon, I will be useless on Friday. So I stay under my capacity here on purpose.

Friday: maintenance and future-proofing

Friday is anti-heroic. That is by design.

• 08:30 – 10:30: Loose build block. Finish any near-done feature. Merge, clean up, document.
• 11:00 – 12:00: Weekly review. I walk through my calendar, see what actually happened, and compare it to the plan.
• 13:30 – 15:00: Learning or sandbox. I test some weird CSS thing. Play with a new API. Draft ideas for future posts.
• Afternoon / evening: Coaching or early shutdown, depending on the schedule.

I treat Friday as my safety buffer.

Anything that slipped from earlier in the week can land here. If the week went cleanly, I use this time to set up next week. If the week was chaos, Friday is where I put everything back into some kind of order.

The calendar after reality hits

If you look at my calendar at the start of the week and at the end, you would think two different people made them.

Here is what usually changes:

• Blocks get resized: A 3-hour deep work block becomes 90 minutes. I cut the scope, not the block.
• Tasks move inside blocks: The energy type stays, but the actual task changes. Maybe I write instead of code, but I still treat it as deep focus.
• Coaching expands: Weather, travel, extra planning. If the field time grows, something else shrinks that day.
• Evenings get reclaimed: If a day gets wrecked, I do not immediately steal from sleep to compensate. I prefer to slip a task to Friday or kill it.

The important part is this. I am not trying to defend my exact schedule. I am defending my energy budget.

I want roughly:

• 3 to 4 deep build blocks per week.
• 2 writing blocks.
• 1 solid planning session.
• Enough slack so that coaching does not destroy me.

As long as I hit those numbers, I do not care if a block moved by 90 minutes or traded days.

The constraints that keep me from burning out

Time blocking is easy. Not torching yourself is where it gets tricky.

I follow a few hard constraints. They are non-negotiable, because I learned the hard way.

1. No heroic late nights after games

Coaching is intense. I am on my feet, talking, deciding, moving. If I get back late and then decide to "catch up" for two hours, I pay for it for three days.

So I have a simple rule. If there is a night game or late training, that evening has zero cognitively important work. I can stretch, read, or stare at the wall. That is it.

2. One overloaded day max

Sometimes everything lands at once. Deadline, travel, game, family thing. Old me would turn three days into overloaded fire drills.

Now I accept that sometimes one day will be stupid. Packed, messy, too much.

But I force the days around it to be lighter. If Thursday looks insane, I carve down Wednesday and Friday on purpose. Fewer tasks. Smaller scope.

3. Deep work is a quota, not a fantasy

A lot of productivity content pretends you can run four deep work blocks every day if you "optimize" hard enough. I think that is nonsense for most humans with families, clients, and external commitments.

My quota is simple:

• Two deep work blocks are mandatory.
• Three is a good week.
• Four is rare and I do not plan for it.

If a week is heavy with coaching, I am happy with two solid blocks and no guilt. That is the tradeoff for standing on a field and actually working with players instead of staying in a chair.

4. Planning is work, not overhead

The weekly review and planning on Friday and Monday used to feel like "not real work." I would skip them when I felt behind.

That was stupid. Skipping planning is how you end up behind in the first place.

Now I treat planning as its own block with one outcome. My goal is to leave that session with:

• Three concrete build goals for the week.
• Two writing topics picked.
• Coaching sessions and games locked on the calendar.
• At least one afternoon that is intentionally light.

I do not need every hour planned. I just need the big rocks pinned, and I need to see where the week will be heavy.

Tools I actually use

Nothing fancy here. I do not think tools solve this for you. They just make the pain slightly smaller.

• Google Calendar for hard calendar events and high-level blocks.
• A task manager (I rotate, but the pattern is the same) for daily lists broken down from those blocks.
• Plain text notes for weekly reviews and "what actually happened" logs.

The log is underrated. Every Friday I write three bullets:

• What I planned.
• What really happened.
• Why it changed.

Over a few months, patterns appear. Certain days always blow up. Certain clients always push last-minute. Certain coaching periods are heavier.

Then I adjust the baseline week for that season instead of pretending next week will somehow be different.

The honest tradeoffs

I cannot do everything every week. Neither can you. Time blocking does not magically bend time around that fact.

What it does for me:

• It forces me to see the actual tradeoffs between coaching, building, and writing.
• It gives me a default week I can distort without completely losing structure.
• It keeps my deep work quota realistic, which keeps me from burning out.

My calendar still looks perfect on Sunday night.

By Friday afternoon it looks like a crime scene. Blocks moved, resized, scratched out, colors everywhere.

But if I hit my deep work quota, got my players better, shipped a couple of things, and still want to show up again next week, then the system did its job.

The goal is not a clean calendar. The goal is a life you can keep running without grinding yourself into the ground.