Executive Strategy · Capacity and Choice
A New Priority Needs a Place on the Stop-Doing List
Translate executive priorities into real capacity decisions before asking an already busy organization to deliver more.
In this article
The leadership team agrees on a new priority. Everyone leaves the meeting with more work. Nobody leaves with less.
That is often the first implementation problem. The strategy may be sound, but it has been placed on top of a fully committed organization. Employees are then expected to make the tradeoffs privately, usually by delaying something whose importance was never formally withdrawn.
A priority needs a capacity source
Ask which people, decisions, budget, and calendar time the initiative requires. Do not settle for a project-team headcount. A senior specialist needed for two hours at the right moment may be more constrained than a full-time team member. Approval capacity can become the bottleneck even when production capacity appears available.
Map the roles by week or phase. Include preparation, review, implementation, support, and the work that continues after launch. A plan that counts only the visible build period can look feasible while quietly overloading operations.
Choose among stopping, reducing, delaying, and transferring
These are different actions. Stopping ends a commitment. Reducing changes its service level or frequency. Delaying moves it to a defined later point. Transferring assigns it elsewhere with the necessary capability and capacity.
Each needs an owner and an explanation. “Do less reporting” is too vague. “Replace the weekly slide deck with the existing monthly dashboard for the next quarter, with exceptions escalated directly” describes a change people can execute, if the reporting obligation permits it.
A hypothetical customer-onboarding redesign
A company wants operations, technology, and sales to improve onboarding. The same leaders are also running a CRM cleanup, a new reporting project, and routine account reviews. The initiative cannot proceed simply because all four workstreams matter.
The team pauses a discretionary report redesign, narrows the CRM work to fields required for onboarding, and changes the cadence of lower-risk account reviews. It explicitly preserves contractual and customer-critical obligations. The capacity comes from named choices, not an instruction to work more efficiently.
Evaluate the cost of making room
A stop-doing list is not a contest to identify useless work. Some displaced activity has real value. Compare the expected consequence of pausing it with the expected benefit and timing of the new priority. Make uncertainty visible rather than assigning false precision to every outcome.
Ask who experiences the cost. A leadership team may save its own meeting time while pushing more coordination work onto frontline staff. That is a transfer, not a reduction. Verify that the receiving team can absorb it before describing capacity as freed.
Record the tradeoff where people can find it
A priority decision record
Name the outcome, accountable leader, first evidence of progress, required capacity, displaced work, consequences of displacement, protected obligations, and review date.
Include a restart condition for paused work. “After launch” is not enough if nobody can say what launch completion means or who decides the work returns.
This is a useful meeting artifact because it keeps a difficult question visible: what did we knowingly choose not to do? Without that record, a paused task can reappear as a surprise failure in someone’s performance review.
Give managers permission to enforce the choice
Leadership must communicate the change to stakeholders whose requests will now wait. A manager cannot protect a priority if every executive can privately restore their favorite task. Establish how exceptions are decided and who can change the allocation.
When an exception is approved, name the resulting tradeoff again. Avoid treating small requests as free simply because each looks manageable on its own. A series of “quick” additions can consume the review time the main initiative depends on.
Account for the work of stopping
Pausing an initiative can itself require work: notifying partners, closing a purchase commitment, preserving research, or moving an unresolved customer obligation. Do not count all of the project’s capacity as immediately available.
Give the shutdown or pause a small plan. Name what must be completed safely, what can cease now, what knowledge should be retained, and who will communicate the change. This prevents the organization from leaving a trail of half-finished obligations that later return as emergencies.
Then distinguish released capacity from hoped-for efficiency. If a team expects a new tool to save time but has not yet demonstrated the saving, treat it as an assumption. A priority should not depend on people somehow finding hours that the operating plan has already spent.
The calendar has to show the decision
Consider a constructed planning example. An operations lead needs two protected review sessions each week for an onboarding redesign. Leadership cancels a weekly reporting meeting and assumes the problem is solved. But the meeting lasted thirty minutes, while preparing its deck consumed the analyst’s time, not the operations lead’s. The announced saving and the required capacity belong to different people.
A first-fortnight test
Before the change: identify the two decisions the lead must make, what information each requires, and when that information will be available.
At release: remove or reassign the specific obligations that occupy those review windows. Tell their requesters what will happen instead.
After two weeks: compare planned and actual review time. Record interruptions, missing inputs, and any displaced task that returned through another channel.
If the sessions stayed empty because the research was late, the constraint was readiness. If they filled with old approvals, the stop decision lacked authority. If the lead attended but could not decide, the organization may have released meeting time without releasing decision capacity. Each result calls for a different correction.
Ask the receiving teams what the change cost them. The analyst might now answer five separate requests because the shared report disappeared. That does not automatically invalidate the decision, but those requests belong in the capacity account. A saving that exists only on the sponsor’s calendar is too narrow a measure.
The review should end with one explicit disposition: keep the arrangement, change the displaced work, reduce the new initiative’s scope, or revise its timing. The point is to make the priority feasible in the ordinary working week. A heroic fortnight of overtime is evidence that the capacity plan still needs work.
Review capacity as evidence changes
Check whether the expected time was actually released and whether the new work is using it productively. If a dependency is blocked, decide whether to redeploy capacity temporarily or resolve the blockage. Protecting a priority does not mean refusing to learn.
Track milestones, decision delays, overtime pressure, and the consequences of paused work. Use those observations to refine the plan. This belongs within executive strategy and execution, where choices must become operating commitments.
For marketing teams, marketing strategy should include the same discipline. A campaign, positioning change, or new channel needs an honest place in the organization’s available attention.