The always-on illusion: When availability became a productivity myth

The busiest product leader I have ever worked with was also the one producing the least important work. He answered every Slack message within four minutes, attended every meeting he was invited to, and kept his calendar so full that his lunch breaks were fifteen-minute windows labelled "bio break" so nobody would schedule over them. He was, by every visible measure, deeply committed. But he was also, by every outcome measure, falling behind. His decisions had a pattern: fast, confident, and wrong about forty per cent of the time.

The correlation was not a coincidence.

I have watched this pattern repeat for two decades across companies on three continents.

The people who look the most available are often the ones doing the least thinking.

Act I: The Setup

Startup culture has always treated availability as a proxy for commitment. If you are online at eleven at night, you are serious. If you respond to messages within minutes, you care. If your calendar has gaps, the unspoken assumption is that you are either not important enough to be needed or not dedicated enough to fill the space. The always-on founder became the aspirational archetype. Sleep four hours, answer every ping, never let a question sit overnight.

At my first startup, I was that person. I wore the exhaustion like a badge. My co-founder and I had a running joke about who had slept less, as though chronic fatigue were a competitive sport. One week I worked six consecutive eighteen-hour days building a feature integration while managing a client escalation. By day five, I was making decisions that I would not have accepted from a junior PM on day one. But I could not see it. Exhaustion does not announce itself as impairment. It disguises itself as determination.

I shipped the integration on the seventh day. It had three critical bugs. A well-rested version of me would have caught at least two of them in review. Well-rested was not an option I believed I had.

The setup was simple: we confused presence for productivity, hours for output, and availability for virtue. And most of the industry built its culture around that confusion.

Act II: The Conflict

The data arriving this year tells a story that the always-on culture does not want to hear. Research across multiple studies finds that past a threshold of roughly fifty hours per week, additional hours correlate negatively with decision quality. Not neutrally. Negatively. You are not just getting less return per hour. You are actively making worse choices.

I call this the threshold inversion. Before the threshold, more time produces more output. After it, more time produces worse output. The relationship inverts. And the person experiencing it is usually the last to notice, because the subjective feeling of working hard is indistinguishable from the subjective feeling of working well. You feel busy. You feel engaged. You feel like things are happening. But the things happening are increasingly low-quality.

At Freshworks, I watched a product director burn through a quarter this way. She was brilliant. Strategic mind, strong instincts, respected by her team. But she had fallen into the availability trap, the pattern where constant responsiveness leaves no uninterrupted time for the kind of slow, deliberate thinking that strategic work requires. Her days were a sequence of reactions. Slack message, meeting, Slack message, review, Slack message, decision. Every individual response was competent. But the decisions she made at four in the afternoon, after eight hours of continuous reactivity, were measurably different from the ones she made at nine in the morning.

I know because I reviewed her roadmap decisions across a quarter. The morning decisions were thoughtful, connected to long-term strategy, and showed evidence of second-order thinking. But the afternoon decisions were narrow, focused on immediate problems, and optimised for resolution speed rather than outcome quality. Same person. Same intelligence. Different cognitive state.

She was not lazy. She was depleted.

And the culture she worked in read depletion as dedication.

Act III: The Resolution

The most effective product leader I have worked alongside did something that looked, to the always-on crowd, like professional negligence. He checked messages twice a day. He blocked four hours every morning as unavailable. He left meetings that ran past their scheduled time. His team initially found it frustrating. But within two quarters, something interesting happened. His decisions were consistently better than those of peers who worked longer hours. His roadmap had fewer reversals. His team shipped more, not because they worked more, but because they received clearer direction and wasted less time on rework from fatigued decisions.

He told me once, "Availability is not a virtue. It is a design choice. And most people are designing it badly." That line has stayed with me because it reframes the entire conversation. We treat availability as a moral quality, evidence of commitment or character. But it is actually a resource allocation decision. Every hour spent being available for other people's questions is an hour not spent on problems that require uninterrupted concentration.

The reframe matters because it moves the conversation from identity to design. You are not a bad founder if you check messages twice a day. You are a founder who has designed their availability for decision quality rather than response speed. But making that argument in most startup cultures still feels like confessing to a lack of seriousness. The deeply held belief that more hours equals more commitment is remarkably resistant to evidence.

I spent a year making this transition myself. The hardest part was not the logistics. It was the guilt. Every time I did not respond to a message immediately, I felt a twitch of anxiety that I was letting someone down. That anxiety was not rational. It was conditioned. Years of startup culture had trained me to equate responsiveness with responsibility, and the training ran deeper than the data.

But the results were undeniable. My error rate on product decisions dropped. My ability to spot strategic signals through operational noise improved. I started seeing patterns I had been too busy to notice when I was responding to everything in real time. The irony is thick: I became more useful to my team by being less available to them.

What this actually means

A body of founder essays circulating this year carries a common thread. The authors describe periods of overwork that they believed were productive, followed by a realisation that much of what they produced during those periods was mediocre, redundant, or actively counterproductive. The pattern is so consistent it reads less like anecdote and more like diagnosis. But nobody wants to say it plainly: we built an entire professional culture around a productivity model that, past a measurable threshold, produces the opposite of what it promises.

I think about that first startup. The eighteen-hour days. The competitive sleep deprivation. The three critical bugs I shipped because I was too exhausted to review my own work. I thought I was being serious. But I was being self-destructive in a way that the culture could not distinguish from dedication. That is the always-on illusion: not that the hours are wasted, but that past a point, they are actively harmful, and the culture rewards them anyway.

The question for any product leader is not how many hours you are willing to work. It is whether you have designed your availability for the quality of thinking your role requires. Most people have not asked that question, because the culture never gave them permission to ask it.

But permission, like availability itself, is something you can design. And the people who design it well tend to produce work that outlasts the people who simply worked longer.