Stop Glorifying Weekend Work

We often glorify weekend work.

“Worked all Saturday.”
“Spent Sunday fixing the release.”
“The team worked through the weekend to meet the deadline.”

These statements are sometimes shared with pride—as if sacrificing a weekend automatically demonstrates commitment, ownership, or high performance.

But should it?

There will always be exceptional situations. A critical production issue, an important launch, an unexpected customer problem, or a deadline that genuinely cannot move. Occasionally working a weekend is part of professional life.

The problem starts when the exception becomes the culture.

If people regularly need evenings and weekends to finish their work, perhaps we should stop celebrating the extra hours and start asking better questions.

Was the deadline realistic?

Did we plan properly?

Do we have enough people?

Are our processes inefficient?

Are we rewarding outcomes—or simply rewarding visible busyness?

A team consistently working weekends isn't necessarily a high-performing team. It could be a sign of poor planning, unrealistic expectations, technical debt, or insufficient resources.

And there is another cost that doesn't appear on project dashboards: recovery.

People need time away from work—to spend with family, exercise, pursue hobbies, learn something new, or simply do nothing. Rest isn't the opposite of productivity. It helps make sustained productivity possible.

As leaders, perhaps we should celebrate something different.

Not:

“My team worked the entire weekend and delivered.”

But:

“My team planned well, executed well, delivered—and still had their weekend.”

Working hard when the situation demands it is admirable.

Building a culture that constantly demands it isn't.

Weekend work should be an exception, not a badge of honor.