On Friday, we had aligned on the engineering risks that mattered most. Together with our Staff Engineers, we had mapped technical risks, organizational bottlenecks, and initiatives worth addressing before they became emergencies. Everyone agreed on the priorities. On Monday, none of them existed in my calendar.
It was full of interviews, one-on-ones, roadmap discussions, Slack questions, and escalations. Every item was legitimate. Many were exactly the conversations a leader should have. But our agreement on what mattered had not allocated any time, people, or decision-making energy to act on it.
That is the trap behind the familiar urgent-versus-important distinction. Recognizing important work is not the same as making it happen. Inside an engineering organization, priorities compete in an internal attention economy. The work that changes the system usually needs more than agreement. It needs a sender.
How the internal attention economy works
An attention economy is not a literal market with a price tag on every meeting. It is the system through which an organization directs its finite attention: its meetings, decision-making energy, interruptions, and capacity to think. Requests that arrive with urgency, a visible stakeholder, or an escalation naturally receive more of it.
That allocation is often sensible. It is also not neutral. The person who can create the most immediate pressure is not necessarily pointing at the most consequential problem.
By sender, I do not necessarily mean a person. I mean a mechanism that makes work hard to ignore: an owner who needs a decision, a recurring forum, a document that must be updated, a review date, or a commitment that someone will notice if it slips.
Reactive work usually arrives with one. A recruiter needs a decision because a candidate has another offer. A Tech Lead needs help with a difficult situation. Product needs a trade-off resolved before a roadmap meeting. An executive needs input for tomorrow’s presentation. Someone is waiting, and that naturally creates urgency.
Strategic work often does not arrive this way. Redesigning ownership, developing leaders, reducing a recurring architectural risk, or diagnosing why teams keep escalating the same decision can remain a vague concern for a long time. The cost is distributed and delayed. There may be no single person who can say, “I need an answer by tomorrow.” It makes it less likely to win by default.
In this attention economy, urgency is a powerful allocation mechanism. Without a counterweight, it reliably favors work with a sender over work whose cost is delayed and distributed.
Reactive work is part of the job
It would be easy, and wrong, to turn this into an argument for declining meetings or ignoring Slack. Helping a Tech Lead think through a hard situation is leadership. Supporting Product through a real trade-off is leadership. Responding quickly during an incident is leadership.
Reactive work also provides useful signals. If the same ownership question keeps returning, if the same class of incident keeps interrupting teams, or if the same decision needs to be escalated, that repetition is evidence. It may point directly to the strategic work the organization has postponed.
The problem begins when incoming urgency becomes the only way leadership attention is allocated. A calendar then reflects who asked most recently and most forcefully, rather than the combination of work that keeps the organization running and work that makes it work better.
Agreement is not allocation
The workshop taught me that a shared priority list is a weak commitment on its own. It tells people what matters, but it does not answer the harder questions:
- Who is accountable for moving this forward?
- What decision, outcome, or artifact will show that progress has been made?
- Which people have capacity to do the work?
- When will we look at it again, even if nothing is on fire?
Until those questions have answers, an important initiative is competing against a full calendar with only goodwill on its side. This is why migration weeks, architecture reviews, and strategy offsites can be useful, but only when they produce follow-through. A migration week protects engineering capacity. An architecture review creates a recurring decision point. An offsite can create enough distance to identify a problem worth solving. None of them works merely because it has an impressive name on the calendar.
For more strategic work to survive, it needs a small operating system around it. In practice, that means giving each priority:
- a named owner and, where needed, an executive sponsor;
- a concrete next decision or deliverable, rather than an aspiration;
- explicitly reserved capacity, not time people hope to find later; and
- a review rhythm that continues until the work is completed, changed, or consciously stopped.
Those elements give strategic work a sender. They turn “we should improve our decision-making” into “the owner will bring a proposed decision model to the architecture forum on this date.”
Focus time is a tactic
I now protect recurring time for longer-term work and reschedule it immediately when a genuine priority displaces it. That helps. It is also not enough.
A protected block does not create capacity from nowhere. It makes a trade-off visible. If leaders want room for strategy, something else may need to be declined, shortened, delegated, delayed, or redesigned so that it no longer requires their direct involvement. If none of those choices is possible, the organization may have a capacity problem rather than a calendar problem.
“Protect your focus time” can become individual advice for a structural failure: unclear decision rights, too few leaders, an approval-heavy process, or teams that lack the context and authority to resolve ordinary issues themselves. A leader’s calendar is often a symptom of those problems, not just a personal productivity challenge.
Treat repetition as data
One practical starting point is to look at the last month of reactive work. Which questions, escalations, or approvals repeated? Which meetings existed only because a decision was not clear elsewhere? Which risks were widely acknowledged but had no owner, decision date or capacity attached?
Those are candidates for strategic work. They do not all deserve a new initiative—some may need a quick decision or a clearer boundary. But each deserves an explicit choice rather than another month of accidental deferral.
Leadership is not choosing between serving the organization today and improving it for tomorrow. It is managing both. Reactive work keeps the current organization running. Strategic work changes how it runs.
Only one of them arrives automatically. If strategic work exists only when nobody interrupts you, it will lose. Give it an owner, a decision date, a forum, and capacity that someone has explicitly chosen to protect.