The One Challenge Your Business Case Recommendation Must Solve

Strong business cases do not try to solve everything.

They identify the critical challenge that matters most and show why the recommended option is the strongest response for delivering value.

Many business cases lose strength because they try to solve too much at once.

They describe multiple problems, multiple benefits, multiple objectives, and multiple reasons to invest. On the surface, that can make the business case appear comprehensive. In practice, it often makes the recommendation less convincing.

Why? Because the recommendation is not clearly solving the one challenge that matters most.

When that happens, the business case is more likely to be questioned, delayed, reworked, or rejected because decision-makers cannot see clearly what problem the recommendation is designed to solve.

This issue is closely related to the difference between good strategy and bad strategy in business cases. As we explained in our article on Good Strategy/Bad Strategy in Business Cases, stronger business cases are built on a clear diagnosis, real options, and a recommendation that represents the strongest strategic response — not a slogan, a preferred solution, or a vague ambition.

This is a common weakness in business case development. A case may contain sound analysis, reasonable numbers, and well-structured content, yet still struggle to gain approval because it does not isolate the critical obstacle standing between the organisation and the desired outcome.

A stronger business case does not try to solve everything at once. It identifies the one challenge that must be overcome and builds the recommendation around it. That is what sharpens the case for change, strengthens the strategic logic, and gives decision-makers greater confidence that the preferred option is the right one to approve.

What is the “one challenge” in a business case?

In business case terms, the “one challenge” is the critical obstacle, constraint, or issue that the preferred option must overcome for the recommendation to succeed.

It is not every issue facing the organisation. It is not a long list of ambitions. And it is not a generic statement such as “we need to improve performance” or “we need to modernise”.

It is the challenge that matters most in determining whether the initiative will actually work.

This is important because many business cases confuse symptoms with the core issue. Rising costs, delays, poor service, or duplicated effort may be visible symptoms, but the one challenge is the underlying constraint causing those symptoms and putting outcomes at risk.

For example, the one challenge might be:

• a service model that is no longer fit for purpose

• fragmented systems causing poor decisions and duplicated effort

• a delivery bottleneck that limits growth

• a facility or asset that can no longer support operational needs

• a capability gap that prevents strategy from being executed

When a business case identifies this clearly, the recommendation becomes much stronger. It is no longer trying to justify a broad aspiration. It is showing how the preferred option will solve the problem that really matters.

A practical example: identifying the one challenge

Consider a business case for a finance transformation initiative.

A weak version of the case might say the organisation needs better reporting, more efficient finance processes, stronger controls, lower administrative cost, and improved systems. While all of these may be relevant, together they can make the recommendation too broad and less persuasive
​​​​​​​
A stronger business case would identify the one challenge that matters most. For example, the central issue may be that fragmented systems and manual finance processes are producing delayed reporting, inconsistent data, and poor management visibility, reducing confidence in the numbers used for decision-making. Once that challenge is clear, the recommendation becomes easier to assess: which option best improves the quality, timeliness, and reliability of management information with acceptable cost, implementation risk, and organisational disruption

That shifts the business case from a broad transformation wish list to a more focused recommendation with clearer strategic and financial logic.

Why this matters for approval

Executives, CFOs, and boards are not looking for the longest document or the most ambitious proposal. They are looking for confidence.

They want confidence that the organisation has correctly understood the challenge, assessed real alternatives, and selected a recommendation that is capable of addressing the issue in a practical and affordable way.

That is why focus matters.

When a business case tries to solve too many things at once, the recommendation can start to look vague or overextended. It may promise growth, savings, service improvement, capability uplift, technology modernisation, better compliance, and cultural change all at once. While that may sound compelling, it often weakens the logic of the case.

Decision-makers are then left asking:

• What is the actual problem we are solving?

• Why is this the right response?

• What is the key reason this should be approved now?

• What will determine whether this succeeds or fails?

If the business case does not answer those questions clearly, approval confidence drops.

A stronger business case is more disciplined. It identifies the one challenge that must be solved and then shows why the preferred option is the strongest strategic response.

Identifying the critical issue is not only important for winning approval; it is fundamental to delivering the value that CFOs and boards expect after approval.

Decision-makers do not approve business cases merely to release funding. They approve them to solve a material problem, realise benefits, and improve performance.

​​​​​​​A business case that is clear about the challenge that matters most is more likely to drive focused investment, disciplined implementation, and stronger benefits realisation. Without that clarity, projects can drift into secondary priorities, lose focus, and deliver less value than promised.

Where this shows up in a business case

This discipline should be visible throughout the business case, not just in the recommendation.

The case for change

The case for change should explain why action is needed and why the issue matters now.

This is where the one challenge first needs to become clear. If the case for change is too broad or too generic, the rest of the business case can easily lose focus. A strong case for change identifies what is at risk if nothing changes and why delay or incremental improvement is unlikely to be enough.

The strategic logic statement

The strategic logic statement should connect the challenge, the preferred option, and the intended outcome.

This is where the business case explains, in plain language, why the recommended option is the best response to the issue. If the strategic logic is weak, the recommendation can sound more like a preference than a reasoned conclusion.

The options analysis

The options analysis should test which option best addresses the one challenge.

