How to beat shallow work chaos, read smarter, and master a hard job

Executive overview

Unexpected shallow tasks erode deep work not because planning fails, but because setup and execution aren't separated. Abstract productivity systems (read 5 papers a week, do 5 hours of deep work) collapse without a concrete goal driving them. Career improvement in a hard role follows the same logic: get organised first, then you can see where to improve.

Getting intentional about what's possible right now beats chasing a perfect schedule.

Taming the productivity hydra

• Time block planning measures intentionality, not perfect schedule adherence — a disrupted plan is not a failure.
• Revise the plan whenever something interrupts it; always ask "what's the best I can do with what remains?"
• Separate setup from execution: gather materials and context as a shallow task, then do the actual deep work block with no live connections to the outside world.
• Deep work blocks work best when there is no incoming channel — no email, no logins, no live system access during the block.
• Recurring shallow chaos often signals too much administrative complexity; simplify or systematise the source rather than managing each interruption.
• Work the System (Sam Carpenter): framework for turning a chaotic business into documented, employee-run processes.
• Company of One (Paul Jarvis): argues for raising rates rather than growing headcount — retains autonomy while income grows.

Reading to the cutting edge as a PhD student

• Abstract reading quotas ("4 papers a week") are hard to sustain because they feel like an ungraded, uncredited class.
• Let current research drive reading: papers directly improve experimental design, citations, methodology, and publication quality.
• Concrete goals ("get this proof done in a week — what do I need to read?") sustain behaviour better than abstract targets.
• Reading tied to a specific output compounds quality at an accelerated rate.

Shifting from generalist to specialist mid-career

• Vague intentions to "specialise" need a concrete human anchor: find a specific person whose career setup resonates with you.
• Interrogate what actually resonates — location, workflow, type of projects — because the answer shapes the plan entirely.
• Study how they got there like a journalist: deconstruct the story, identify which skills unlocked the position.
• Don't ask for advice directly; ask for their story — advice given on the spot tends to be the first coherent thing the person can grab, not the real cause of their success (the colored folder effect).
• Once the path is clear, build it into quarterly plans, then weekly and daily time blocks.
• Emotion-driven, vague career swings ("I need a change, this seems fun") regularly lead to regret — avoid them.

Getting good at a difficult job you weren't trained for

• No degree directly prepares someone for a highly specific management role; the question is willingness to get after it.
• Foundation first: nothing falls through the cracks, commitments are met on time, everything is visible.
• Use shared task boards (Trello, Asana, Flow): every item has a status, owner, and thread of notes — not an inbox.
• Use a ticketing system for high-volume incoming issues so the whole team can see status and progress.
• Hold regular synchronous team check-ins anchored to the shared task board.
• Once organised, shortcomings become visible: you can see where you're falling short, where a process is missing, where you need outside help.
• Systematically address one shortcoming at a time — reflect, improve, repeat.
• Don't assume a replacement hire would do better; strong candidates are scarce, and a driven person with good systems may be the best realistic outcome for the organisation.