Meridian

Opinion

Productivity Starts With Deleting Work, Not Accelerating It

The fashionable productivity conversation is obsessed with speed. The harder and more useful question is which work should stop existing.

By Diego Arroyo3 min read

Updated

AI-generated 16:9 cover image for "Productivity Starts With Deleting Work, Not Accelerating It", covering productivity, work, management, opinion on The Meridian Hub.
Higgsfield Nano Banana Pro / The Meridian Hub generated cover

The office buzzes with the familiar hum of productivity tools, new apps, faster workflows, and automated reports. But amidst this whirlwind, I find myself wondering: are we actually getting more done, or just moving faster through unnecessary tasks? The prevailing wisdom suggests that speed is the key to productivity. Yet, as I sit here typing away at my keyboard, trying to outpace the clock, I can't help but feel like there's a fundamental flaw in this approach.

Acceleration feels easier because it allows us to avoid confronting the hard truth: much of what we do might be unnecessary. We buy new tools and redesign workflows without questioning whether the work itself should continue at all. Deletion is harder; it requires admitting that certain tasks, meetings, or reports serve no real purpose. But isn't this avoidance precisely why so many organizations struggle with productivity?

Consider the useless report that takes four hours to produce. At least in its current form, it's visible waste, something we can see and question. Yet when we automate it, reducing production time to mere minutes, the report becomes a ghost of efficiency past: cheap enough to live on indefinitely despite its lack of value.

This is where deletion comes into play. A serious productivity program should start with a register that lists every recurring task, identifies its owner, audience, decision impact, and consequence if skipped for one cycle. If the work's purpose isn't clear or its audience undefined, it's likely anxiety masquerading as administrative necessity. Deleting such tasks is not about austerity but about focusing attention on what truly matters.

Once we've deleted the unnecessary, then, and only then, should acceleration enter the conversation. The remaining work will be clearer and more valuable, having survived a test tougher than mere habit. Only then can tools compress necessary tasks and teams automate processes that deserve to exist.

This approach is not just about efficiency; it's about decision quality and institutional memory. It forces us to separate what sounds urgent from what actually changes outcomes. The question isn't how fast we can do things, but which work should stop existing altogether.

Historically, this tension between acceleration and deletion has played out in various industries. In the early days of the Industrial Revolution, factories focused on speeding up production lines without questioning whether all products were worth making. This led to inefficiencies that could have been avoided with a more disciplined approach to what was being produced.

Today's organizations face a similar choice: do we accelerate existing processes or delete unnecessary work? The answer lies in focusing on the latter. By deleting first, we create space for meaningful acceleration later. This shift is crucial because it changes incentives and accountability within teams and across entire companies.

The practical impact of this approach often appears in planning assumptions, counterparty risk, and timing. When managers have to price uncertainty into budgets, when vendor relationships become strained due to hidden risks, or when timelines start shifting unpredictably, these are the moments that reveal whether a productivity program is truly making a difference.

So what should we watch for next? We need to track which assumption the argument depends on most; this is usually where the story becomes measurable. Look for proof in ordinary life and see who benefits if the status quo continues. These details separate surface-level movement from real change.

But here's the rub: useful evidence isn't just about announcements or high-profile contracts. It includes signed documents, changed service terms, delivery dates, customer notices, staffing moves, budget allocations, repeated behavior over several weeks that shows tangible impact.

The risk is over-interpreting a single data point. One announcement doesn't prove a trend; one delay doesn't prove failure. The story becomes useful intelligence when it changes incentives, prices, access, timelines, or accountability for the people touched by the issue.

In essence, productivity starts with deleting work, not accelerating it. This isn't just about efficiency; it's about making better decisions and ensuring that what remains is truly valuable.

The daily digest

One email each morning, all the day’s reporting.