Pull-Based Communication Boundaries
Choose when to receive routine messages while keeping urgent calls open
- Difficulty
- Moderate
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 94%
Pull-Based Communication Boundaries divide communication by urgency and let the recipient choose when routine information enters their attention. Neville removed email and WhatsApp from his phone, kept email on his iPad, and asked people to call him when a real problem required immediate action. Bartlett describes a related setup in which an assistant reviews his inbox, places relevant items on a list, and leaves notifications off. The mechanism is not total disconnection: routine communication becomes pull-based and batched, while a phone call remains the escalation path. Neville also warns that early-morning emails can pressure recipients and that written tone can damage culture. The method therefore combines device boundaries, channel rules, and sender restraint rather than simply ignoring messages.
Origin
Neville and Bartlett describe the communication boundaries they developed while managing high message volumes and multiple businesses.
Core principles
- 01Routine messages should not control attention
- 02Urgent problems need a clearly available channel
- 03Channel choice affects team pressure and culture
- 04Written messages can obscure tone
How to run it
- 1
Define urgency
Agree what constitutes a problem that needs an immediate response and what can wait for a routine review. Make the distinction clear to the people who rely on you.
Watch out Without an escalation rule, reduced notifications can turn into silent unavailability.
- 2
Move routine channels
Remove email and high-volume group messaging from the device that is always with you, or disable their notifications. Keep them available on a device or list you open deliberately.
Pro tip Neville keeps email on his iPad rather than his phone.
- 3
Choose review windows
Process routine communication when you are ready rather than whenever it arrives. Use an assistant or triage list where appropriate.
Watch out Set a cadence that still meets legitimate response expectations.
- 4
Keep calls open
Invite colleagues to call when a serious problem needs immediate attention. Treat that channel as a responsibility, not a decorative exception.
Watch out Do not label every routine request urgent to bypass the boundary.
- 5
Reduce sender pressure
Before sending early or emotionally toned messages, consider the pressure and ambiguity they may create for recipients. Use a conversation when tone or urgency matters.
In the wild
Neville says an alarming email seen at 4:00 a.m. can prevent him from returning to sleep. He therefore removed email from his phone, kept it on his iPad, removed WhatsApp, and tells people to ring when something is genuinely urgent.
→ Routine messages become deliberate inputs while urgent access remains available by phone.
Common mistakes
Closing every route
Removing notifications without an urgent escalation channel can leave colleagues unsupported.
Moving the same compulsion
Constantly checking a different device preserves the interruption pattern even if the phone is quieter.
Is it for you?
Best for
It is best for leaders and operators whose email or messaging volume repeatedly captures their attention.
Not ideal for
It is not ideal without clear coverage in roles that require immediate written monitoring for safety, care, or operations.
From the transcript
“I've taken email off my phone. It's only on my iPad”
“I choose when I go to it. It doesn't notify me that that it needs me now.”
“if there is a problem and something's gone wrong, then just ring”
From the episode
Gary Neville: From Football Legend To Building A Business Empire