🎧How to Be Indistractable
Most PM days are stolen by Slack, meetings, and other people's urgencies. The ones who reclaim their time win.
The single biggest input to PM output isn't intelligence — it's protected time for thinking and writing. PMs who let Slack and meetings consume their day produce mediocre work. PMs who carve out 2-3 hours of deep work daily ship 2-3x more strategic output.
Distraction isn't an external attack; it's a choice to engage with external triggers. The fix is a small set of habits: time-block your calendar, batch your Slack, ruthlessly cancel low-value meetings, and protect your peak hours for L (leverage) work. Nir Eyal's framework is the most-cited modern playbook.
The four-part Indistractable framework (Nir Eyal)
- Master internal triggers. Recognize when discomfort (boredom, anxiety, loneliness) pulls you to your phone. Pause, name it, redirect.
- Make time for traction. Block your calendar around your most important work. If it's not on the calendar, it won't happen.
- Hack back external triggers. Notifications off. Slack on schedule, not always-on. Email batched 2-3x per day.
- Prevent distraction with pacts. Tools like Freedom, Cold Turkey, or self-imposed deadlines to make distraction harder.
PM-specific tactics
- Time-block the calendar. Two 2-hour blocks daily for L work. Marked as 'do not disturb.' Engineers will respect it.
- Slack on a schedule. Open at 9am, 1pm, 4pm. Not in between. Notifications off.
- No-meeting Wednesday. If your team supports it, take a day per week with zero meetings. Use for deep work.
- Default to async. Slack thread or written doc instead of meeting. Reclaim 5-10 hrs/week.
- Cancel recurring meetings quarterly. Audit your calendar. Cancel anything where you can't articulate the value.
The Sunday hour
One hour every Sunday: review the week. What were the L tasks? Did they get done? What's coming up? Plan the L blocks for the next week.
This single habit changes everything. It's where the senior PM rhythm starts.
The dangerous urgency trap
Most "urgent" Slacks aren't actually urgent. They're someone else's anxiety leaking onto you. The discipline: pause before responding. "Will this matter in a week?" If no, defer.
The exception: real production incidents, customer escalations with real revenue stakes, exec meeting prep. Those are real urgencies. Everything else can wait 3 hours.
Real-world examples
Asana institutionalized 'No Meeting Wednesdays' for the entire engineering and product org. Internal data showed strategic output (PRDs, design docs, code reviews of significant changes) increased 30%+. The discipline is now copied across many tech companies.
Go deeper — recommended reading
Interview questions (1)
Q1How do you protect time for deep work as a PM?behavioralmid▼
Three habits:
- Time-block the calendar. Two 2-hour blocks daily for high-leverage work — usually mornings. Marked 'do not disturb.' Engineers and my team respect it because I've communicated it explicitly.
- Slack on a schedule. I open Slack at 9, 1, and 4. Not in between. Notifications are off. Most 'urgent' Slacks turn out to be not-urgent when you check them 3 hours later.
- No-meeting Wednesday. Whole day, no meetings. Use for the things that require thinking — strategy docs, deep PRDs, customer call synthesis.
The result: even on a busy week, I get 8-10 hours of real deep work time. That's where 80% of my actual output comes from. Without the discipline, those hours evaporate into Slack and meetings.
The discipline is hard for the first 6 weeks — you'll feel like you're missing things. After 6 weeks, your team adapts and the rhythm becomes normal.