environmental-scanning-foresight
$
npx mdskill add lyndonkl/claude/environmental-scanning-foresightScans external trends to forecast futures and trigger early warnings.
- Enables strategic planning through horizon scanning and scenario development.
- Integrates PESTLE frameworks to map macro-environmental forces.
- Validates weak signals before projecting plausible future outcomes.
- Delivers actionable signposts for adaptive organizational responses.
SKILL.md
.github/skills/environmental-scanning-foresightView on GitHub ↗
---
name: environmental-scanning-foresight
description: Monitors external trends across PESTLE dimensions, detects weak signals of emerging change, develops scenario-based futures, and sets adaptive signposts for early warning. Use when scanning external trends for strategic planning, detecting early indicators of change, planning scenarios for multiple futures, setting signposts and indicators for early warning, or when user mentions environmental scanning, horizon scanning, trend analysis, scenario planning, strategic foresight, or futures thinking.
---
# Environmental Scanning & Foresight
## Table of Contents
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)
## Workflow
Copy this checklist and track your progress:
```
Environmental Scanning Progress:
- [ ] Step 1: Define scope and focus areas
- [ ] Step 2: Scan PESTLE forces and trends
- [ ] Step 3: Detect and validate weak signals
- [ ] Step 4: Assess cross-impacts and interactions
- [ ] Step 5: Develop scenarios for plausible futures
- [ ] Step 6: Set signposts and adaptive triggers
```
**Step 1: Define scope and focus areas**
Clarify scanning theme (technology disruption, market evolution, regulatory shift), geographic scope (global, regional, local), time horizon (short 1-2yr, medium 3-5yr, long 5-10yr+), and key uncertainties to explore. See [resources/template.md](resources/template.md#scanning-scope-definition) for scoping framework.
**Step 2: Scan PESTLE forces and trends**
Systematically collect trends across Political, Economic, Social, Technological, Legal, Environmental dimensions. Identify drivers of change (demographics, technology, policy), assess magnitude and direction, and track sources (reports, data, news, expert views). See [resources/template.md](resources/template.md#pestle-scanning-framework) for structured scanning.
**Step 3: Detect and validate weak signals**
Identify early indicators that diverge from mainstream expectations—anomalies, edge cases, emergent behaviors. Validate signal credibility (source quality, supporting evidence, plausibility) and assess potential impact if signal amplifies. See [resources/methodology.md](resources/methodology.md#weak-signal-detection) for detection techniques.
**Step 4: Assess cross-impacts and interactions**
Map how trends interact (reinforcing, offsetting, cascading). Identify critical uncertainties (high impact + high uncertainty) and predetermined elements (high impact + low uncertainty). See [resources/methodology.md](resources/methodology.md#cross-impact-analysis) for interaction mapping.
**Step 5: Develop scenarios for plausible futures**
Create 3-4 distinct, internally consistent scenarios spanning range of outcomes. Build scenarios around critical uncertainties (axes with most impact), develop narrative logic, and test strategies against each scenario. See [resources/template.md](resources/template.md#scenario-development-template) for scenario structure.
**Step 6: Set signposts and adaptive triggers**
Define leading indicators to monitor, set thresholds that trigger strategy adjustment, and establish monitoring cadence (monthly, quarterly, annual). Validate using [resources/evaluators/rubric_environmental_scanning_foresight.json](resources/evaluators/rubric_environmental_scanning_foresight.json). **Minimum standard**: Average score ≥ 3.5.
## Common Patterns
**Pattern 1: Industry Disruption Scanning**
- **Focus**: Technology shifts, business model innovation, competitive dynamics
- **PESTLE emphasis**: Technological (new capabilities), Economic (cost curves), Social (adoption patterns)
- **Weak signals**: Startups with novel approaches, technology breakthroughs in adjacent fields, early adopter behavior
- **Scenarios**: Disruption speed (rapid vs gradual), winning model (incumbent adaptation vs new entrant dominance)
- **Example**: Media industry scanning streaming, AI content generation, attention economy shifts
**Pattern 2: Regulatory & Policy Foresight**
- **Focus**: Government policy, regulatory trends, compliance requirements
- **PESTLE emphasis**: Political (election outcomes, party positions), Legal (regulatory proposals, court decisions)
- **Weak signals**: Pilot programs, stakeholder consultations, legislative drafts in one jurisdiction presaging others
- **Scenarios**: Stringency (light touch vs heavy regulation), speed (gradual vs sudden), scope (sector-specific vs economy-wide)
- **Example**: Finance sector scanning crypto regulation, data privacy laws, central bank digital currencies
**Pattern 3: Market Evolution & Consumer Trends**
- **Focus**: Customer behavior, demand patterns, value shifts
- **PESTLE emphasis**: Social (demographics, values, lifestyle), Economic (income, spending), Technological (enabling platforms)
- **Weak signals**: Subculture behaviors, Gen Z early adoption, influencer/creator economy patterns
- **Scenarios**: Value proposition evolution (what customers prioritize), channel dominance (where they buy), price sensitivity
- **Example**: Retail scanning sustainability values, experiences over ownership, social commerce
**Pattern 4: Geopolitical & Macro Risk Monitoring**
- **Focus**: Political stability, trade relations, conflict risk, economic conditions
- **PESTLE emphasis**: Political (elections, tensions), Economic (growth, inflation, debt), Environmental (climate, resources)
- **Weak signals**: Diplomatic incidents, policy U-turns, capital flows, social unrest indicators
- **Scenarios**: Geopolitical alignment (cooperation vs fragmentation), economic regime (growth vs stagnation), resource availability
- **Example**: Multinational scanning supply chain resilience, tariff risks, energy security
**Pattern 5: Climate & Sustainability Foresight**
- **Focus**: Climate impacts, transition risks, sustainability regulations, stakeholder pressure
- **PESTLE emphasis**: Environmental (physical risks, biodiversity), Political (climate policy), Social (public opinion), Legal (disclosure rules)
- **Weak signals**: Extreme weather anomalies, stranded asset warnings, investor divestment, youth climate activism
- **Scenarios**: Transition speed (orderly vs disorderly), policy stringency (ambitious vs incremental), physical impacts (moderate vs severe)
- **Example**: Energy company scanning net-zero commitments, carbon pricing, renewable cost curves, grid resilience
## Guardrails
**Key requirements:**
1. **Scan systematically across all PESTLE dimensions**: Cover Political, Economic, Social, Technological, Legal, Environmental even if some seem less relevant. Selective scanning creates blind spots, and weak signals often appear in unexpected domains.
2. **Distinguish weak signals from noise**: Weak signals are early indicators with potential impact, not every random anomaly. Validate each signal: Does the source have credibility? Is there supporting evidence? Is amplification plausible? Would the impact be significant if it scales?
3. **Scenarios should be plausible, not preferred or feared**: Scenarios are not predictions or wish fulfillment. They should span the range of outcomes based on critical uncertainties, be internally consistent, and challenge current assumptions. Avoid creating only optimistic scenarios or dystopian extremes.
4. **Focus scenario-building on critical uncertainties**: These have both high impact and high uncertainty. High impact + low uncertainty = predetermined elements (plan for them). High impact + high uncertainty = critical uncertainties (build scenarios around). Low impact = context (note but do not build scenarios around).
5. **Map cross-impacts between trends**: Trends interact: reinforcing trends accelerate (renewable cost decline + climate policy + corporate commitments), offsetting trends create tension (privacy vs personalization), cascading trends trigger others (pandemic to remote work to office demand collapse). Treat trends as interconnected rather than isolated.
6. **Make signposts observable and leading**: Signposts trigger adaptation before the full trend materializes. Leading indicators precede outcomes (building permits before housing prices). Lagging indicators confirm but arrive too late (GDP growth rate). Thresholds should be specific (">20% market share" not "significant adoption") and monitorable (data exists, update frequency known).
7. **Foresight informs strategy without dictating it**: Scenarios reveal possibilities and test strategy robustness, but do not automatically prescribe action. Use scenarios to stress-test plans ("does our strategy work in scenarios A, B, C?") and identify no-regrets moves (work in all scenarios) vs hedges (work in some).
8. **Update scans regularly**: Environmental conditions change. Set scanning cadence (quarterly PESTLE review, monthly weak signal scan, annual scenario update). Foresight is continuous monitoring, not a one-time exercise.
**Common pitfalls:**
- ❌ **Confirmation bias in scanning**: Only collecting evidence supporting existing beliefs. Seek disconfirming evidence, alternate views.
- ❌ **Extrapolating linearly**: Assuming current trends continue unchanged. Consider inflection points, reversals, discontinuities.
- ❌ **Treating scenarios as predictions**: Scenarios are not forecasts. No probabilities assigned (or equal probability). They explore "what if" not "what will".
- ❌ **Too many scenarios (>4)**: Overwhelming decision-makers, diluting focus. Aim for 3-4 distinct scenarios covering key uncertainties.
- ❌ **Ignoring wild cards**: Low-probability, high-impact events (pandemic, breakthrough, collapse). Acknowledge them even if not primary scenarios.
- ❌ **Anchoring to recent past**: Recency bias makes recent events (pandemic, financial crisis) loom large. Consider longer historical patterns.
## Quick Reference
**Key resources:**
- **[resources/template.md](resources/template.md)**: PESTLE scanning framework, weak signal template, scenario development template, signpost definition template
- **[resources/methodology.md](resources/methodology.md)**: Weak signal detection techniques, cross-impact analysis, scenario construction methods, horizon scanning approaches
- **[resources/evaluators/rubric_environmental_scanning_foresight.json](resources/evaluators/rubric_environmental_scanning_foresight.json)**: Quality criteria for scans, scenarios, and signposts
**PESTLE Dimensions:**
- **Political**: Elections, policy priorities, geopolitical tensions, governance shifts
- **Economic**: Growth, inflation, trade, investment, employment, income distribution
- **Social**: Demographics, values, lifestyle, education, health, inequality
- **Technological**: Innovation, digitalization, automation, infrastructure, R&D
- **Legal**: Regulation, standards, liability, IP, compliance requirements
- **Environmental**: Climate, pollution, resources, biodiversity, circular economy
**Time Horizons:**
- **Short-term** (1-2 years): Operational planning, current trend extrapolation, tactical adjustments
- **Medium-term** (3-5 years): Strategic planning, inflection points, scenario planning
- **Long-term** (5-10+ years): Visioning, transformational change, paradigm shifts, wildcards
**Scenario Archetypes:**
- **2x2 Matrix**: Two critical uncertainties create four scenarios (common structure, easy to communicate)
- **Incremental vs Disruptive**: Gradual evolution vs sudden shift
- **Optimistic vs Pessimistic**: Best case vs worst case (with realistic middle)
- **Inside-out vs Outside-in**: Organization-driven vs environment-driven change
**Typical workflow time:**
- PESTLE scan (initial): 4-8 hours (comprehensive literature review, data collection)
- Weak signal detection: 2-4 hours (scanning edge sources, validation)
- Cross-impact analysis: 2-3 hours (mapping interactions, prioritizing)
- Scenario development: 4-6 hours (narrative development, consistency checking)
- Signpost definition: 1-2 hours (indicator selection, threshold setting)
- **Total initial scan**: 15-25 hours
- **Ongoing monitoring**: 2-4 hours/month (depends on cadence and scope)
**When to escalate:**
- Quantitative modeling (system dynamics, agent-based models for complex systems)
- Delphi studies or expert panels (requires facilitation and multi-round synthesis)
- Large-scale scenario workshops (requires professional facilitation)
- Econometric forecasting (requires statistical expertise)
→ Consult professional futurists, scenario planners, or strategic foresight specialists
**Inputs required:**
- **Scanning theme** (what aspect of environment to focus on)
- **Geographic scope** (global, regional, local)
- **Time horizon** (short, medium, long-term)
- **Key uncertainties** (what do we not know that matters most)
**Outputs produced:**
- `environmental-scanning-foresight.md`: PESTLE scan results, weak signals identified, cross-impact analysis, scenarios developed, signposts defined, strategic implications
More from lyndonkl/claude
- abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
- academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
- adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
- adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
- alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
- analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
- answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
- attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
- auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
- auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".