Audit the leak — where tech takes more than it gives

June gave me something I had not had in a long time: I finished four books in one month — because I canceled an event I had been planning and rested instead. June's newsletters stayed more consistent than they had in months — not because I pushed harder, but because I stopped spinning up new content formats that were not landing with my readers anyway. The newsletter-and-checklist cadence held without sprint videos or a live event — and for the first time in ages, rest felt like rest, not like failure.

I'm in a slower season right now. This month we're back with Maya — the solo creative from May's Mindful Automation arc — while she walks through boundaries in a world full of client Slack, inbox badges, and "quick question" pings.

June was about caring for the human on the other end of your screen. This month: when you are that human — and tech is taking more than it gives.

~4 min read

• This week: Audit the leak — where is tech taking from you vs. giving back?

• Try today (15 min): Pick one surface — phone, inbox, or calendar. List three interactions from yesterday. Mark each take or give. Include one external leak (client or collaborator channel) if it applies.

• When it stings: Use NAA — Notice · Adjust · Acknowledge (not pass/fail detox).

• Workbook: Tech Boundaries Workbook (PDF) — printable take/give worksheet.

• 🔥 Fire Horse principle (Lead with Independence): Write the list without grading yourself.

Part 1: Maya, week 1 — last year's leak vs. this year's flow

Last summer, Maya was in the thick of it: a brand collaboration on Slack, Gmail open all day, Canva one tab away for "just fix this shop graphic" — phone notifications on for every client thread. She would sit down to illustrate and get a Slack "quick question" or slide into a Canva tweak — reasonable, friendly, nothing on fire — and lose the block anyway. By evening she felt behind on art and rude for not answering faster. That was the leak: not doom-scrolling, but respectable interruption that looked like being a good collaborator.

This year, a few things became seamless — not because she got stricter, but because she got clearer:

1. Gmail batched late morning and early afternoon — client threads and shop inquiries in named windows, not live-in-the-inbox. The onboarding doc says so; collaborators stopped reading silence as neglect.

2. Google Calendar blocks titled with the client project — deep work visible the same way a call would be.

3. Canva moved to a shop admin window (twice weekly with email batch) — still her go-to for social graphics and client mood boards, no longer open during illustration hours.

4. Todoist with the free tier's project cap — three lists: active client, shop admin, personal. Same app. Different boundary.

What still takes: she cannot leave the brand's Slack entirely. She mutes after 6pm and set a status line with her window. Worth writing down — not a failure. Audit first, perfect later.

Your 15-minute action: One surface only.

1. List three tech interactions from yesterday.

2. Mark each take or give.

3. Circle one take you will name out loud — to yourself or a collaborator. Naming is the first boundary.

The Tech Boundaries Workbook has a printable take/give matrix.

Part 2: The take/give audit

Last July I called this a "digital wellness audit" on the Tech Boundaries hub. Same idea, clearer words: take vs. give.

	Give	Take
Feel	You close the app calmer or clearer	You close it vaguely worse
Time	Bounded — you chose the window	"Quick check" became twenty minutes
After	Creative work or rest is still possible	You need recovery from the recovery

Maya's Slack ping during illustration hour was pure take. So was opening Canva for a "quick" shop graphic mid-block. Gmail in her batch window and Canva in shop admin hours are give. The apps did not change — the line did.

Part 3: Values belong in the audit too

Looking back over the year — Maya's and mine — boundaries shifted from "organize better" toward "preserve sanity."

Where does money go? Where does data go? Who gets funded when you pay for software? Maya cannot always choose the client's stack. She can name when Slack (a Salesforce product) sits in a shared workspace she did not pick — and mute, batch, and script around it instead of pretending it is neutral.

I watch acquisition rumors, CEO politics, and values anxiety the same way many of you do. You can use a tool today and leave tomorrow when the audit updates. May's folder-as-workbench habit means context can travel when ethics shift. I'll pick up tool-swapping when values shift next week.

Part 4: NAA when the audit stings — no detox required

A lot of digital wellness advice still sounds like pass/fail detox. NAA works better here: Notice · Adjust · Acknowledge.

Here is how Maya used it on her Slack leak:

• Notice: Illustration block interrupted; closed the app feeling behind and vaguely guilty. Take.

• Adjust: Slack muted after 6pm; status line with response window; illustration blocks on calendar.

• Acknowledge: Client work still ships; evening belongs to her again more often.

When tech makes you anxious, name what the screen is doing to your nervous system first — urgency theater, false scarcity, the terror of being "rude." That's where tech confidence starts.

Part 5: Audit personal and shared leaks

Organizing your own apps is only half of it. The harder part: boundaries tested by other people.

Source	Example take
Your apps	Canva tweak during illustration; Gmail "just checking" outside batch window
Client/collaborator channels	Slack ping during a protected block
Platform defaults	Badge that feels like a verdict on your worth
Values / vendors	Shared tool you did not choose but still live inside

This week: name one external leak alongside a personal one. Both belong in the workbook.

Personal update

I am still reading — four books in June did not happen by accident. I log my reads on Fable. I canceled what was on the calendar, rested on purpose, and let the lighter cadence do its job. June's consistency came from not chasing formats my readers were not asking for.

My inbox is quieter than Maya's these days. Hers still runs on Gmail, Slack, Google Calendar, and Canva — plus the guilt of async. If her week sounds like yours, this month is for you.

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

Think about the past twelve months:

1. What tech boundaries have you set — on purpose, or because something finally broke you?

2. Where have you used NAA without calling it that — a mute, a batch window, a "quick check" you stopped pretending was quick?

3. What software feels more seamless now — and why? (Maya's answer: Gmail windows + Canva in shop hours only + visible Calendar blocks. What's yours?)

4. What still takes more than it gives, including shared tools you cannot fully leave?

If your list is mostly takes right now, start there.

Hit reply. I read every one.

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

The Fire Horse does not start July with a detox. It starts with eyes open — what is taking from you while pretending to help?

Look at what's taking from you. Write it down.

🔥 Charge forward with: One take you will name out loud this week — to yourself, a collaborator, or in a status line.

What's next

Next Friday: Maya declines the wrong tools — and picks one back up when the audit says yes.

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

— Amanda

Resources

Resource	Best for
Tech Boundaries Workbook (free PDF)	Take/give audit worksheet
Tech Boundaries hub	2025 deep dives + July 2026 issues
Mindful Automation	May — meet Maya
Accessible Tech Design	June bridge — care for people you reach

• Book a reflection session — 20min ($95), 60min ($255), or Async ($75) → pythonessprogrammer.com/services

• Browse free resources → pythonessprogrammer.com/resources

• Shop → stickyspells.etsy.com

• Support → pythonessprogrammer.com/support

• Forward this issue to someone who needs permission to audit without guilt

Reflection sessions, not rescue. Tech That Works, for People Like Us.

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