PESTEL Analysis

Ask a strategy meeting what is happening outside the company and the answer almost always comes back as competitor news. Everyone in the room knows who shipped which feature and who raised how much. But competitors are frequently not what shakes a company. Interest rates climb and customers cut the software line of the budget first. A privacy rule changes and suddenly the contract asks which country the data sits in. Neither had ever come up in the meeting.

The reason they go missing is that people watch their own patch and no further. Sales tracks competitor pricing, engineering tracks where the technology is going, the founder tracks the funding market. Whatever nobody is assigned to sits quietly empty until it turns into an incident. The pattern repeats: a deal falls through, someone asks why, and the account owner says the rule was never part of their remit — which is true, so there is nobody to blame.

PESTEL analysis is a device for creating those empty boxes in advance. Rather than leaving the choice of what to watch to whoever happens to be curious, it writes down six categories first and asks for at least one line in each. It is not a tool for watching competitors but for checking whether the board the competition is played on has started to move.

Open each of the six letters, write down the changes that belong there, keep only the ones that reach the business, and attach an action to those.

1. Fix the scope before anything else. Set it as wide as "our company" and every box fills with global macroeconomics. Something like "team document collaboration in Korea, the next two years" pins down a market and a time horizon.
2. Fill the six boxes. Each one covers a specific kind of change.
   • Political — elections, public procurement policy, industry subsidies: anything that shifts because a government decided something.
   • Economic — interest rates, exchange rates, the business cycle, labor costs. This is the box where your customers' budgets grow or shrink.
   • Social — population structure, how people work, what they want to buy. More remote work pulls demand for collaboration tools along with it.
   • Technological — capabilities that have just become available, and the competitors already using them. Document summarization turning into a default feature through generative AI belongs here.
   • Environmental — climate, energy costs, carbon rules. At a software company this usually narrows to server power draw and reporting obligations.
   • Legal — the laws covering privacy, employment, contracts and advertising, plus amendments to them. Rules that carry fines for a breach, such as Korea's Personal Information Protection Act (PIPA), are the typical entries.
3. Cut the list down. Score every line twice — size of effect and likelihood — as high, medium or low, and keep only the lines that score high on both. Write twenty-five lines and two or three usually survive.
4. Attach an action to what survives. Separate what you are working on now from what you are only watching, and for the watched ones write down what you would have to see before you moved. A trigger like "once the amendment reaches the legislature" lets the next person make the call.
5. Set a date to do it again — every six or twelve months, timed so the output arrives as an input to the meeting that sets strategic priorities.

The two places this fits best are deciding whether to enter a new market and the weeks before annual planning. Both have a horizon longer than a year, and both flip if outside conditions change. Moving into a tightly regulated area such as healthcare or finance raises the stakes, because the legal box alone can settle whether entry is possible. It does nothing for deciding which feature goes into this sprint or what the next price increase should be. The changes it deals with move more slowly than a quarter.

There are three real limits. The first is that it easily ends as a list and nothing more. Fill six boxes conscientiously and you get a thirty-line document; skip the cutting in step 3 and it changes no decision, then gets copied next year with a new date. The second is that it is not a forecast. It will tell you that privacy regulation is tightening, but not when that tightening turns into a clause in a contract. Items like regulatory risk, where the direction is readable and the timing is not, get handled by preparing a response rather than predicting a date. The third is that filling the boxes alone produces only what you already know; sales and legal have to be in the same room before an empty box shows up as empty.

You also don't have to force every box. At a forty-five person software company the environmental box is usually blank or one line long, and leaving it blank beats inventing something.

"We ran a full PESTEL and the only real risk was in the L box. Everything else we just watch."

All six boxes got filled, but the list of things needing a response narrowed to the legal one.

"That's competitor movement, not an outside condition, so it doesn't belong in this table."

Sending an item back because the competitive structure calls for a different framework.

"The cross-border transfer clause we parked in last year's PESTEL is now sitting in our enterprise contracts."

An item classified as watch-only has turned into a revenue condition.

At Pagedeck, Grace runs one two weeks before annual planning. Sofia puts the conditions she keeps getting asked for in public sector bids into the political box, Theo puts the shift toward document summarization as a default competitor feature into the technological box, and Grace adds a pending privacy amendment to the legal box. Twenty-three lines came in and three survived the filter. One of the three — whether customer data can be kept in the country — became a condition of that year's enterprise contracts. It had never appeared on a competitor comparison sheet, and the response took two quarters.

The most common mistake is treating a filled set of boxes as a finished analysis. The framework is made of boxes, so a full set naturally looks like a completed job. But filling is collection and analysis is cutting. If nobody decides what to do with the thirty lines, no one opens the document again, and next year it comes back with only the date changed.

Almost as common is the idea that this belongs to large companies. Words like political and economic sound distant from a forty-five person team. In practice the small company is the one that gets knocked over by a single rule, because with no dedicated legal staff one requirement swallows a whole quarter of the roadmap. Skip the exercise and you learn the board has moved only after you lose the deal.