work
Running Off the Inbox, Not a Plan
I’ve spent weeks answering email promptly, attending the meetings, and ending each day tired, while the work I cared about barely moved. The sent-mail count looked respectable. The work I’d intended to finish was still waiting.
I call it running off the inbox. It’s easy to keep doing because the day feels full and people appreciate the replies. You can be useful to everyone who contacts you and still neglect something important to your own business.
Why I keep falling into it
Email gives me a ready-made list. Each message comes with a sender, a request, and often a deadline. The work I need to decide on for myself has none of those advantages. Nobody is waiting for me to think through a product idea or call someone I should have kept in touch with. I can put it off without having to explain the delay to anyone.
Answering messages also provides a satisfying sense of completion. There was a request; I dealt with it. A difficult proposal may take two hours before I have anything worth sending. It’s tempting to clear a few more messages first, particularly when I’m unsure how to begin.
There is a social reward, too. A fast reply is visible. Time spent thinking about a problem usually isn’t, at least until it produces something. That makes responsiveness an easy habit to defend, including to myself.
I’ve tried inbox-zero discipline, task managers, folders, and filters. They can make email easier to handle. They haven’t helped much with the decision about what deserves my attention before I start answering it.
Choose something you can finish
The most useful change is to choose one or two outcomes before opening email, ideally the night before. I want to make that choice while I can still think about the work, before a new set of requests starts competing with it.
The wording matters. “Work on the proposal” gives me something to spend time on. “Send the proposal” tells me what I’m trying to finish. If sending it isn’t realistic yet, choose a smaller outcome: finish the estimate, for example, or resolve the question that’s holding up the scope.
A list of thirty priorities doesn’t help me here. I want to know what would make today worthwhile even if the rest slips. Once that’s clear, I can give it a place on the calendar.
An unscheduled intention is easy to displace. Someone asks for a meeting at ten, ten looks free, and I say yes. Putting the work on the calendar forces me to notice the trade I’m making. I can still move it, but I have to decide when it will happen instead.
The first block of the day is a good place for work that needs sustained attention. It also means the rest of the day can go wrong without taking all of it away. If mornings belong to clients or another fixed responsibility, use a block you can realistically protect. A plan that depends on nobody needing you all morning won’t survive many mornings.
Make room for the replies
After that block, the inbox is still there. So are the people who need an answer. The aim is to visit it at times you’ve chosen, handle what’s there, and close it long enough to concentrate on something else.
Some jobs don’t allow much of that. If you run support, handle operations, or receive the company’s escalations, responding is a substantial part of the work. Treating every interruption as a failure to prioritize would be unfair and impractical. The question is how much time you can protect for improvements or decisions that won’t happen while you’re responding. It may be a small part of the week rather than a daily morning block.
And some messages really do matter more than what you had planned. A calendar appointment with yourself isn’t a reason to ignore a client emergency. It gives you a plan to return to when the emergency is over.
I don’t expect to stop having reactive days. I’d like fewer weeks where I look back and realize that every day was one. Choosing an outcome and giving it time on the calendar is a small enough change that I can return to it whenever I notice I’ve drifted.