Move from issue analysis to conclusion using a clear board-level recommendation flow.
A Day 1 recommendation must flow from the analysis. The reader should be able to trace the path from the current update to the issue, from the issue to the evidence, from the evidence to the implication, and from the implication to the recommendation.
Weak responses often contain the right topics but in the wrong order. They repeat the case, list unrelated calculations, mention risks, and then state a conclusion that does not clearly follow. Recommendation flow fixes that problem by making the logic visible.
Day 1 is a strategic case response linked to Capstone 1. The response should not feel like a collection of disconnected technical notes. It should read like advice prepared for a board or senior-management audience.
A clear recommendation flow usually includes:
| Element | Purpose |
|---|---|
| Current issue | Identifies what changed and what decision is required. |
| Strategic context | Connects the issue to the baseline case, objectives, and constraints. |
| Evidence | Uses calculations, qualitative facts, technical implications, and risk. |
| Implication | Explains what the evidence means for the decision. |
| Recommendation | States what the board should do. |
| Condition or next step | Adds implementation, monitoring, or further-information requirements. |
The order can vary, but these elements must be connected. If a conclusion appears before the evidence is interpreted, the answer may look unsupported. If analysis is detailed but no recommendation follows, the answer remains incomplete.
A recommendation flows when the strongest case facts point toward it. It does not flow merely because management prefers it or because the candidate has written many points about it.
Use these tests:
| Test | Ask |
|---|---|
| Evidence test | Did the answer use the strongest financial and qualitative facts? |
| Constraint test | Did the answer address the fact that could block or qualify the option? |
| Comparison test | Did the answer explain why the recommended option is better than the main alternative? |
| Baseline test | Did the answer fit the entity’s established strategy and current update? |
| Action test | Did the answer tell the board what to do next? |
If any test fails, the recommendation may need revision. For example, if the analysis shows a financing constraint but the recommendation approves a large expansion without conditions, the conclusion does not flow. If the analysis identifies severe stakeholder opposition but recommends immediate implementation without mitigation, the conclusion is incomplete.
Recommendation flow does not require every piece of evidence to receive equal space. A strong answer selects evidence that matters and arranges it in a way that supports judgment.
One practical structure is:
| Sentence role | Example function |
|---|---|
| Issue sentence | Name the board-level decision and current update. |
| Evidence sentence | Summarize the most important quantitative or qualitative support. |
| Implication sentence | Explain what that support means for feasibility, risk, or ranking. |
| Recommendation sentence | State the action. |
| Condition sentence | Add implementation, monitoring, or missing-information conditions. |
This structure is useful because it keeps the response concise. It also prevents the common error of writing analysis that never reaches advice.
Unsupported conclusions often come from three habits. First, the candidate repeats management’s preference and treats it as the recommendation. Second, the candidate chooses the option with the best single metric and ignores constraints. Third, the candidate gives a cautious conclusion without explaining which fact justifies caution.
A better conclusion points back to the analysis:
| Unsupported conclusion | Better conclusion |
|---|---|
| “Management should proceed with the expansion.” | “Management should proceed only with a staged expansion because projected demand is favorable but cash capacity and staffing remain constrained.” |
| “The board should reject the proposal.” | “The board should reject the proposal because the downside case would breach the funding constraint and no mitigation is available in the current facts.” |
| “More information is needed.” | “The board should delay approval until customer commitments are confirmed, because the recommendation depends on volume assumptions that drive the projected margin.” |
The stronger version shows the evidence, the implication, and the action.
| Pitfall | Correction |
|---|---|
| Ending analysis without advice. | State the recommended action and any condition. |
| Repeating management’s preference. | Test preference against evidence, constraints, and risk. |
| Jumping to a conclusion too early. | Interpret the strongest evidence before recommending. |
| Writing disconnected paragraphs. | Use a visible issue, evidence, implication, recommendation flow. |