Notification Rules and AI-Free Thinking Periods
In the last lesson you shaped the physical and digital space around you: closed tabs, a clean desk, a phone in another room. That handles distraction you can see coming. This lesson handles the distraction that arrives on its own schedule, and it adds a deliberate block of time where your own thinking runs without an AI assistant finishing your sentences.
By the end of this lesson you can:
- Explain why "just turn everything off" usually fails within a week.
- Write notification rules in a trigger, channel, and response-time format.
- Define an AI-free thinking period with clear boundaries.
- Schedule one daily AI-free block and protect its edges.
- Draft a one-page notification policy as the first artifact of your two-week routine.
From Default Alerts to Deliberate Rules
Every notification is a small claim on your attention, and each one leaves residue when you return to the task. You already know the cost. The problem is that turning everything off is too blunt: you miss the one message that actually mattered, feel guilty, and turn it all back on. So instead of on or off, you write rules.
A useful notification rule has three parts:
| Part | Question it answers | Example |
|---|---|---|
| Trigger | What event creates the notification? | A direct message from a teammate |
| Channel | How does it reach me? | Badge only, no sound, no banner |
| Response time | When am I expected to react? | Within the next check window, not instantly |
Sort every source into one of three tiers.
- Tier 1, live: rings or vibrates immediately. Reserve this for genuine harm if delayed 30 or more minutes: on-call alerts, a call from a caregiver, a hard deadline handoff. Keep this tier at two sources or fewer.
- Tier 2, batched: delivered silently and processed in two or three scheduled check windows per day, for example 11:00 and 16:00. Most work messages belong here.
- Tier 3, silent: digests, promotions, social activity, product updates. Read on your own terms, or unsubscribe.
flowchart TD
N["๐ Notification arrives"] --> Q{"Would 30+ minutes of delay cause real harm?"}
Q -->|Yes| E["๐ Tier 1: rings live"]
Q -->|No| Q2{"Is a person actively waiting on me?"}
Q2 -->|Yes| B["๐๏ธ Tier 2: batch for the next check window"]
Q2 -->|No| S["๐ฅ Tier 3: digest or unsubscribe"]
Exercise 1. List your ten most frequent notification sources. Assign each one a tier, then write the two Tier 1 entries as full trigger / channel / response-time rules.
Click to reveal a sample answer
Sample rule: "Trigger: on-call page from the incident tool. Channel: phone ring, bypassing Do Not Disturb. Response time: within 5 minutes, at any hour." A second rule might be: "Trigger: call from my partner. Channel: phone ring. Response time: as soon as I can step away, within 15 minutes." If your Tier 1 list grows past two or three sources, nothing is really Tier 1 anymore.
AI-Free Thinking Periods, Defined
An AI-free thinking period is a scheduled block where you work on a thinking task with no AI assistant, no autocomplete, no chatbot, and no AI search summary in front of you. Paper, a plain text editor, or a blank document only.
Why bother in a course about focus? Because an AI suggestion is a very fast interruption that feels like help. It arrives mid-thought, you accept or reject it, and your own line of reasoning is cut. The residue is subtle: you leave the block with output, but not with the thinking you meant to do. For a first draft, a diagnosis of a stuck problem, or a decision, the slow version is often the better version.
Two rules keep the block honest:
- Name the thinking task. "Draft section 2 of the project brief" is a thinking task. "Check email" is not.
- Write a boundary statement. One sentence describing what you will not do: "No prompts, no autocomplete, and no searching for answers until I have written my own first attempt."
_____ are scheduled blocks where no AI assistant or autocomplete is available while you work through a thinking task.
Scheduling Blocks and Guarding Their Edges
Start smaller than feels impressive. One 25-minute block per day, at a time when your energy is decent and your calendar is honest. Place it before your first inbox check, so you are not already answering someone else's question.
Then protect the edges, because the block fails at its borders more often than in its middle:
- Entry edge: decide the task and the boundary statement the evening before. A block that starts with "what should I do?" burns ten minutes.
- Exit edge: end with two minutes of notes on where your thinking stopped, so the next block starts warm.
- Escape hatch: if you get genuinely stuck, write the question down and leave it. Do not open a chat window mid-block.
A well-written notification rule states the _____, the _____, and the committed _____. The default state for any notification source should be _____, with exceptions added back deliberately. During an AI-free thinking period the escape hatch is to _____, not to open a chat window.
Exercise 2. Choose a daily slot for your AI-free block, write its boundary statement, and write the check windows for your Tier 2 messages.
Click to reveal a sample answer
Slot: 08:45 to 09:15, before the first inbox check. Boundary: "No prompts, no autocomplete, no search summaries until I have written a rough first attempt at the project brief." Check windows: 11:30 and 16:30, ten minutes each. Notice the check windows sit after the block. That ordering is what makes the block survive.
Rules of Thumb That Survive a Busy Week
- Batch, do not block. Silent, scheduled processing beats total abstinence, which rarely lasts.
- Two Tier 1 sources, maximum. Every extra live channel teaches you that live channels are normal.
- Check windows are short and bounded. Ten minutes with a timer. A check window with no end becomes an afternoon.
- Do not evaluate the block on day one. The first few AI-free blocks feel slower. That feeling is the muscle being used, not evidence that the block is a bad idea.
- Keep a fallback. On a chaotic day, a five-minute version of your block still counts. Consistency of the slot matters more than length.
- Common mistake: changing the whole policy at once. Change one tier per week and see what breaks.
What to Carry Forward
- Notifications become rules when you specify trigger, channel, and response time, and sort every source into live, batched, or silent.
- AI-free thinking periods protect the slow part of thinking by removing fast suggestions and naming the task and the boundary.
- The block works because of its edges: task chosen in advance, notes at the end, and a written escape hatch for getting stuck.
Your one-page notification policy plus your daily AI-free block are now the first two entries in your two-week routine. The checkpoint in the next lesson will ask you to explain your policy and justify each tier, so keep it where you can find it.
Front: What three parts make a complete notification rule? Back: Trigger, channel, and committed response time.
Front: What is the default state for a notification source in a personal policy? Back: Off, with exceptions added back deliberately.
Front: Tier 1 (live) notifications are reserved for what? Back: Events where a delay of 30 or more minutes causes real harm, such as on-call pages or a caregiver's call.
Front: How many Tier 1 sources should most people keep? Back: Two or fewer; every extra live channel makes interruption feel normal.
Front: What is batching in notification management? Back: Sending notifications silently and processing them in two or three scheduled check windows per day.
Front: Which tier do most work messages belong in? Back: Tier 2, batched: silent delivery, answered within a check window.
Front: What is an AI-free thinking period? Back: A scheduled block where you work on a thinking task with no AI assistant, autocomplete, chatbot, or AI search summary.
Front: Why does an AI suggestion cost more attention than it appears to? Back: It arrives mid-thought and cuts your own reasoning, leaving residue even when it feels helpful.
Front: What is a boundary statement for an AI-free block? Back: One sentence naming what you will not do during the block, such as no prompts or searches until your own first attempt exists.
Front: Where should the AI-free block sit relative to the first inbox check? Back: Before it, so you start with your own question rather than someone else's.
Front: What is the escape hatch when you get stuck during an AI-free block? Back: Write the question down and leave it for later instead of opening a chat window.
Front: How long should a first AI-free block be? Back: About 25 minutes, once per day, extended only when it starts to feel easy.
Front: Why do the edges of a focus block matter most? Back: Blocks fail at entry (no task chosen) and exit (no notes on where thinking stopped), more often than in the middle.