A situation analysis starts outside the organisation, because strategy that ignores the environment it operates in is strategy built on guesswork. PESTLE is the most widely used tool for this macro-environment scan: it organises external forces into Political, Economic, Social, Technological, Legal and Environmental factors. The framework traces back to Aguilar's (1967) 'ETPS' taxonomy — Economic, Technical, Political, Social — which various authors across the 1980s and since extended first into PEST (Fahey and Narayanan, 1986) and then, as legal and environmental concerns became harder to ignore, into PESTEL and PESTLE. There is no single fixed version of the acronym and no need to treat one letter order as more correct than another; what matters is scanning systematically, not the order of the letters.

The discipline that actually matters, and the one most learners skip, is relevance. A PESTLE exercise that lists every political, economic, social, technological, legal and environmental fact a search engine can supply produces a long document and very little insight, because most of those facts have no bearing on the specific market in question. A rising interest rate is a PESTLE factor for almost any business, but it matters enormously to a capital-intensive manufacturer and barely at all to a debt-free subscription software company. The test for each factor is not "is this true" but "does this change what this organisation should do, and by when" — a factor that fails that test belongs in general knowledge, not in a situation analysis a plan will be built on.

For a consumer drinks brand, the factors that typically bite are social (shifting health and sugar consciousness), economic (disposable income and retailer margin pressure) and legal (labelling and sugar-tax rules), while political and environmental factors may be real but marginal to that specific strategic question. Judging which PESTLE boxes deserve weight, rather than filling in all six out of habit, is the actual skill this lesson teaches.

Where PESTLE looks outward, SWOT turns the lens on the organisation itself and its immediate competitive position: internal Strengths and Weaknesses set against external Opportunities and Threats. SWOT's origins are genuinely contested. It is commonly traced to Harvard Business School's Business Policy course in the early 1950s, associated with professors George Albert Smith Jr and C. Roland Christensen, but it is just as commonly attributed to Albert Humphrey's work with Fortune 500 companies at the Stanford Research Institute in the 1960s. A recent historical reconstruction traces SWOT through the 'SOFT' approach developed at the Stanford Research Institute in the 1960s and stresses how little of that early work was ever formally published (Puyt, Lie and Madsen, 2025); with no single definitive original publication for either claim, the honest position is that the attribution remains contested rather than settled on one named inventor.

What the historical dispute doesn't resolve is SWOT's most common failure in practice: generic statements that could describe almost any organisation in the sector. "Strong brand" or "intense competition" are not strengths or threats — they are adjectives with no evidence attached, and they tell a reader nothing they could act on. A rigorous SWOT entry states a specific, evidenced claim: not "loyal customers" but "a repeat-purchase rate of 40% among customers acquired in the brand's first two years" (an illustrative figure, not a Birchwater fact) — a statement someone could check and that implies something about what to protect or exploit. Hill and Westbrook's (1997) review of SWOT in practice found exactly this failure at scale: consultants' SWOTs routinely ran to forty or more factors, generally worded and never prioritised, with no evidence that anyone used the output afterwards.

The competitive half of SWOT also needs naming real rivals rather than an abstract "competition" box: an opportunity or threat is only useful once you can say which competitor's move, or which gap in the market, it actually refers to.

A completed PESTLE and SWOT is not yet a strategy, and most practitioners stop exactly here. McDonald and Wilson (2011) describe this as one of the most common failures in marketing planning: a plan built from pages of analysis with no step that asks what the analysis actually implies, so the objectives that follow bear little relation to anything found in the SWOT or PESTLE that preceded them. The missing step is issues analysis — the deliberate move from a list of factors to the two or three strategic issues the organisation actually has to resolve.

An issue is not a restatement of a SWOT entry; it is a question or problem that combines several entries into something a management team can be held accountable for addressing. Weihrich's (1982) TOWS matrix formalises part of this move by pairing internal and external factors deliberately — asking how a strength could be used against a threat, or how a weakness leaves an opportunity unexploited — rather than leaving the four boxes to sit unconnected. A strength and an opportunity that don't actually connect to each other are not an issue; a weakness that a named threat is about to exploit is.

The remaining discipline is ruthless prioritisation: two or three issues, not ten. An organisation that claims it has ten equally urgent strategic issues has not done the analytical work of ranking them, and a plan built to address ten issues at once will under-resource all of them. The test for whether something deserves to be one of the two or three issues is whether the organisation's current trajectory, left unchanged, makes that issue materially worse — not whether fixing it would simply be nice to have.

A strategic issue identifies a problem; an objective commits the organisation to a measurable response to it. The most widely used standard for writing one is SMART, introduced in Doran's (1981) short Management Review article that has outlasted almost everything else published on goal-setting that year — though the version most practitioners use today has drifted from his own wording: Doran originally wrote Specific, Measurable, Assignable, Realistic and Time-related, while the now-standard popularisation drops Assignable, keeps Doran's realism under Achievable, and adds Relevant. The popularised form is what this module uses: specific means naming the exact outcome rather than a direction of travel; measurable means stating a number a plan can be checked against later; achievable means stretching the organisation without setting a target nobody believes; relevant means the objective actually addresses one of the strategic issues identified in the previous lesson rather than an unrelated ambition; and time-bound means attaching a deadline, because an objective with no date is a hope, not a commitment.

The habit that most undermines SMART objectives in practice is writing them before the issues work is done, so that "grow revenue" or "increase brand awareness" get decorated with a number and a date without ever being traced back to a specific, evidenced issue. An objective that doesn't answer a named strategic issue is just as likely to be the wrong objective, however precisely it is dated and measured. The other common failure is setting an objective that is measurable but not actually relevant to the two or three issues that matter most — hitting it would feel like success without changing the underlying problem.

Objectives set this way become the standard every later strategic choice in a marketing plan — segmentation, positioning, pricing, the channel mix — is checked against, which is why getting them right here, rather than fixing them later, matters more than any other single step in a situation analysis.