Day 1 lessons for strategic alternatives, transactions, financing, operations, market change, sustainability, technology, people, and constraints.
Strategic and operational issue analysis is the middle of the Day 1 response. Candidates should identify the major decisions, test feasibility, recognize constraints, and avoid treating operational details as isolated technical issues.
Day 1 issues should be analyzed as board-level decisions, not as disconnected technical tasks. A strong response identifies the strategic choice, compares realistic options, tests constraints, and explains how operational facts affect recommendation feasibility.
flowchart LR
A["Strategic issue"] --> B["Options"]
B --> C["Constraints"]
C --> D["Operational feasibility"]
D --> E["Board choice"]
| Section | Decision focus | Response habit |
|---|---|---|
| 2.1 Alternatives | Compare realistic alternatives and identify mutual exclusivity. | Rank options against shared constraints and objectives. |
| 2.2 Transactions | Analyze acquisitions, divestitures, alliances, partnerships, and expansion. | Test strategic fit, due diligence, integration risk, and capacity. |
| 2.3 Financing | Evaluate liquidity, borrowing room, covenants, and capital capacity. | Treat financing as a feasibility constraint, not just a calculation. |
| 2.4 Operations | Identify capacity, supply chain, staffing, and execution bottlenecks. | Decide whether the operational issue blocks, delays, or qualifies the option. |
| 2.5 Market Demand | Interpret customer, competitor, pricing, and demand updates. | Link market evidence to forecast reliability and option ranking. |
| 2.6 Financial Effects | Use revenue, cost, margin, EBITDA, and cash-flow signals. | Explain whether the financial effect supports, weakens, or qualifies the recommendation. |
| 2.7 Sustainability | Assess reputation, social responsibility, and long-term value. | Weigh short-term return against trust, stakeholder effects, and durability. |
| 2.8 Technology | Evaluate systems, data, cybersecurity, and transformation risk. | Connect technology readiness to strategy and implementation feasibility. |
| 2.9 People & Change | Analyze leadership, culture, HR, and change-management barriers. | Treat people constraints as execution risks that may require staging. |
| 2.10 Legal Constraints | Identify regulatory, legal, contractual, and compliance limits. | Qualify or delay recommendations when compliance affects feasibility. |
Read each section as a Day 1 response habit. Identify the board-level decision, separate baseline facts from current updates where relevant, integrate limited quantitative and qualitative evidence, and write a recommendation that fits the entity’s constraints.
For public exam context, CPAWSB describes Day 1 of the CFE as connected to the Capstone 1 case: Common Final Examination.
| Trap | Better response |
|---|---|
| Repeating the case instead of updating it. | Explain what changed and why it matters now. |
| Treating Day 1 like Day 2 depth. | Keep the answer strategic, integrated, and board-focused. |
| Ending with vague advice. | State the recommendation, condition, implementation step, and monitoring point. |