Some people are at their sharpest before sunrise. Others do their best thinking long after sunset. Yet for decades, most workplaces have expected everyone to perform according to the same timetable.

Whether it’s replying to emails before 8 am, staying active on Slack throughout the day, or being the last person to log off, visibility has often been treated as a proxy for productivity. But is being seen really the same as being effective?

The Clock Is Lying: Why Your Most Productive Hours Aren’t 9 to 5

Every performance review season, someone gets quietly penalised for logging in at 10:15 instead of 9:00, and someone else gets a halo for being online at 11 pm. Neither of them is necessarily working harder. One of them is probably just fighting their own biology to look busy at the “right” time, and the other is doing their best work exactly when their brain is built to do it. If you’re still running your team on a uniform 9-to-5, you’re not optimising for output — you’re optimising for visibility, and those are not the same thing.

Visibility isn’t productivity, and we all secretly know it

Think about the last time you were “at your desk” from 9 am but didn’t produce anything worth mentioning until 11. Or the report you finally cracked at 9 pm after staring at it uselessly all afternoon. Every knowledge worker has faced productive hours shortfalls.

And yet most companies still treat presence during a fixed eight-hour window as the primary signal of commitment — replying to email before 8 am, staying visibly active on Slack, being the last name to go offline. None of that measures whether the work got done well. It measures whether you performed diligence on cue.

The uncomfortable truth is that the 9-to-5 was never designed around cognition. It was designed around factory shifts and shared commuting hours a century ago, then inherited by offices that had no reason to question it. Nobody built it by asking when the human brain is actually sharp.

Your body already has an opinion on productive hours

Chronobiology — the study of the body’s internal clocks — has a blunt answer: people aren’t at peak productive hours all the time. Each of us runs on a chronotype, a biological rhythm that decides when we’re naturally alert and when we’re running on fumes.

Some people — “larks” — wake up sharp but their productive hours fade by early evening. Others — “owls” — spend the morning in a fog and don’t hit their stride until well after lunch. Most of us have productive hours that actually sit somewhere in between, a category researchers call “third birds,” but even within that middle ground, the productive hours pattern of the day is real and personal.

Author Daniel Pink, who wrote an entire book on the science of timing about productive hours, breaks the day into three phases: a peak — best for analytical, high-focus work like writing a report or auditing numbers; a trough — the dead zone where nothing productive happens no matter how much coffee you drink; and a recovery window — not your sharpest, but often your most creative, best suited to brainstorming and insight work rather than precision tasks.

The mistake most workplaces make is scheduling the same type of task — meetings, deep work, admin — across all three phases for everyone, regardless of which phase each person is actually in.

This isn’t fringe theory anymore. A 2025 study published in Occupational Health Science tracked how chronotype interacts with time of day to shape productive hours — a combination of vitality and learning. The finding was precise: employees with an earlier chronotype saw their vitality drop steadily as the day went on, while their capacity to learn stayed flat.

Employees with a later chronotype saw the reverse — productive hours improved as the day progressed, while vitality held steady. In other words, larks and owls aren’t just “more” or “less” productive at different times — they experience different kinds of decline and improvement, which means a single companywide schedule is guaranteed to be wrong for the productive hours of your workforce on any given day.

A separate large-scale Japanese study spanning productive hours across multiple industries — IT, finance, government, broadcasting, consulting — followed over 8,000 office workers’ productive hours between 2017 and 2019 and found something equally specific: it isn’t chronotype alone that predicts productivity loss, it’s mismatch. Morning types who stayed up late suffered. Evening types who were forced to rise early suffered. The damage came from forcing people against their own rhythm, not from being a lark or an owl in the first place.

Why productive hours matter more now than in 2020

Hybrid work broke the excuse companies used to have for ignoring all of this. When everyone had to be in a shared building at a shared time, uniform hours were at least a logistical necessity. That constraint is gone for a large share of knowledge work, and yet most schedules haven’t caught up — they’ve just moved the same fixed hours onto a laptop at home to catch up on productive hours.

“Chronoworking” — deliberately shifting work blocks to match a person’s natural rhythm rather than the clock — is gaining traction precisely because the infrastructure to support it (flexible hours, async collaboration, results-based reviews) already exists in most modern workplaces. It’s not a moonshot. It’s an unused feature.

That said, chronoworking isn’t a licence for total time anarchy for adding productive hours, and treating it that way is the fastest way to discredit it. Work-science researchers are explicit that flexibility without any boundaries tends to blur into constant availability — the opposite of the wellbeing gain it’s supposed to deliver. The useful version of this isn’t “work whenever you feel like it.” It’s “protect a person’s known peak window for their highest-focus work, and don’t punish them for a trough that happens to fall inside the traditional 9-to-5.”

What productive hours mean if you’re hiring

