Nobody is working for 8 hours a day, Why?

Featured on Hashnode

Subscribe to my newsletter and never miss my upcoming articles

Recently I came across an interesting question on twitter about average working hours per day.

A knowledge worker spends an average of only 2 to 4 hours a day on productive work. The rest of the time is not used to do any meaningful work (I read this in multiple places too, but can't find any original research on this).

Since I can't find any reliable sources to cite, I am writing this based on my personal experience. I work an average of 4 or 5 hours on a good day without any interruptions. On a bad, fragmented day, it'll be far less than that. There are multiple reasons for this.

40-hour workweek is a relic of the industrial era.

In the industrial era, the output is directly connected with the amount of time you put in. Most of the jobs don't require any thinking. Repetition was the key.

Imagine an assembly line worker putting together a few parts of a car. They almost did the same thing every day and their output is measured by the number of things they can put together per hour. When Henry Ford took brought the conveyer belt to the factory, it was seen as a revolution. It eliminated all the extra movements and increased performance. But the core principle of hours = output remains the same.

Enter our knowledge work era, things are blurry. Imagine a developer sitting in his desk thinking about something. Are they thinking about the current problem or just wandering? You'll never know. We can't measure the performance here by measuring the number of hours they put in. This is a fact that everyone knows. But we're collectively still hanging to the 40 hours work week.

If you're in a position of managing people who do creative work, understanding this simple fact is essential. Hours are not equal to performance. I believe in creative bursts that let people do a lot of work within a short time. performance scientists call this as flow state.

If a worker had a flow state of 3 hours per day their brain needs recharge time. The company is paying both for the peak and the recharge time.

Can we stay in the flow state more than 3 hours? Certainly.

Can we repeat it every day? Certainly, not.

Trying to push more than this average limit can have negative effects in the long run such as burnout. In this case, how to understand if someone is slacking? Start measuring their performance by their output, not by their time.

Knowledge workers contribute by their judgment, not time

I read The Almanack of Naval Ravikant recently and what he told about judgment struck a chord.

My definition of wisdom is knowing the long-term consequences of your actions. Wisdom applied to external problems is judgment. They’re highly linked; knowing the long-term consequences of your actions and then making the right decision to capitalize on that.

What a knowledge worker provides is their judgment and skills. Most of their job is decision making considering the trade-offs and benefits. The time they take has very little relevance. We can't rush to a decision if we care about the long term wins.

The human brain is not optimized for long, focused work

We were hunter-gatherers for a long portion of history. Humans lived and hunted as a group. The main rule is "when in doubt, run". Those who thought long and hard often perished in a predator's jaw. We're the descendants of those quick decision-makers. There was no point in history that an average human needed to use his brain for a long time and earn a living.

Our brain is not optimized for a long period of focused work, it gets tired. The attention span is an average of 20 minutes for humans. The contribution of push notifications and social media could have reduced that even further. So it is better to take breaks in between instead of pretending to be paying attention.

There is also a benefit by taking breaks which leads us to the next point based on the Zeigarnik Effect.

Knowledge work is not limited to the clock

It is not possible to shut off your brain from thinking of work problems after the clock. The brain works hard to solve difficult problems when you're doing something else on the surface. People claims about getting solutions for problems when they're taking a shower or going for a walk.

When you have an unfinished task or problem, it'll take the larger part of your attention and will stay in your brain even when you try to do other things. This factor is known as the Zeigarnik Effect. So it is natural for people to think about work after work hours and find good solutions.

In a way, knowledge workers are working outside of the clock as well. They're learning things in their spare time that impact their work at a later point in time.

A while ago, I was reading about optimizing angular performance. A couple of months later, when we faced some performance issues, I suggested a few ideas I learned from that post. The company is benefitting from the knowledge I gathered on my own time. The reverse is also true, Most of my skills are learned while getting paid from the company for it.

These are the reasons that people tend to work less than 8-hours a day. But there are business needs to measure and document everything.

How to measure productivity?

There is no actual way to measure the productivity of an individual developer. Many have tried and failed. Instead of trying to measure what's not measurable, You can think o the following.

  1. Measuring the outcome of their work
  2. How they contribute to the success of their team and to your business?

Ask the following questions about your team,

  1. They miss deadlines regularly?
  2. Your customers are frustrated because of your engineering team's velocity?
  3. Does your team surprise you with reasons at the last minute?

The answer to these questions can create a discussion. If your organization is transparent you can find the problems and fix them easily. Trusting your team to do their job well can take you far then nitpicking on irrelevant details.

How to improve productivity?

There are ways that you can help your team to get more done by creating the ideal environment that is optimized for knowledge work.

Open offices are bad

I am aware of the serendipity aspect of open office plans. But the noise, mobile ringtones, chatter really beats that advantage. To be honest, I hate open office setup.

Ironically, I live in India where the population density is so high, open offices are the only way to keep real-estate costs in control for businesses. It is not practical to completely remove open office plans, but can improve the quality of your office by,

  • Create focus rooms and encourage people to use it.
  • Enforce some rules about distractions within the focus rooms.
  • Try to reduce the unwanted distractions in the open floor
  • Buy noise-cancellation headphones and earplugs for your workforce.

Difference between the manager's schedule and the maker's schedule

Paul Graham wrote an excellent article about this. In short, the knowledge worker's schedule needs long periods of uninterrupted work. If you schedule meetings in the middle of such periods, time is fragmented into two less useful pieces of time.

To avoid the fragmentation,

  • Implement no meetings days in a week or no meetings time range in a workday.
  • Plan all your meetings within the first or second half of the day.
  • Reduce the number of meetings you need, asynchronous discussions are more than enough.

If you're running a business or managing a team of creative people, stop thinking about the time and start thinking in terms of the value created. Their judgment and skills are important than their starting and closing time. Create an ideal work environment and trust your team to deliver results.

Note: My thoughts might be biased, attributed to my limited experience in other areas of business. I am happy to make any changes if someone provides a good counter-argument.

Rakesh Vardan's photo

Great insights Vignesh M 👍

Vignesh M's photo

Thank you so much. You left the first comment in my blog post in the two years I've been writing.🎉

Rakesh Vardan's photo

Vignesh M Glad for your reply. Being a novice blogger myself, I can feel the pain. Your articles really have the unique content and covers different topics. Keep the momentum going !

Rajan Panchal's photo

This is an amazing article.

Dallas Spohn's photo

This only speaks to bloggers or developers still working in a silo style environment. in a high-velocity DevOps environment, not all of this would fly. But with that said. It was a great read and kept me engaged.

Show +1 replies
Dallas Spohn's photo

Vignesh M DevOps is the merger of development and operations into one title. Pre DevOps we use to work in silos that suffered from communication problems between the developers and the sysadmins that postponed the release of the product. I've worked for companies that had the developers on one floor and the operations on another. Since the merger of DevOps (tearing down he silos so to say) by moving us all into an open environment allowed for better communication and more efficient turnaround time from feedback loops.

High velocity is a 24/7 monitoring and maintenance of networks in shifts to keep the product available worldwide. I have a quick rundown of DevOps if you are not familiar with it (46 minute read) spohnz.com/cliff-notes-of-the-devops-handbo.. So you can understand how your casual approach to development does not apply to a global scale company. I am not saying I didn't enjoy the writing. I did very much.

Vignesh M's photo

Thank you for the detailed reply. I have experience with devops and worked on such teams. But I did not work on worldwide products that need 24*7 care yet. As you said these won't work with such high demand teams.

I'll give your article a read. Dallas Spohn

Skay's photo

Great Article Vignesh M!!

Vignesh M's photo

Thank you.

Victoria Lo's photo

This is very true. That's why being a freelancer, I feel like I can be in charge of my own time and make the most value out of it. It's not about the quantity, but the quality of hours. Thanks for this insightful article!

Mohd Shad Mirza's photo

This was such a good read

Anuradha Kumari's photo

Very insightful, loved reading it... 👏👏👏

Vignesh M's photo

Thank you.

Tapas Adhikary's photo

Awesome Vignesh M!

Vignesh M's photo

Thank you so much.

Edidiong Asikpo's photo

This is a fantastic article Vignesh M. I love the analysis and thoughts shared here. Amazing!

Vignesh M's photo

Thank you so much.

Sunil Kumar's photo

Nice article Vignesh. Keep sharing articles like these!

Vignesh M's photo

Thanks, Sunil.

Júlio César Ködel's photo

Speak for yourself.

I often work, focused, for 6 hours straight (without any pause). Sometimes, a lot more than that.

Doing what I like, for a product I own, it's totally different.

But, some days, I can't even start to work... And there are days like this that just forcing to start to work it works and I stay focused for a long time.

I guess the article title should be: no company slave can work 8 hours straight. =)

Vignesh M's photo

Slave is a strong word.

I work on my own product too and faced the same problems in the article. It really depends on one's self.

It is great if you can work focused like that but most people I know agreed with what I experienced.

Maximilian Berkmann's photo

You make a good point to which I can somewhat relate to, however "slave" to describe people working others isn't right (even if you are Joshua Fluke v2).