What Leaders/Managers Can Learn from The 36-Hour Day
Renata managed a claims-processing team, and one of her longest-tenured staffers, Oskar, had started missing details he used to catch easily. Renata read it as a motivation problem and responded with tighter oversight: daily check-ins, stricter deadlines, a written warning. Oskar grew more anxious and his error rate climbed. It wasn't until a peer mentioned that Oskar's shift had recently moved to a louder part of the floor near a new printer bank that Renata considered the environment rather than the person. She moved his desk, and within a week his accuracy returned to normal. She had spent a month enforcing discipline against a problem that a change of seat would have solved, and had made a reliable employee feel judged in the process.
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
Look past the symptom to the setup
A dip in someone's performance, a sudden silence in meetings, or repeated pushback on a request usually has a specific trigger: a change in workload, an unclear handoff, an ambiguous priority, or something happening outside work. Assuming the person has simply become less capable or less committed skips the step that would actually fix the problem, and it often gets repeated with the next person who shows the same symptom.
A manager assumes a formerly strong performer has "checked out" and route them around important projects instead of asking what changed.
The next time performance shifts unexpectedly, open your next one-on-one with a genuine question about what's different, before any mention of the metric.
Change the conditions before you change the person
Once you understand the cause, the fix is often structural: a different workload split, a quieter workspace, a clearer template, fewer simultaneous priorities. Leaders sometimes treat this as coddling, but adjusting conditions to match what a person can actually sustain is a core part of getting good, consistent work from real people.
A team keeps missing a recurring deadline, and leadership responds with a stricter deadline rather than examining whether the workload itself is realistic.
For one recurring team problem, change one structural condition (schedule, tooling, handoff point) before you change any expectation of the people involved.
Give direction that people can actually follow under pressure
Long, nuanced explanations feel thorough to the person giving them and overwhelming to someone already stretched thin or anxious. Under pressure, people retain short, concrete instructions far better than context-heavy reasoning, even when the reasoning is sound. Calm and specific beats comprehensive.
A leader responds to a stressed team's confusion with a lengthy strategy memo instead of naming the one next step each person should take.
Before your next difficult message, cut it down to one clear ask and deliver it in a steady, unhurried tone.
Your steadiness is a resource you have to manage
Leadership often runs on the unstated assumption that the leader's patience and clarity are unlimited. They aren't. A leader running on empty defaults to sharper words, faster judgments, and less willingness to investigate before reacting, which affects every person on the team, not just the leader. Deliberately protecting your own bandwidth, through real breaks, delegation, and honest limits, is part of leading well, not a distraction from it, and it is far easier to build into the calendar before a crisis than to recover after one.
Investigating a cause takes time, and organizations often want a decision immediately. The resolution isn't to skip the investigation but to bound it: a short, structured conversation or observation period before any formal action, so you're acting on information rather than assumption, without stalling the team indefinitely while you look for certainty you'll never fully have.
Name one thing, honestly
Which current performance concern on your team might actually be a condition problem wearing a person's name?
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 your next difficult message, cut it down to one clear ask and deliver it in a steady, unhurried tone.