In this topic 10 sections
- 01Strategy, tactics and strategic management
- 02Evolution of strategic management
- 03The six-stage strategy development process
- 04External and internal analysis
- 05Strategy evaluation
- 06Deliberate, emergent and realised strategy
- 07Implementation, monitoring and the learning loop
- 08Big data and the four Vs
- 09Analytics and evidence-based judgement
- 10Sources and further reading
Strategy, tactics and strategic management
Strategy is an organisation's overall approach to achieving its purpose through connected choices about direction, resources and activities. It explains how the organisation expects to succeed and what it will prioritise. An ambition such as “become the leading provider” states a desired position; it still needs an explanation of customers, activities and resource commitments.
- Strategy
- The overall choices that guide the organisation and explain how it expects to create value.
- Tactics
- Specific actions used to carry out those choices, such as a trial offer or revised delivery timetable.
- Objectives
- Results to achieve, with a clear measure and time frame where possible.
- Strategic management
- The continuing work of analysing, choosing, implementing and reviewing strategy.
Concept sources: NIST: strategy, business.gov.au: business planning — Concept references; cards prepared for these notes.
Strategic thinking interprets the situation and considers possible directions. Strategic planning turns choices into documented priorities, responsibilities and resource commitments. Neither replaces the other: imaginative ideas without implementation remain intentions, while a detailed plan can execute the wrong idea very efficiently.
Strategy and tactics differ in their role, not simply their duration. A short decision to leave a market can change the whole organisation. A maintenance programme lasting several years may support an existing strategy without changing it. Ask whether a decision changes the overall approach or helps deliver that approach.
Evolution of strategic management
Strategy's military origins emphasised coordination and deployment towards an overall objective. Business strategy extends beyond winning a contest: organisations can cooperate, create new demand and serve different groups. Its development brings together several useful perspectives.
| Perspective | Main contribution | Question it helps answer |
|---|---|---|
| Formal planning: Chandler and Ansoff | Connect longer-term direction with deliberate action and resource decisions | What are we trying to achieve, and what commitments are required? |
| Competitive positioning: Porter | Choose a distinctive position supported by compatible activities and trade-offs | Why should customers choose us, and how will the economics work? |
| Learning and emergence: Mintzberg | Examine patterns that develop through action, including unplanned ones | What are experience and behaviour revealing that the plan missed? |
Concept sources: Scoblic: strategic foresight and planning traditions, Harvard Business School: strategy explained, Mintzberg: Tracking Strategies — Concept references; table prepared for these notes.
These perspectives complement each other. Planning helps coordinate commitments; positioning tests the competitive argument; learning helps the organisation adapt. A forecast should therefore support judgement rather than create false certainty. The farther a decision reaches into an uncertain future, the more useful it becomes to identify assumptions, possible changes and review points explicitly.
The six-stage strategy development process
The six stages below provide a useful organising sequence. They connect direction, analysis, choice and execution. In practice, the process is iterative: an internal capability gap may require another option, and implementation evidence may change the original context.
- 01Set context
- 02External analysis
- 03Internal analysis
- 04Explore options
- 05Develop strategy
- 06Implement and monitor
Review and learn throughout: new evidence can change earlier decisions.
Concept sources: NIST: strategy, business.gov.au: business planning — Concept references; diagram prepared for these notes.
| Stage | Work to do and why it matters | Useful output |
|---|---|---|
| 1. Set context | Clarify purpose, scope, stakeholders and the decision required; establish what success means | Agreed objectives, boundaries and assumptions |
| 2. External analysis | Investigate customers, competitors, industry pressures and wider change; identify conditions affecting success | Prioritised opportunities, threats and uncertainties |
| 3. Internal analysis | Assess finances, people, assets and capabilities; distinguish ambition from delivery capacity | Evidence of strengths, weaknesses and resource gaps |
| 4. Explore options | Generate genuinely different responses; avoid treating the first idea as the only choice | Alternatives with likely benefits, costs and risks |
| 5. Develop strategy | Evaluate alternatives and select a coherent approach; specify priorities and trade-offs | Chosen direction, resource commitments and action responsibilities |
| 6. Implement and monitor | Execute, measure results and review assumptions; adapt when evidence warrants it | Actions, performance reviews and decisions to continue, change or stop |
Concept sources: NIST: criteria commentary, strategy development and implementation, business.gov.au: SWOT analysis — Concept references; table prepared for these notes.
A stage is useful only if it changes a decision. For example, listing ten market trends adds little unless the team explains which trend affects demand, cost, timing or risk. Likewise, “excellent staff” is too vague for internal analysis. Identify the particular skill, evidence of performance and capacity available for the proposed work.
External and internal analysis
External analysis concerns the environment; internal analysis concerns the organisation. SWOT summarises this distinction through strengths, weaknesses, opportunities and threats. A growing market is an opportunity, not an internal strength. A skilled service team is a strength, not a market opportunity.
Prioritise findings by their significance to the decision. A useful strategic issue connects evidence with an implication: “Demand is growing, but our limited distribution coverage prevents us serving the most attractive segment.” This is more actionable than separate lists of favourable and unfavourable facts.
Generate alternatives by changing a real choice: customers served, service scope, delivery channel, timing, ownership or partnership. Include a sensible continuation option so that the comparison does not assume change is always preferable. The current approach also carries risk if demand or competition is changing.
Distinguish an option from an implementation variation. Recruiting two different candidates for the same approved role may be an implementation choice. Building a capability internally versus contracting for it may alter cost, control and the future business model sufficiently to be strategic.
Keep assumptions visible. “Customers will pay more” should identify which customers, what additional benefit they receive and the evidence supporting willingness to pay. An unsupported assumption should become a research question, not quietly become a forecast fact.
Strategy evaluation
Strategy evaluation compares alternatives against the organisation's objectives and constraints. Before commitment, it tests the proposal. After implementation, evaluation examines actual results and whether the strategic logic still holds. A profitable-looking spreadsheet is one input, not a complete evaluation.
| Decision test | Evidence to examine |
|---|---|
| Purpose and problem fit | Whether the option addresses the important issue and supports the organisation's objectives |
| Customer or stakeholder benefit | Whether the intended users receive a benefit they value |
| Delivery capability | People, systems, capacity, partners and implementation time |
| Financial affordability | Funding availability, working capital and timing of cash requirements |
| Risk and reversibility | Downside exposure, assumptions, dependencies and the ability to adjust |
| Overall value | Expected benefits compared with the resources used and alternatives forgone |
Concept sources: HM Treasury: Green Book appraisal principles — Concept reference; table prepared for these notes. Its formal requirements concern public-sector appraisal; the decision questions above are general study prompts.
Use comparable assumptions across alternatives. Consider a realistic range of outcomes, not only the most favourable forecast. A weighted score can organise discussion, but an impressive total does not repair missing evidence or override an unacceptable legal or ethical issue. A pilot can reduce uncertainty before a large commitment.
Deliberate, emergent and realised strategy
Intended strategy describes the starting intention. Deliberate strategy is the part carried through as intended; an abandoned intention is unrealised. Emergent strategy develops through a pattern of action that was not originally planned. The realised strategy is the pattern the organisation actually follows.
| Deliberate strategy | Emergent strategy |
|---|---|
| Direction is substantially specified before implementation | Direction develops as people learn through action |
| Coordination follows explicit priorities and commitments | Repeated useful responses may become a new direction |
| Main risk: holding to assumptions after conditions change | Main risk: drifting without coherence or sufficient review |
| Useful where commitments need coordination and conditions are reasonably understood | Useful where uncertainty makes experimentation and adaptation valuable |
Concept sources: Mintzberg and Waters: Of Strategies, Deliberate and Emergent — Concept reference; table prepared for these notes.
A rational planning approach stresses systematic analysis before choice. An iterative approach revisits choices as evidence arrives. Neither requires the organisation to abandon discipline. Experimentation can have a budget, an owner and stopping conditions; a formal plan can allow adaptation.
Implementation, monitoring and the learning loop
Implementation needs named responsibility, resources, milestones and coordination. A statement such as “improve service” does not tell staff what to change. Monitoring should combine results with evidence about whether the approach is working as expected.
Lagging measures describe outcomes already produced, such as operating profit or customer renewals. Leading measures track conditions expected to influence those outcomes, such as unresolved service failures. A leading measure is useful only if its assumed connection with the outcome is credible.
- State the assumption
- Choose an action and measure
- Observe the outcome
- Explain the difference
- Improve execution or revise the assumption
- Test again
Concept sources: NIST: learn and improve — Concept reference; diagram prepared for these notes.
Two levels of learning matter. An execution review asks whether the intended work happened. An assumption review asks whether the underlying explanation was right. If a service misses its sales target, better advertising may be appropriate; alternatively, the intended customers may not value the offer. Repeating the same action more forcefully does not resolve an incorrect assumption.
Leaders encourage learning by inviting contrary evidence and separating honest experimentation from careless execution. They should ask what would change their view, avoid punishing every unfavourable finding and give teams a route to escalate emerging problems. Clear direction and constructive challenge can coexist.
Big data and the four Vs
Data supports strategy when it informs a decision. A larger dataset does not automatically provide a better explanation. The four Vs identify different data-management challenges.
| Term | Meaning | Strategic implication |
|---|---|---|
| Volume | Amount of data available | Select relevant evidence; do not confuse size with usefulness |
| Velocity | Speed of arrival and change | Match analysis speed to the decision deadline |
| Variety | Different formats and sources | Combine information without losing its meaning |
| Veracity | Reliability and uncertainty | Check errors, missing records and possible bias |
Concept sources: IBM: big data — Concept reference; table prepared for these notes.
Data quality means fitness for the intended use. Accurate records can still be unsuitable if they are outdated, cover the wrong population or use inconsistent definitions. Check where the data came from, what is excluded, when it was collected and whether figures can be compared. Access controls, accountable ownership and documentation help make analysis reproducible.
Analytics and evidence-based judgement
| Type of analytics | Main purpose | Illustrative output |
|---|---|---|
| Descriptive | Summarise recorded activity | Monthly cancellations by service |
| Diagnostic | Investigate reasons and relationships | Analysis of where cancellations cluster |
| Predictive | Estimate possible future outcomes | Forecast cancellation levels under stated assumptions |
| Prescriptive | Compare or recommend actions under constraints | A proposed staffing allocation within a budget |
Concept sources: IBM: prescriptive analytics and the four analytics types — Concept reference; table prepared for these notes.
A pattern is a starting point for investigation. Correlation alone does not establish causation, and a forecast is conditional on data and assumptions. Combine analysis with operational knowledge, customer research and judgement about what has changed. Explain uncertainty instead of hiding it behind a precise number.
An analytics culture requires more than software: staff need shared definitions, the ability to question results and time to use findings. Decision-makers should document the evidence behind important choices and revisit it after implementation. For revision, practise explaining the sequence from strategic question to evidence, interpretation, action and review.
Sources and further reading
The references support the concepts. Examples are teaching illustrations.
- NIST: strategy — Direction, priorities and implementation.
- NIST: criteria commentary — Strategy development and deployment.
- business.gov.au: business planning — Objectives and review.
- business.gov.au: SWOT analysis — Internal and external factors.
- Scoblic: Strategic Foresight as Dynamic Capability — Planning traditions and uncertainty.
- Harvard Business School: strategy explained — Positioning and coherent choices.
- Mintzberg: Tracking Strategies — Patterns of strategy development.
- Mintzberg and Waters: Of Strategies, Deliberate and Emergent — Strategy terminology.
- HM Treasury: the Green Book — Option appraisal principles.
- NIST: learn and improve — Reviewing performance.
- NIST: data and analysis — Measures and evidence.
- IBM: big data — The Vs of data.
- ABS: data quality framework — Fitness for purpose.
- IBM: prescriptive analytics — Four analytics types.
- IBM: diagnostic analytics — Investigating causes and relationships.
