Your Playbook Is the System

Four weeks ago you identified one task that costs more energy than it deserves.

Three weeks ago you looked at when your communications land — and whether that was a decision or a default.

Two weeks ago you mapped where your clients fall through gaps your system doesn't notice.

Today we build the document that holds all of it.

The automation playbook is one document that answers five questions. A document you can open, read, update, and hand off — to your future self, to a collaborator, to an AI assistant, or to the version of you who comes back to this work after a long break and needs to remember exactly how things work. A Notion database with thirty linked tables will not do what this document does, because you will stop maintaining it.

The document that describes your automations is the thing that keeps them running over time. Build that first.

Two days from now we go live. Bring yours — or bring the questions you still have about building it.

~3 min read

• This week: Building the automation playbook — one document, five questions. The Y.O.U.R. self-assessment to close the arc. And Maya's story reaches its conclusion — the version where the system actually worked.

• Do this today: Open a new file. Name it automation-playbook.md. Write at the top: Last updated: May 29, 2026. That is the first line. You can do the rest at your own pace — I give you the five questions below.

• IDE tip (live today): Cursor Rules, AGENTS.md, playbook, and GitHub — capstone blog + video at From Files to Playbook and YouTube. Resource guide: Resources hub — Mindful Automation.

• Sunday: Live event — May 31 at 3:30pm ET. Add to calendar →

• 🔥 Fire Horse principle (The Record Is the Guide): The playbook is the record of what you actually did — and that makes it a better guide than any plan.

MAIN FEATURE — Building Your Automation Playbook

One document. Five questions. Here is what it answers:

1. What automations do I currently run?

List them. Not a technical spec — plain language. Confirmation email when someone registers for an event. Weekly newsletter on Friday mornings. Follow-up email with replay link 2 hours after an event ends.

If you cannot list them all in ten minutes, you have more automations than you can currently maintain. That is useful information.

2. What does each one do if it fails?

One sentence per automation: If the event confirmation fails, manually send a confirmation email from my personal address within 2 hours.

This is the backup plan section. Write it before you need it, not during the emergency.

3. What is my client journey from first contact to post-event follow-up?

Map it as a sequence. Every step, what the client receives, and what they are expected to do. Anywhere you see a gap — information they have to remember, a link they have to find again, a follow-up they are expected to initiate — mark it. That is your error-proofing to-do list.

4. What is the timing of my communication cadence?

If you did Week 2's tip, this is already in my-rhythms.md. Copy the relevant section here or link to it. Newsletter day. Reminder windows. Follow-up timing. In plain sentences, not platform settings.

5. What is my context file for AI tools?

A short plain-text description of who you are, how you work, what your naming conventions are, and what tools you use. This is O.U.R. Context in document form — the thing you give any AI assistant, collaborator, or script so it understands your system without requiring you to re-explain it every time.

For the IDE walkthrough — rules, AGENTS.md, and putting the folder on GitHub — see From Files to Playbook.

Part 2: The Y.O.U.R. Self-Assessment

Use these questions to close the arc. You do not have to answer all of them today. But read them once before Sunday.

Y — Your Unique Brain: Does your automation reflect how you actually work, or how you thought you should work when you set it up? Where are the gaps between design and reality?

O — Observe & Optimize: Where did you observe a client experience gap this month? What is one specific thing you changed, or plan to change, based on what you saw?

U — Uncomplicate & Understand: What is the simplest version of your most complex automation? Have you confirmed the simple version works?

R — Reach: Is your client journey designed for your client's brain, or for your admin dashboard? Where are you assuming more from your clients than is actually fair?

Part 3: Maya, Week 4

This is how Maya's story ends — the version where the system was designed for her.

On Tuesday May 26, Maya receives a different kind of reminder email.

The subject line is simple. The email is short: what the event is, what she would walk away with, a direct calendar link, and a single line: Have a question you want me to answer live? Hit reply.

She replies. She writes two sentences about an automation she has been staring at for three months and doesn't know how to fix.

On Sunday she shows up at 3:30pm.

Within one hour of the event ending, she receives a follow-up email with the replay link, the resource page URL, and one next step — not twelve. One.

That is the playbook working. Tuesday's email was a design decision. The single-step follow-up was a design decision. The reply prompt was a design decision.

None of them required a new tool. They required a creator who looked at their system from the client's side and made different choices.

Maya is fictional. The pattern she represents is not. Your Maya is real — and whether she gets this version of the story depends on the choices you make in your system.

CURSOR / VSCODE TIP — R: You Built an Engineering Repository

Look at what you have built over the last four weeks:

• A folder open in a single window with your file tree visible

• my-rhythms.md — your communication cadence in plain language

• At least one template saved as a Markdown file

• A terminal tab you have opened at least once

That is an engineering repository. Not because it contains code — because it contains structured, maintained, searchable knowledge that any tool can act on.

To make it permanent and AI-readable: add .cursor/rules/, AGENTS.md, and GitHub via GitHub Desktop — no terminal required. The full screen walkthrough is in today's capstone post and video.

Capstone blog + video (live today): From Files to Playbook · Watch on YouTube · Resources hub

New to GitHub? Start with GitHub Basics: Your Profile README as a First Project.

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

This week's prompt:

What is the one thing you most want to automate that you haven't started yet — and what is the real reason you haven't started?

Reply on the site or bring it Sunday.

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

The Fire Horse documents the thing it just shipped before it moves on to the next one. Not because it is meticulous — because a system you cannot describe is a system you cannot improve, hand off, or return to after six months away.

The playbook is the record of what you actually did. That makes it more useful than any plan you made before you did the work, because it reflects reality instead of intention.

Write the first line today: Last updated: May 29, 2026. The rest can come later.

🔥 Charge forward with: One document, first line written, named and saved in your folder before Sunday.

WHAT'S NEXT

This Sunday, May 31 at 3:30pm ET:

Automate with Intention: Building Systems That Work for You and the People You Serve

YouTube Live + Luma. Walkthrough of the Y.O.U.R. Framework, live O.U.R. Context demo, the full Maya debrief, and open Q&A. Bring your real automation questions, your broken sequences, your "I don't know where to start."

Register: luma.com/indojpzh

Add it to your calendar now. (Maya would want you to.)

If anything in this arc landed for you, tell me on the site or at the live event.

See you Sunday.

— Amanda

The Pythoness Perspective is free, always. If it helps you, here are ways to support the work:

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

• May 31 live event — free. Register at luma.com/indojpzh

• Browse free resources → pythonessprogrammer.com/resources

• Leave a tip via Stripe — see support page

• Cash App $ANCreative · Venmo @ANCreative · Zelle hello@amanda-nelson.com

• Shop → stickyspells.etsy.com

• Forward this issue to someone who needs a brain-friendly path into automation

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

Part of the Mindful Automation series — pythonessprogrammer.com/mindful-automation

Capstone blog: From Files to Playbook · Previous: Your IDE Is a Workbench