Skip to main content

Someone wanted to learn this too, so Grasp built them a personal learning path.

You can keep exploring this one or create your own

Analysing Initiative Outcomes

Hello. In the previous lesson, you distinguished executives by the outcomes they are accountable for. Now put those perspectives to work on a single initiative. An innovation leader might see a promising new offering; a product leader might see a customer problem; a business-unit head might see new costs and operating commitments. An executive analysis needs to hold all of those views together.

This lesson gives you a compact way to assess a current initiative through its customer, financial, strategic, and organisational outcomes. Allow about 35–40 minutes, including a short video and reading. You do not need to know how to read financial statements yet; the aim is to make the initiative’s claims, evidence, and unanswered questions clear.


Begin with outcomes, not activity

Suppose a product company is piloting an assistant that helps maintenance planners respond to vehicle alerts. “We launched the pilot” describes an activity. “Planners make sound decisions faster” describes a customer outcome. “Customers pay enough to sustain the service” describes a financial outcome. The distinction matters: delivery can be on schedule while the initiative fails to create value.

A balanced scorecard offers a useful starting point because it looks beyond financial results. Watch this brief explanation for the four perspectives and, especially, the reason to measure what enables a result as well as the result itself.

The Balanced Scorecard explained

Watch “The Balanced Scorecard explained” from Sim Institute for a quick introduction to assessing performance from more than one viewpoint.

Watch the full explanation. In the café example, notice how staff capability, operating performance, customer experience, and financial results answer different questions about the same business. Treat the final distinction between leading and lagging indicators as a useful tendency, not a guarantee that one metric causes another.

For an initiative, translate those perspectives into four executive questions:

  • Customer: What improves for the intended user or buyer? Who, specifically, receives the benefit?
  • Financial: What additional revenue or cost—and eventually financial return—does the initiative create for the business?
  • Organisational: Can the company deliver, support, and improve it repeatedly? This includes processes, skills, systems, and clear ownership.
  • Strategic: Why is this initiative a good use of attention and resources for this company, given its priorities and alternatives?

The first three draw directly on scorecard perspectives: customer, financial, and the combination of internal process with learning and growth. Strategic fit is an additional judgement across them, not merely another metric to place beside them. An initiative can improve customer experience yet pull scarce engineers away from a more important product commitment. Conversely, an initiative may have modest revenue today but generate credible evidence for a strategically important future offering.


Make the proposed value creation visible

The scorecard becomes more useful when you state how the results are supposed to arise. In the maintenance example, the proposition is that better access to relevant alert information will help planners decide faster; a dependable service will encourage continued use; and enough customers will then choose to pay for it. Each connection is a hypothesis to test, not a fact established by putting it on a slide.

The template below separates objectives—the changes sought—from measures and targets. Its four rows also prompt you to ask whether the organisation has the capabilities and processes needed to produce the hoped-for customer and financial results.

A blank strategy-map and balanced-scorecard template with financial, customer, process, and learning-and-growth rows. Its columns distinguish the objectives an initiative pursues from the measures and targets used to judge progress.

Read the short passages below to see how to choose those objectives and measures. The source discusses a company-wide scorecard; here, you are applying the same logic at the smaller scale of one initiative.

What Is a Balanced Scorecard? | HBS Online

Read Harvard Business School Online’s “What Is a Balanced Scorecard?” for the four perspectives, the role of a strategy map, and a test for whether a measure is useful.

In “What Is a Balanced Scorecard?”, read the four perspectives, through the sentence introducing the strategy map. In “How to Create a Balanced Scorecard: 3 Steps,” focus on “1. Craft a Strategy Map”: read the strategy logic, paying attention to why the author connects objectives rather than listing measures. Then, in “2. Select Measures,” read the measure test and its customer-satisfaction example. The key question is whether a measure can tell you something decision-useful about the objective.

A practical initiative review gives each important outcome an objective, a measure, and a comparison point. “Improve the planning experience” is an objective but not yet an assessment. “Reduce median time from alert to planner decision from 20 to 15 minutes within three months, without increasing incorrect decisions” says what improvement means, when to look, and what must not deteriorate.

