Read a sample: 1. The Work That Keeps Getting Pushed Aside
You begin the day intending to make progress on a project that matters. Perhaps it is a proposal a client needs, a process your team has been waiting to improve, or a decision that requires a little uninterrupted thought. You know what you want to do first.
Then a message arrives. A colleague needs a file. A meeting runs long. Someone asks for a quick answer before lunch. By midafternoon, you have handled a dozen things, but the important project is still where you left it.
You may even have worked hard all day. That is part of what makes the situation confusing. The problem is not that nothing got done. The problem is that the day’s most visible demands chose what got done.
A busy day is not automatically a poorly spent day. Some requests deserve immediate attention. A customer issue may affect today’s delivery. A teammate may genuinely be blocked. A problem discovered this morning may be more consequential than anything you planned yesterday. The difficulty begins when every new demand receives the same fast response, regardless of what it displaces.
This book is about making those tradeoffs visible. It will not ask you to ignore your colleagues, reject every interruption, or build a schedule so rigid that one unexpected call ruins it. Instead, you will learn to identify your commitments, estimate the time you actually have, and make a weekly plan that leaves room for both important work and the realities of your job.
The first step is to notice what keeps getting pushed aside.
Important work does not always announce itself as urgent. Some of it has a distant deadline. Some of it has no formal deadline at all. It may be complex enough that you cannot finish it in the gaps between meetings, or uncertain enough that the first step is not obvious.
Consider a team lead, Maya, who wants to improve a handoff process that routinely causes confusion. Each week she intends to map the current process and identify where information gets lost. Each week she responds to questions about individual handoffs instead. Her responses help people in the moment, so the day feels productive. But because the underlying process remains unchanged, similar questions keep coming back.
Maya’s immediate work is not meaningless. Her colleagues need answers. Yet the improvement project matters too, partly because it could reduce the recurring confusion that fills her days. If she waits until no one needs her, she may never find the right moment to begin.
Important work might look different in your role:
- Preparing a recommendation before a decision has to be rushed.
- Developing a new service while continuing to serve existing clients.
- Reviewing a team’s workload before missed commitments become a crisis.
- Documenting a process that currently depends on one person’s memory.
- Completing a task you promised someone but have avoided because it is difficult to start.
- Learning a skill required for work already on the horizon.
These examples have something in common: their value may be substantial even when their next action is quiet. They do not necessarily produce a new notification when they need attention.
You do not have to decide that this work is more important than everything else. You do need to recognize that it is competing with everything else. If the competition remains invisible, the most immediate request will often win by default.
Most professionals have responsibilities that must be maintained alongside longer projects. Messages need answers. Customers need service. Routine work keeps an organization functioning. The aim is not to divide your job into “real work” and everything else.
A more useful distinction is between maintaining the flow of work and making progress on an outcome that requires deliberate attention. Both can be important. The question is whether the balance reflects your responsibilities or merely the order in which demands arrive.
Suppose a designer spends a morning answering questions from colleagues. Some answers prevent costly rework. Others concern decisions that could wait until a scheduled review. If the designer responds to each message as soon as it appears, the morning may feel equally urgent from start to finish. Yet the consequences of a short delay are not the same for every request.
Treating all requests as urgent creates several problems.
First, it makes priorities difficult to see. If a request that can wait until tomorrow receives the same treatment as a problem affecting today’s delivery, urgency stops conveying useful information.
Second, it transfers the cost of one person’s request to another commitment. The cost may fall on your own project, a colleague waiting for your review, or a client who expects a finished deliverable. That cost is easy to miss because the displaced work is often silent.
Third, it encourages a pattern of constant switching. Returning to a task may require you to find your place, recover your reasoning, or reopen materials. A brief interruption is not always brief in its effect, especially when it breaks a complicated train of thought.
Finally, immediate responsiveness can conceal a capacity problem. If you absorb every new request by postponing planned work, the people making requests may see a quick answer while the missed commitment remains out of view.
None of this means you should delay every response. It means a response is also a choice about the work you are not doing at that moment. Sometimes…