Burnout is not a badge of honour

In my first startup, I once fell asleep during a product demo. Not a casual nodding off. A full, chin-on-chest, pen-rolling-off-the-table surrender to gravity. The client was mid-sentence. My co-founder kicked me under the table, which I barely registered. Afterwards, he did not ask if I was okay. He said, "That was embarrassing, but at least it shows we are working hard." I accepted that framing completely. I was twenty-seven and running on four hours of sleep a night, and I wore the exhaustion like a medal.

It took me years to understand that what I was wearing was actually a symptom.

Act One: The Gospel of the Grind

Startup culture has, for at least two decades, operated on a foundational belief: more hours equals more commitment, and more commitment equals better outcomes. The mythology is relentless. Founders sleeping under their desks. Engineers pulling seventy-hour weeks and tweeting about it. Product leaders answering Slack messages at midnight and calling it "being responsive." The message, absorbed through a thousand conference talks and founder interviews, is clear. If you are not grinding, you are not serious.

I believed this deeply. At Freshworks, during a particularly intense product launch cycle, I tracked my own working hours for a month. The average was sixty-three hours a week. I was proud of that number. But what I did not track, and what nobody around me was tracking, was the quality of the output those hours produced. The decisions I made in week three of that sprint were measurably worse than the ones I made in week one. I approved features I would have questioned. I let timelines slide that I would have challenged. I signed off on copy that, three weeks later, I could not believe I had agreed to.

But the hours looked right. So nobody questioned it.

This is what I have come to call The Grinding Fallacy: the belief that effort and output are linearly related, that doubling the hours doubles the results. A comforting belief. But it is wrong in exactly the way that matters most for people making consequential decisions under sustained pressure.

Act Two: The Data Arrives

A 2024 survey of 156 founders found that 53% had experienced burnout within the past year. More than half. That number alone should prompt reflection. But what makes it more pointed is the secondary finding: burnout was not merely a personal wellbeing issue. It was correlating with measurably worse business outcomes.

Balderton Capital and several other institutional investors have begun reframing burnout as a business performance variable. Not a lifestyle concern. Not a wellness perk to be addressed with meditation apps and ping-pong tables.

A variable that directly affects the quality of the decisions a founder makes, the signals they catch or miss, and the people they retain or lose.

The logic is straightforward. Exhausted founders make worse decisions. They miss market signals. They retain fewer people because burned-out leaders create burned-out teams. And they produce worse products, because product quality is downstream of decision quality, which is downstream of cognitive capacity, which is downstream of recovery.

Every link in that chain is obvious.

But somehow, the startup world spent two decades pretending the chain did not exist.

I saw this firsthand at a petroleum company I consulted for. The head of digital products was a brilliant strategist who, over the course of six months, transformed from someone who asked sharp questions in every meeting to someone who rubber-stamped whatever was put in front of him. The change was gradual enough that most people did not notice. But I had worked with him early in the engagement, and the contrast was stark. His decision quality had not declined because the problems got harder. It declined because he had been running at full intensity for so long that he had nothing left to bring to the table.

Nobody used the word burnout. They said he was "having a rough patch."

He left four months later. The product direction he had rubber-stamped took nearly a year to correct.

The Cost Nobody Budgets For

Burnout is not a badge of honour. It is a performance bug that nobody files a ticket for.

What makes this particularly insidious in product roles is that the symptoms look, from the outside, like competence. The burned-out PM still attends every meeting. They still reply to every message. They still hit their deliverables. But the nature of their contributions shifts. They stop challenging assumptions. They stop asking the second question. They start optimising for speed of resolution rather than quality of outcome.

I have mentored interns who, three months into their first product role, were already showing early signs. Not because the work was too hard. But because they had absorbed the culture's message that working long hours was the price of being taken seriously. One of them told me she felt guilty leaving the office before 8pm. She had been in the role for eleven weeks.

The culture was not teaching her to build great products. It was teaching her to perform suffering. And she could not see that, because everyone around her was performing the same thing.

Act Three: The Athlete Model

The counter-frame that has gained the most traction in 2024 is what practitioners are calling The Athlete Model. The insight is borrowed from elite sports: the best performers in the world do not train by maximising hours. They train by optimising the balance between exertion and recovery. A sprinter who trains at maximum intensity every day does not get faster. They get injured.

The same principle applies to cognitive work. But the startup world has been remarkably slow to accept it.

An athlete who never rests is not dedicated. They are poorly coached. But a founder who never rests is still, in many circles, celebrated.

The Athlete Model asks a different question. Not "how many hours can I sustain?" Instead: "what is the sustainable intensity that produces my best thinking over months and years, not just this week?" It is the difference between a sprint pace and a marathon pace. And most founders, by the time they recognise the distinction, have already been sprinting for too long.

When I moved from Bangalore to Wayanad, part of what I was doing, though I would not have articulated it this way at the time, was redesigning my own operating rhythm. Fewer hours of deep work, yet higher quality. More recovery built into the week, not as indulgence, as infrastructure. The output did not decline. If anything, it improved. But the shift required accepting something that the startup gospel had spent years telling me was weakness: that rest is not the absence of work. It is part of the work.

That distinction still makes people uncomfortable.

What Gets Better

When founders begin treating recovery as a performance variable rather than a reward, three things tend to improve. Decision quality goes up, because the cognitive resources that decisions draw on are being replenished rather than perpetually depleted. Team retention improves, because sustainable leadership creates sustainable teams. And product quality improves, because the people making the calls about what to build and why are doing so from a position of clarity rather than exhaustion.

But this requires a cultural shift that goes beyond individual behaviour. Investors who celebrate the sixty-hour-week founder are subsidising burnout. Boards that reward velocity over sustainability are creating the conditions for the very decline they fear. The Athlete Model only works if the people around the founder accept its premise.

That means roughly half the products being built right now are being shaped by people whose cognitive resources are depleted. Not occasionally. Structurally.

The best work does not come from the person who stayed latest. It comes from the person who still had something left to give when the decision that mattered most arrived quietly, on a Tuesday afternoon, disguised as a routine call.