What Entrepreneurs Can Learn from The 36-Hour Day
Marcus ran a six-person delivery startup out of a converted warehouse, and for three weeks his newest coordinator, Priya, kept botching the same intake step. He assumed she just didn't care enough to get it right, and said so, twice, in front of the team. She grew quieter and the errors continued. Frustrated, he sat down to walk her through the process again, this time watching instead of talking. He saw it immediately: the intake form buried the one critical field three screens deep, after a run of near-identical questions. Priya wasn't careless. The system was asking her to hold too much in her head at once. Marcus rebuilt the form around the single step that mattered, moved it to the top, and the errors stopped within a day. He'd spent three weeks correcting a person for a problem his own design had created.
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
Diagnose before you judge the behavior
When a cofounder, employee, or customer pushes back, resists a new tool, or seems to "not get it," the instinct is to read that as low effort or bad attitude. Usually something more specific is happening: unclear instructions, a broken handoff, competing priorities, or simple overload. Treating the reaction as the problem, rather than a signal pointing to the real problem, wastes time and damages trust you will need later, and it teaches the person that raising a problem gets them blamed instead of helped.
A manager assumes a slipping employee is disengaged and puts them on a performance plan without ever asking what changed in their workload.
Before addressing a repeated problem, ask the person one direct question about what's getting in their way, and listen to the full answer before responding.
Redesign the system, not just the person
Once you know the real obstacle, the fix is rarely a lecture. It's usually a change to the process, tool, or expectation itself: fewer steps, clearer defaults, a different format. Expecting people to simply try harder inside a flawed system produces the same failure on a loop, no matter how talented or motivated they are.
After three onboarding failures, a founder adds another training session instead of shortening the onboarding checklist itself.
Pick one recurring friction point this week and change the system around it, not the instructions for using it.
Say it simply, say it calmly
Under pressure, founders default to persuasion: more data, more urgency, a longer explanation of why something matters. When someone is overwhelmed, confused, or defensive, a long argument adds noise rather than clarity. A short, calm, specific instruction lands better than a compelling case.
A founder responds to a confused new hire's question with a ten-minute strategic monologue instead of the one next step they actually need.
When giving direction under stress, cut your explanation to one sentence and one clear next action.
Your capacity is company infrastructure
Founders often treat their own exhaustion as a rounding error, something to push through until the next milestone. But a depleted founder makes worse calls, reads neutral behavior as hostile, and runs out of patience exactly when steady judgment matters most. Protecting your own rest and support isn't separate from building the company; it's part of what keeps the company's decisions sound, and it's a discipline worth scheduling as deliberately as any product deadline.
Diagnosing causes takes time you often don't have, and startup urgency rewards quick, decisive action. The tension resolves by keeping diagnosis fast rather than skipping it: one clarifying question and a few minutes of observation usually reveal enough to act on, and that small investment is still cheaper than the repeated failures a wrong assumption produces.
Name one thing, honestly
Where in your business have you been correcting a person for a problem your own system created?
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
When giving direction under stress, cut your explanation to one sentence and one clear next action.