For recruiters and managers, productive hours count as a metric. You don’t need a company-wide schedule overhaul on day one. Start by treating “core hours” as a much narrower band — say, three hours of guaranteed overlap for meetings — and let the rest of the day flex around when each person’s peak actually falls.

Stop using early morning productive hours as an unspoken proxy for work ethic in performance conversations; it tells you about someone’s chronotype, not their output. And when you’re evaluating candidates, ask what conditions they do their best work under — a question almost nobody asks in interviews, despite it predicting performance better than half the standard behavioural questions we default to.

The bigger shift, though, is cultural. As long as “being seen” online continues to substitute for “having delivered,” organisations will keep rewarding the wrong signal, and the larks and owls who are actually the most effective people on the team will keep contorting themselves into a schedule that was never built for their biology in the first place.

The clock on the wall says 9 to 5. Your best people’s productive hours are running on a completely different one — and the companies that figure this out first are the ones that will get more out of the same headcount without spending a rupee more on it.

Where late-night hours are already the whole business model

Nowhere is chronotype mismatch more consequential — or more instructive — than in the India-US delivery relationship, and here the story isn’t purely cautionary. Done right, late-night and night-shift work in Indian tech isn’t a punishment shift; it’s a genuine competitive advantage that some teams have learned to design around rather than merely survive.

Take customer support and incident-response teams built specifically to cover US business hours. Because IST sits 10.5 hours ahead of US Eastern and 13.5 ahead of Pacific, an India team covering a US client’s live 9-to-5 has no choice but to work evening through night.

The teams that do this well don’t treat it as a graveyard shift bolted onto a daytime culture — they build the entire pod, staffing, pay, and rest structure around it as a genuine “follow-the-sun” handoff: the India shift owns every ticket the US day team hands off at their sign-off, works it through what is effectively their own daytime-equivalent alertness window, and hands back a clean queue before the US team logs back on.

Structured this way, a night shift stops being “the same job, just later” and becomes its own discipline with its own peak hours — and crucially, it’s often staffed by people who self-select into it because they’re natural night owls in the first place, not people dragged into it by roster luck.

The same logic shows up in engineering. Global Capability Centres running product engineering for US-headquartered parents have increasingly moved away from forcing full-day real-time overlap and toward a narrow, protected sync window — often just a couple of hours of genuine live overlap with the US team — with the rest of the Indian team’s day structured around when their own output actually peaks, not when a US manager happens to be awake.

Some GCCs have gone further, deliberately building “swing” pods: a smaller group whose contracted hours run into the evening specifically to own the real-time collaboration slice with US or European stakeholders, while the bulk of the engineering team keeps standard daytime hours doing the deep-focus work that doesn’t need anyone else awake to happen. The result is that the people absorbing the odd hours are opting into a schedule that suits them, rather than the whole team paying a chronotype tax for a handful of client calls.

This distinction — designed night work versus imposed night work — is also now backed by regulation, not just good management. India’s new Labour Codes, effective from late 2025, explicitly require transport, safety provisions, and additional compensation for any shift that runs past 10 pm, and cap weekly hours to prevent the old pattern of permanent, uncompensated graveyard rotations.

Rajasthan has separately moved to let women opt into factory and night-shift work with statutory safeguards, treating night hours as a choice to be protected rather than a burden to be endured. None of this eliminates the underlying time-zone problem, but it does force a shift in how companies plan around it: night and late-evening hours are being treated, on paper and increasingly in practice, as a distinct shift with its own economics, rather than an unpaid extension of the standard day.

The lesson for any Indian tech employer isn’t “avoid night hours” — global delivery makes that unrealistic for a large share of the industry. It’s that the teams getting real productivity out of odd hours are the ones who stopped treating 9-to-5 as the default and everything else as an exception, and started asking who on the team is actually wired to do their best work at 9 pm, then building the roster, the pay, and the rest periods around that person — instead of around whoever happened to be free.

The takeaway

None of this requires a grand HR initiative or a new piece of software — it requires admitting that the schedule you inherited was never actually about performance. Once you stop conflating a fixed clock-in time with commitment, the fix is almost boringly simple: protect a narrow band of true overlap, judge people on what they ship rather than when they logged on, and let biology do the rest. The organisations that keep clinging to the old timetable aren’t protecting productivity — they’re protecting a habit. The ones willing to let the clock be wrong are the ones who’ll actually get the best hours out of their best people.

For recruiters and CHROs specifically, this changes what “flexibility” should mean in your policy documents. It isn’t a perk you advertise on a careers page — it’s a sourcing and retention lever. Start asking candidates about their natural working rhythm in interviews, the same way you ask about relocation or notice periods.

Track attrition by shift type, not just by role or tenure, and you’ll likely find your night and swing-shift churn has a chronotype-mismatch signature hiding in it. Build shift design into your workforce planning the way you already build in compensation bands. The employer brand of the next five years won’t be built on ping-pong tables — it’ll be built on whether you actually let people work when they’re good at producing productive hours.

Read on India Today