The CEO Has 17 Priorities. What Do You Cut?

The Difficult Problem

A leadership team has labeled nearly every worthwhile initiative urgent. People are busy, but attention, decision capacity, and accountability are spread too thin for the most important work to move.

Executive problems rarely arrive as clean questions. They arrive as missed targets, competing explanations, urgent requests, and partial information. A useful diagnosis must distinguish the visible symptom from the mechanism creating it. It must also identify what is not yet known, because confident action based on a weak premise can make the situation harder to reverse.

The purpose of this framework is not to replace the knowledge of people inside the organization. It is to create a disciplined way to combine that knowledge, expose conflicts, and decide what deserves scarce executive attention. The output should be a small number of owned actions and measures, not another presentation that describes the problem without changing it.

The first operating question is what must remain true while the problem is being solved. That may be liquidity, customer continuity, safety, a regulatory obligation, critical talent, or the ability to reverse a decision. Naming those constraints prevents a fast intervention from destroying the capacity needed for recovery.

The second question is where authority and information meet. A person cannot own an outcome if the essential information arrives late or another function controls every meaningful choice. A useful problem map therefore shows decisions, handoffs, dependencies, measures, and escalation thresholds, not only reporting lines.

Finally, the team needs a learning loop. The initial diagnosis is a working explanation, not a performance of certainty. Each action should produce evidence. Leaders should decide in advance what result would support the explanation, what result would weaken it, and when they will reconsider the plan. That discipline makes speed compatible with intellectual honesty.

What Leaders Usually Get Wrong

• Ranking projects by enthusiasm or political sponsorship instead of enterprise consequence
• Calling everything a priority while leaving staffing, capital, and executive attention unchanged
• Cutting the easiest work rather than the work with the weakest strategic or economic case

These errors are understandable because each offers the appearance of movement. The test is whether the action changes the mechanism sustaining the problem, preserves necessary options, and creates evidence that the diagnosis is correct.

How I Would Diagnose It

Start with the outcome the organization must protect or produce during the next operating period.

Map each initiative to a measurable outcome, an accountable owner, a real dependency, and a cost of delay.

Identify which commitments are mandatory, which unlock other work, which protect cash or customers, and which are merely attractive.

Test whether the same people or systems are critical dependencies for several initiatives. That collision is often the real bottleneck.

Before recommending a larger change, I would run a short operating review with the people closest to the work. The purpose is to compare the formal process with what actually happens, identify exceptions and workarounds, and locate the decision where delay or rework first appears. I would record disagreements rather than average them away, because a disagreement often reveals that teams are optimizing different outcomes. The resulting map should make clear which observation is verified, which is an inference, which assumption needs a test, and what decision can safely be made now.

I would then ask what evidence could disprove the leading explanation. That question protects the team from building a confident plan around the most convenient story. The diagnosis should state assumptions, missing information, and triggers that would change the recommended course.

Simple Action Framework

1. 1. Name the one or two outcomes that matter most
2. 2. Protect mandatory and irreversible commitments
3. 3. Fund the few initiatives that directly move those outcomes
4. 4. Pause work whose value depends on assumptions not yet proved
5. 5. Assign one accountable owner and a next decision date to every surviving priority

Each action needs an owner, a near-term decision date, and a measure that reveals whether the intervention is working. Measures should describe the outcome or bottleneck, not simply report that meetings occurred or tasks were completed.

Prioritization is not a better list. It is an explicit decision about what will receive scarce attention now and what will not.

Related work

Watch and read Daily Difficult Problems for short examples of the same diagnostic approach.

Related book · Research and scholarship