The Cost of Context Switching
Why asynchronous intros beat synchronous asks.
The Myth of the "Quick Call"
A "15-minute intro chat" never costs 15 minutes. It costs 5 minutes of prep, 15 minutes of execution, 10 minutes of follow-up, and 20 minutes of recovery time to get back into deep work. Total cost: 50 minutes.
| Task | Perceived Cost | True Cognitive Cost |
|---|---|---|
| Reviewing a blind intro email | 1 min | 5 mins (Task switching penalty) |
| Taking an unprepared intro call | 15 mins | 50 mins |
| Reviewing a double opt-in request | 2 mins | 2 mins (Asynchronous batching) |
Asynchronous Batching Protocol
We recommend batching all network maintenance and opt-in reviews into two specific 30-minute blocks per week (e.g., Tuesday at 4 PM, Friday at 3 PM). This isolates the context switch and protects maker time.
Common Mistakes
- Keeping Slack/Email notifications on during deep work blocks.
- Agreeing to synchronous calls when an asynchronous voice note or email would suffice.
- Not aggressively protecting calendar whitespace.
FAQ
What if the request is urgent? 99% of network introductions are not urgent. If it involves a server outage, a term sheet deadline, or a critical health issue, break the protocol. Otherwise, wait.
Internal Links: Double Opt-in Standard, Inbound Filter Tool, Homepage, Writing Forwardable Emails, Pricing, All Guides, All Tools, Cost of Context Switching, Sender Reputation, Network Maintenance, ROI Calculator, Network Value, Template Generator, Spam Checker, Time Zone Tool, Follow-up Cadence, Relationship Scorer, Security Policy, Terms of Service, Privacy Policy.