By 6days · v1.0 · Updated 7/20/2026
Scan the six external forces that will shape your market whether or not you act.
Fill this in for your own situation — a private worksheet only you can see.
When to use
Use it when entering an unfamiliar market or geography, when setting strategy over a multi-year horizon, or when a business is heavily exposed to regulation, commodity prices, or public sentiment. It pairs naturally with a competitive analysis, which handles the forces PESTEL deliberately ignores.
When not to use
Avoid it for operational or short-horizon decisions, where macro forces move too slowly to matter and the exercise becomes theatre. It also has no opinion about your competitors, your customers, or your own capabilities — mistaking a completed PESTEL for a strategy is the standard failure.
Organisations are fluent about competitors and customers and largely silent about the wider environment those competitors and customers live in. Then a regulation lands, a currency moves, or a social expectation shifts, and a strategy that looked sound is suddenly answering last year's question. The failure is rarely analytical ability; it is that nobody was assigned to look outward in a systematic way.
PESTEL walks the macro-environment through six lenses: political, economic, social, technological, environmental, and legal. Each lens is a prompt to ask what is changing outside your control that could alter the value of what you are building. The point is not to fill six boxes but to force attention onto categories a team would otherwise skip — most groups are comfortable with technology and economics and quietly ignore the social and environmental columns until those columns produce a crisis.
Framework by 6days on 6days — https://6days.apexaion.ai/framework/pestel-analysis
Scope the scan to a specific market and period. Macro forces are only meaningful relative to a horizon: an interest-rate move matters enormously to an eighteen-month plan and barely registers against a ten-year one.
Under each of the six headings, record what is changing rather than what is true. 'Data protection law exists' is a condition and helps nobody. 'Enforcement of cross-border data transfer rules is tightening, with the first fines expected next year' is a change you can plan against.
Most of what you record will not matter to you. Keep only the forces that would plausibly change a decision you are about to make, and discard the rest without ceremony. An unfiltered PESTEL is a reading list, not an analysis.
For each surviving force, ask how likely it is within the horizon and how hard it would hit. This separates the genuinely urgent from the merely interesting, and it is the step that converts a scan into a prioritised watch list.
For each material force, name someone accountable for watching it and state the observable event that would make you act. A force nobody owns is a force nobody will notice moving.
Worked example
A payments company assesses expansion into a new country. Political: a stable government with an explicit fintech agenda. Economic: high inflation compressing consumer spending. Social: rapid adoption of mobile wallets among under-35s. Technological: a national instant-payment rail launching next year. Environmental: negligible. Legal: a licensing regime requiring a local entity and capital reserves. The filter leaves two things that actually decide the question — the licensing cost and the payment rail's timing — and the expansion case is rebuilt around those rather than around the optimistic social trend that first attracted attention.
The framework grew by accretion rather than invention. Environmental-scanning checklists circulated in strategic planning literature from the 1960s onward under several acronyms, with letters added over time as environmental and legal factors gained prominence. No single originator is credibly identified, and the six-letter form is best understood as a convention that settled through use.
Related ways to think about this.
Sort what you know about a decision into four buckets so the gaps become obvious.
Use when Use it early, when a group needs to pool what it collectively knows before choosing a direction — entering a market, responding to a competitor, or opening annual planning. It is most valuable when the people in the room hold different pieces of the picture and have never assembled them in one place.
Avoid when Avoid it when you need a decision rather than an inventory: SWOT ranks nothing and will not tell you what to do. It rewards confident assertion, so it degrades badly in rooms with a strong seniority gradient. And it is a snapshot — for anything fast-moving it dates quickly, and a stale SWOT presented as current is worse than none.
Explain why an industry is profitable — or isn't — before you commit to competing in it.
Use when Use it before entering an industry, before a major capital commitment, or when strong execution is somehow producing weak margins and you need to know whether the problem is you or the structure you are operating inside.
Avoid when Avoid it for short-term or tactical calls — it describes structure, which moves over years. It fits industries with recognisable boundaries better than fluid ecosystems and platforms, where roles blur and today's supplier is next year's competitor. It also says nothing about your own capabilities, and it is a snapshot of a structure that will keep moving after you present it.
Compete somewhere else: redraw the offer so the current rivalry stops being the question.
Use when Use it in a commoditised market where competitors are near-indistinguishable and margins are eroding, or when a large population plainly declines to buy from anyone in the category and you want to know why.
Avoid when Avoid it in a young market where the rules are not yet settled — there is no convergence to escape. Be wary of it as a rationalisation: 'we compete differently' is the most comfortable thing a losing company can tell itself, and the framework supplies attractive language for it. The literature also selects heavily on winners, so the base rate for this working is far lower than the case studies imply.