Home
cd ../playbooks
Product ManagementIntermediate

PESTEL Analysis

Systematic macro-environmental analysis across Political, Economic, Social, Technological, Environmental, and Legal factors — for market entry, strategic planning, and risk assessment.

30 minutes
By communitySource
#pestel#strategy#market-analysis#risk-assessment#planning#external-factors

You're writing next year's strategy, and your only macro frame is "the economy is uncertain." That's not an analysis — that's a vibe. PESTEL forces the six specific forces you control for: is the EU AI Act about to obsolete your product, are exchange rates killing your EU pricing, and is remote work the tailwind you're ignoring?

Who it's for: PMs entering new markets, strategy leads running annual planning, founders pitching to investors, product leaders assessing regulatory risk, teams doing 3-5 year roadmaps

Example

"Run PESTEL for our AI invoice automation launching in EU" → Political (AI Act transparency requirements) + Economic (digital services tax, Euro weakness) + Social (remote freelancer growth) + Tech (LLM advances) + Environmental (B Corp sustainability demand) + Legal (GDPR compliance) → top 3 opportunities, threats, and strategic recommendations

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

Or install from your terminal:
npx ccplaybooks add pestel-analysis
# PESTEL Analysis

Systematic analysis of macro-environmental factors — **Political, Economic, Social, Technological, Environmental, Legal** — that could impact your product or initiative. Identifies external opportunities and threats, informs strategic planning, assesses market entry risks.

Not internal analysis — outward-facing assessment of big-picture forces shaping your product's environment.

## The Framework

From Francis Aguilar (1967 PEST, extended to PESTEL):

1. **Political** — Government policies, stability, trade regulations, taxation
2. **Economic** — Growth rates, inflation, exchange rates, consumer spending

Get new playbooks like this one

One email a week with new Claude Code workflows. Free, like everything here.

No spam. Unsubscribe anytime.

README.md

What This Does

Structured analysis across six external factor categories (Political, Economic, Social, Technological, Environmental, Legal), each with specific prompts, real-world examples, and quality checks. Synthesizes into Top Opportunities, Top Threats, and Strategic Recommendations with actions.

Built on Aguilar's 1967 PEST framework extended to PESTEL. Pairs with recommendation-canvas, positioning-statement, and problem-statement.


Quick Start

mkdir -p ~/Documents/PESTEL
mv ~/Downloads/CLAUDE.md ~/Documents/PESTEL/
cd ~/Documents/PESTEL
claude

Provide product, geographic scope, time horizon, and available market research. Claude walks through all six factors and synthesizes actionable insights.


The Six Factors

Factor Focus Example
Political Policies, stability, trade, taxation EU AI Act transparency requirement
Economic Growth, inflation, exchange, spending Euro weakness vs. Dollar → regional pricing
Social Demographics, culture, lifestyle Remote work boom expands freelancer market
Technological Advancements, R&D, automation LLMs enable better invoice extraction
Environmental Climate, sustainability, resources B Corps prefer carbon-neutral vendors
Legal Compliance, IP, employment, safety GDPR data residency for EU customers

Tips & Best Practices

  • Product-specific, not generic. "EU AI Act requires transparency → our invoice automation must explain recommendations" beats "regulations exist."
  • Cite sources. "SMB sector growing 5% (US Census 2025)" beats "economy strong."
  • Be honest about low-impact factors. If climate change doesn't affect your SaaS, say so — don't force relevance.
  • Synthesize into actions. Long factor lists without "Top Opportunities / Threats / Recommendations" = dead-end analysis.
  • Review annually. PESTEL goes stale as regulations and markets shift.

Common Pitfalls

  • Generic analysis without product-specific impact
  • Forcing relevance where factor has minimal effect
  • No data sources (vague claims, low credibility)
  • Long list of factors with no strategic synthesis
  • Treating it as a one-time exercise

$Related Playbooks

Product Management

Proof of Life Probe Advisor

Pick the right PoL probe (Feasibility, Task-Focused, Narrative, Synthetic Data, Vibe-Coded) based on hypothesis, risk, and timeline — match the cheapest prototype to the harshest truth.

10 minutes
Intermediate
Product Management

Proof of Life (PoL) Probe

Define and document a lightweight, disposable validation artifact designed to surface harsh truths before expensive development — the artifact template that pairs with pol-probe-advisor.

15 minutes
Intermediate
Product Management

Positioning Statement (Geoffrey Moore)

Fill in the For/that need/is a/that + Unlike/provides template from Crossing the Chasm — forces hard choices about target, category, need, and defensible differentiation.

15 minutes
Intermediate
Product Management

Positioning Workshop

Run a structured 5-question discovery (target → need → category → benefit → differentiation) that outputs a Geoffrey Moore positioning statement — not a brainstorm, a forcing function for hard choices.

90 minutes
Intermediate
Product Management

PRD Development

Build a structured PRD that connects problem, users, solution, and success criteria across 8 phases — from scattered Slack threads to engineering-ready document for major initiatives.

2-3 days
Intermediate
Product Management

Press Release (Amazon Working Backwards)

Write a customer-perspective press release before building — Amazon's Working Backwards forcing function for clarity. If you can't write a compelling PR, the idea may be weak.

60 minutes
Intermediate
Product Management

Prioritization Framework Advisor

Pick the right prioritization framework (RICE, ICE, Value/Effort, Kano, Buy-a-Feature) based on product stage, team context, decision needs, and data availability — avoid framework whiplash.

30 minutes
Intermediate
Product Management

Problem Framing Canvas (MITRE)

Run MITRE's three-phase canvas — Look Inward (your biases), Look Outward (who's affected and who's left out), Reframe (problem + How Might We) — to solve the right problem before solutions.

60-90 minutes
Intermediate
Product Management

Problem Statement (User-Centered)

Write an empathy-driven problem statement (I am / Trying to / But / Because / Which makes me feel) that frames product work around user outcomes — not feature requests or business symptoms.

30 minutes
Beginner
Product Management

Product Sense Interview Answer

Six-part spine (clarify → rationale → goal → segmentation → pain → solution) for PM product-sense interviews — sound thoughtful out loud instead of over-scripted on paper.

20-30 minutes per practice answer
Advanced
Product Management

Product Strategy Session

End-to-end product strategy workflow orchestrating positioning, problem framing, discovery, prioritization, and roadmap across 6 phases over 2-4 weeks — with explicit decision points.

2-4 weeks
Advanced
Product Management

Recommendation Canvas (AI Product)

10-component canvas for evaluating AI product proposals — business + customer outcomes, hypothesis with tiny experiments, PESTEL risks, value justification, SMART metrics, and next steps.

90-120 minutes
Advanced

Browse all Product Management playbooks →