This issue of Pythoness Perspective was sent to newsletter subscribers. Browse all issues
Pythoness Perspective
Decline the wrong tools — and pick one back up
- From
- Amanda Nelson · Pythoness Programmer
- Reply-To
- help@pythonessprogrammer.com
- Sent
- Authors
- Amanda Nelson

Maya week 2: remove, archive, honest return — Notion out, Drive in, and a Google Form capture that replaces dashboard guilt.

Last week's audit named Slack-after-hours and inbox-always-open as takes. This week: decline the wrong tools — and pick something up again when the audit says yes. Boundaries are not one-way doors.
Maya is fictional. Tool guilt is very real.

~4 min read
This week: Remove · archive · honest return — choose on purpose, not from guilt or FOMO.
Try today: One decline or one intentional return, with a one-line why written down. Optional: start a 28-day daily-use test on the system you kept.
Workbook: Tech Boundaries Workbook — decline/return log.
🔥 Fire Horse principle (Ship the Smallest Version That Serves): Sometimes the smallest version is Gmail, Drive, and a Form on your home screen.
Part 1: Maya, week 2 — Notion out, Drive in
Last year, Maya bought Notion mostly for the AI. She hoped it would finally hold her client wiki, portfolio notes, shop tasks, and the half-formed ideas she captured on her phone. It looked like the organized illustrator life. It became a second job: templates to maintain, pages to reorganize, guilt when the dashboard was stale.
Then the news landed: Notion is shutting down Notion Mail and leaning harder into AI agents for inbox work. Maya was not using that email product. She still recognized the feeling — paying for a tool that kept drifting toward features she did not need, while the parts she actually used (files, quick captures) already lived somewhere else.
She did not fail at productivity. She ran the audit and kept it simple: finished client folders in Google Drive, client threads in Gmail, illustration in the software she already draws in, Todoist for what ships this week. Same summer. Fewer tabs. Canceling the Notion subscription stopped feeling like quitting and started feeling like consolidating — her tech and her projects — so the slower months could go to drawing instead of dashboard maintenance.
Honest return: Google Calendar for client booking. She had left it when she over-customized event types and spent a week fixing confirmation emails instead of drawing. She tried a spreadsheet, then a simpler setup, then returned — same tool, fewer knobs.
Still KEEP: Canva for shop graphics and client mood boards — not because it is perfect, but because it fits when it stays in the shop admin window. Last year she let it sit open all day; that was the drain, not the tool. Lately she has been reaching for Canva's newer video tools more often too — short clips for the shop and mood boards, same bounded window, one less app to open. I have been doing the same.
The inbox she actually needed: a simple Google Form — one field for the idea, and the braindump for her to sort through later — pinned to her phone home screen, with a recurring Todoist task so she remembers to empty any ideas lingering into it. Same job as her old Notion inbox. No second workspace to maintain. She will know the system is working when she uses it daily for 28 days and it becomes a habit — not when the dashboard looks impressive, but when it has data to analyze, and brain dump inspirations to come back to.
Part 2: Three moves — not just "delete everything"
| Move | When | Maya's example |
|---|---|---|
| Remove | Costs more energy than it returns | Notion subscription canceled |
| Archive | Done for now; might inspire later | Old client boards → Google Drive folder |
| Honest return | Audit says yes again; shame stays out | Google Calendar with two event types, not twelve |
| KEEP (bounded) | Right tool, wrong window last year | Canva — graphics and video in shop admin hours only |
| Replace simply | Same job, less upkeep | Notion inbox → Google Form on home screen + Todoist reminder (28-day habit test) |
Decline without drama. Return without apology.
Part 3: Values are a decline reason too
Tool cycling is not only friction and price. It is who your money supports and what your data feeds.
Maya cannot always leave a client's Slack. She can decline paying for tools on her own dime that spike values-anxiety — and name the take when a shared workspace was chosen without her.
In March I put Cal.com in my DRAIN bucket; I tried alternatives; I put it back when the math said return. Todoist stays KEEP. Same skill Maya is practicing — the record is allowed to update.
Part 4: Tool guilt scripts
| Old script | Better script |
|---|---|
| "I failed at decluttering." | "I ran the audit again." |
| "I shouldn't need this tool." | "This tool costs X and returns Y — today's math says keep." |
| "Going back means I wasted time." | "Leaving taught me what I actually need." |
| "Switching tools makes me disloyal." | "My files travel. I choose where I open them." |
Part 5: Archive without building plumbing
Last July's workspace issue went deep on organizing your digital environment. This year's version is simpler: archive without building a system you have to maintain.
| Medium-energy move | No code required |
|---|---|
| Folder move | Finished client work → Google Drive Archive/ |
| Desktop sweep | Three files off the active surface — notice the relief |
| Decline / return | Notion out; Calendar back with a simpler setup |
| Capture on the go | Google Form on phone home screen + Todoist reminder — 28 days to habit |
| Canva boundary | Shop graphics and video in the admin window only — not during illustration |
| Todoist | Three projects max — forces "what ships this week" |
You get the result of a good system by using it for 28 days — not by maintaining a second workspace you dread on a low-energy day.
Personal update
I've been getting into poems again — and going through old art — after my cousin Avery Valenciano's Liturgy For an Ugly Cry: and other poems, which prints some of her artwork from over the years right in the pages. Ten years into a chronic health journey has clarified a lot about my health, my attention, and my patterns. Pulling old work into a poem book of my own and seeing the same cycles across decades is a new, fairly exciting thing in my mid-thirties. Avery's reminder that art is art was the last little push I needed to start organizing and finalizing.
Your tech struggles, reflected back. Got one? Send it in.
Look back at the past year:
What did you remove, archive, or walk away from — and was any of that about values, AI FOMO, or a product shifting under you?
What did you pick back up without apology when the audit changed?
What simpler capture could replace a dashboard you maintain out of guilt — a form, a note, a Todoist inbox?
Where does "decline" feel like disloyalty when it is actually consolidating your stack — and what would 28 days of daily use prove about the system you kept?
Hit reply. I read every one.

🔥 The Fire Horse's Callout: What to Charge Forward With
The Fire Horse does not collect tools like trophies. It keeps what runs — and drops what doesn't — without making either move a moral event.
Ship the smallest version that serves. Sometimes that is a return trip.
🔥 Charge forward with: One decline or one intentional return this week — with a one-line why written down.

What's next
Next Friday: Maya names her response windows out loud — so collaborators stop reading silence as neglect.
No July live this month — newsletter and workbook only, same as June.
— Amanda
Resources
| Resource | Best for |
|---|---|
| Tech Boundaries Workbook (free PDF) | Decline/return log |
| Tech Boundaries hub | Full July arc + last year's depth |
| Mindful Automation | May — meet Maya |
| Notion Mail shutdown (Ars Technica) | The news that nudged Maya's cancel |
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 stuck in tool-guilt instead of tool-truth
Reflection sessions, not rescue. Tech That Works, for People Like Us.
Part of the Tech Boundaries series — pythonessprogrammer.com/tech-boundaries

This issue was sent to newsletter subscribers. Sign up to receive the next one (weekly, march–november).
Pythoness Perspective
Weekly issues, March through November only. Each month is one arc—a deep dive through a tech sovereignty resource I teach, with practical steps each week tied to the same frameworks in my free guides and sessions.


