I want to talk about a four-hour workday. Not a four-day work week. Not a four-hour work week. A four-hour focused work window, five or six times a week. That's the goal I'm designing toward.
When I say that out loud, I get one of two reactions. Must be nice. Or: you can't run a business that way. Both reactions are worth pulling apart.
Because the four-hour workday isn't about working less because you can't handle more. For me, it's the opposite. It's about working at the edge of what I can actually do, and protecting the rest of my life accordingly.
Listen: Substack · Spotify · Apple Podcasts · YouTube
In this episode
The week I had every hour accounted for and got to Friday with no actual thinking
The two kinds of busy: one that fills your calendar, one your calendar usually doesn't have space for
Where the eight-hour workday actually came from, and why it was built for a household that doesn't exist anymore
AuDHD, time blindness, the Time Timer, and starting somewhere
Build seasons vs. integration seasons, and why both belong on the calendar
Intensity is not the same as chaos
The voice that shows up Tuesday afternoon to tell me I'm not working enough
Busy vs. productive: the relay seat
Not too long ago I had a week where every hour of my workday was accounted for. Calls, meetings, vendor check-ins, a consultation, a team check-in, two networking coffees. By any productivity standard I was winning that week. Calendar full, inbox active, phones going.
And I got to Friday and realized I hadn't had a single thought. Not a strategic thought, not a creative thought, not the kind of thought where a piece of business architecture clicks into place. I had been busy. I had not been thinking.
For that entire week, I had been the relay between other people. Vendor to client, client to team, team to me, me to the next vendor. Important work. But none of it was the work I was actually built to do.
There's a kind of busy that looks like work and there's a kind of work that doesn't look busy. The first one fills your calendar. The second one needs space your calendar usually doesn't have. And most of us are running models that reward the first and starve the second.
Why the eight-hour workday doesn't fit
The eight-hour workday isn't ancient. It's about 100 years old. Henry Ford standardized it at Ford Motor Company in 1914, because his factories needed a way to run three shifts around the clock. Before that, 14-hour workdays were the norm. Two years later, the US federal government followed for railroad workers with the Adamson Act in 1916. During both world wars, governments leaned on that structure even harder.
It wasn't a gift to the workers. It was an economic decision. By 1938, the US wrote the 40-hour work week into federal law with the Fair Labor Standards Act.
Here's the part I keep coming back to. That 40-hour week was designed around a household where one adult worked and one adult ran the home. Cooking, cleaning, childcare, errands, appointments, laundry, groceries, bills. All of it lived outside the 40 hours. That is not most households today. Most of us are running both jobs, and we're wondering why eight hours feels impossible to sustain.
Eight hours wasn't designed for the modern knowledge worker. It was designed for assembly lines. We just inherited it and forgot why.
How many hours of deep work you can actually do
For my brain, it's three to four hours of focused work in the right conditions on the right thing. If I push past that, I get diminishing returns. Not slowly. Sharply. Hour five looks the same on the calendar as hour three, but hour five is one-third the output with two times the friction, and it's burning the fuel I'll need on Wednesday. The math is not mathing. It never worked. I just used to override it.
I am AuDHD, autism and ADHD. The more I learned about that, the more I realized I needed to change how I worked. I have time blindness, so I got a Time Timer, a 60-minute clock that counts down in red. In meetings I can watch the time and keep us on track. And if the work of a meeting is done early, I've given myself permission to say: let's give ourselves back that 20 minutes. Nobody wants to deny a gift.
Whatever works for you, start somewhere. Take the time to really lean into how your brain works, where it thrives, where it struggles, and start with small changes.
Build seasons and integration seasons
Events are built in sprints. You don't plan a wedding in a steady 40-hour week for nine months. You build the framework, let it sit, make decisions, let things sit again, then six weeks out the sprint kicks in, and then it's over. The healthy rhythm of event work is build, rest, sprint, recover. The disaster rhythm is sprinting all the time on every project with no recovery. I lived that for years.
So there are two kinds of seasons in the way I work now. A build season is a finite window of intensive output. A specific outcome. A deadline. Recording batches of episodes, building out a consultation offer, producing an event, shooting a campaign. Build seasons are intense by design, and honestly, I love them.
But a build season is a season. It has a start and an end. What comes after it is an integration season. Integration seasons are not vacation. They're where the thinking lives. Did it work? How do we make it work? Reading. Talking to people in my industry. Sitting at the dining table with tea and a notebook. Watching how a podcast lands. It's where the next build season gets designed. You can't sprint without integration. Sprint just becomes a treadmill.
Both of them go on my calendar. If integration isn't on the calendar, it gets eaten. By a quick call, by a "while you have a minute," by a vendor escalation that didn't really need me. Integration has to be defended like any other commitment.
The four-hour workday isn't a permanent state. In a build season, four hours is the floor, not the ceiling. In an integration season, some days it's two. What's consistent is that I'm not pretending to work eight hours just to feel legitimate.
Intensity is not the same as chaos
A lot of us who run our own businesses confuse the two. We grew up professionally in environments where work was urgent because someone had let it become urgent. A vendor missed a deadline. A client changed their mind two weeks out. That kind of urgency is reactive. It's chaos dressed up as performance.
Chaos is not a build season. Chaos is a system that's collapsing in slow motion. A build season is intentional. You chose it. You designed it. You scoped it. Both are intense. Only one is sustainable.
A few things I've changed: I batch hard. Content gets recorded in batches, calls get clustered, admin gets a defined slot. I have a no-meeting Monday. I plan a recovery week after big events. And I let my inbox wait. A response within 24 to 48 hours is professional. A response within 15 minutes is just being available.
The part that's still hard is the voice that tells me I'm not working enough when the calendar is light. That voice was trained by every job that measured presence instead of output. It shows up Tuesday afternoon when I've finished the work I planned and there's still daylight left. The old version of me would invent something to do. The new version is trying to let it be Tuesday afternoon.
Key line
If the answer is uncomfortable, you're not lazy. You're under-designed. And that's a fixable problem.
Reflection question
If you mapped out your last full week, hour by hour, how many of those hours were you actually working at the edge of what you can do? And how many were you in that relay seat, that Groundhog Day scenario? Moving information between other people, performing busyness, filling the calendar to feel legitimate.
Timestamps
00:58 What I mean by a four-hour workday
01:25 "Must be nice" and "you can't run a business that way"
03:28 The week every hour was accounted for
13:33 Busy that looks like work vs. work that doesn't look busy
14:01 Miriam Wexler on how the events industry rewards exhaustion
17:03 Where the eight-hour workday came from
19:47 Three to four hours of focused work, and diminishing returns
20:52 AuDHD, time blindness and the Time Timer
29:46 Events are built in sprints
32:38 Build seasons and integration seasons
42:43 Intensity is not the same as chaos
44:40 What I've changed: batching, no-meeting Monday, letting the inbox wait
46:09 The voice that says I'm not working enough
49:25 Reflection question
FAQ
Can you really run a business on a four-hour workday?
It's a four-hour focused work window, five or six times a week, not a permanent cap. In a build season four hours is the floor, not the ceiling. In an integration season some days are shorter. The point is working at the level the season calls for instead of pretending to work eight hours to feel legitimate.
Where did the eight-hour workday come from?
Henry Ford standardized it at Ford Motor Company in 1914. The Adamson Act applied it to US railroad workers in 1916, and the Fair Labor Standards Act wrote the 40-hour week into US federal law in 1938. It was designed around a household where one adult worked and one ran the home.
What's the difference between a build season and an integration season?
A build season is a finite window of intense output with a specific outcome and a deadline. An integration season comes after it. It isn't time off. It's where you observe, adjust and design the next build. Both go on the calendar.
How do you tell intensity from chaos?
Intensity is chosen, designed and scoped. Chaos is reactive urgency, a system collapsing in slow motion. Both feel intense. Only one is sustainable.
This post is based on Season 1, Episode 10 of Work, By Design, a podcast by Amanda Douglas & Co. about redesigning how you work.
Want help with your own version of this? Start a conversation
Read next: Identity Lag and Imposter Syndrome in a Career Pivot
