pestel-analysis

deanpeters/product-manager-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/deanpeters/product-manager-skills --skill pestel-analysis
0 commentsdiscussion
summary

Systematic macro-environmental analysis across political, economic, social, technological, environmental, and legal forces.

  • Structured six-factor framework (PESTEL) for identifying external opportunities and threats that could impact product strategy, market entry, or roadmap decisions
  • Includes step-by-step guidance for scoping analysis, evaluating each factor with specific examples, and synthesizing insights into actionable strategic recommendations
  • Designed for strategic planning h
skill.md

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.

Key Concepts

The PESTEL Framework

Originating from Francis Joseph Aguilar's 1967 PEST analysis, PESTEL extends the framework to six categories:

  1. Political: Government policies, stability, trade regulations, taxation
  2. Economic: Growth rates, inflation, exchange rates, consumer spending
  3. Social: Demographics, cultural trends, lifestyle changes, consumer attitudes
  4. Technological: Advancements, R&D, automation, digital transformation
  5. Environmental: Climate change, sustainability, resource scarcity, regulations
  6. 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 i
how to use pestel-analysis

How to use pestel-analysis on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add pestel-analysis
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/deanpeters/product-manager-skills --skill pestel-analysis

The skills CLI fetches pestel-analysis from GitHub repository deanpeters/product-manager-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/pestel-analysis

Reload or restart Cursor to activate pestel-analysis. Access the skill through slash commands (e.g., /pestel-analysis) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.642 reviews
  • Charlotte Singh· Dec 28, 2024

    pestel-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ganesh Mohane· Dec 16, 2024

    We added pestel-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Arjun Farah· Dec 16, 2024

    pestel-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Dev Singh· Nov 19, 2024

    We added pestel-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 7, 2024

    pestel-analysis reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Alexander Ndlovu· Nov 7, 2024

    Keeps context tight: pestel-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Pratham Ware· Oct 26, 2024

    pestel-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Arjun Flores· Oct 26, 2024

    We added pestel-analysis from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Dev Smith· Oct 10, 2024

    Keeps context tight: pestel-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Harper Singh· Sep 17, 2024

    pestel-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.

showing 1-10 of 42

1 / 5