Review questions

Integrated summary: Foundations of Strategic Management and Strategic Choice

Subject 1 establishes the language of strategic thinking before introducing the main analysis tools. Strategy is not a list of initiatives and it is not the same as operational effectiveness. An organization may reduce time, errors, or cost and gain real value from those improvements, yet the strategic question remains: whom will we prioritize, what value will we promise, what activities make that promise possible, and what trade-offs protect distinctiveness? In the fictional services firm, trying to combine fast standardized delivery with deep customization for every customer at the same price and lead time creates tension because the activities and resources supporting one promise can undermine the other. Exceptions can be sensible, but they should be deliberate rather than an uncontrolled second model.

Operational effectiveness concerns performing activities better. Strategy concerns a coherent pattern of choices. A target such as 'grow sales by 20%' is an objective; automating reports is an initiative; training the team is an enabling action. None is a strategy on its own. Strategic logic appears when a priority customer or need is linked to a value proposition, reinforcing activities, and explicit trade-offs. The logic should be judged by clarity, testable assumptions, and coherence rather than document length or number of slides.

Strategic management then becomes a cycle of learning and decision: analyze context, formulate options and choices, execute them, and review performance and new signals. These movements overlap. Execution can reveal that an assumption about customers or capabilities was wrong, and review can reopen analysis or formulation. Revising a plan after credible new evidence is therefore not necessarily weakness; it can be disciplined learning when the reason and decision are clear. Continuous change without criteria or logic, however, is not strategic adaptation merely because it is fast.

Decision level also matters. Corporate strategy in a multi-business organization asks which businesses the organization should be in and how resources are allocated across them. Business-unit strategy asks how to compete or create distinctive value in a particular activity. Functions translate these higher choices into priorities for capabilities, technology, operations, finance, and other areas. A function can optimize its local metric and still damage the strategy if its behavior contradicts the chosen promise; alignment matters more than isolated local success.

Vision, mission, and objectives provide direction and alignment. Vision describes a desired future state, mission clarifies purpose, core work, and audience, and a strategic objective states a priority result that can be monitored. They still do not constitute the entire strategy. Two organizations can share a broad vision and mission while choosing very different customers, activities, and trade-offs. Objectives also require separation of outcome, indicator, and initiative: increased retention is an outcome, renewal rate is a possible indicator, and redesigning the customer journey is an initiative that may contribute to the result. Completing the initiative does not prove the outcome.

Before jumping to a solution, management should frame the issue as a decision question. 'Demand increased' is a signal; 'open a new branch' is a proposed solution. 'What is the most suitable way to absorb demand growth over the next 24 months while preserving service quality and financial flexibility?' opens the decision to alternatives and introduces a horizon and criteria. Next, separate what is known from what is inferred and assumed. An increase in custom requests from 12 to 20 can be verified, but it does not prove that all customers will pay a premium. That is an assumption requiring separate evidence.

Criteria and weights can organize judgment. In the fictional example, strategic fit carried 40%, feasibility 35%, and resilience 25%. Option A scored 4, 3, and 2, giving 3.15; option B scored 3, 4, and 4, giving 3.60. When weights changed to 60%, 25%, and 15%, A became 3.45 and B 3.40, reversing the ranking. The lesson is not that either option is actually superior. It is that the output can be sensitive to the judgments embedded in the weights. A matrix makes reasoning discussable; it does not transform a strategic decision into mathematical truth.

End the subject with a practical sequence. Frame the issue without assuming the answer. Record evidence, inference, assumptions, and constraints separately. Define the strategic question and horizon. Generate genuine alternatives. Define criteria before seeing scores. Check decisive constraints. Test sensitivity to weights and assumptions. Then connect the recommendation back to vision, mission, objectives, and explicit choices. Later subjects will reuse this language for external and internal analysis, option design, execution, measurement, and learning. No tool in the sequence automatically produces the 'correct strategy'; its value is in making judgment, assumptions, and trade-offs clearer and reviewable.