Use AI in one bounded block at the start of a deep work session to set up your thinking, then close it and work alone. The trap isn't AI itself. It's treating AI like a chat buddy you keep pinging mid-task, which scatters your attention the same way notifications do.
I've watched plenty of people, past me included, open an AI tool to "save time" and lose an hour to a rabbit hole of clever-sounding tangents. Here's the system I use to keep AI on the useful side of that line.
Why AI quietly breaks focus
Deep work depends on holding one problem in your head long enough to get somewhere with it. Every time you switch to ask AI something, you pay to switch back. AI feels different from social media because it's "productive," so we don't guard against it. But an open chat window is an open loop. It invites the next question, and the next.
The fix isn't banning AI. It's giving it a defined role and a defined time, then getting out.
The Focus Defender Playbook
This is the loop I run for any deep work session where AI is involved. Four phases. Once you know it, the setup takes about ten minutes.
1. Front-load the AI (the prep block)
Before the real work starts, spend one short block using AI to remove friction, not to do the thinking for you. Good prep jobs:
- Turn a vague goal into one concrete sentence for the session.
- Generate an outline or a list of the sub-problems you'll need to solve.
- Surface questions you haven't thought to ask yet.
- Stress-test your plan: "Where am I likely to get stuck?"
Notice what these share. They set you up to work, then hand the work back. You're using AI to sharpen the problem, not to skip it.
2. Define the exit condition out loud
Before you close the tab, decide what "done with AI for now" means. Something like: "I have my objective and a three-step outline. That's enough to work for 90 minutes." Say it, write it at the top of your doc, then close the AI window. Not minimize. Close.
This one habit does most of the heavy lifting. An open loop you can't see is much easier to leave alone.
3. Do the work alone
Now run your deep work block with no AI at all. If a question comes up, don't switch. Write it on a "park it" list, on paper or in a scratch note. Most of those questions answer themselves as you work. The few that don't become your next prep block.
This is the part people skip, and it's the whole point. The value of deep work is you doing the thinking. AI that interrupts that isn't helping.
4. Debrief with AI at the end (optional)
If you've got a final short block, bring AI back to review what you made, catch gaps, or plan tomorrow. Same rule: bounded time, clear exit, then close it.
The one thing that makes this stick: better prompts
The playbook lives or dies on your prep-block prompts. A lazy prompt invites a sprawling conversation, which drags you right back into the scatter you're trying to avoid. A sharp prompt does the opposite. It gives you a specific output and a natural place to stop.
A prep prompt worth using generally gives the AI a clear role, a constraint on how much it should return, and a hard stop so it doesn't expand into next steps you haven't asked for. That structure keeps the tool from filling your whole morning.
Writing those prompts well, every time, for every kind of session, is tedious. That's the gap I built the Focus Defender Deep Work Prompt Pack to fill. It's a Notion template with ready-to-run prompts for scoping, planning, park-it triage, and end-of-session review, each structured to keep AI in its lane. If you want the playbook above without writing all the prompts yourself, that's the shortcut.
A simple daily version
If four phases feels like a lot, start here:
- One 10-minute AI block to scope the session.
- Close every AI tab.
- 90 minutes of solo work, with a park-it list.
- Reopen AI only if you've got a real, written-down question left.
Do that for a week and you'll feel the difference. AI becomes a thing you use on purpose instead of a thing that uses your attention.
FAQ
Isn't it faster to just keep AI open the whole time?
It feels faster and usually isn't. Constant switching costs you the deep-focus state that produces your best work. A bounded AI block plus solo work almost always beats a scattered, chat-driven session on quality.
What should I never hand to AI during deep work?
The core thinking, the part only you can do: the argument, the design decision, the actual writing or problem-solving. Use AI to scope and support, not to replace the thing you're trying to get good at.
How long should the AI prep block be?
Short. Five to fifteen minutes is plenty for scoping a session. If your prep block keeps running long, that's usually a sign your prompts lack a clear stopping point.
Do I need a special tool, or just a normal AI chat?
A normal chat works fine. The system is about how you bound the interaction. A prompt pack helps because it removes the friction of writing tight prompts every time, but the playbook works with whatever AI you already use.