Strategy Explore
PESTLE and Its Extensions
PESTLE scans political, economic, social, technological, legal, and environmental forces, including the ethical and geographic extensions.
The questionWhich outside forces could change this client's options in the next few years, and which of them should we act on?
Also written PESTEL. Related forms include PEST, STEEPLE, and LoNGPESTLE.
- Political Tax, trade rules, subsidies, stability
- Economic Growth, rates, inflation, exchange rates
- Social Demographics, values, labor supply
- Technological Adoption, cost curves, automation
- Legal Employment, consumer, competition, data law
- Environmental Climate, resources, emissions, physical risk
When to use it
- A client is entering a new country or sector and nobody has written down the outside conditions its plan depends on.
- Strategy discussions are driven by internal capability, and regulation, demographics, and technology change are missing from the room.
- You are preparing inputs for scenario planning and need a first list of drivers to rank.
- A new team needs a shared first view of the external context in an afternoon.
When to avoid it
- You need to understand specific competitors or customers. This scan covers broad context, and a framework such as Ohmae's 3C looks at the company, customer, and competitors directly.
- The output will be a single page of forty bullets. Stop at the ranking step, or do not run it.
- The client already tracks a few external variables and the argument is about how to respond. Move on to scenarios or decision analysis.
- The decision turns on an internal operating problem that outside forces do not explain.
Overview
PESTLE is a checklist for scanning the external environment: political, economic, social, technological, legal, and environmental forces that sit outside the client’s control but affect its options. It supports one early choice, which outside developments the team will study before committing to a strategy or an investment.
On its own the list does little. The value comes from ranking each item by its impact on the decision and the uncertainty around it, so the scan ends in a few assumptions and a few things to watch, and not a page of bullets. PEST, PESTLE, STEEPLE, and the geographic versions differ only in what they add. Agree on the list with the client at the start.
The factors
Political
How governments affect the client's industry. Look at tax policy, trade rules, subsidies, public procurement, regulation under development, and political stability, along with elections that could change any of these.
Economic
Growth, interest rates, inflation, exchange rates, input costs, and employment. Pick the ones the client is actually exposed to, such as a currency it pays suppliers in.
Social
Demographics, attitudes, values, customer expectations, and labor supply. Often written as socio-cultural. A shift in how people buy or work is a social factor even when technology drives it.
Technological
Adoption rates, cost curves, automation, and standards. The question is what has changed in what is practical or affordable, not what has been invented.
Legal
Employment law, consumer protection, competition rules, data protection, and health and safety. Some versions fold this into Political. Keep it separate when regulation is the main exposure.
Environmental
Climate exposure, resource scarcity, emissions rules, energy costs, and physical risk to sites and supply chains. Some versions write it as Ecological.
Extensions
Ethical, added in STEEPLE, for reputation and conduct questions. Demographic, in some versions. Local, national, and global levels in LoNGPESTLE, which fits clients whose exposure differs by geography.
What it is not
- A forecast. It lists the forces and says nothing about what they will do. It helps explain past changes more than predict coming ones.
- A complete taxonomy. Categories overlap, and a carbon tax is political, economic, legal, and environmental at once. Where an item is filed matters less than whether it is ranked.
- A single fixed framework. PEST, PESTLE, and STEEPLE differ by author and textbook, so agree on the list with the client before you start.
The steps
-
Fix the question and the horizon
Write down which decision the scan serves and how far out it looks. A fleet purchase with a twelve-year life needs a different scan from a quarterly pricing review. Without a decision, the scan has no way to rank anything.
-
Agree on the version and the scope
Settle the factor list with the client, PESTLE by default, adding ethical or geographic cuts where they matter. Name the geographies and the industry boundary.
-
Gather evidence for each factor
Use regulators, statistics, industry data, and interviews. Write each item as a development with a source, such as a program that ends in a given year, not as a heading such as Politics.
-
Rank by impact and uncertainty
Score each item on how much it would change the decision and how uncertain the outcome is. High impact and low uncertainty items become planning assumptions. High impact and high uncertainty items go to scenarios or monitoring. Low impact items drop out.
-
State the implications
Say what the ranked factors mean for the decision in front of the client. Assign an owner and an indicator to each high-uncertainty item, so the scan does not end at the offsite.
In practice
Forty-one bullets were on the slide when the project lead asked which three would change the client's capital plan. The client was a regional bus operator weighing a switch to electric vehicles. The bullets covered grant programs, electricity prices, battery costs, driver supply, emissions rules, and remote work.
The team ranked them by impact on the fleet decision and by uncertainty. Battery costs had high impact, but the direction was predictable, so they became a planning assumption. Whether the state grant would be renewed and where electricity tariffs would settle had high impact and high uncertainty. Those two went to scenario work, each with an owner and an indicator. The remaining thirty-eight bullets either ranked low or became footnotes.
What you leave with
- An agreed factor list and scope, written as developments with sources.
- A short ranked list of the factors that matter for the decision.
- Planning assumptions for factors that are high impact and low uncertainty.
- The high impact, high uncertainty factors, each with an indicator and an owner.
- A statement of what the scan implies for the decision in question.
Failure points
The dump
Forty bullets, no ranking. Bullets are easy to generate, so the list grows, and the slide shows the client a list of things it cannot control. Nobody decides anything from it.
Generic factors
Items such as economic uncertainty could appear on any client's slide. A factor is only useful when you can say what it changes for this client and by when.
Arguments over category
The team spends an hour on whether an item is legal or political. The category does not change the ranking, so the hour is wasted.
A scan that is filed
It is done once for an offsite and never updated, and nobody owns an indicator. A year later the factors that mattered most have moved and no one noticed.
Evidence collected after the decision
The strategy is already chosen, and factors are gathered to support it. Items that cut against it get dropped as low impact.
The failures above are usually Framing: the wrong problem was chosen before this framework was applied.
Origin
The usual root is Francis Aguilar's Scanning the Business Environment, published by Macmillan in 1967 and revised from his Harvard thesis. Aguilar studied how managers collect information about their environment and sorted it into economic, technical, political, and social sectors, sometimes written ETPS. The acronym PEST came later, and sources do not agree on who first used it or when.
The variants came as users added what they needed. PESTLE, or PESTEL, adds legal and environmental factors. STEEPLE adds an ethical factor, and some versions add demographics. LoNGPESTLE crosses the six factors with local, national, and global levels, which suits multinational clients. Others exist for specific uses, such as PMESII-PT in military planning and TELOS in project feasibility work. No variant is standard, and the names are generic.
Further reading
- PEST analysis, Wikipedia
A neutral summary of the variants and their components, with the criticism that the framework helps explain past change better than it predicts the future. Use it to settle which variant a client means.
- Scanning the business environment, Open Library
The catalog record for Aguilar's 1967 book, the usual root of the framework. It is a catalog listing and not the text, so you will need a library copy to read it.
Last updated