pestel-analysis

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

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.

对可能影响你的产品或项目的宏观环境因素——政治、经济、社会、技术、环境和法律（PESTEL）——进行系统性分析。通过此方法识别外部机遇与威胁，为战略规划提供依据，评估市场进入风险，并在不受你控制的大环境背景下，做出基于数据的产品方向决策。

这并非内部分析，而是针对塑造产品所处环境的宏观力量的外部评估。

Key Concepts

核心概念

The PESTEL Framework

PESTEL框架

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

源自Francis Joseph Aguilar于1967年提出的PEST分析，PESTEL将框架扩展至六大类别：

政治因素：政府政策、稳定性、贸易法规、税收政策
经济因素：增长率、通货膨胀、汇率、消费者支出
社会因素：人口统计、文化趋势、生活方式变化、消费者态度
技术因素：技术进步、研发活动、自动化、数字化转型
环境因素：气候变化、可持续性、资源稀缺、相关法规
法律因素：合规要求、知识产权、劳动法、健康与安全法规

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

不是竞品分析：PESTEL关注宏观因素，而非竞争对手
不是内部分析：聚焦外部环境，而非公司的优势/劣势
并非静态分析：宏观环境不断变化——需定期重新评估

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)

进入新市场或新地域
战略规划（年度路线图、3-5年规划）
在环境变化中评估产品可行性
新产品initiative的风险评估
向高管或投资者汇报（展现对环境的认知）

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)

战术性、短期决策（应使用竞品分析）
外部因素稳定且已充分了解的情况
替代客户调研（PESTEL是宏观分析，而非微观分析）

Application

应用方法

Use

template.md

for the full fill-in structure.

使用

template.md

获取完整的填充模板。

Step 1: Define the Scope

步骤1：定义分析范围

Clarify what you're analyzing:

markdown

undefined

明确你要分析的对象：

markdown

undefined

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

---

项目/产品名称： [例如："AI-Powered Invoice Automation for SMBs"]
分析目的： [例如："评估在欧盟市场推出产品的可行性"]
分析人员： [你的姓名或团队]
日期： [分析日期]
地域范围： [例如："美国和欧盟"]
时间范围： [例如："未来12-24个月"]


**质量检查要点：**
- **具体性**：不要写"分析市场"，而要写"评估欧盟市场的产品推出可行性"
- **时效性**：PESTEL因素会变化——明确你的分析时间范围

---

Step 2: Analyze Political Factors

步骤2：分析政治因素

Examine government and regulatory influences:

markdown

undefined

考察政府和监管的影响：

markdown

undefined

1. Political Factors

1. 政治因素

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"]

[政府政策会如何影响产品？]
[示例："欧盟AI法案要求AI决策具备透明度；我们的发票自动化工具必须解释推荐理由"]

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?

---

[分析税收政策及其影响]
[示例："欧盟数字服务税（收入的3%）可能影响定价策略"]


**质量检查要点：**
- **产品针对性**：不要罗列通用政策——要解释对产品的具体影响
- **可操作性**：你能否根据此洞见调整战略？

---

Step 3: Analyze Economic Factors

步骤3：分析经济因素

Examine economic conditions:

markdown

undefined

考察经济状况：

markdown

undefined

2. Economic Factors

2. 经济因素

Economic Growth

经济增长

[Evaluate growth rates and their impact]
[Example: "SMB sector growing 5% annually in US; strong demand for automation tools"]

[评估增长率及其影响]
[示例："美国SMB（中小型企业）领域年增长率5%；对自动化工具需求强劲"]

Inflation Rate

通货膨胀率

[Consider inflation and its effect on pricing/costs]
[Example: "High inflation (6%) pressures SMB budgets; price sensitivity increases"]

[考虑通货膨胀对定价/成本的影响]
[示例："高通胀（6%）给SMB预算带来压力；价格敏感度上升"]

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?

---

[评估消费者支出水平]
[示例："SMB因衰退担忧削减非必要支出；在营销信息中需强调ROI（时间节省）"]


**质量检查要点：**
- **数据驱动**：使用真实的经济指标（GDP增长率、通货膨胀率等）
- **产品针对性**：这些趋势如何影响*你的*产品？

