What Career Professionals Can Learn from The 36-Hour Day
Devin had worked alongside Sofia on the same project team for two years, and lately she'd started missing details in her handoffs and asking him to repeat instructions he'd already given in writing. He decided she'd stopped taking the work seriously and began cc'ing their manager on routine emails as a quiet form of documentation, expecting the pressure to sharpen her up. Instead she became visibly anxious in meetings and started double- and triple-checking everything, slowing the whole team down. Over coffee, a mutual colleague mentioned that Sofia was working nights caring for a parent who'd recently started needing more support, and simply wasn't sleeping. Devin realized he'd spent a month building a paper trail against a colleague who needed a lighter workload, not a witness list. He apologized, quietly took two tasks off her plate for a few weeks, and her old reliability came back on its own.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Assume a reason exists before you assume a flaw
A colleague's dropped ball, sudden defensiveness, or unexplained slowdown usually has a specific cause: a change at home, an overloaded plate, unclear direction from above, or a skill gap nobody's named yet. Deciding it reflects who they are as a professional shuts down the conversation that would actually solve it, and it tends to stick to a person's reputation long after the actual cause has passed.
A colleague quietly builds a case that a struggling teammate is "not cut out for this role" instead of asking what changed recently.
The next time a reliable colleague slips, ask them directly and privately what's changed before mentioning it to anyone else.
Change the setup around the work, not just the person doing it
Once you know what's actually driving the problem, a workload rebalance, a clearer process, or a temporary adjustment usually works better than repeated reminders to do better. Expecting a struggling colleague to simply perform at full capacity inside an unchanged setup rarely produces a lasting fix.
A team keeps assigning the same person the same overloaded set of tasks, assuming better time management will eventually solve it.
Propose one specific, temporary adjustment to a struggling colleague's workload rather than only offering encouragement.
Choose clarity over cleverness under pressure
A carefully worded email documenting every failure feels professional, but it often lands as an attack and produces defensiveness rather than change. A short, direct, calm conversation, focused on one concrete issue, moves things forward faster than a well-argued case.
A manager sends a detailed written breakdown of a colleague's mistakes instead of having a five-minute conversation about the one thing that needs to change.
Before writing a lengthy message about a work problem, ask whether a two-minute direct conversation would work better, and default to that instead.
Your own bandwidth shapes your judgment at work
A professional running on too little rest or support tends to interpret ambiguous situations less generously and reach for documentation and escalation faster than calm inquiry. Protecting your own workload, sleep, and support outside of work isn't a distraction from your career; it's part of what keeps your judgment reliable when a colleague actually needs it, and it's usually cheaper to protect early than to repair after a conflict has already hardened.
Investigating a colleague's situation takes a level of trust and time that a fast-moving deadline may not seem to allow. The practical resolution is to keep the deadline conversation and the cause conversation separate: address the immediate deliverable calmly and quickly, then have the slower, private conversation about what's really going on once the immediate pressure has passed.
Name one thing, honestly
Which colleague's recent slip have you already filed away as a character issue without ever asking what changed?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before writing a lengthy message about a work problem, ask whether a two-minute direct conversation would work better, and default to that instead.