On Email Bankruptcy

On Email Bankruptcy

Preempting this drastic measure and mitigating its cultural and tactical damage

Mike Stein

Oct 27, 2026

3

5

Share

Photo by

Melinda Gimpel

on

Unsplash

People like the “

bankruptcy

” metaphor for

permanently giving up on a backlog, often of email, that has grown too large to reasonably handle

.

My first thought on the metaphor was that it’s a little hard-hitting, unpleasant and callous for a regular piece of workplace jargon. My second thought, however, is that this is actually at the right level of seriousness for a last-resort action with long-term consequences. The real dissonance is the flippancy with which it is discussed and declared.

So let’s treat this seriously, both on how to handle it, and how to prevent ever needing to handle it.

We’ll use “email bankruptcy” as the example here, but similar principles apply to other types of communications inflow or even tasks in your to-do list.

When and when not to consider email bankruptcy

Real-world bankruptcy occurs when an entity has accrued more debts than it can possibly repay. Email bankruptcy occurs when you’ve accrued more unread or unactioned emails than you can possibly handle.

The following must all be true before you should even consider email bankruptcy:

It has to be very costly for you to pay down your email debts.

If you could solve your overflowing inbox by finding, say, an hour or two to skim all of your emails, you should probably just find those hours.

You need to be confident that you’re not deleting anything truly critical.

If you work in a culture where you’d have also heard elsewhere about the most important things, that makes email bankruptcy safer.

There have to be ways to get important things back on your radar.

You’ll never have full confidence in the above; it’s hard to know the importance of something you don’t read. So you need a team that will help you by redelivering important information you missed.

Even when these are all true,

email bankruptcy is a drastic action that will have an adverse effect on your “credit score”: your working relationships

. I have always prided myself on being a reliable counterparty for all of my teammates and clients, and that has paid dividends throughout my career. If you’re here reading this, you probably do, too. Your colleagues certainly value it.

Your declaration of email bankruptcy is

admitting that you’ve failed your team

. This should drive your approach.

How to productively declare email bankruptcy

The medium for this declaration should be permanent and reach everyone – probably an email, maybe also a Slack post or a mention in a team meeting.

Be contrite.

I’ve seen too many declarations of email bankruptcy made casually, tongue-in-cheek, or even with an implicit glorification of how “busy” the declarer is with “real work”. This not only disrespects the team, but it vastly lowers the bar of cultural expectations. At the risk of beating the metaphor here beyond recognition, it could set off a cascading wave of defaults across your team, leading to a market crash in collaborative work.

Your need to declare email bankruptcy wasn’t some small, relatable mistake like getting a speeding ticket.

This was you totaling the company car by neglecting to steer it.

Acknowledge the impact.

You have let people down. You have done unknown and unbounded amounts of damage to your team and its output. So you should

lead with apology, identify ways that your mistakes may have impacted your work

, and

make a call to action on how your teammates can help mitigate the harm you have caused.

A good default: identify the timeframe of the unread emails you’re deleting and ask people to re-flag anything from then where you didn’t get them the response they expected.

An even better default: reach out 1-on-1 to those you work most closely with and ask what the

top three most important things they need from you right now are

. This frames the path forward as a clean-slate reset and will help you rebuild your focus around what matters most, not what mattered last month but isn’t worth thinking about anymore.

Commit to what you’ll do differently from now on.

Review all of your processes around email and conduct a postmortem on what went wrong. Were you not filtering away the least important emails effectively enough? Did the time you had set aside for email get too crowded out by emergencies? Or had you simply not had any process for your email in place, thinking it would be ok? Either way, you’ve learned it doesn’t work.

A key orienting principle here:

find smaller, less-impactful buckets to preemptively pare down and reclaim time from

before ever getting close to the overall bankruptcy that would affect your important work.

Here’s my toolbox for your postmortem (or for your premortem to avoid reaching bankruptcy in the first place):

Reexamine your core processes for handling your email. There are

effective alternatives to inbox zero

that you should explore.

If you haven’t previously set aside time each day or week for reviewing your email or other inbound communications,

time blocking your calendar

is definitely worth a try.

Declare preemptive, small, time-bounded bankruptcies more often, such as telling your team that you won’t ever read any Slack messages sent while you’re

out of office

or

surging

.

Similarly, you should filter low-signal-to-noise emails into

batches that you’ll often skim weekly, but can avoid and let “expire” when busy

. If you see your unread count ballooning, you might try searching to focus your attention on the emails most likely to be important, e.g. from your manager. Useful searches can be promoted into useful email filters.

Do an inventory of your typical task and email inflow against

my important, urgent & quick task framework

. Where these fall in the Venn diagram informs how you should preempt bankruptcy on each category:

The

important and urgent

probably aren’t the tasks that build up unread in your inbox but can be the straws that break the camel’s back of your

time portfolio

. If these increase, you need to decide on more work not to do. Your

time is finite

.

If your buildup towards bankruptcy is coming mostly from

important, non-urgent, non-quick tasks (your “Deep work”)

, these tasks may benefit the most from routine reprioritization. Before picking something old back up from this bucket, gutcheck its current importance with your team.

If your bottleneck is

important, non-urgent, quick tasks (your “Defer to next batch”)

, prune this backlog even more aggressively. These are the types of tasks or emails that are best done semi-promptly, but then might be better off discarded rather than done late.

And make sure you are calibrated properly around what’s

unimportant, non-urgent, and non-quick (the tasks you “Don’t” do)

. The fastest way to slow the inflow of emails and tasks is to find more to just say no to.

Set up a brief weekly self-review each Friday to check in on what’s working and what needs to be tweaked around your email processes.

Put it into practice

Declaring bankruptcy when you need to is the second-best move. It’s much better than

not

declaring bankruptcy, once you’re sure you need it.

But

never reaching the point of bankruptcy is a clear best move

. Review the bullets above to give your preemptive processes a tune-up.

Improve your team’s culture around bankruptcy by being an early warning system for your teammates: if they aren’t meeting your expectations on the emails you send to them, start a conversation to realign those expectations, or share some useful resources:

Share Processes for People

Receive new posts and subscriber-exclusive take-home templates in your inbox with a free or paid subscription:

📰In other news…

I recently joined Fred Li’s podcast on Forward Deployed Engineering for a deep conversation about building cultures and processes for strategic and tactical success around my favorite type of people: Forward Deployed Engineers.

Much of the discussion is tangential to the core, generalizable productivity methods I write about here, but everything I’ve learned about optimal operations was either built or reforged in the high-velocity operating environment in which FDE teams constantly live. I believe that, if a process is good enough for FDEs and robust enough to hold up under their needs, it’s worth considering for all sorts of teams.

Check it out if you’re interested:

https://stipulate.work/blog/what-does-a-forward-deployed-engineer-do-mike-stein

I’ve organized my archives into a recommended reading order. You can learn more about this “book”

here

or hop to the next or previous “chapter” via the links below.

Previous chapter:

The Antisurge

Mike Stein

·

Apr 14

A “surge” is a short period of particularly intense work on completing a high-priority goal. If you work in tech, you’ve probably heard of it, and surges may be a frequently recurring pa…

Read full story

Next chapter:

Optimal OOO, Part 1: Preparing for Effective Leave

Mike Stein

·

May 5

As you plan your vacation for the summer, you should also plan to step away from work the right way.

Read full story

3

5

Share

Previous

Next