The comparison point might be performance before the change, a group that did not receive it, or a previously agreed target. Without one, “users spent 14 minutes per decision” is difficult to interpret. A target says what would count as success; observed results say what happened. Keep the two separate, particularly when presenting an early pilot.

Choose a small set of measures that can expose a false success story. Faster decisions matter less if they are less accurate. More paying customers matter less if serving them costs more than the revenue they bring in. Training completion matters less if teams still cannot support the service reliably. Some measures give an early warning; others show a later result. Neither substitutes for examining whether the assumed connection between them is actually holding.


Read a pilot across all four outcomes

Consider an illustrative second-month review of the maintenance-planning assistant. Eight existing customer accounts have tried it. The company’s strategic intent is to extend its established alerting product into decision support for the same buyers. These figures are invented for learning purposes, not a benchmark for similar products.

Lens Intended outcome Evidence so far What remains uncertain
Customer Help planners make sound alert decisions faster Among the eight pilot accounts, median time from alert to decision fell from 20 to 14 minutes compared with their earlier workflow Were decisions equally sound? Will the improvement persist outside a closely supported pilot?
Financial Add sustainable paid revenue Four pilot accounts are paying each per month: in additional monthly revenue. Estimated additional running costs are per month Can paying demand grow, or running costs fall, enough to support the service? An earlier build cost is not included in the monthly comparison
Organisational Support the assistant as part of normal operations Support work has risen by about six hours a week; the team has no agreed runbook for wider rollout Who owns recurring support, and can data access and service quality be managed at larger scale?
Strategic Deepen the company’s value to its existing target customers All eight pilot accounts are in that target group; the assistant addresses a problem adjacent to the existing product Is extending into decision support more valuable than improving alert accuracy for the wider customer base?

Read across the rows rather than declaring a winner from any single number. The customer evidence is encouraging: the observed median time fell by six minutes, or 30 percent. But a small, selected pilot does not establish that the assistant caused all of that improvement. Planners may have received extra help during the pilot, or the mix of alerts may have changed. Decision quality also needs checking; speed alone is not the promised outcome.

The financial evidence is less favorable at this stage. The four paying accounts bring in per month, while estimated additional running costs are per month. That is an monthly shortfall before considering the earlier build cost or any wider business effects. It does not prove the initiative can never work: both demand and costs may change. It does mean “customers are paying” is not yet the same claim as “this is financially sustainable.” Later modules will give you more precise tools for analysing these economics.

The organisational row explains why a promising pilot may be difficult to scale. Extra support hours can be reasonable while learning, but they cannot remain invisible in a rollout plan. The missing runbook raises a decision-rights question from the previous lesson: which operating team agrees to take responsibility, and under what conditions? The strategic row then asks whether resolving all this is worth doing relative to another use of the same people and funding. Alignment with the existing customer base is a reason to investigate—not, by itself, a reason to invest without limit.


Turn the analysis into a decision

An executive review should end with a judgement proportional to the evidence. For this illustrative pilot, a defensible recommendation is continue a bounded test, but do not approve a broad rollout yet. Preserve the chance to learn from the customer improvement while placing limits on further spending and operational commitments.

The next review would need evidence on three points: whether faster decisions remain accurate under ordinary use; whether more target customers will pay or the ongoing cost can be reduced; and whether an operating team can support the assistant without undermining the core alerting product. The product and innovation leaders can help define the test and its evidence threshold. The business-unit head must weigh its commercial and operating implications. A major shift of resources away from enterprise priorities may require a broader executive decision.

This is what makes an outcome analysis more than a dashboard. It states what appears to be working, what is not yet working, what could reverse the conclusion, and who must decide the next commitment. Where evidence is missing, say so plainly rather than replacing it with enthusiasm or false precision.


Conclusion

To analyse an initiative, distinguish its activity from its customer, financial, organisational, and strategic outcomes. Use a small number of measures with clear comparison points, examine the assumptions connecting them, and make a decision that matches the strength of the evidence. An attractive customer result can coexist with weak economics or an unprepared operating team; an executive has to see all three, plus the strategic alternative.

In the next lesson, you will turn this outward-looking judgement inward: which capabilities and evidence of achievement would help you progress toward an innovation-led executive role?

Can't find a good explanation? Sign up and we'll make it for you

Sign up