Use scenario, sensitivity, uncertainty, and assumption risk to qualify strategic recommendations.
Scenario risk is the risk that the recommendation changes when a key assumption changes. Day 1 candidates do not need to produce a full risk model, but they should recognize when an attractive option depends on uncertain demand, cost, timing, financing, approval, capacity, or stakeholder behavior.
Uncertainty should not paralyze the response. The goal is to give useful board advice while being clear about the assumption that could change the decision.
Because Day 1 is linked to the Capstone 1 case, the baseline case often contains assumptions about strategy, resources, competitive position, stakeholders, or governance. The Day 1 update may confirm those assumptions, weaken them, or introduce new uncertainty. A strong response notices that change.
Scenario and sensitivity thinking helps answer questions such as:
| Question | Why it matters |
|---|---|
| What assumption most affects the recommendation? | Focuses the response on decision risk rather than generic uncertainty. |
| Would a downside case reverse the ranking? | Shows whether the recommendation is robust or fragile. |
| Which variable should the board monitor? | Converts uncertainty into an implementation control. |
| Can the risk be mitigated? | Determines whether the option should be accepted, modified, delayed, or rejected. |
The response should distinguish ordinary uncertainty from decisive uncertainty. Ordinary uncertainty exists in almost every strategic decision. Decisive uncertainty changes the recommendation, the timing, the size of the commitment, or the condition attached to approval.
A sensitivity analysis is useful when it identifies the assumption that matters most. For example, a forecast may be sensitive to volume, pricing, retention, exchange rates, financing cost, construction timing, or supplier reliability. The exam response should not merely state that the result is “sensitive.” It should explain what the board should do because of that sensitivity.
| Sensitivity result | Possible board-level implication |
|---|---|
| Recommendation remains favorable under the downside case. | Proceed, but monitor the key variable. |
| Recommendation becomes unfavorable under a modest downside case. | Stage the project, reduce exposure, or gather stronger evidence before full approval. |
| One assumption drives most of the result. | Make approval conditional on validating that assumption. |
| Downside risk threatens liquidity or reputation. | Reject, delay, or redesign the option unless mitigation is practical. |
This is where many weak responses stop too early. They identify the risk but do not connect it to advice. A stronger answer says whether the risk changes the ranking, creates a condition, requires monitoring, or makes further action inappropriate.
Qualified advice is not vague advice. It is a recommendation with a condition. The condition should be specific enough that the board knows what must happen before management proceeds.
Examples of useful qualification include:
| Situation | Better qualification |
|---|---|
| Demand is uncertain. | Approve a limited launch only after confirming customer commitments or pilot demand. |
| Financing is uncertain. | Proceed only if financing terms do not breach covenant or liquidity constraints. |
| Capacity is uncertain. | Delay full implementation until staffing, systems, or supplier capacity is confirmed. |
| Governance approval is uncertain. | Require board approval, conflict review, or independent analysis before commitment. |
Avoid qualifications that avoid judgment. “More analysis is needed” is too weak unless the missing analysis is named and linked to the decision. A board-level response should say what evidence is missing, why it matters, and what interim action is appropriate.
Day 1 cases may present a management preference. Scenario risk is a useful way to test it. If management’s preferred option works only in an optimistic case, the response should say so. If it remains acceptable under a reasonable downside case, that strengthens the recommendation.
The key is not to oppose management automatically. The key is to assess whether management’s preference is supported by the current update and the entity’s risk tolerance. If the preference is fragile, recommend a narrower version, a staged approach, or a monitoring requirement. If the preference is supported, still identify the assumption that should be watched after approval.
| Pitfall | Correction |
|---|---|
| Calling everything uncertain. | Identify the assumption that most affects the recommendation. |
| Treating sensitivity as a calculation only. | State whether the sensitivity changes ranking, timing, size, or conditions. |
| Refusing to recommend because facts are uncertain. | Give conditional advice when enough evidence exists to guide the board. |
| Ignoring downside consequences. | Explain whether the downside case threatens liquidity, strategy, reputation, or feasibility. |