I Run My Work Week Like a Gym Program

Tuesday sprints need Monday’s clarity or you’re sprinting blind.

It’s a Tuesday morning. My calendar is empty on purpose. Phone in a drawer, Slack closed, three projects queued up in the order I’m going to touch them. I’ll work on the first one until lunch, the second one until 3, the third one until I’m done for the day. No calls. No “quick syncs.” No deciding what to do next, because I already decided yesterday.

Six months ago this would have been impossible, not because I didn’t have the time, but because I never had a clean block of it. Calls would land at 11 and 2 and turn the day into three useless slivers. Scoping decisions I’d been avoiding would surface mid-sprint and derail whatever I was building. Admin would creep into the morning, when my brain is sharpest, because it was the easiest thing to clear off the desk.

So I started an experiment. I split my week into two modes. I’ve been running it for about six months now, and it’s actually working.

The setup

Blue days, Monday / Wednesday / Friday. These are horizontal. I do whatever’s important: planning, scoping, calls, resolving ambiguity, reviewing things, admin, the inbox, the conversations I’ve been putting off. A lot of Blue day time goes to networking and catching up with people in my industry, mostly unstructured, mostly without an agenda. The unifying rule is that nothing on a Blue day requires uninterrupted depth. If a task can survive being interrupted by a call, it belongs here.

Blue days have a soft internal shape too. Mornings are for open tasks and the things I’d otherwise procrastinate on. Calls go in the afternoon, starting at 1, and I cut the call window off around 3. The cutoff is deliberate: there’s a “mop up” phase at the end of every day where leftover loops surface and need closing, and I haven’t figured out how to make that phase go away. The 3pm wall keeps my work from spilling into the evening regularly. It’s really the only guardrail I have on that.

Red days, Tuesday / Thursday. These are also horizontal across projects, but vertical within each one. I’ll work on multiple projects in a single Red day, but each one gets a full structured block of total focus before I move on. No calls. No meetings. No context-switching inside a block. The day is built so that whatever needs deep work this week gets a real run at it, not a sliver.

The point isn’t that Red days are “work days” and Blue days aren’t. Blue days are work too, just a different kind. The two kinds of work were eating each other when I tried to do them on the same day, and separating them gave both of them room to breathe.

Where the idea came from

Two loose inspirations, both more vibe than blueprint.

The first is gym programming. Lifters don’t squat heavy five days a week. They cycle intensity and volume, because the kind of work that taxes your central nervous system needs different work as recovery, not just sleep. I started suspecting deep work behaves the same way. After a real Red day I’m cooked in a specific way that another Red day wouldn’t fix, but a Blue day full of conversations and decisions actually does. Blue days aren’t rest. They’re active recovery.

The second is my high school. I went to Thomas Jefferson High School for Science and Technology, and we had a red/blue block schedule: half your classes met on red days, half on blue days, instead of every class meeting every day. The effect, as I remember it, was that each subject got real depth on its day. You weren’t getting a forty-five minute drip of seven things, you were getting a long sit with a few. I think school figured out something offices forgot.

They’re just the two places I’d seen the pattern before: alternate the kind of load, and you can carry more of both.

Who this is for (and isn’t)

If you control your own calendar, try it. Founders, freelancers, indie devs, anyone whose week is mostly self-directed.

If your job is to be reactive, this won’t work. You can’t have Red days if your role is “answer the thing the moment it lands.” That’s fine, it’s just a different game.

What I’m still figuring out

Six months in, the structure is holding, but the interesting questions are still open.

• Friday is technically a Blue day but it has a different gravity than Monday or Wednesday. Maybe it should be a half-Red. Maybe it should be off entirely.
• What happens in a week with travel, or with one unmovable Tuesday meeting? Does the Red day move, or does it just die?
• Do Blue days need their own structure beyond “do whatever’s important”? Right now that rule is enough. I suspect it won’t always be. I’m experimenting with doing a brain dump in the morning and just listing out all the highest impact “stuff” on my plate and then batching those tasks.
• The “mop up” phase at the end of every day. Loose ends surface and demand closure. I’ve tried ending earlier, batching it, ignoring it. It’s still there. I don’t know if it’s a scheduling problem or just the cost of doing business.

If you’ve tried something like this, or something nothing like this that solves the same problem, I’d love to hear about it. This is an experiment, not a system, and I’m collecting notes.