The Distracted Mind
Entrepreneurs
DropRegion · Lessons from The Distracted Mind · Adam Gazzaley & Larry Rosen

What Entrepreneurs Can Learn from The Distracted Mind

It's 7:40 a.m. and the founder has three tabs open: the investor deck, a spreadsheet of runway numbers, and a bug report from last night. She means to finish the deck before the 9 a.m. call. Instead, a Slack message from her cofounder about a delayed shipment pulls her into a side conversation, and while typing a reply she remembers she never followed up with the candidate for the ops role. She opens a new tab to email him, sees an unrelated notification about a payment failure, and clicks through to check it. Twenty minutes later the deck is untouched, the payment issue turned out to be nothing, and she feels the familiar guilt of having "wasted the morning" through sheer lack of discipline. But the problem was never her discipline. It was a mismatch between how many things she wanted to hold in mind and how much focus a single mind can actually sustain at once — and that reframe changes what she does next.

01 · The Book in One Minute

The whole book, compressed

01The Founder's Bandwidth Problem
02Naming What's Actually Interference
03Structuring Around It Instead
04An Always-expanding Set Of Pulls

This edition works through 4 core lessons — take them one at a time, not all at once.

02 · Where Are You Now?

What's different for your conditions

Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.

You are almost always running more open loops than any single role would require, because founding a company means being several roles at once.
Your interference often arrives disguised as urgency, since a cofounder's message or a customer's complaint can feel indistinguishable from a genuine fire.
You have unusually weak boundaries between "work" and "everything else," so personal and business interference blend together all day.
You lack the organizational scaffolding — assistants, fixed meeting blocks, gatekeepers — that could normally absorb interference before it reaches you.
Your own ambition is a major interference source, since new ideas competing for attention are self-generated, not external.

0 of 5 selected

03 · Core Lessons

The core lessons, applied to you

The Founder's Bandwidth Problem

The founder's bandwidth problem

The idea

Wanting to build the product, close the round, hire the team, and keep customers happy simultaneously is a completely ordinary drive, but no founder's mind can execute all four with full focus at the same moment. The book's argument is that this gap is structural, not a character flaw.

What it looks like

A founder blocks two hours for product strategy but keeps her phone face-up "in case a customer needs something," checks it nine times, and finishes with three shallow paragraphs instead of a real plan.

Try this

Before any block of founder-only work, write down the one goal that block serves, and put the phone in another room rather than face-down on the desk.

Naming What's Actually Interference

Naming what's actually interference

The idea

Not every pull on attention is the same kind of pull. Some comes from outside — a message, a ping, a hallway question — and some comes from inside, like a nagging worry about payroll. Telling the two apart is the first step to handling either one.

What it looks like

During a hiring call, a founder outwardly nods along while internally rehearsing what he'll say to an investor later that day, and misses the candidate's answer to the question that mattered most.

Try this

When attention drifts mid-conversation, silently name whether the pull is external or internal — it takes one second and often breaks the spell.

Structuring Around It Instead

Structuring around it instead of white-knuckling

The idea

Trying to simply resist interference through willpower is a losing strategy over a long founder day. Restructuring the environment — batching, closing tabs, setting explicit windows for reactive work — holds up far better than resolve alone.

What it looks like

A founder tells himself he'll "just ignore Slack" during deep work, then breaks his own rule within ten minutes because the app is still open and one green dot away.

Try this

Physically close or log out of every messaging tool before starting focused work, so returning requires a deliberate act rather than a glance.

An Always-expanding Set Of Pulls

An always-expanding set of pulls

The idea

As a founder's tools multiply — more channels, more dashboards, more integrations meant to help — so do the entry points for interference. This isn't a problem solved once with a clean inbox; new sources of pull keep arriving as the business and its software stack grow, which means managing attention is an ongoing operating habit, not a one-time fix.

When the clusters compete

Naming interference and structuring around it can pull against each other: pausing to label every internal worry mid-task can itself become a distraction. The practical resolution is to name quickly and move on, saving deeper reflection on recurring internal pulls for a scheduled review rather than the middle of focused work.

04 · Choose Your Priority

Name one thing, honestly

What is the one open loop you're carrying right now that has nothing to do with the task in front of you, and where could it live instead of in your head?


Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.

05 · Put It Into Practice

The practices from this edition

Before any block of founder-only work, write down the one goal that block serves, and put the phone in another room rather than face-down on the desk.
When attention drifts mid-conversation, silently name whether the pull is external or internal — it takes one second and often breaks the spell.
Physically close or log out of every messaging tool before starting focused work, so returning requires a deliberate act rather than a glance.

0 of 3 selected

06 · Small Experiment

Run this for seven days

Physically close or log out of every messaging tool before starting focused work, so returning requires a deliberate act rather than a glance.

07 · Remember This
If you remember only 4 things
01The Founder's Bandwidth Problem. Wanting to build the product, close the round, hire the team, and keep customers happy simultaneously is a completely ordinary drive, but no founder's mind can execute all four with full focus at the same moment.
02Naming What's Actually Interference. Not every pull on attention is the same kind of pull.
03Structuring Around It Instead. Trying to simply resist interference through willpower is a losing strategy over a long founder day.
04An Always-expanding Set Of Pulls. As a founder's tools multiply — more channels, more dashboards, more integrations meant to help — so do the entry points for interference.
08 · Your Next Step

What will you do differently because you read this?

For the fuller case behind this reframe, the original argument comes from Adam Gazzaley and Larry Rosen's The Distracted Mind.

Also in this series — Lessons from The Distracted Mind
1. Entrepreneurs
2. Leaders & Managers
3. Teachers
4. Parents
5. Students & Young Adults
6. Career Professionals
7. Creators & Innovators
8. Coaches & Mentors
9. Sales & Customer-Facing
10. Everyday Life