pestel-analysis
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 horizons (12–24 months), not tactical decisions or competitive analysis
- Common pitfalls section covers generic analysis, unsourced claims, and one-time exercises; emphasizes data-driven, product-specific insights with regular reassessment
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:
- 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
More from deanpeters/product-manager-skills
prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
1.7Kuser-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1K