PESTLE Analysis

A General Manager hired from consumer tech into healthcare services, 10 weeks into the role. The board brought them in for operational efficiency, but early decisions keep hitting regulatory and compliance friction they didn't anticipate. The client frames the problem as 'this organization moves too slowly' - they haven't yet considered that the environment itself constrains speed differently than their previous industry.

Frame this as orientation, not strategy work. 'You keep running into walls you didn't expect. Before we build your 90-day plan, let's map the walls.' The resistance here is impatience - the client wants to act, not analyze. Name it directly: 'I know this feels like slowing down. It is. Fifteen minutes now will save you weeks of building plans that run into barriers you could have seen.' Position the PESTLE specifically as an industry translation exercise: 'You know consumer tech cold. This maps what's different about where you are now.'

The Technological column will fill fast and with high confidence - that's the client's home territory. Watch the Legal and Political columns. If the entries are vague ('healthcare regulations,' 'government oversight'), the client is working from assumptions, not knowledge. Genuine engagement looks like naming specific regulations, pending legislation, or agency actions. If the client fills Economic with consumer-tech market dynamics instead of healthcare economics, they're still mapping their old industry onto the new one.

Start with the column that took the longest. Not 'what was hard?' - that invites rationalization. Instead: 'Read me what you wrote in Legal.' Listen for specificity. Then ask: 'Who on your team could fill this column in five minutes?' That question shifts from 'I don't know this' to 'I haven't built the right information channels yet.' Follow with the cross-column connections: 'Where does a Political entry create a Legal constraint that changes what's possible in Technology?'

A CEO of a mid-market manufacturing company, coaching engagement focused on scaling the business. The client is experienced, articulate, and confident in their environmental read. They complete all six PESTLE columns quickly and thoroughly - no hesitation, no sparse areas. The completed tool looks textbook-perfect, which is the problem.

This client won't resist the tool. They'll comply efficiently and produce something that looks complete. The framing needs to pre-empt that: 'I want you to do this exercise, but with a constraint. For each entry, write one thing your board would agree with, and one thing your board would push back on. I want the entries that make you uncomfortable, not just the ones you'd put in a strategy deck.' If the client asks why, be direct: 'You know your environment well. I want to find the places where your confidence might be covering a blind spot.'

Speed and uniformity are the signals. If all six columns have 4-5 entries each, written in similar language, at similar specificity - the client is producing from a well-rehearsed mental model. That model may be accurate, but it's not generating new information. Look for absent entries: no mention of workforce demographic shifts in Social, no mention of supply chain environmental regulations, no mention of emerging competitors from adjacent technology. The tell is not what's wrong - it's what's missing that someone in this industry should be tracking.

Do not start with the content. Start with the process. 'You filled this in fast. When was the last time one of these factors actually surprised you?' If the answer is 'it's been a while,' that's the conversation. Then go to each column and ask: 'What would your newest board member add to this column?' or 'What would your head of operations add that you didn't?' The goal is to surface what the CEO's seniority filters out - the signals that reach other levels of the organization but not the top.

A VP of Strategy at a financial services firm, in coaching because the CEO questioned the rigor of their last strategic plan. The client is competent and data-driven but has been producing strategy documents that over-index on Economic and Technological factors because those are what the executive committee responds to. The client expects this exercise to confirm their thoroughness.

Position the PESTLE as a completeness check, not a new framework. 'You build strategy documents for a living. This isn't teaching you something new - it's testing whether the inputs you're using cover the full field.' The resistance will come after completion, not during. When the Social, Environmental, and possibly Political columns turn out sparse, the client's instinct will be to explain why those factors are less relevant to financial services. Pre-frame: 'Some columns will fill faster than others. The interesting part isn't what you know - it's comparing where you spend attention against where you don't.'

The Economic and Technological columns will be dense and specific - these are the client's professional territory. Watch the Social column: if 'workforce expectations' is absent or treated as an HR issue rather than a strategic input, the client is segmenting topics by department rather than by impact. Watch Environmental: financial services leaders often assume this column is irrelevant to their industry. If the entry is blank or says 'not applicable,' that's where the coaching conversation lives - ESG regulation, climate risk in lending portfolios, and carbon disclosure requirements are reshaping financial services.

