PESTLE analysis done well, beyond a list of bullet points

Most people have seen a PESTLE analysis: six headings, a handful of bullet points under each, and a slide that nobody refers to again. “Inflation.” “New technology.” “Changing consumer attitudes.” Every point is true, and none of it helps anyone decide anything.

A good PESTLE is different. It identifies the few outside forces that will most affect a specific decision, backs them with evidence, and says what to do about them. This guide shows how to get there.

What PESTLE is

PESTLE is a structured scan of the external environment. The CIPD factsheet describes it as “a broad fact-finding activity around the external factors that could affect an organisation’s decisions”. The six headings are:

• Political: government policy, tax, trade rules, stability.
• Economic: growth, interest and inflation rates, wages, unemployment, exchange rates.
• Social: demographics, cultural attitudes, lifestyles, career expectations.
• Technological: new tools such as AI and automation, and the pace of change.
• Legal: laws on employment, consumer protection, trade, data and tax.
• Environmental: climate pressures, sustainable sourcing, ethical supply chains.

The idea goes back to Francis Aguilar, who proposed an environmental scanning framework in 1967, as summarised on Wikipedia. Many variants exist, such as PEST, STEEP and STEEPLE. The UK government’s futures toolkit calls PESTLE, STEEP and STEEPV “all versions of the same approach”. Pick one and use it consistently; the headings are a checklist to make sure nothing is missed, not the analysis itself.

Why most PESTLEs disappoint

The Wikipedia summary quotes the researchers Tovstiga and Aylward: “it is all too easy to produce lists of factors”. Listing is easy. Understanding how each factor will affect your business is the hard part, and it is the part that matters.

Weak PESTLEs share a few features. They have no question, so they include everything. They describe trends without saying what they mean for the organisation. They treat all factors as equally important. And they are done once, then filed. The CIPD lists the opposite risks too: relying on too little data or on assumptions that prove wrong, and gathering so much information that it causes “paralysis by analysis”.

A step-by-step method

The CIPD sets out eight steps, from defining the scope to agreeing actions. The version below follows that sequence and adds the toolkit’s way of ranking drivers.

1. Set the question and scope. Name the decision, the markets or regions, and the time horizon. “What outside changes could affect our plan to open two shops in Leeds over the next three years?” is a usable scope.
2. Involve different people. The CIPD recommends several people or teams collecting data, so the scan reflects different views. Finance, operations and sales will each spot things the others miss.
3. Use reliable sources. Official statistics, regulators, industry bodies and published research are better than opinion pieces. Note the source for each point.
4. Write each point as driver, trend and implication. For example: “Driver: the legal minimum wage. Trend: future rates are decided by government, not by us. Implication: most of our staff are paid close to the minimum, so we need a margin buffer for increases.”
5. Rank by impact and certainty. The toolkit plots drivers on an importance-versus-certainty grid. Important and fairly certain drivers go straight into your plans. Important and uncertain ones need contingency plans or scenarios. Low-importance drivers go on a watch list.
6. Decide responses and owners. For each high-priority driver, agree an action and who is responsible.
7. Share and monitor. Present the findings to decision-makers, and set a date to review. The CIPD stresses that “to be effective, a PESTLE analysis needs to be done regularly”.

A better format than bullet points

Replace the six-box slide with a table. One row per driver makes it much harder to hide vague points.

Keep the final list short. Five to ten priority drivers, clearly explained, are worth more than forty bullet points.

A worked illustration

An example (illustration only). A family-owned chain of three cafés in Leeds is considering two new sites. Instead of filling six boxes, the owners ask what outside changes could make the new sites fail or succeed within three years. Their priority list includes:

• Economic: wages and energy prices are their two largest cost lines after rent. Impact high, certainty medium. Response: model the new sites at higher wage and energy assumptions, and only proceed if they still break even.
• Social: more people working from home part of the week changes weekday footfall in the city centre. Impact high, certainty medium. Response: favour a site in a residential area over one next to offices.
• Environmental: customers increasingly ask about packaging. Impact medium, certainty high. Response: switch to reusable cups at the new sites from day one.
• Legal: licensing and planning conditions for outdoor seating. Impact medium, certainty high once checked. Response: confirm with the council before signing a lease.

Political and technological points went on the watch list. The result fits on one page and changed two decisions: which site to choose and how to set prices.

Common mistakes

• No question. Without a decision to inform, the scan has no way to decide what matters.
• Internal factors in an external scan. “Our staff turnover” belongs in a SWOT or internal review.
• Trends with no implication. Every point should finish the sentence “which means that we…”.
• Arguing over headings. Whether data protection is legal or technological does not matter; capturing it does.
• Assuming the future repeats the past. The CIPD warns against this directly, and Wikipedia notes that PEST explains past change better than it predicts future change.

When to use it, and what to pair it with

Use PESTLE before entering a new market, when setting a multi-year plan, before a major investment, or when an outside change has caught the organisation by surprise. Repeat it at least yearly, or when a big shift happens.

On its own it only covers the wider environment. The CIPD suggests combining it with SWOT, Porter’s five forces and scenario planning. A practical sequence is PESTLE for the wide view, five forces for the industry, then SWOT to link outside findings to your own strengths and weaknesses. For the most uncertain drivers, build scenarios rather than guessing a single outcome.