---

Step 4: Analyze Social Factors

步骤4：分析社会因素

Examine societal and cultural trends:

markdown

undefined

考察社会和文化趋势：

markdown

undefined

3. Social Factors

3. 社会因素

Demographics

人口统计

[Examine demographics and market influence]
[Example: "Aging SMB owners (Baby Boomers) less tech-savvy; younger Gen X/Millennial owners more receptive to automation"]

[考察人口统计数据及其对市场的影响]
[示例："SMB所有者老龄化（婴儿潮一代）对技术敏感度较低；年轻的X世代/千禧一代所有者更易接受自动化"]

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"]

[考虑生活方式变化的影响]
[示例："远程工作热潮增加了solo创业者和自由职业者的数量；核心目标市场正在扩大"]

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

---

[评估消费者态度和行为]
[示例："消费者对AI处理常规任务（发票、日程安排）的信任度提升；比5年前的抵触情绪少很多"]


**质量检查要点：**
- **基于趋势**：参考实际的文化转变，而非假设
- **已验证**：使用调研数据、研究报告或人口统计研究结果

---

Step 5: Analyze Technological Factors

步骤5：分析技术因素

Examine technology landscape:

markdown

undefined

考察技术格局：

markdown

undefined

4. Technological Factors

4. 技术因素

Technological Advancements

技术进步

[Identify advancements and their impact]
[Example: "Large language models (LLMs) enable better invoice data extraction; competitive advantage if adopted early"]

[识别技术进步及其影响]
[示例："大语言模型（LLMs）提升了发票数据提取能力；若早期采用可获得竞争优势"]

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"]

[评估自动化的影响]
[示例："竞争对手正在采用AI驱动的自动化；这是市场进入的必备条件——必须匹配或超越"]

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?

---

[考虑数字化转型趋势]
[示例："SMB正在采用云优先工具（QuickBooks Online、Xero）；需要强大的集成能力才能成功"]


**质量检查要点：**
- **竞争背景**：技术格局如何影响你的市场地位？
- **可操作性**：你需要开展哪些研发或合作？

---

Step 6: Analyze Environmental Factors

步骤6：分析环境因素

Examine environmental and sustainability issues:

markdown

undefined

考察环境和可持续性问题：

markdown

undefined

5. Environmental Factors

5. 环境因素

Climate Change

气候变化

[Analyze climate change implications]
[Example: "Minimal direct impact; however, B Corps and sustainability-focused SMBs prefer vendors with carbon-neutral operations"]

[分析气候变化的影响]
[示例："直接影响极小；但B Corp认证企业和关注可持续性的SMB更倾向于选择碳中性运营的供应商"]

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?

---

[考察环境法规]
[示例："欧盟碳边境调节机制（CBAM）对SaaS产品无直接影响"]


**质量检查要点：**
- **如实评估**：如果影响极小，直接说明（不要强行关联）
- **市场定位**：环境因素能否成为差异化优势？

---

Step 7: Analyze Legal Factors

步骤7：分析法律因素

Examine legal and compliance landscape:

markdown

undefined

考察法律与合规格局：

markdown

undefined

6. Legal Factors

6. 法律因素

Compliance Requirements

合规要求

[Identify legal/compliance requirements]
[Example: "GDPR compliance required for EU customers; must implement data residency, right-to-be-forgotten, consent management"]

[识别法律/合规要求]
[示例："欧盟客户需符合GDPR合规要求；必须实施数据本地化、被遗忘权、同意管理等措施"]

Intellectual Property Rights

知识产权

[Evaluate IP importance and protection]
[Example: "Patent landscape for AI invoice processing is crowded; focus on trade secrets over patents"]

[评估知识产权的重要性和保护方式]
[示例："AI发票处理的专利格局拥挤；应聚焦商业秘密而非专利"]

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

步骤8：整合分析洞见

After analyzing all six factors, summarize:

markdown

undefined

完成六大因素的分析后，进行总结：

markdown

undefined

Strategic Insights Summary

战略洞见总结

Top Opportunities:

核心机遇：

[Opportunity 1] - [Description and action]
- [Example: "Social: Remote work boom expands target market → Increase marketing to freelancers"]
[Opportunity 2] - [Description and action]
[Opportunity 3] - [Description and action]

