A leadership team can leave a planning meeting with sensible priorities and still lack an answer to the question that matters most: what is holding progress back? Service needs attention, costs are rising, delivery is slow, and capability needs investment. Funding a workstream for each concern may look thorough. It may also spread effort without changing what limits the result.
The harder task is diagnosis. Leaders need to identify a consequential challenge, explain why it persists, and decide whether they can address it. A shorter list helps only if it follows from that reasoning. Otherwise, the organization has simply become more selective about the wrong work.
Start with the result, then trace what limits it
Richard P. Rumelt calls an important, addressable part of a larger challenge the crux in The Crux: How Leaders Become Strategists. It is more demanding than naming a top priority. “Grow revenue” states an ambition; “improve sales execution” names an area of work. Neither explains what prevents growth or why a particular response should work.
In Good Strategy/Bad Strategy: The Difference and Why It Matters, Rumelt connects diagnosis to a guiding approach and coherent action. Leaders can assign owners, set targets, and approve projects before establishing how those projects will overcome the challenge. The plan then records decisions about activity without resolving the decision about cause.
Take a hypothetical distributor whose on-time delivery is falling. Its leaders could propose workstreams on forecasting, warehouse productivity, carrier management, and customer communication. The best starting point depends on what happens to orders. If many spend days waiting for an inventory exception to be resolved, faster picking may do little for delivery. If carrier capacity causes most delays, clearing exceptions might improve a warehouse measure while customers still receive orders late.
The team should follow orders from receipt to delivery, including time spent waiting between steps. It should compare late orders with those delivered on time and ask how much of the overall delay each explanation accounts for. The aim is not to find an irritating queue. It is to find a condition whose change could make a meaningful difference to customers.
Find the cause, not just the queue
Eliyahu M. Goldratt and Jeff Cox use a fictional operations story in The Goal: A Process of Ongoing Improvement to distinguish the output of an individual step from the flow of completed work. If one step limits what the whole operation can finish, producing more elsewhere can create more work waiting for that step. It is a reason to judge improvements by the end-to-end result, not solely by the measure of the team making them.
A strategic challenge is not necessarily a crowded workstation, however. Goldratt later described a reversal in his own thinking: installing scheduling software could distract plants from changes to measurements and procedures that mattered more to how they operated. His account explains his judgment; it is not independent proof of the plants’ results. It points to a better question for the distributor: what keeps producing the delay?
Suppose the hypothetical distributor finds that many late orders wait for approval of routine product substitutions. Investigation might show that local employees send these decisions to a central team because they lack authority to make them. The queue is visible; the decision rule is a possible cause. Changing that rule could help more than asking the central team to work faster, provided central approval is not protecting an essential customer or quality requirement.
That explanation needs testing. Substitution approvals may affect only a small share of late orders. Central review may prevent errors whose costs outweigh the time saved. A credible diagnosis identifies these competing possibilities before turning a plausible story into a major investment.
Donella H. Meadows offers a wider systems perspective in Thinking in Systems: A Primer and her essay on places to intervene in a system. Recurring behavior can be shaped by information flows, rules, goals, and feedback, not just physical capacity. Delays can also hide the effects of a change. Removing an approval might shift errors downstream; adding delivery capacity might expose another limit. The most conspicuous queue is therefore a place to investigate, not automatically the best place to intervene.
Two existing OutcomesLab principles clarify the choice without replacing the evidence. Strategic Friction is the avoidable resistance created when an organization’s structures, processes, incentives, information flows or behaviors work against its stated strategic choices. The distributor’s approval rule may be such friction if it repeatedly obstructs the delivery priority without providing a necessary safeguard. Focus Multiplier is the disproportionate impact created when an organization concentrates scarce resources and attention on the few choices that matter most. Concentration becomes a better bet once leaders have established why this obstacle matters to the result.
Make a plan the evidence can change
The case for diagnosis is not a case against planning. Peter Maik Hamann, Oliver Halw, and Thomas W. Guenther synthesized 183 independent study samples and found a positive association between corporate planning and organizational performance. The finding does not establish that planning causes better performance, or show that a long priority list works. It does challenge the claim that planning itself is the problem. A diagnosis needs a plan that turns it into coordinated action.
Nor will every situation yield one stable constraint. The distributor could face both approval delays and insufficient carrier capacity. Fixing one might reveal the other. A narrow search for a single answer may also favor what is easy to count: minutes in an approval queue may be clearer than the effects of poor product information or conflicting incentives. Leaders need enough focus to act and enough openness to revise their explanation.
One practical approach is to state the desired result, name the condition currently believed to limit it, and identify the strongest competing explanation. Then specify what should change if the diagnosis is right and what observation would call it into question. This makes a judgment easier to challenge; it is not a validated test that guarantees the right answer.
For the hypothetical distributor, a limited trial might give local employees authority over a defined class of low-risk substitutions while retaining quality safeguards. The team could compare approval time, on-time delivery, and substitution errors with the earlier pattern and with orders outside the trial. Faster approvals without better delivery would weaken the case that approvals are the main limit—or suggest another limit has become decisive. Unacceptable errors would require redesign even if delivery improved.
The next planning decision is more specific than whether to add another priority. Before committing substantial resources, ask the team to show how its proposed work should change the customer result, what evidence supports that explanation, and what will stop or wait so the work has sufficient attention. Then review the diagnosis as the operation responds. Focus is most useful when leaders are willing to change where they place it.