pestel-analysis
PESTEL Analysis is a systematic framework for evaluating macro-environmental forces, political, economic, social, technological, environmental, and legal, that affect a product or strategy. Use this skill when entering new markets, conducting long-term strategic planning, assessing product viability amid changing conditions, or identifying external risks and opportunities that fall outside your direct control but could materially impact your roadmap or business decisions.
git clone --depth 1 https://github.com/deanpeters/Product-Manager-Skills /tmp/pestel-analysis && cp -r /tmp/pestel-analysis/skills/pestel-analysis ~/.claude/skills/pestel-analysisSKILL.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: ```markdown ## 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: ```markdown ## 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: ```markdown ## 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: ```markdown ## 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: ```markdown ## 4. Technological
Run a structured discovery flow from problem framing through opportunity mapping and validation planning.
Guide PM to Director to VP/CPO transition planning with role-fit diagnostics and onboarding guidance.
Turn strategy and validated opportunities into a sequenced roadmap with clear tradeoffs.
Select what to work on next using the right prioritization method for your context.
Build product strategy from positioning through opportunity and roadmap decisions.
Create a decision-ready PRD by chaining problem framing, requirements definition, and story scaffolding.
Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.
Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.