[机遇1] - [描述与行动]
- [示例："社会因素：远程工作热潮扩大了目标市场 → 增加针对自由职业者营销投入"]
[机遇2] - [描述与行动]
[机遇3] - [描述与行动]

Top Threats:

核心威胁：

[Threat 1] - [Description and mitigation]
- [Example: "Economic: Recession fears increase price sensitivity → Emphasize ROI in messaging, offer lower-tier pricing"]
[Threat 2] - [Description and mitigation]
[Threat 3] - [Description and mitigation]

[威胁1] - [描述与缓解措施]
- [示例："经济因素：衰退担忧提升了价格敏感度 → 在营销信息中强调ROI，推出低价层级"]
[威胁2] - [描述与缓解措施]
[威胁3] - [描述与缓解措施]

Strategic Recommendations:

战略建议：

[Recommendation 1] - [Action to take]
[Recommendation 2] - [Action to take]
[Recommendation 3] - [Action to take]

---

[建议1] - [行动方案]
[建议2] - [行动方案]
[建议3] - [行动方案]

---

Step 9: Update Regularly

步骤9：定期更新

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

年度回顾：在战略规划期间重新评估PESTEL因素
触发事件更新：当重大外部事件发生时更新分析（如新法规出台、经济转型等）
追踪变化：记录因素随时间的演变情况

Examples

示例

See

examples/sample.md

for a full PESTEL analysis example.

Mini example excerpt:

markdown

undefined

查看

examples/sample.md

获取完整的PESTEL分析示例。

迷你示例片段：

markdown

undefined

1. Political Factors

1. 政治因素

EU AI Act requires transparency in AI decision-making

欧盟AI法案要求AI决策具备透明度

2. Economic Factors

2. 经济因素

High inflation increases SMB price sensitivity

undefined

高通胀提升了SMB的价格敏感度

undefined

Common Pitfalls

常见误区

Pitfall 1: Generic Analysis

误区1：泛泛而谈的分析

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."

症状："政治因素：存在相关法规。经济因素：经济影响消费。"

后果：无法得出可操作的洞见。

解决方法：具体化："欧盟AI法案要求AI具备可解释性 → 需在2026年第三季度前完成透明度功能开发。"

Pitfall 2: Ignoring Low-Impact Factors

误区2：强行关联低影响因素

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.

症状：强行赋予无关因素相关性（例如："气候变化影响我们的SaaS产品..."）

后果：浪费时间，分散注意力。

解决方法：如果因素影响极小，直接说明。将精力集中在高影响领域。

Pitfall 3: No Data Sources

误区3：无数据支撑

Symptom: "Economic growth is strong" (no citation)

Consequence: Unverifiable claims, low credibility.

Fix: Cite sources: "SMB sector growing 5% annually (US Census Bureau, 2025)."

症状："经济增长强劲"（无引用来源）

后果：主张无法验证，可信度低。

解决方法：引用来源："SMB领域年增长率5%（美国人口普查局，2025年）。"

Pitfall 4: Analysis Without Action

误区4：分析无行动导向

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

误区5：一次性分析

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.).

症状：PESTEL分析仅做一次，后续不再回顾

后果：随着宏观环境变化，洞见会过时。

解决方法：每年回顾一次，或在重大外部事件发生时更新（如新法规出台、经济转型等）。

References

参考资料

Related Skills

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

Francis Joseph Aguilar，Scanning the Business Environment（1967）—— PEST分析的起源
PESTEL（PEST的扩展，加入环境和法律因素）
Michael Porter，Competitive Strategy（1980）—— 与PESTEL互补的行业层面分析框架

Dean's Work

参考来源

PESTEL Analysis Prompt Template (adapted from Aguilar's framework)

PESTEL分析提示模板（改编自Aguilar的框架）

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

改编自

https://github.com/deanpeters/product-manager-prompts

仓库中的

prompts/pestel-analysis-prompt-template.md

。

技能类型： 组件 建议文件名：

pestel-analysis.md

建议存放路径：

/skills/components/

依赖项： 参考

skills/recommendation-canvas/SKILL.md

、

skills/positioning-statement/SKILL.md