Why Cause Matters More Than the Outcome
A business can suffer an adverse result because it chose a strategy that did not work, because an operational failure disrupted a sound strategy, or because both occurred. The financial outcome alone does not tell you which explanation applies. A loss of revenue, a missed target, or a customer complaint may be the consequence of very different causes.
For risk classification, ask what happened and how it produced the adverse result. A deliberate decision about the markets to enter, products to offer, or resources to commit is strategic. An event involving a failed process, human error, system breakdown, or external disruption is operational when it causes loss or impairs the organization’s activities. The same strategic objective can therefore be affected by either kind of risk, but the objective and the event are not the same thing.
This distinction is aligned with the CAS Exam 9 (Risk Management for Actuaries) syllabus. It is consistent with the earlier material on defining operational risk and classifying process, people, systems, and external risks. Here, the focus is the boundary between an operational event and a deliberate business choice.
A Practical Classification Test
Use a causal sequence rather than starting with a label such as “bad business result.” First identify the initiating action or event. Then ask whether it was a deliberate choice about business direction or a breakdown in execution or operating capability. Finally, connect that cause to the specific consequence. This prevents a strategic objective from being mistaken for the event that disrupted it.
State what someone deliberately chose, or what actually failed or was disrupted. Avoid starting with a general outcome such as “profit was below plan.”
Ask whether the outcome followed from a planned business choice, or from a process, people, system, or external-event failure. If relevant, identify more than one cause.
Separate direct losses, missed opportunities, delays, and impacts on strategic objectives. Do not assume that every consequence has the same risk classification.
A loss does not automatically prove an operational failure, and an operational event does not turn the affected strategic objective into an operational event.
The logic is causal: the outcome is downstream of the initiating cause and the mechanism through which it operates. If a market choice produces fewer sales than forecast while processes work as intended, the shortfall reflects the result of the choice and market response. If a system outage prevents a planned launch, the outage is an operational event and the delayed launch is a consequence. The objective helps describe the impact; it does not replace the cause in the classification.
Worked Applications
Worked Example: A Deliberate Market Entry Underperforms
A hypothetical specialty insurer deliberately enters a small commercial market after reviewing available information. Its approved plan forecasts first-year revenue of $1,500,000 and operating costs of $1,100,000. Actual revenue is $1,200,000, while actual operating costs are also $1,100,000. Assume there were no process, staffing, system, or external-event failures and that the figures are comparable on the same accounting basis. Calculate the actual profit, the forecast profit, and the shortfall from forecast. Classify the outcome.
Method. Calculate forecast and actual profit using revenue minus operating costs, then compare the two amounts. The stated assumption that operations worked as intended is important: the problem gives no operational event to explain the revenue difference.
Forecast profit. Forecast revenue less forecast costs is $1,500,000 − $1,100,000 = $400,000.
Actual profit. Actual revenue less actual costs is $1,200,000 − $1,100,000 = $100,000.
Shortfall from forecast. Forecast profit less actual profit is $400,000 − $100,000 = $300,000. Equivalently, revenue was $1,500,000 − $1,200,000 = $300,000 below forecast, with no difference in the stated costs.
The actual result is still a $100,000 profit, but it is $300,000 below the plan. On the facts given, the result is an adverse outcome from the deliberate market-entry decision and the market response, not an operational event. The calculation checks: the $300,000 shortfall equals the revenue variance because costs are unchanged.
Common mistake. Calling the $300,000 shortfall an operational loss simply because it is unfavorable. That label would need an operating failure or disruption as its cause; none is stated here.
Worked Example: A System Failure Disrupts a Strategic Objective
A hypothetical insurer is migrating policy renewals to a new digital platform as part of a deliberate objective to reduce manual handling. During a scheduled update, a configuration error stops renewal notices from being generated. As a result, 80 renewals require manual handling. The company incurs $250 of overtime cost for each affected renewal and reverses a $100 service fee for each of 12 customers whose notices were late. Assume these costs do not overlap and that no other financial impacts are measured. Calculate the stated direct cost and classify the event and the strategic impact.
Method. Identify the initiating failure, calculate each distinct cost component, and add them only because the problem states they do not overlap.
Manual-handling overtime. There are 80 affected renewals at $250 each, so the cost is 80 × $250 = $20,000.
Reversed service fees. There are 12 affected customers at $100 each, so the amount is 12 × $100 = $1,200.
Total stated direct cost. Add the two non-overlapping amounts: $20,000 + $1,200 = $21,200.
The configuration error is the operational event: a system failure disrupted the renewal process. The delayed migration objective is a strategic consequence of that event, not a separate description of its cause. The $21,200 is the total of the two specified cost items only; it does not include any unmeasured effect on customer retention or future performance.
Common mistake. Classifying the case only as strategic because it affects a strategic objective. The objective explains why the disruption matters; the configuration error explains what happened and how the stated costs arose. The calculation checks: $20,000 + $1,200 = $21,200, with no overlapping amount counted twice.
Worked Example: Separating a Planned Discount From a File-Transfer Error
A hypothetical insurer intentionally enters a new regional market and approves a $200 discount for each of 100 policies as part of its market-positioning decision. Separately, a file-transfer error prevents a $150 surcharge from being applied to 40 of those policies. Assume each amount represents a distinct reduction in premium relative to the insurer’s stated reference amount, with no overlap, and assume the policy counts are accurate. Calculate the total premium reduction and classify each component.
Method. Calculate the effect of each cause separately before summing. The intended discount is a deliberate strategic choice. The missing surcharge results from an operational process failure.
Planned discounts. There are 100 policies at $200 each: 100 × $200 = $20,000.
Missing surcharges. There are 40 policies at $150 each: 40 × $150 = $6,000.
Total premium reduction relative to the reference amount. Because the two amounts are stated to be distinct and non-overlapping, add them: $20,000 + $6,000 = $26,000.
The $20,000 planned discount is associated with the strategic decision to position the product in the new market. It is not an operational failure simply because it reduces premium relative to the reference amount. The $6,000 missing surcharge is associated with the file-transfer error, an operational event. The combined $26,000 describes the total reduction but should not be assigned wholly to one category. The calculation checks: the component amounts sum to $26,000, and each component retains its own cause.
Common mistake. Labeling the entire $26,000 as operational because the file error is operational, or labeling the entire amount strategic because the market entry was intentional. Separating the causes avoids both errors.
Boundary Cases and Classification Traps
Intent is useful, but it is not by itself a complete classification rule. A deliberate choice to enter a market or accept a lower margin is strategic. An intentional act that violates an established process or misuses operating access can still be the cause of an operational event. The key is to identify what the act was doing in the causal chain: setting business direction, or creating a failure in the way the organization operates.
A related trap is to treat a strategic objective as though it were an event. “Grow digital sales” is an objective. “The application became unavailable because of a failed system update” is an operational event. If the system failure delays digital sales growth, report the operational cause and the strategic consequence separately. This is more informative than forcing the whole case into one label.
Mixed cases may involve more than one cause. When the available facts support separate components, describe each component and its mechanism. When the facts do not support a confident split, state what is known, identify the uncertainty, and avoid inventing a precise allocation. A classification should follow the evidence, not the preferred reporting category.
| Situation | Primary classification | Reason |
|---|---|---|
| A deliberate product-positioning choice reduces the planned premium per policy. | Strategic decision | The reduction is an intended feature of the business choice. |
| A system fault prevents planned policy changes from being processed. | Operational event | A system failure disrupts an operating process. |
| A process failure delays an initiative to enter a new market. | Operational event, with strategic impact | The process failure is the cause; the delayed market objective is a consequence. |
| A planned market entry earns less than forecast, with no operating failure identified. | Strategic outcome | An unfavorable result alone does not establish an operational event. |
The distinction matters because different causes call for different analysis. If the cause is a strategic decision, review the decision, its assumptions, and the resulting business performance. If the cause is an operational event, identify the breakdown and the mechanism of loss. If both contribute, keep their effects distinguishable. This classification is not a claim that one type of risk is more important than another; it clarifies what happened and where further investigation should focus.
Check Your Understanding
For each case, identify the cause, classify the relevant effect, and show any requested arithmetic. Treat the scenarios as hypothetical.
- A hypothetical insurer approves a new distribution channel. It forecasts $900,000 of revenue and $650,000 of costs, but actual revenue is $820,000 and costs are $650,000. No operating failure is identified. Calculate forecast profit, actual profit, and the shortfall from forecast, then classify it. (Answer: Forecast profit = $250,000; actual profit = $170,000; shortfall = $80,000; strategic outcome, with no operational event stated.)
- A system fault prevents 50 scheduled account updates. Each update costs $180 in manual work, and 8 affected customers receive a $75 fee reversal. Assume no overlap. Calculate the stated total cost and classify the cause. (Answer: Manual work = 50 × $180 = $9,000; fee reversals = 8 × $75 = $600; total = $9,600; operational event.)
- A deliberate product choice gives 60 customers a $120 discount. Separately, a processing error omits a $90 charge for 20 customers; assume these amounts do not overlap. Calculate the combined reduction and give the separate classifications. (Answer: Planned discount = 60 × $120 = $7,200; omitted charges = 20 × $90 = $1,800; combined reduction = $9,000; $7,200 is strategic and $1,800 is operational.)
- A company’s objective is to launch a new service by July. A failed internal handoff delays required system testing, and the launch occurs in September. No financial loss amount is provided. Identify the operational event and explain the role of the strategic objective. (Answer: The failed handoff is the operational event; the September launch is a two-month delay to the strategic objective. No financial loss can be calculated from the information given.)
- A business deliberately enters a market and earns $40,000 less than forecast. A separate software outage causes $12,000 of documented overtime costs. Assume the amounts are distinct. How should the effects be reported? (Answer: Report the $40,000 forecast shortfall as the outcome of the strategic decision and market result, and the $12,000 overtime cost as an operational-event impact; combined adverse amount = $52,000, with the two causes kept separate.)