Doing nothing at work

TL;DR

Before you orderOffer from Amazon

Get smart everyday buys delivered free with Prime

• Fast, free delivery on millions of items
• Prime Video, Amazon Music and more included
• Member-only deals all year

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Recent discussions highlight that engineers should sometimes work less or do nothing to maximize impact. This approach can prevent burnout and enable high-impact work during critical moments, though it remains a counterintuitive concept.

A recent discussion among software engineers has emphasized the strategic value of doing less or nothing during work hours to maximize impact and reduce stress. This perspective challenges traditional productivity norms and is gaining attention in tech communities.

According to a post on Hacker News, many engineers could benefit from working fewer hours or at a slower pace, focusing on high-impact opportunities rather than constant task execution. The author suggests that working at around 80% capacity allows engineers to remain alert for critical, time-sensitive opportunities such as closing major deals, mitigating incidents, or enabling high-profile feature launches.

These opportunities often depend on trivial but timely changes—like toggling a feature flag or fixing a minor bug—that can have outsized effects. The key is maintaining enough slack in the schedule to notice and act on such moments, which are often missed when engineers are perpetually busy with low-priority tickets. The post also advocates for deliberate inaction during low-pressure periods, such as avoiding unnecessary glue work or technical debt tasks that are not explicitly prioritized, to preserve mental clarity and readiness for urgent tasks.

Implications for Engineer Productivity and Well-Being

This approach suggests that strategic inaction can lead to better outcomes for both organizations and engineers. By working less or doing nothing during certain periods, engineers can avoid burnout, improve focus during high-pressure incidents, and be more available for impactful work. It also challenges conventional productivity metrics that equate constant activity with value, emphasizing quality over quantity in software development.

Shift in Work Culture and Impact on Engineering Practices

The idea of doing less at work builds on broader conversations about burnout, mental health, and the inefficiency of relentless productivity in tech. Historically, engineers have been encouraged to maximize output, often at the cost of well-being. Recent discussions, including posts on Hacker News and social media, highlight a growing recognition that strategic downtime and deliberate inaction can be beneficial. This perspective aligns with movements toward sustainable work practices and mental health awareness in the tech industry.

“Doing nothing at work, intentionally, can be a strategic move to stay alert for high-impact opportunities and avoid burnout.”

— Hacker News contributor

Unclear Long-Term Effects of Reduced Work Engagement

It remains uncertain how widespread adoption of this approach will affect long-term career progression, organizational productivity, or company outcomes. There is also limited empirical data on whether intentionally doing less consistently leads to better impact or if it risks being perceived as disengagement.

Potential for Broader Adoption and Organizational Change

Further discussions and case studies are needed to assess how organizations can integrate strategic inaction into their culture. Future steps may include formal policies encouraging engineers to allocate time for reflection, or research into the impact of reduced active work on innovation and productivity.

Key Questions

Is doing nothing at work a new concept?

While not entirely new, the idea has gained renewed attention through recent online discussions emphasizing strategic inaction for impact and well-being.

Can doing less harm my career?

It depends on how the approach is perceived by managers; if framed as strategic and impactful, it can enhance reputation. However, it could be misunderstood if not communicated properly.

Does this apply to all types of work?

This approach is most relevant in roles where impact depends on timing and strategic decisions, such as engineering, product management, or incident response. It may be less applicable in routine or compliance-focused roles.

How can organizations support this mindset?

Organizations can foster a culture that values quality over quantity, encourages reflection, and recognizes strategic inaction as a form of contribution.

Source: Hacker News