Purpose
Conduct a systematic analysis of macro-environmental factors—Political, Economic, Social, Technological, Environmental, and Legal—that could impact your product or project. Use this to identify external opportunities and threats, inform strategic planning, assess market entry risks, and make data-driven decisions about product direction in the context of broader forces beyond your control.
This is not internal analysis—it's outward-facing assessment of the big-picture forces shaping your product's environment.
Input
Works best with: The product, market, or strategic decision the analysis should serve.
Also useful: Geography, time horizon, and which forces you already suspect matter most.
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill asks what product/market and geography to analyze before scanning the six forces — an unanchored PESTEL is a trivia exercise.
Example invocation: PESTEL for launching our telehealth platform in Germany over the next 18 months.
Key Concepts
The PESTEL Framework
Originating from Francis Joseph Aguilar's 1967 PEST analysis, PESTEL extends the framework to six categories:
- Political: Government policies, stability, trade regulations, taxation
- Economic: Growth rates, inflation, exchange rates, consumer spending
- Social: Demographics, cultural trends, lifestyle changes, consumer attitudes
- Technological: Advancements, R&D, automation, digital transformation
- Environmental: Climate change, sustainability, resource scarcity, regulations
- Legal: Compliance, IP rights, employment laws, health/safety regulations
Why This Works
- Comprehensive: Covers all major external forces affecting your product
- Proactive: Identifies threats and opportunities before they become critical
- Strategic: Informs long-term planning, not just tactical decisions
- Risk management: Highlights vulnerabilities in your product strategy
Anti-Patterns (What This Is NOT)
- Not competitive analysis: PESTEL looks at macro factors, not competitors
- Not internal analysis: Focuses on external environment, not your company's strengths/weaknesses
- Not static: Macro environment changes—reassess regularly
When to Use This
- Entering a new market or geography
- Strategic planning (annual roadmapping, 3-5 year planning)
- Assessing product viability in a changing environment
- Risk assessment for new product initiatives
- Pitching to execs or investors (shows environmental awareness)
When NOT to Use This
- For tactical, short-term decisions (use competitive analysis instead)
- When external factors are stable and well-understood
- As a substitute for customer research (PESTEL is macro, not micro)
Application
Use template.md for the full fill-in structure.
Step 1: Define the Scope
Clarify what you're analyzing:
## Overview
- **Project/Product Name:** [e.g., "AI-Powered Invoice Automation for SMBs"]
- **Analysis Purpose:** [e.g., "Assess viability of launching in EU market"]
- **Analyst:** [Your name or team]
- **Date:** [Date of analysis]
- **Geographic Scope:** [e.g., "United States and European Union"]
- **Time Horizon:** [e.g., "Next 12-24 months"]
Quality checks:
- Specific: Not "analyze market" but "assess viability of EU launch"
- Time-bound: PESTEL factors change—state your horizon
Step 2: Analyze Political Factors
Examine government and regulatory influences:
## 1. Political Factors
### Government Policies
- [How could government policies impact the product?]
- [Example: "EU's AI Act requires transparency in AI decision-making; our invoice automation must explain recommendations"]
### Political Stability
- [Assess stability in relevant regions]
- [Example: "US political stability is moderate; potential for regulatory changes in financial tech under new administration"]
### Trade Regulations
- [Examine trade regulations and their effects]
- [Example: "Brexit complicates data transfer between UK and EU; may require separate infrastructure"]
### Taxation Policy
- [Analyze taxation policies and implications]
- [Example: "Digital services tax in EU (3% on revenue) could impact pricing strategy"]
Quality checks:
- Specific to your product: Don't list generic policies—explain the impact
- Actionable: Can you adjust strategy based on this insight?
Step 3: Analyze Economic Factors
Examine economic conditions:
## 2. Economic Factors
### Economic Growth
- [Evaluate growth rates and their impact]
- [Example: "SMB sector growing 5% annually in US; strong demand for automation tools"]
### Inflation Rate
- [Consider inflation and its effect on pricing/costs]
- [Example: "High inflation (6%) pressures SMB budgets; price sensitivity increases"]
### Exchange Rates
- [Analyze exchange rate fluctuations]
- [Example: "Weak Euro vs. Dollar makes US pricing less competitive in EU; may need regional pricing"]
### Consumer Spending
- [Assess consumer spending levels]
- [Example: "SMBs cutting discretionary spending due to recession fears; emphasize ROI (time savings) in messaging"]
Quality checks:
- Data-driven: Use real economic indicators (GDP growth, inflation rates, etc.)
- Product-specific: How do these trends affect your product?
Step 4: Analyze Social Factors
Examine societal and cultural trends:
## 3. Social Factors
### Demographics
- [Examine demographics and market influence]
- [Example: "Aging SMB owners (Baby Boomers) less tech-savvy; younger Gen X/Millennial owners more receptive to automation"]
### Cultural Trends
- [Analyze cultural trends and demand impact]
- [Example: "Growing 'hustle culture' among freelancers increases demand for time-saving tools"]
### Lifestyle Changes
- [Consider lifestyle changes and implications]
- [Example: "Remote work boom increases solo entrepreneurs and freelancers; core target market expanding"]
### Consumer Attitudes
- [Assess consumer attitudes and behaviors]
- [Example: "Increasing trust in AI for routine tasks (invoicing, scheduling); less resistance than 5 years ago"]
Quality checks:
- Trend-based: Reference actual cultural shifts, not assumptions
- Validated: Use survey data, research reports, or demographic studies
Step 5: Analyze Technological Factors
Examine technology landscape:
## 4. Technological Factors
### Technological Advancements
- [Identify advancements and their impact]
- [Example: "Large language models (LLMs) enable better invoice data extraction; competitive advantage if adopted early"]
### R&D Activity
- [Evaluate sector R&D levels]
- [Example: "High R&D investment in fintech automation; rapid innovation cycle—need to iterate fast"]
### Automation
- [Assess automation implications]
- [Example: "Competitors adopting AI-powered automation; table stakes for market entry—must match or exceed"]
### Digital Transformation
- [Consider digital transformation trends]
- [Example: "SMBs adopting cloud-first tools (QuickBooks Online, Xero); need strong integrations to succeed"]
Quality checks:
- Competitive context: How does the tech landscape affect your position?
- Actionable: What R&D or partnerships do you need?
Step 6: Analyze Environmental Factors
Examine environmental and sustainability issues:
## 5. Environmental Factors
### Climate Change
- [Analyze climate change implications]
- [Example: "Minimal direct impact; however, B Corps and sustainability-focused SMBs prefer vendors with carbon-neutral operations"]
### Sustainability Practices
- [Evaluate sustainability impact]
- [Example: "Growing demand for 'green tech'; marketing opportunity to highlight cloud efficiency vs. on-prem servers"]
### Resource Scarcity
- [Assess resource scarcity risks]
- [Example: "Low risk; software product doesn't depend on physical resources"]
### Environmental Regulations
- [Examine environmental regulations]
- [Example: "EU's Carbon Border Adjustment Mechanism (CBAM) doesn't affect SaaS directly"]
Quality checks:
- Honest assessment: If impact is minimal, say so (don't force relevance)
- Market positioning: Can environmental factors be a differentiator?
Step 7: Analyze Legal Factors
Examine legal and compliance landscape:
## 6. Legal Factors
### Compliance Requirements
- [Identify legal/compliance requirements]
- [Example: "GDPR compliance required for EU customers; must implement data residency, right-to-be-forgotten, consent management"]
### Intellectual Property Rights
- [Evaluate IP importance and protection]
- [Example: "Patent landscape for AI invoice processing is crowded; focus on trade secrets over patents"]
### Employment Laws
- [Consider employment laws and implications]
- [Example: "Remote hiring across EU requires understanding of local labor laws (Germany, France have strict employment contracts)"]
### Health and Safety Regulations
- [Assess health/safety regulations]
- [Example: "Not applicable (software product)"]
Quality checks:
- Legal risk assessment: What could block or delay your product?
- Compliance costs: Budget for legal, data residency, certifications?
Step 8: Synthesize Insights
After analyzing all six factors, summarize:
## Strategic Insights Summary
### Top Opportunities:
1. **[Opportunity 1]** - [Description and action]
- [Example: "Social: Remote work boom expands target market → Increase marketing to freelancers"]
2. **[Opportunity 2]** - [Description and action]
3. **[Opportunity 3]** - [Description and action]
### Top Threats:
1. **[Threat 1]** - [Description and mitigation]
- [Example: "Economic: Recession fears increase price sensitivity → Emphasize ROI in messaging, offer lower-tier pricing"]
2. **[Threat 2]** - [Description and mitigation]
3. **[Threat 3]** - [Description and mitigation]
### Strategic Recommendations:
1. **[Recommendation 1]** - [Action to take]
2. **[Recommendation 2]** - [Action to take]
3. **[Recommendation 3]** - [Action to take]
Step 9: Update Regularly
- Annual review: Reassess PESTEL factors during strategic planning
- Trigger events: Update when major external events occur (new regulations, economic shifts, etc.)
- Track changes: Document how factors evolve over time
Examples
See examples/sample.md for a full PESTEL analysis example.
Mini example excerpt:
### 1. Political Factors
- EU AI Act requires transparency in AI decision-making
### 2. Economic Factors
- High inflation increases SMB price sensitivity
Common Pitfalls
Pitfall 1: Generic Analysis
Symptom: "Political: Regulations exist. Economic: Economy affects spending."
Consequence: No actionable insights.
Fix: Be specific: "EU AI Act requires explainable AI → Need transparency features by Q3 2026."
Pitfall 2: Ignoring Low-Impact Factors
Symptom: Forcing relevance where none exists (e.g., "Climate change affects our SaaS product...")
Consequence: Wastes time, dilutes focus.
Fix: If a factor has low impact, say so. Focus effort on high-impact areas.
Pitfall 3: No Data Sources
Symptom: "Economic growth is strong" (no citation)
Consequence: Unverifiable claims, low credibility.
Fix: Cite sources: "SMB sector growing 5% annually (US Census Bureau, 2025)."
Pitfall 4: Analysis Without Action
Symptom: Long list of factors, no strategic recommendations
Consequence: Insights don't inform decisions.
Fix: Synthesize into "Top Opportunities," "Top Threats," and "Strategic Recommendations."
Pitfall 5: One-Time Exercise
Symptom: PESTEL analysis done once, never revisited
Consequence: Stale insights as macro environment shifts.
Fix: Review annually or when major external events occur (new regulations, economic shifts, etc.).
References
Related Skills
skills/recommendation-canvas/SKILL.md — PESTEL factors inform risk assessment in canvasskills/positioning-statement/SKILL.md — PESTEL insights shape competitive positioningskills/problem-statement/SKILL.md — Social/economic factors influence customer problems
External Frameworks
- Francis Joseph Aguilar, Scanning the Business Environment (1967) — Origin of PEST analysis
- PESTEL (extension of PEST to include Environmental and Legal)
- Michael Porter, Competitive Strategy (1980) — Complements PESTEL with industry-level analysis
Dean's Work
- PESTEL Analysis Prompt Template (adapted from Aguilar's framework)
Provenance
- Adapted from
prompts/pestel-analysis-prompt-template.md in the https://github.com/deanpeters/product-manager-prompts repo.
Skill type: Component
Suggested filename: pestel-analysis.md
Suggested placement: /skills/components/
Dependencies: References skills/recommendation-canvas/SKILL.md, skills/positioning-statement/SKILL.md
