Lean Business Case

Traditional business cases are often long documents that try to predict the full costs and benefits of an initiative years into the future. They take weeks to prepare, rely heavily on assumptions and tend to be optimistic, because their purpose is to win approval. Once approved, they are rarely revisited. Sponsors who have spent weeks building a case are also reluctant to admit when its assumptions prove wrong. A lean business case takes a different approach. It states the idea as a hypothesis, estimates costs and benefits in broad terms and proposes a small, fast experiment, the minimum viable product, to test whether the hypothesis is true before committing more money.

The lean business case is a key part of lean portfolio management in the Scaled Agile Framework, but the idea applies to any organization that wants to fund initiatives in stages. For portfolio leaders and IT finance teams, it reduces the cost of preparing proposals, makes assumptions explicit and limits the money spent on ideas that do not work.

Definition of a Lean Business Case

A lean business case is a concise proposal for a significant initiative that frames its expected outcomes as a testable hypothesis, defines a minimum viable product and the measures that will show success, and estimates the cost of both the test and the full initiative.

It is typically used to move initiatives through a portfolio Kanban, where it is prepared during the analysis stage and reviewed before implementation is approved.

Typical Contents

The description summarizes the initiative and the problem or opportunity it addresses. It should be understandable to someone outside the team in a minute or two.

The business outcome hypothesis states the measurable result the initiative is expected to achieve, such as reducing processing time by 30% or increasing conversion by two percentage points.

Leading indicators are early signals that show whether the hypothesis is likely to be true, measured during the minimum viable product.

The minimum viable product is the smallest version of the initiative that can test the hypothesis, with its estimated cost and duration.

The full estimate gives a rough range for the cost of the complete initiative if the test succeeds, along with key risks, dependencies and the people who will be affected.

Lean vs Traditional Business Cases

A traditional business case seeks approval for the full initiative. A lean business case seeks approval to test the idea first.

A traditional business case often runs to many pages with detailed forecasts. A lean business case is usually one or two pages, with ranges rather than precise figures.

A traditional business case is rarely revisited after approval. A lean business case is updated as evidence arrives, and the decision to continue depends on that evidence. This approach has much in common with a stage-gate process, but with lighter documentation and gates based on test results.

Importance of the Lean Business Case in Strategic Portfolio Management

The lean business case reduces wasted investment. Testing ideas with a minimum viable product means weak ideas are stopped before most of their budget has been spent.

It speeds up decisions. Short, focused proposals take less time to prepare and review, so good ideas can start sooner.

It also improves honesty. Framing benefits as a hypothesis to be tested, rather than a promise to be defended, encourages realistic estimates and makes it easier to stop work that is not succeeding.

The Lean Business Case and Financial Management

Funding is released in stages, starting with the cost of the minimum viable product, which limits financial exposure on unproven ideas.

Rough cost ranges for the full initiative give finance teams enough information to plan, while acknowledging uncertainty.

Comparing test results with the hypothesis gives leaders evidence for continuing, changing or stopping the investment, which is a better basis for capital allocation than a forecast made before any work was done.

Tracking how much money is saved by stopping initiatives after their tests helps show the value of the approach.

Common Challenges

Leaders used to detailed business cases may be uncomfortable approving work based on a short document with broad estimates.

Minimum viable products are sometimes too large, turning the test into a full project and losing the benefit of early learning. A useful rule is that the test should cost a small fraction of the full initiative and take weeks or a few months rather than a year.

Without clear success measures agreed in advance, test results can be interpreted to support whatever decision sponsors already wanted.