How to maintain focus and cognitive health during distracting news cycles

Executive overview

Persistent breaking news creates a long-term destabilization of focus that continues for days after an acute event — not during it. Your experience of the world is determined by what you pay attention to; treat your mind like a private garden and be deliberate about what you let grow there.

During an acute event, stop working entirely. Afterwards, use six structured tactics to prevent the ongoing chatter from eroding your cognitive state.

The real problem is not the news itself but the endless low-quality information stream that follows — and the compulsive checking it triggers.

Two caveats before the six tips

• During a major breaking news event, it is completely fine — and rational — to stop working.
• Trying to work through an acute crisis is pseudo-productivity: visible activity used as a proxy for useful effort.
• Slow productivity reframes this: quality results over time matter, not moment-to-moment activity. One lost day changes nothing; a week of fractured focus does.
• All six tips below apply to the days after an acute event, when chatter and rumination persist.

Tip 1: Go into newspaper mode

• Commit to one defined daily ingestion window for news — nothing outside it.
• Treat everything else as noise that will be aggregated and filtered before your next check-in.
• Social media creates the illusion you need up-to-the-minute information. You don't.
• You are not Anderson Cooper. The world will be fine if you are 24 hours behind.

Tip 2: Move up the information food chain

• Social media and Twitter are the algae layer: high volume, low calorie, infinite scroll.
• As you move up the chain — newsletters, trusted independent sources, major newspapers — information becomes more processed, verified, and finite.
• Higher-quality sources are self-limiting: one newsletter, three articles. You can't lose hours in them the way you can in a social media feed.
• During breaking news periods, cut the algae entirely and consume only concentrated, high-quality sources.

Tip 3: Seek flow states

• Find activities — professional or personal — that produce full absorption: deep work projects, athletic training, board games, novels, films.
• Flow states are a cleaning pass on the brain: they clear the anxious rumination chemicals that a breaking news cycle generates.
• Getting lost in an unrelated activity is not avoidance — it is resetting your cognitive baseline.

Tip 4: Implement the hard day protocol (HDP)

• Designed for acute, persistent sources of stress (breaking news, a hurricane tracking toward your city, personal upheaval).
• Morning check-in: consume the available information, then apply cognitive behavioural therapy — identify distortions (catastrophising, black-and-white thinking, future-predicting), and end with a grounded summary of where things actually stand.
• Evening check-in: repeat the same process later in the day.
• Between the two sessions: when the urge to ruminate arises, acknowledge it and redirect — "we already processed this in the morning session; we'll revisit at the evening check-in."
• The protocol prevents ruminative grooves from deepening. It confines thinking to bounded windows, and the urge to spiral passes faster.

Tip 5: Take a hard break from your phone

• The phone is the primary vector for compulsive checking during breaking news.
• Put the phone in a fixed location. Go to it if you need it — don't carry it.
• Remove social media apps. Log out of browser-based social media and don't save the password.
• Add enough friction that checking requires deliberate effort.
• Leave the phone in the car on hikes. Work at a coffee shop without it.
• You are not on call. 60–90 minutes unreachable will not matter.

Tip 6: Start something delightful

• Begin a new project — personal or professional — that is genuinely exciting and completely unrelated to the news.
• The startup phase is especially good: planning, researching, exploring possibilities. Low stakes, high curiosity.
• Examples: an automated art portfolio, an animatronic Halloween build, a new technical side project.
• Each session in a delightful project is another cleaning pass that prevents negative chemicals from stagnating.

Listener questions

Dealing with a boss who demands constant availability (Krishna)

Three options, used together or separately:

• Deep-to-shallow work ratio conversation: sit down with your boss and establish what the ideal split is for your role. A session only counts as deep work if it is completely uninterrupted — context switches reset the cognitive state.
• Structured check-ins: propose twice-daily scheduled calls (morning and early afternoon) to replace ongoing asynchronous back-and-forth. This benefits the boss too — no more tracking a scattered thread of messages.
• Safety valve: give your boss your personal cell number with a note that it's in Do Not Disturb mode, but calls come through. This alleviates the fear of emergencies without providing low-friction interruption access.

Stay at a risky startup or leave? (Tion)

• Don't leave proactively. Coming out of a failed startup is not a black mark — it signals experience and makes you attractive to the next employer.
• Use the flexibility of startup life to build career capital: take on high-value technical domains (API architecture, digital marketing) rather than becoming the glue person who does shallow coordination work.
• The more rare and valuable skills you accumulate, the more control you gain over the nature of future work.

Preventing source calls from disrupting a journalist's deep work (Brendan)

• Assign rough windows for calls and interviews: for example, Tuesday–Thursday afternoons.
• Tell sources: "I'm generally free Tuesday through Thursday afternoons — just call me."
• When scheduling outgoing calls, offer that window rather than asking open-ended availability.
• Monday, Friday, and mornings remain protected without requiring rigid restrictions that alienate sources.

Reading long and difficult books (Carolina)

• Read difficult books at a regular, dedicated time — even 20–30 minutes daily adds up significantly.
• Pick difficult books you are genuinely fascinated by. Forced reading on hard books fails.
• Combine the difficult book with lighter reading running in parallel — don't make the big book the only thing you can read.
• Don't track pace or set deadlines unless you have a public commitment to do so.

Slow productivity corner: starting at 30 (Josh)

• Your 30s are the right time to start, not a late start.
• Decade framing: 20s are about becoming an autonomous adult; 30s are about figuring out what you want your working life to actually be.
• Priority one: obsess over quality (Slow Productivity principle 3). Mastery of something valuable takes 1–3 years to pay off — starting now is correct timing.
• Priority two: lifestyle-centric planning. Identify what you want your day-to-day life to look like in the second half of your 30s — where you live, daily rhythm, characteristics of work and leisure. Work backwards from that vision rather than forwards from a grand singular goal.
• Career capital generated through mastery creates the options and autonomy to pursue that lifestyle. These two reinforce each other.

Case study: lifestyle-centric planning and discipline in practice

• A senior developer found himself managing people in a direction he disagreed with. Instead of resigning for a grand new goal, he used lifestyle-centric planning: identified that he preferred solitary, focused coding work over management and senior leadership friction.
• Found an internal remote developer role — less prestigious, likely less pay, but a much closer match to his ideal work characteristics.
• Separately, he began learning the flute. After 3–4 months of no visible progress, skill began to emerge. His takeaway: discipline practised in one domain transfers. Completing hard things builds efficacy — a general confidence in your ability to pursue and accomplish difficult things over time.

Justine's call: joining a reactive, unstructured team as a structured performer

• Being responsive and being a high performer are two separate variables. Don't conflate them.
• As you deliver strong results, you accumulate idiosyncrasy credits — social licence to operate differently.
• Move team-level structure onto yourself individually:
  • Maintain a transparent personal work-in-progress queue (Kanban-style: waiting / working on / done) with a WIP limit of two active items.
  • Use office hours and scheduling links to deflect ad-hoc back-and-forth into bounded real-time slots.
  • Respond to asynchronous messages by redirecting to a scheduled meeting rather than engaging in a thread.
• The team gets clarity (their question has a next step); you get protection for deep work blocks.
• Over time, consistent delivery turns your systems from an oddity into something colleagues ask you to explain.