Why the eighty-hour workweek is a status signal, not a strategy

A friend of mine at a large consulting firm sent a Slack message at 11:47 p.m. on a Tuesday. It said "still heads down." I asked him the next morning what he'd shipped between 9 p.m. and midnight. He thought about it for a while and said, "honestly, I reread a deck and moved some boxes around." He wasn't lying to me. He'd been lying to himself for about three years.

That's the pattern I want to look at, because the advice he'd absorbed — the same advice a lot of ambitious people absorb somewhere between their first internship and their second promotion — goes something like this:

"If you want to get ahead, you have to outwork everyone else. Eighty-hour weeks are the price of admission."

It's not a dumb idea. It came from somewhere real. But it's doing something different now than what it says on the tin.

Where the advice came from, and where it still works

The eighty-hour week as a career strategy has two clear origin stories. One is investment banking in the 1980s, where junior analysts genuinely did model deals until 3 a.m. because the deals had hard closing dates and the work was linear — more hours meant more pages of due diligence, more comps pulled, more scenarios run. The other is early-stage startups, where Paul Graham's essays canonized the idea that founders in the first two years of a company are in a race against runway, and hours are one of the few variables they control.

In both of those cases, the advice holds up. If you are 24, at Goldman, on a live deal with a Friday close, working until midnight is not a signal. It's the job. If you are a founder with nine months of cash and a product that doesn't work yet, the math on your hours is brutal and real.

The pattern in both: the output is bounded, measurable, and time-sensitive. A pitch book either exists by Friday or it doesn't. A product either ships before the money runs out or the company dies. The hours convert into a thing you can point at.

That's the case the advice was built for. Now watch what happens when you take it out of that case.

The tell: output you can't point at

Here's the pattern that gives it away. Ask someone who works eighty hours a week to tell you, specifically, what they produced in the last two hours of yesterday. Not what they worked on. What they produced. A decision made. A document finished. A bug fixed. A customer signed.

When the work is real, they can tell you in about four seconds. "I closed the Henderson contract" or "I got the migration script passing tests." When the work is performance, you get a longer answer. "I was aligning with the London team on the Q3 planning framework." "I was in the weeds on the deck for Thursday." "I was thinking through the strategy."

Those longer answers are almost always the sound of someone who's been at their desk for the correct number of hours to signal seriousness, but whose actual productive window ended around hour six or seven. The remaining time is spent on activities that look like work — reading, rereading, restructuring, responding to Slack at a cadence designed to prove presence — but that don't move anything.

Research on this is pretty consistent. John Pencavel at Stanford ran the numbers on munitions workers in 2014 and found output per hour drops sharply past 50 hours a week, and total output essentially flatlines past 55. That was manual work with clear measurable output. For knowledge work, where you can't count widgets, the flattening happens sooner and is easier to hide from yourself.

So if the hours past 55 aren't producing much, what are they doing? They're signaling. To your boss, to your peers, and — this is the uncomfortable part — to yourself, because working late is one of the few ways to feel like you've done enough on a day when the outcomes were ambiguous.

What the signal actually pays for

It's worth being honest that the signal is not worthless. In a lot of workplaces, being visibly hardworking correlates with being promoted, respected, and trusted with bigger projects. If you refuse to send Slack messages after 7 p.m. in a firm where everyone else does, you will pay a price for that, and anyone who tells you otherwise is selling something.

But here's what's changed. The signal used to be scarce. When only a few people were staying late, staying late meant something. Now, in a lot of white-collar workplaces, everyone is doing it, which means the signal has inflated to the point where it barely differentiates you. You're paying with your evenings for a status marker that's now table stakes.

What differentiates people at that stage is different: it's whether they can point at outcomes. The person who leaves at 6:30 and closed three deals last quarter beats the person who's online until midnight and "drove alignment" on four workstreams. Not always, not everywhere, but reliably, over a few years.

What to do instead

The replacement isn't "work less." It's "make your output legible." Two moves.

First, at the end of every week, write down — for yourself, not for your manager — the three specific things you produced. Not worked on. Produced. If you can't fill in three, the problem isn't that you need more hours. The problem is that your role, or your focus inside it, isn't set up to generate visible output, and no amount of hours will fix that.

Second, when performance review season comes and you're arguing for a raise or a promotion, lead with those outputs, not with your effort. Try something like this:

"Last year I closed X, shipped Y, and led Z. I'd like to talk about what that's worth, and what the next level of scope looks like."

Notice what's not in there. No mention of hours. No mention of weekends. No mention of how hard it was. The people who get promoted fastest, in my experience watching this for fifteen years, are the ones who talk about their work the way a portfolio manager talks about returns: here are the numbers, here's what changed, here's what's next.

The eighty-hour week made sense when the work was bounded and the signal was scarce. Neither of those things is true anymore in most jobs. If you're working those hours and your career is moving, the hours probably aren't the reason. If you're working those hours and it isn't moving, the hours are almost certainly not the fix.

Try this tonight: write down what you actually produced today, in one sentence, in the voice of someone reporting to a board. If you can't, the extra two hours you're about to work won't help. Go home.