The original is one click away. Open original ↗
Cal Newport's process for writing New Yorker articles and managing context
Executive overview
Mixing unrelated email contexts in one inbox creates cognitive drag even during shallow work. Separate workspaces eliminate that drag by keeping each context isolated.
Meeting processing is the most neglected productivity habit — closing loops immediately after each meeting prevents end-of-day overwhelm. Cal's New Yorker writing process is designed to occupy as little of the normal workday as possible: one weekday morning and a Sunday session, with structure determined on foot.
The core insight: context fragmentation is a hidden tax on all work, not just deep work.
Separating email into distinct Google workspaces
- Six email addresses feeding one Gmail inbox caused severe context-switching drag even during brief inbox checks
- Solution: three separate Google Workspace accounts — Georgetown, personal, calnewport.com — each with its own Gmail, calendar, and Drive
- Checking any one inbox is now fast and contextually coherent
- New Yorker address kept intentionally separate; a colleague forwards only what requires attention
- Inbox should process to zero; using it to store reminders or ideas signals a leak in the broader system
Shutting down the workday when afternoons are meeting-heavy
- Moving the daily shutdown earlier — e.g. to lunchtime — is a legitimate and effective option
- Process inbox and review the weekly plan at lunch; afternoons then focus entirely on calls and meetings
- Open loops from unprocessed meetings accumulate silently and drain cognitive energy by end of day
- Schedule a 15–30 minute processing block immediately after every meeting, as a calendar entry
- Use that block to capture commitments, send follow-up emails, update task lists, and set reminders
- After four back-to-back meetings with processing blocks, end-of-day shutdown becomes lightweight
Deep life buckets vs. value-based multiscale planning
- Value-based multiscale planning is the persistent operating system: values → semester/quarter plan → weekly plan → daily time-block plan
- The bucket system is a one-time overhaul: craft, community, constitution, contemplation (or equivalent categories)
- Bucket method step one: establish a non-trivial keystone habit for each bucket, tracked daily
- Bucket method step two: dedicate 4–6 weeks per bucket to overhauling that area of life
- The two systems intersect inside the semester plan — the current bucket overhaul becomes a line item that percolates into weekly and daily plans
- Multiscale planning is how you live; the bucket system is a periodic recalibration toward the deep life
Meeting prep vs. processing for heavy-meeting roles
- Preparation (agendas, pre-read memos) matters but receives disproportionate attention relative to its impact
- Processing — the 15–30 minutes immediately after a meeting — is the higher-leverage habit
- Book processing time as a calendar block attached to every meeting so it cannot be displaced by another invite
- Close every loop opened in the meeting: commitments, reminders, task-list updates, follow-up emails
- Shared agenda documents rarely get reviewed by other attendees unless they report directly to you; maintain your own systems instead
- Going meeting to meeting without processing creates compounding cognitive debt; effectiveness drops sharply
Cal's New Yorker writing process
- Two article types: a twice-monthly column and longer, infrequently published reported pieces; the column process is described here
- Research is constrained to what is already known, plus scheduled interviews and one or two relevant books — done weeks in advance
- Production alternates week by week: one writing week, one editing/fact-checking week
- Ideal writing schedule for a column:
- Outline the article on foot (e.g. during a morning walk) — no desk time required
- Happy hour session (end of a workday, early in the week): pull sources into Scrivener, write the opening paragraph
- Thursday or Friday morning: aim to complete roughly half the article
- Sunday morning: finish the draft
- Monday or Tuesday morning: polish and file
- When the schedule slips, add Saturday and/or an extended Monday block — semester breaks provide crucial recovery time
- The process is designed so only one weekday morning per cycle is consumed, leaving the rest of the workweek intact
- Longer reported pieces with multiple interviews operate over months; steady, non-urgent progress suits that format better
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.