The suggestion of a 70 to 90-hour workweek has sparked significant debate, but the focus is fundamentally misplaced. Most discussions have centred around the negative effects of long work hours, criticising management for their insensitivity towards employee well-being. There is no denying that long working hours encroach on employees' personal and family time, leading to numerous negative effects. Beyond work, young parents juggle responsibilities such as childcare, elder care, and household chores. Yet consider environments where individuals willingly stretch and work long hours, yet remain happy, and others where fewer hours yield higher output without stress. The difference lies not in the hours themselves, but in the conditions that foster higher output and motivation, or in other words, high employee engagement levels. If we understand the conditions that drive these exceptional outcomes and behaviours, we can replicate them in any setting. While environments may differ, human behavioural patterns remain universal. The key question: Why do some people happily work long hours? Instead of debating how many hours people should work, we should examine environments where individuals willingly push their limits while remaining engaged and fulfilled. Consider a project team involved in a satellite launch, a group building a stadium for a grand opening, or a team working tirelessly to meet a major product launch deadline. During this start-up, the entire team works tirelessly. In all these scenarios, a shared sense of purpose drives individuals to contribute beyond their usual expectations, fostering a collective commitment to success. They aren’t just clocking in time; they are part of something meaningful, a mission that fuels their motivation.  A strong sense of purpose drives individuals, whether promoters, top management, or employees, to contribute beyond expectations. Every job, regardless of level, holds the potential to be meaningful.  At work, two key factors create a sense of achievement:<ol style="list-style-type:lower-latin;"><li>Successfully completing a task only when the task is inherently value-adding</li><li>Innovating or adding value to ongoing work, or in other words, being part of a high-impact improvement projects </li></ol>In the absence of a connection to a larger purpose, people may still not complain even if the work hours are exactly at the official limit.So, when do people complain about long work hours? They start complaining when they have to face the following two conditions:<ul style="list-style-type:square;"><li>Feeling forced to compensate for someone else’s shortcomings or held accountable for outcomes they don’t control</li><li>Chronic overstretching</li></ul><h2> </h2><h5>1. Feeling forced to compensate</h5>Work environments plagued by constant task arrival delays, prolonged waiting, urgent escalations, frequent interruptions, and a lot of avoidable rework violate the feeling of doing something meaningful. When employees feel they have not created anything meaningful within the given time, productivity declines and frustration builds.  After all, no one finds satisfaction in being unproductive. In such environments, the real issue with extended work hours isn’t just the extra effort; it’s the stress that comes from feeling forced to compensate for someone else’s shortcomings.Consider these scenarios:<ul style="list-style-type:disc;"><li>If the sourcing team prioritises the lowest cost without considering quality, the execution team may struggle with rework and service failures.</li><li>When the design team delivers incomplete outputs, the development team is burdened with unnecessary rework.</li></ul> <h5>2. Chronic overload</h5>Occasionally, stretching to meet commitments is a normal part of work. But when employees are consistently overloaded, the real issue isn’t just the workload; it’s the chronic stress that comes with it. Persistent overburdening of employees is a clear sign of flawed capacity planning. This is especially true in fields where human expertise determines output, such as engineering, software development, and project-based industries. In these environments, experience and skill levels dictate capacity. Yet constant firefighting wastes capacity and makes leaders believe they have not received adequate returns on the invested capacity. When capacity is not added, employees feel overwhelmed and overloaded. These disconnected viewpoints on capacities between top management and the operating team make it difficult to resolve the issue. Many leaders believe the issue is that resources are not 'stretching enough', while the operating team feels burnt out. Without clear visibility into workload distribution and capacity utilisation, organisations risk perpetuating workplace stress. The real issue is productivity, not work hours. The workplace challenges described above are not isolated issues; they are symptoms of a deeper problem: poor productivity. Poor productivity is a chronic problem in the vast majority of organisations across sectors. In low-productivity environments, even working 70 to 90 hours per week may not be enough to achieve the desired output. The solution isn’t to stretch hours; it’s to improve productivity. The ongoing debate over longer work hours assumes that productivity is fixed and that nothing can be done about it.  Organisations can address this by fostering two key conditions in the workplace: <h5>1) The state of flow: The productivity sweet spot</h5>Peak productivity occurs when employees work in a ‘state of flow’, a work environment designed for deep focus and free from unnecessary disruptions. This means:<ul style="list-style-type:disc;"><li>Minimising interruptions</li><li>Taking on fewer tasks at a time and completing them before starting new ones</li><li>Prioritising task completion over multitasking</li><li>Ensuring clean handovers between employees and across functions</li></ul>When employees operate in this state, they deliver their best output in the shortest possible time. <h5>2) Eliminating the blame culture</h5>A culture that focuses on assigning blame instead of identifying root problems stifles productivity. Shifting the focus from ‘Who is at fault?’ to ‘What is the problem?’ fosters collaboration, problem-solving, and continuous improvement. Productivity over hours.  Numerous studies and real-world experiments have shown that re-engineering workflow practices and reducing work hours lead not only to just happy employees but also to better business outcomes. There is no conflict if one approaches the problem by re-engineering workflow practices to make it productive. A classic example is Henry Ford's introduction of the eight-hour workday in 1926, which was well enabled by the assembly-line way of working. Despite reducing weekly hours from 48 to 40, productivity increased because workers got more rest, they made fewer mistakes and produced more per hour.  ENPRO Industries Pvt. Ltd. is an Indian company engaged in the design and manufacture of mechanical fluid systems and process equipment for a variety of applications. By re-engineering workflow practices from order inflow to order fulfilment, the company could drastically cut order execution time by 50%-60%, eliminate output skew in the shop, and reduce design revisions by over 60%. As a result, sales went up by 47%, and inventory turns improved by 50%. This huge leap in productivity enabled the team to transition to a five-day workweek rather than stretching to six days.  The key takeaway isn’t about reducing or increasing work hours; it’s about creating conditions that drive productivity. Instead of debating hours, organisations should ask:<ul style="list-style-type:disc;"><li>How can we help employees achieve a state of flow?</li><li>How can we eliminate the blame culture to foster better collaboration?</li></ul>By focusing on these questions, companies can unlock true efficiency without imposing the unnecessary strain of longer hours.

Key Takeaways

Do long work hours really kill productivity, or is there a deeper problem? Discover why some thrive in high-stretch environments while others burn out, and what truly drives efficiency.

70 to 90-hour workweek: A misguided debate

Long work hours cannot fix low productivity. See how creating a state of flow and eliminating rework cuts execution time without stretching hours.