A leadership team can approve a new initiative for 2027, allocate the money, and still leave one question unanswered: when will the people assigned to it have time to do it? The operations manager who will lead the rollout already has reviews to run, approvals to make, and problems to resolve. The analyst who will prepare the data still owes the same reports. Before approving the start date, ask what will change in those people’s existing work. If the answer is that they will fit it in, the plan is counting on time no one has set aside.
Why existing work survives the planning meeting
New initiatives have to make a case for themselves. Recurring work can escape that scrutiny because it already has a place on the calendar. A report may still go out every week even though the decision it informed now happens monthly. An approval added after a mistake may still apply to every request, even after the process has changed. Each activity had a reason to exist. The planning meeting is a chance to find out whether that reason still holds and whether the work still needs to happen in its current form.
In eight experiments, Gabrielle Adams and colleagues found that participants were less likely to identify useful changes that involved removing something when they were not prompted to consider removal. The experiments did not study annual business planning, so they cannot tell us how often companies carry unnecessary work into a new year. They do suggest a useful change to the planning agenda: whenever the team considers adding a commitment, give it time to examine what could come off the schedule.
Decide what to keep, simplify, or retire
Start with the people the new initiative will depend on. Review their recurring commitments and ask who uses the output, what decision or obligation it serves, and what would happen if it changed. Include less visible work such as preparing for reviews, reconciling inputs, and chasing approvals. The meeting itself may take an hour, but preparation and follow up can make it a much larger commitment.
Keep work that still supports a decision, fulfills an obligation, or provides a necessary control. Where the work remains useful, ask whether it can be simplified by reducing its frequency, narrowing its scope, or removing an approval that no longer serves a purpose. Consider retiring work when the original need has ended or another process already meets it. Before making a change, check who relies on the work and what information or safeguards need to stay in place.
Take a recurring report as a practical test. Ask recipients which decisions they made with it over the last few cycles and whether they needed the full report each time. If a smaller version appears sufficient, agree on a trial and check whether preparation takes less time and recipients can still make their decisions. The Institute for Healthcare Improvement’s guidance on testing changes describes this method in a healthcare improvement context: try a change on a small scale, observe what happens, and use the results to decide what to do next. The same testing discipline can help here, provided the trial preserves required controls.
Check whose time you actually free
A reduction in total hours can look promising while leaving the new initiative stalled. If a reporting change frees an analyst’s time but the rollout is waiting for an operations manager to approve changes, the bottleneck remains. A shorter report may also save time for its author while leaving several recipients to reconcile the missing figures themselves. Count that extra effort and any temporary handover work before deciding how much capacity the change will create.
The UK Government’s Project Delivery Functional Standard treats capacity as a question of having people with the right skills available when needed. It calls for revising plans when resources are insufficient. For a business, that means checking whether the person needed for the new initiative will have time they can actually use. Sophie Leroy’s research on attention residue explains how attention can remain on unfinished work after someone switches tasks. If the new initiative requires concentration, look for a block of time the person can protect in their schedule. Several short gaps between existing commitments may leave the work just as difficult to start.
Make the decision before January
A practical example of how CleverXEL approaches an operations review is to trace a recurring activity from the person who prepares it to the person who uses it. In the reporting example, that means following the work through to the manager’s decision. If managers rely on one measure to spot exceptions, preserve that measure and the process for acting on it. Then test whether reducing the rest of the report gives the team more time while managers continue to resolve exceptions promptly. That gives leadership a basis for deciding whether to keep the change.
Before approving a new priority, ask the person responsible for delivering it to point to the time they’ll actually have to do the work. Record which existing commitment will change, who will make that change, and when you’ll check that the time was freed. If the people needed are still committed elsewhere, narrow the scope, move the start date, or provide additional support. A credible plan for January starts with a decision in November about what can come off the calendar.
Sources
Adams, G. S., Converse, B. A., Hales, A. H., & Klotz, L. E. (2021). People systematically overlook subtractive changes. Nature.
Institute for Healthcare Improvement. Model for Improvement: Testing Changes.
UK Government Project Delivery. Government Functional Standard GovS 002: Project Delivery, sections 5.3 and 7.4.
University of Washington Bothell. Sophie Leroy: Research on attention residue.