Protect creative fire — one block that counts

Last week Maya named her response windows out loud. Her brand manager stopped treating silence like neglect. This week: protect creative fire — one deep-work block that is not a reward she earns after everything else is done.

Her illustration hours kept getting eaten — not by drama, by death by a thousand reasonable pings. Vague "focus time" moved whenever a client asked. They asked because they could not see what the block was for. This year the block sits on Google Calendar like a real meeting, titled with the project name, and named in onboarding so nobody has to guess when she is in deep work.

Maya is fictional. "Just a quick thing" during creative time is very real.

~4 min read

• This week: One protected block for deep work — non-negotiable, scheduled, real.

• Try today: Put one 90-minute block on your calendar this week. Title it with the project name (not "focus time"). Tell one collaborator — or add one onboarding line — when you are unreachable.

• Workbook: Tech Boundaries Workbook — protected block planner + energy map.

• 🔥 Fire Horse principle (The Record Is the Guide): If it's on the calendar, it counts.

Part 1: Maya — The Block That Became Seamless

Last year, Maya's "focus time" was a vague calendar block she moved when clients asked. Illustration hours leaked into evenings; evenings leaked into guilt. She still felt behind on the art and rude for protecting it.

This year, she titles Google Calendar blocks with the client project name — same visibility as a client call. Her onboarding doc says: "When you see [Client Name — illustration block] on my calendar, I am in deep work. I will reply in my next email window."

What became seamless: fewer "are you free for a quick thing?" messages — not because people got nicer, because the map got clearer. Phone in the kitchen during the block. Slack muted. Canva closed — shop graphics wait for the admin window. Gmail and Todoist stay outside the block too.

Missed blocks still happen. The failure mode is not missing once — it is never putting it back.

Part 2: Protected Block Ritual (Maya's Version)

1. Calendar — block titled with the project, not "focus time."

2. Phone — another room; not on the desk.

3. One app surface — illustration file open; not Slack, Gmail, or Canva in the same hour.

4. Exit — stop when the block ends, even mid-stroke. Put the next block on the calendar before guilt sets in. The record says she showed up.

The workbook has a 15-minute setup: name the project, schedule 60–90 minutes, tell one person, plan the exit.

Part 3: When the Block Gets Challenged (Copy, Adapt, Own)

Client asks to move it:

I can move this if something is truly urgent — otherwise this block protects delivery for [project]. What works in my next window?

Guilt after saying no to a ping:

I wasn't rude. I was protecting the block I put on the calendar on purpose.

Ending on time (even mid-task):

The block ends at [time]. I'll pick this up at the next scheduled block — that's how it ships without burning out.

They are not walls. They are how the calendar stays honest when someone else's urgency shows up.

Part 4: Energy-Aware Boundaries (Three Modes)

Last July's energy-aware automation insight still holds:

Mode	Maya's attention	Boundary
High	Illustration / deep client work	Protected calendar block; Slack, Gmail, Canva closed
Medium	Gmail batch, shop Canva graphics, Slack file drops	Batched; not mixed into deep block
Low	Rest, personal reading	No Gmail; Slack stays muted

Match the mode honestly instead of forcing high-energy performance on a low-energy body.

Part 5: Gentle Automation (No Code Required)

Respectful automation means technology protects your nervous system — not that everyone builds workflows from scratch.

Principle	Maya's plain-language version
Start simple	Slack mute + Focus mode during illustration block
Build in recovery	Friday admin hour on calendar — no guilt required
Rest as automation	No shop DMs during deep block; autoresponder points to email

Focus mode and notification settings are automation. So is a calendar block your clients can see.

Part 6: When the Block Gets Interrupted

Notice · Adjust · Acknowledge:

• Notice: What ate the block — ping, guilt, or you moved it for someone else?

• Adjust: One change — mute, visible calendar title, script in onboarding, phone out of the room.

• Acknowledge: Did any of the work still ship? Did you put the next block back?

That is enough. Put the next block back. The record stays the guide.

Part 7: How Maya's Month Holds Together

• Audit: Slack + Canva during illustration hour — take. Gmail batch + Canva shop window — give.

• Decline/return: Notion out; Google Calendar back, simpler.

• Comms: Onboarding + signature scripts — manager thanked her.

• Creative fire: Named illustration blocks — fewer ambiguous pings.

Protecting creative fire is what the other three make possible.

Part 8: AI That Waits to Be Asked

Many of you are navigating AI inside creative tools — chatbots that feel intrusive, autocomplete that finishes sentences you did not ask for. Protecting creative fire includes on-request help, not ambient nagging.

One concrete move this week: In one tool you already use, turn off proactive suggestions / "helpful" pop-ups during your protected block — or close that surface entirely until the block ends. Keep the hour where your thoughts still belong to you.

Community Corner

Question I get: "Won't clients think I'm unavailable if my calendar shows deep work?"

My answer: Unavailability without a map reads as flakiness. A named block reads as professionalism — the same way a client call does. Maya's pings dropped because the calendar finally said what the silence meant.

If someone only respects your time when it is unlabeled and interruptible, that tells you something about the fit.

Personal update

June's reading streak is still going — slower in July, which feels honest. My protected blocks look different from Maya's, but the principle is the same: having a self left when the work ships. The turn-over Do Not Disturb on my new phone helps — not available on purpose, for one stretch of deep work.

Your tech struggles, reflected back. Got one? Send it in.

Think about flow over the past year:

1. What software feels more seamless now — and why?

2. What still spikes anxiety even when it is "powerful"?

3. When did you last protect a creative block — and did anyone know it was real?

4. What would change if collaborators could read your calendar without you apologizing?

Hit reply. I read every one.

🔥 The Fire Horse's Callout: What to Charge Forward With

The Fire Horse does not wait for permission to run — but it records where it ran. Calendar, not vibes.

If it's on the calendar — and your people know what it means — it counts.

🔥 Charge forward with: One 90-minute block this week, titled with the project name, told to one collaborator.

What's next

Next Friday: Month closeout — Maya's year in review and all four boundaries together.

No July live this month — newsletter and workbook only, same as June.

— Amanda

Resources

Resource	Best for
Tech Boundaries Workbook (free PDF)	Protected block planner + energy map
Tech Boundaries hub	This month's guides + workbook
Boundaries Premium (Etsy)	Fillable workbook

• Subscribe to the newsletter → pythonessprogrammer.com/newsletter/subscribe

• Browse free resources → pythonessprogrammer.com/resources

• Shop → stickyspells.etsy.com

• Support → pythonessprogrammer.com/support

• Forward this issue to someone who treats deep work like a reward they have to earn

Philosophize your tech use.

Part of the Tech Boundaries series — pythonessprogrammer.com/tech-boundaries