How to respond when overload hits: three concrete steps

Executive overview

Workload doesn't move in a straight line — it oscillates. Trying to stay just below your limit means you'll regularly spike above it. Overload is partly structural, not a personal failure.

The fix isn't to work harder through it. Reduce first, then systematize, then prevent.

Preventing overload means compressing the amplitude of that oscillation — not stopping it.

Why overload is hard to avoid

• Obligations behave like a supertanker: momentum carries you past where you wanted to stop
• Keeping obligations near your limit produces oscillations above and below it
• Lowering your target to avoid peaks creates valleys that are too empty to be viable
• Some overload is therefore structurally inevitable for most people

Step 1: Reduce what you can right away

• The goal is breathing room — not a perfect fix
• Cancel, defer, or step back from anything that isn't essential right now
• This includes social plans, volunteered commitments, agreed talks, non-urgent meetings
• The resistance to pulling back is moral, not practical — being the person who "handles it" feels important
• Pulling back in response to overload is a rational response, not a failure

Step 2: Systematize the remaining workload

• Having a plan doesn't reduce the hours, but it eliminates the background anxiety
• Block time in advance for specific tasks — don't leave execution to chance
• Set up autopilot scheduling for ongoing work that generates repeated small decisions (e.g. 35 minutes each morning on a high-friction project)
• Create or protect large unbroken blocks: negotiate with partners, add childcare, use Sunday mornings
• Once your brain sees a credible plan, the hum of anxious monitoring stops

Step 3: Plan to prevent similar overload in the future

• Do this before you've made significant progress on the current overload — the psychological boost is immediate
• It shifts the locus of control back to you: this is hard, but I've learned from it
• Not about stopping oscillation — about squeezing its amplitude

Tools for reducing future overload

• Quotas — decide in advance how much of a recurring obligation type you'll accept per quarter (e.g. four peer reviews per semester); use the quota as a ready-made polite no
• Future time blocking — when considering a new commitment, find and block the actual sessions needed in your calendar first; if you can't find them, don't say yes
• Automatic no list — categories of requests you decline without deliberation
• Hard nos — when saying no, don't leave wiggle room; vague nos just route more work back to you
• Deferred yeses — don't commit in the moment; say "let me check my schedule and get back to you Monday"; this breaks the social pressure of the live request and lets you decide clinically later
• Bigger shifts — treat workload controllability as a serious career factor alongside content and location; chronic overload in a role is a signal worth acting on

Slow productivity: on collaborative research stalls

• Projects stalling on collaborator availability is partly a pace problem — great intellectual work rarely moves in a straight line
• Measure productivity at the scale of years, not months
• Find collaborators for whom your shared project is their tier-one priority
• Collaborators at the same institution (accessible in person, regularly) reduce coordination overhead
• Some projects benefit from solo phases you fully control

Second brain systems

• You need some trusted external store for information you can't hold in your head
• The complexity of the system matters less than having one — simpler often works fine
• Elaborate cross-linked systems (Notion databases, tagging) rarely pay off over basic notebooks or folder structures
• The system cannot do the thinking; intellectual work remains hard regardless of storage sophistication
• Over-investing in the system can displace the actual thinking

Billable hours and deep work breaks

• If billable targets require more total hours than the work itself takes, reduce non-billable breaks rather than extending them
• Deep breaks — throttle cognitive intensity without switching context: shift from hard drafting to organizing notes, writing careful process-oriented emails, or filing
• These breaks are still billable, allow cognitive recovery, and keep total hours closer to billed hours

Hyperactive hive mind in large organizations

• Constant unscheduled messaging is a collaboration strategy, not an inevitable feature of work
• In large organizations, managerial incentives favor stability and risk-reduction over efficiency — the hyperactive hive mind is hard to change from within
• Meaningful change requires leaders, not managers, to impose it
• Individuals can improve their situation at the margins; structural change requires organizational will
• If a role is fundamentally a high-intensity hyperactive hive mind role, assess the trade-off honestly rather than assuming it's fixable

Smartphones and declining academic performance

• OECD reading, math, and science scores have declined consistently since roughly 2012 — predating pandemic learning loss
• 2012 coincides with smartphones crossing 50% ownership and becoming common among adolescents
• The hypothesis is straightforward: devices that undermine concentration produce worse performance on tasks requiring concentration
• Knee-jerk skepticism from elite commentators often reflects status signaling more than genuine analytical complexity
• The pattern parallels tobacco: evidence has accumulated to the point where "it's complicated" is no longer a sufficient response