Async-first is not ghosting — it's a professional default

Maya canceled Notion last week and consolidated into Gmail, Drive, and a Form on her home screen. Her brand manager still Slacks sometimes at 8pm. Friendly. Reasonable. Nothing on fire. Maya used to read it anyway — badge lit, brain treating unread messages like unfinished tasks, "responsive" wired to "safe" somewhere in her history. She would start typing, delete it, feel mean for not sending, and lie awake wondering if she was becoming someone who "doesn't care."

She was not. She was missing communication boundaries she had never drawn out loud.

May taught hospitality — design for the human on the other end. July's flip: if Maya is always available, she has nothing left to illustrate with. Clarity, not coldness.

Maya is fictional. Late-night ping pressure is very real.

~4 min read

• This week: Draw communication lines — where you can be reached, how fast, on which channel.

• Try today: Paste one script below into your email signature, onboarding doc, or Slack status.

• Workbook: Tech Boundaries Workbook — channel map + script page.

• Maya's windows: Gmail — late morning and early afternoon on weekdays. Slack — project channel only; muted after 6pm. Canva — shop admin batch, not live during client work. Urgent — text, named contacts only.

• 🔥 Fire Horse principle (Lead with Independence): Defaults are someone else's agenda. Claim your response rhythm.

Part 1: Maya, week 3 — Naming the window fixed the guilt

Maya added one paragraph to her client onboarding doc and a line to her Gmail signature:

I batch project email weekday late mornings and early afternoons. Slack is for file handoffs — not live chat for me. Shop inquiries: email only (Gmail), not DMs. Canva comments on shared mood boards — I review in my next batch window. Urgent blockers: text. Everything else lands in my next window and gets a thoughtful reply.

She said it once on a kickoff call — out loud, not just in fine print. Her brand manager replied: "Oh thank god — I don't want to ping you at night either. I just didn't know when you were actually working."

That is the whole lesson. People are not mind readers. Silence without a map reads as neglect. A window reads as professionalism.

Maya still gets the occasional late ping. She answers in her window without the midnight tax. The guilt spiral lost most of its fuel.

Part 2: Three scripts (Copy, adapt, own)

"Not right now"

Thanks for reaching out — I'm not available for a real reply right now. I read messages during [your window] on weekdays. If this is urgent, [your urgent channel]. Otherwise I'll get back to you then.

"Here's when I respond"

I batch email and project messages [days/times]. You haven't been ignored — you're in the queue for my next window.

"Use this channel instead"

For [booking / files / shop orders], the fastest path is [link/channel]. For everything else, email works best: [address].

They are not walls — they are maps. Put them where collaborators actually look: onboarding, signature, Slack status, link-in-bio.

Part 3: Maya's channel map

Channel	Role	Boundary
Gmail	Client admin, deliverables, shop inquiries	Two batch windows; not on phone home screen
Slack	One active brand collab	Muted after 6pm; status shows window
Google Calendar	Client calls + illustration blocks	Shared visibility; blocks titled with project name
Canva	Shop graphics, client mood boards	Twice-weekly shop window; comment notifications off outside batch
Text	True urgent only	Named humans, not "quick question"

When every channel feels equally urgent, you become the integration layer. Lines are how you stop being the glue.

Part 4: Collaborative workspace audit — when the leak is someone else

15-minute audit (workbook channel map):

Shared space	Who pings you?	Take or give?	One setting or script
Client Slack / Discord			Mute after hours; status line
Shared email / Drive comments			Batch notifications; filter to "mentions me"
"Quick call?" texts			Script: "I batch messages [days/times]"

You are not ghosting. You are selectively engaging.

Masking costs executive function. Copy-paste scripts exist so you do not spend scarce energy inventing polite nos every time.

Part 5: May asked outward. July asks inward.

May asked: What does the person on the other end need that they should not have to ask for?

July adds: What do you need so you can still show up for them next month?

Maya's manager doesn't need her at 9pm. They need to know when she will answer, and that the answer will be coherent. Async defaults are care for future-you and future-them.

Personal update

I recently got a new phone — a Moto G Play (2026) — with a feature I wish every phone shipped with: turn-over auto Do Not Disturb. Even with all the notification settings I recommend in my content, having a way to automatically just not be available — even for a Pomodoro — is a level of peace I have not had with a phone before, and I love it. Other tech-sovereignty wins: mic and camera permissions toggle as easily as Bluetooth, so I can friction-maxx on a device I am still learning the gestures for and not accidentally save a voice recording from a pocket. Not available on purpose is a response window too.

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

Reflect on the past year of being reachable:

1. What communication boundaries did you set — or wish you had set — with clients, collaborators, or family?

2. Where did a shared tool become a take (Slack at dinner, email badges, DMs that felt like moral tests)?

3. What happened when you named your window out loud — not just in your head?

4. Who respected it once they knew the map — and what did that teach you about guilt vs. clarity?

"How do I stop feeling rude when I don't reply immediately?" is still the most common version of this. Response boundaries are respectful. They lower emergency-theater energy. Match the channel — onboarding, signature, status line.

Hit reply. I read every one.

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

The Fire Horse does not apologize for choosing when it runs. It runs on purpose — or it rests on purpose.

Your response window is a boundary, not an apology.

🔥 Charge forward with: Paste one script from this issue into your onboarding document, email signature, or status line.

What's next

This Friday (July 24th): Maya protects her illustration block — on the calendar, visible to clients, defended once.

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

— Amanda

Resources

Resource	Best for
Tech Boundaries Workbook (free PDF)	Scripts + channel map
Tech Boundaries hub	Full July arc
Mindful Automation	Y.O.U.R. — hospitality outward

• 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 thinks async means they don't care

Philosophize your tech use.

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