Put the completed tool next to the client's most recent strategic plan (or its table of contents). Ask: 'Which of these PESTLE factors appear in your strategy document, and which don't?' Let the client make the comparison themselves. Then: 'If you added the missing factors, which one would change a recommendation in your current plan?' This moves from abstract completeness to concrete strategic impact. The question that typically creates movement: 'If your CEO did this exercise independently, where would your columns differ from theirs?'

A startup founder (Series A, 85 employees) preparing for a Series B raise in the next 6 months. The coaching engagement is focused on executive presence and investor readiness. The founder is strong on product and technology but has been caught off-guard in investor conversations by questions about regulatory risk, labor market shifts, and macroeconomic headwinds. The client wants to 'not look stupid' in the next round of meetings.

Frame as investor preparation, not strategic planning. 'Investors will probe exactly the areas where you're least prepared. This exercise maps those areas before they do.' The founder's resistance will be scope: 'I don't have time for a full environmental scan, I need to focus on the product.' Address that head-on: 'This isn't about becoming an expert in trade policy. It's about knowing enough to answer the question instead of deflecting it. Thirty minutes now will change how you show up in those rooms.' The PESTLE is useful here because it gives the founder a structured vocabulary for topics they currently handle ad hoc.

The Technological column will be over-specified - the founder will write their product roadmap into it rather than external technology trends. That's telling: the client sees technology as something they build, not something that happens to them. In Political and Legal, watch for the difference between 'I know this is a risk' and 'I know the specific regulation.' Vague entries like 'data privacy laws' signal that the founder has heard the phrase but hasn't done the reading. Genuine preparation looks like naming specific bills, enforcement actions, or regulatory bodies.

Start with the columns that have one or two entries. 'An investor asks you about political risk to your business. Read me your answer from what you wrote.' If the client can't expand beyond what's on the page, the exercise exposed the gap it was meant to expose. Then shift to cross-column: 'Which of these factors, if it changed in the next 18 months, would affect your unit economics?' This is the question investors actually ask, reframed through the PESTLE output. The founder needs to leave the session with 3-4 factors they can speak to fluently, not mastery of all six columns.

A division president at a large industrial company, 4 years in role. Coaching engagement was initiated by the CHRO after a 360 flagged 'strategic myopia' - the leader's team describes them as operationally excellent but disconnected from market shifts. The client doesn't agree with the 360 feedback and frames the problem as 'my team doesn't understand how I think about strategy.'

Do not frame this as addressing the 360 feedback - the client will defend against that framing immediately. Instead: 'Before we look at the 360 data, I want a baseline. Map the external factors that are shaping your division's next 18 months.' The tool becomes a mirror the client builds themselves, before any external feedback enters the conversation. If the client asks what this has to do with the 360, redirect: 'We'll get there. First I want to see how you read the environment right now, in your own terms.'

The diagnostic signal is whether the entries describe current conditions or describe the conditions from when the client first took the role. A leader who has stopped scanning externally will write entries that were accurate 2-3 years ago but miss recent shifts. Compare what's written against what's happened in their industry recently: if major regulatory changes, market entrants, or technology disruptions are absent, the client's environmental model is frozen. Also watch for entries that are actually internal operational items disguised as external factors ('need to upgrade our ERP system' in the Technology column instead of 'AI-driven predictive maintenance adopted by 3 of our 5 competitors').

Start by asking: 'When did each of these entries become relevant to your business?' If most answers are 'a couple of years ago' or 'it's always been true,' that's the data point. Then: 'What changed in your industry in the last 12 months that isn't on this page?' The gap between the PESTLE output and recent industry shifts becomes a concrete, non-defensive way to show the client what their 360 raters are seeing. The client didn't stop being strategic - they stopped updating their inputs. That reframe moves from character ('you're myopic') to behavior ('your scanning frequency dropped').