Weak business cases compare options on superficial grounds such as cost, timing, or stakeholder preference alone. Stronger business cases compare options on a more important basis: which option offers the strongest response to the central challenge, with acceptable risk, affordability, and implementation feasibility.

​​​​​​​This is also why the base case matters. If the ‘do nothing’ or status quo option is not clearly defined, it becomes much harder to test whether the preferred option genuinely addresses the central challenge better than the alternatives.

The recommendation

The recommendation should clearly explain why the preferred option is the strongest response and why the alternatives were not preferred.

This is where many business cases become vague. They describe the chosen option, but do not clearly show why it is better than the others in dealing with the real issue.

The implementation strategy

The implementation strategy should show how delivery will overcome the challenge in practice.

If the business case does not show how the critical obstacle will be managed through sequencing, governance, capability, risk treatment, and change management, then the recommendation may still be vulnerable even after approval.

If the recommendation does not clearly address the one challenge at the centre of the case, the business case is likely to be weaker at both approval stage and implementation stage.

How this fits into the 5 Steps Framework

This discipline is embedded in our 5 Steps Framework for developing solid business cases. It helps ensure the recommendation is not rushed or preselected, but built through a structured process that identifies the opportunity, tests real options, evaluates value and risk, plans implementation, and defines a clear approval pathway.

Step 1: Confirm the Opportunity

This is where the one challenge must first be identified.

The purpose of this step is not just to describe an opportunity or problem. It is to clarify what is really driving the need for action and what issue must be solved for the business case to succeed. This is where the case for change starts to take shape.

Step 2: Analyse and Select Short-listed Options

This is where options are tested against the challenge.

The aim is not simply to generate ideas. It is to identify which options genuinely address the one challenge, and which ones do not. This is what makes the shortlist meaningful.

Step 3: Evaluate the Options

This is where the business case tests value, risk, feasibility, and strategic fit.

A strong evaluation process looks beyond headline cost or popularity. It asks which option best addresses the challenge, remains affordable, is achievable in practice, and is most likely to create value.

Step 4: Develop Implementation Strategy

This is where the business case shows how the preferred option will work in practice.

A sound implementation strategy should demonstrate how the organisation will overcome the critical challenge through sequencing, governance, capability, funding, change management, and risk treatment.

Step 5: Develop Recommendations and Get Approval

This is where the recommendation is brought together into a clear approval-ready argument.

The recommendation should explain why the preferred option is the strongest strategic response, why it should be approved over the alternatives, and how it will address the challenge in a practical and credible way.

This is why the 5 Steps Framework is useful. It helps ensure the recommendation is built on disciplined logic rather than advocacy or a preselected answer.

Common mistakes made by business case leads

There are several common mistakes that weaken business case recommendations in this area.

Trying to solve too many problems at once

Some business cases try to address every issue facing the organisation. That usually creates a recommendation that is broad, unfocused, and harder to defend.

Confusing symptoms with the core issue

It is easy to describe visible symptoms such as cost pressure, delays, poor service, or outdated systems. But unless the business case identifies the underlying challenge, the recommendation may not solve the real problem.

Starting with a preferred solution

Some teams decide early what they want to recommend, then shape the business case around that answer. Once that happens, the options analysis loses integrity and the recommendation becomes harder to defend.

Evaluating options too narrowly

Cost matters, but it is not the only thing that matters. Nor is speed, convenience, or stakeholder familiarity. Options should be assessed in terms of how well they solve the core challenge.

Failing to connect implementation back to the challenge

A recommendation can sound strong at approval stage but still be weak in delivery if the implementation strategy does not address the real obstacle at the centre of the case.

A simple test for the business case lead

Before finalising a recommendation, ask these questions:

• What is the one challenge this recommendation must solve?

• Is that challenge clearly stated in the case for change?

• Does the strategic logic explain why this option is the best response?

• Do the shortlisted options represent real alternatives?

• Does the options analysis test which option best addresses the challenge?

• Does the implementation pathway show how the challenge will be overcome in practice?

• Could a CFO, executive, or board member see clearly why this option should be approved?

If the answer to these questions is unclear, the recommendation is probably not yet strong enough.

Conclusion

Strong business cases do not try to solve everything.

They identify the critical challenge that must be overcome and build the recommendation around it.

That is what sharpens the case for change. That is what improves the strategic logic. That is what strengthens options analysis. And that is what gives decision-makers greater confidence that the preferred option deserves approval.

A business case recommendation becomes much stronger when it can clearly explain:

• what the one challenge is

• why it matters now

• why this option is the strongest response

• why the alternatives were not preferred

• what trade-offs are being accepted

• how implementation will turn strategic intent into results

When that logic is clear, the business case becomes more focused, more credible, and more approval-ready.

Want to build a stronger, approval-ready business case?

My Business Case Hub® offers practical tools to help you clarify the case for change, test real options, strengthen your recommendation, and build more effective business case strategies.

If you want expert support, our Business Case Coaching helps you sharpen the logic, challenge assumptions, strengthen your recommendation, and improve approval readiness before your case goes to executive, CFO, or board review.

Start with our 5 Steps Framework or explore Business Case Coaching to build a stronger business case.