At most companies, a workday is 8 hours.
9 to 6. One hour for lunch. Eight hours of actual work.
It's so normal that most of us never question it.
But if you stop and think about it, it's kind of strange.
Why 8 hours? Why not 5? Why not 6? And why do you have to sit at the office for 8 hours even when your work is already done?
Here's the short answer: the 8-hour day was never a number that science picked as the best length of time for a human being to work.
It started out as a cap meant to stop people from working too long.
Somewhere along the way, though, in modern companies that cap quietly turned into the "standard amount of time you're expected to be on the clock."
That's where a lot of the uneasy feeling about modern work comes from.
8 Hours Was a Cap on Overwork, Not an Ideal Workday
The 8-hour day has its roots in the history of the labor movement.
A famous slogan is said to come from Robert Owen, a 19th-century social reformer:
Eight hours' labor Eight hours' rest Eight hours' recreation
In other words, split the 24 hours into three equal parts.
The idea wasn't "8 hours of work is what's best for humans." It was a way to win back some time for a normal life, in the face of the brutal hours of the Industrial Revolution.
Back then, working 10 hours, 12 hours, or even more was nothing unusual.
Against that background, the 8-hour day was a seawall that said, "No more than this."
The ILO's Hours Convention Also Set "8 Hours a Day, 48 a Week" as a Ceiling
The first hours-of-work convention of the International Labour Organization (ILO), adopted in 1919, limited industrial work to "8 hours a day and 48 hours a week."
What matters here is that a six-day work week was close to the default at the time.
8 hours × 6 days = 48 hours.
So it's a little different from today's "5 days, 40 hours."
It was never decided from the start that "working 8 hours, 5 days a week is the right answer."
Rather, to hold back excessive working hours, the world first agreed on a ceiling of 8 hours a day and 48 hours a week.
In Japan Too, the Legal Limit Is "8 Hours a Day, 40 Hours a Week"
Under Japan's Labor Standards Act, as a general rule an employer may not make anyone work more than 8 hours a day or 40 hours a week.
Japan's Ministry of Health, Labour and Welfare explains it the same way: employers may not, in principle, have people work more than 8 hours a day and 40 hours a week.
Even here, the point of the rule isn't "you must work 8 hours."
It's you must not be made to work more than 8 hours.
In other words, 8 hours was originally a ceiling, not a floor.
But in how companies actually run things, it gets turned into this:
Legally, we can have people work up to 8 hours within the normal schedule. So let's make 8 hours the standard.
That's the switch that happens.
What Was a Ceiling Became the "Standard"
Originally, 8 hours was a ceiling to keep people from being overworked.
At many companies, though, it has become the norm.
What should have been "never beyond 8 hours" has become "being there for 8 hours is just normal."
That's the big reversal.
The meaning of the law is to protect workers. But in company practice, it's often treated as the amount of regular time the company is entitled to hold you.
From the company's side, it tends to look like this:
- Up to 8 hours, we can keep you on the clock at the regular wage
- Up to 8 hours, we can use you without paying overtime
- We're buying an 8-hour block of time
- Even on a slow day, the company gets first claim on that time
- You may be kept on standby for emergencies and odd jobs
- Even if you finish early, the rest of the time still belongs to the company
This is the real source of that modern unease.
It isn't 8 hours because you need to work 8 hours. It's 8 hours because they can hold you for up to 8 hours.
Why Do Companies Want to Hold People for 8 Hours?
So why do companies like making an 8-hour stay the standard?
There are a few reasons.
1. They're buying a block of time
At companies that pay a monthly salary (or a "daily-rate-based monthly salary," where pay is docked for days missed), the company isn't buying only finished work. In part, it's buying a promise: "during these weekday hours, the company comes first."
That's why it's hard to leave even when you've finished early.
The company wants to use the leftover time for other work, odd jobs, emergencies, meetings, phone calls, and visitors.
You could say it's buying priority over your time rather than buying results.
2. It's easier to manage
9 to 6, one hour for lunch, 8 hours of actual work.
That makes attendance tracking easy.
Meetings are easy to schedule. Coordination between departments is easier. Payroll is easier. Staffing is easier.
Giving each person 5, 6, or 7 hours, or letting people work by deliverable, takes real design skill on the management side.
The less a company can do that, the easier it is to just put everybody into the same 8-hour box.
3. They want to be ready for emergencies
Every company gets sudden things.
The phone rings. A client reaches out. A document needs an urgent fix. Someone's out sick. A machine stops. The boss suddenly has an idea. A meeting gets called.
So the company wants to keep "people who can be put to use right now" on hand.
But what's actually needed here is a plan for emergencies.
If emergency response is needed, you should set up on-call duty, standby pay, a person in charge, the conditions for responding, and priorities.
Holding everyone for 8 hours without deciding any of that is pretty sloppy.
4. They can't define what "done" means
To manage by results, you have to decide things like these:
- What counts as finished
- What quality is good enough
- When the deadline is
- Who makes the call
- How far a person can decide on their own
- When to check in
- Who handles emergencies
Companies that can't pin these down tend to manage by hours at a desk instead of by results.
In other words, because they can't define results, they manage by time.
That's one more case of things being left undefined.
Even 8 Hours Wears Some People Out
Even if the 8-hour day began as a ceiling, some people today still find it too long.
That's not a matter of being soft.
Concentration, stamina, the burden of the commute, family circumstances, sensitivity to sensory overload, sleep, and how fast you recover all differ from person to person.
Even the same 8 hours doesn't weigh the same on everyone.
- People with a long commute
- People raising kids or caring for family
- People who get worn out by crowds and noise
- People who get drained by meetings and constant coordination with others
- People who do intense thinking in short bursts
- On the flip side, people who do better working slowly over a long stretch
- People whose jobs are physically tiring
- People whose knowledge work puts a heavy load on the brain
Treating all of these the same way, as "8 hours," is a pretty crude design.
Eight hours isn't the right amount of time for everyone.
For some people it's too long. For others it might be too short. For some jobs it may really be needed. For other jobs it may just be waiting around after the results are already in.
What we should really look at isn't the hours themselves, but the nature and load of the work.
In Knowledge Work, Some Days You Don't Need to Think Hard for All 8 Hours
Especially in work like planning, design, project management, process improvement, writing articles, and using AI, hours worked and results don't rise in simple proportion.
What matters isn't how long you sit there, but things like these:
- Setting the goal
- Spotting what's still undefined
- Putting decision criteria in place
- Deciding priorities
- Sorting out who's involved
- Writing the conditions for "done"
- Breaking it down into steps to carry out
- Turning it into the documents and instructions that are needed
When it all clicks, these can move ahead in a burst of 30 minutes to 2 hours.
On the other hand, you can sit in meetings for 8 hours and decide nothing.
In other words, in thinking work, time spent and actual thinking are not the same thing.
Agonizing for a long time doesn't mean you've thought it through.
If you keep holding meetings while everything stays undefined, that may not be thinking at all. You may just be treading water in a puddle of "undefined."
A Setup Workers Would Truly Welcome
Here's the kind of setup that would really help workers:
What to do is clearly defined. What counts as "done" is decided. If you finish, you can go home without your pay dropping. If emergency response is needed, it's handled by a separate arrangement. If standby is needed, it's treated as standby. People who deliver results don't lose out because they finished early.
Just having this changes how people work quite a bit.
If finishing early only means "you get piled with endless new work," the reason to finish early disappears.
If "you can't leave even when you're done," there's little point in raising your productivity.
If "you're held for 8 hours even when you deliver results," workers naturally start pacing themselves.
That's not laziness. It's a rational way to protect yourself.
If you truly want higher productivity, you need a setup where the people who deliver results don't lose out.
"Go Home When You're Done, Same Pay" Isn't the Same as Performance Pay
The key point here is that "go home when you're done, with the same pay" is a little different from plain performance-based pay.
With performance pay, there are risks: only short-term results get valued, and work that doesn't show gets overlooked.
What's needed isn't extreme results-ism but a monthly-salary setup with clear completion conditions.
For example, break it down like this:
- Completion conditions for regular work
- Required meetings and updates
- Who is in charge of emergencies
- Hours when standby is needed
- Time for improvement, training, and handover
- Conditions under which people can use their own judgment to wrap up for the day
Once those are defined, you can say: "If today's required work is done, you're not the emergency person, and the updates are shared, you can go home."
Then workers have a reason to finish quickly and accurately.
And the company finds it easier to recognize people who move work forward, rather than people who just sit at their desks looking busy.
A 3-Day Weekend Gets Easier, Too
Once you have this kind of setup, a 3-day weekend (a four-day work week) gets easier to introduce.
When people talk about a 3-day weekend, you often hear objections like these:
- The work won't get done
- We can't handle customers
- Someone will end up picking up the slack
- We'd have to cut pay to make it work
- We can't handle emergencies
- Meetings won't work
It's true that if you add days off without defining anything, problems will come up.
But flip that around, and it's easier to introduce once you decide these things:
- Work that gets finished within the week
- Hours when response is absolutely required
- Who handles emergencies
- The point of contact for customers
- Which days to hold meetings
- Work one person can finish alone
- Work the team hands off to each other
- When it's OK to contact someone on a day off
- When it's not OK to contact someone on a day off
In other words, the reason a 3-day weekend is hard is usually not "because people are off" but because completion conditions and response conditions haven't been defined.
A 3-day weekend isn't just a system for adding days off.
It's a system for redesigning the work.
A 3-Day Weekend Doesn't Mean "Cramming 5 Days of Work into 4"
There's a caveat, too.
When you bring in a 3-day weekend, just squeezing five days of work into four makes no sense.
All that does is increase the load per day.
What you really need is to reduce the work.
- Cut pointless meetings
- Cut duplicate reporting
- Automate manual work (with Excel macros, "RPA" software robots, or AI)
- Make clear who decides
- Set completion conditions
- Set the points at which to check in
- Use Excel macros (VBA), RPA software robots, and AI to cut routine tasks
- Get rid of tasks nobody would miss
In other words, before a 3-day weekend is a "system for adding days off," it's a system for making wasted work visible.
If you skip this step and just go to a 3-day weekend, you'll only end up busier.
The 3-Day Weekend as an Experiment
Several experiments with a 3-day weekend or a four-day work week have already been run.
A well-known one is Microsoft Japan's "Work-Life Choice Challenge 2019 Summer."
In the summer of 2019, the company ran an in-house project built around working four days and taking three off each week, and published the results of measuring its effects.
What efforts like this suggest is that working fewer days or hours doesn't necessarily mean results go down.
Of course, this doesn't apply as-is to every company or every kind of job.
Some jobs need constant coverage, such as on-site work, healthcare, nursing care, customer service, manufacturing, maintenance, and customer support.
Even so, the question remains.
Is what's really needed an 8-hour hold? Or is it designing things so that results, standby, emergency response, and handover are separated out?
From the 8-Hour Cage to Designing Completion Conditions
The 8-hour day itself isn't the problem.
For some jobs, 8 hours fits. Some workplaces need 8 hours. Some work requires a team to move at the same time.
The problem is standardizing 8 hours without questioning it and trying to squeeze every kind of work into that box.
What we should look at isn't only time.
- Results
- Quality
- Completion conditions
- Standby
- Emergency response
- Meetings
- Coordination
- Handover
- Recovery
- Life outside work
We need to design these separately.
Eight hours was originally a fence to protect people.
But depending on how it's run, it can become a cage that locks people inside the company.
What we need isn't to stretch work out to fill 8 hours.
It's to define the purpose of the work, its completion conditions, and its response conditions, so that people can work only as long as they need to.
Summary: 8 Hours Was a Ceiling. It Doesn't Have to Be the Standard Time You're Held
The workday is 8 hours not because it's the best number for humans.
Historically, it was a ceiling to stop excessive working hours.
But today, that ceiling has become the standard time people are held.
And at many companies, people are managed by that 8-hour block, with results and completion conditions never defined.
This is what you might call the worship of working hours.
What's truly needed isn't to protect the 8 hours.
Decide what "done" means. Don't lose out by going home once you're done. Design emergency response and standby separately. Don't let people who deliver results lose out for finishing early.
If we can do this, a 3-day weekend gets easier to bring in, too.
Rather than increasing working hours, reduce what's left undefined.
That may be the mindset we need for the way we'll work from here on.
