Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-determine/skills/pestel-analysis

pestel-analysis

Verified

Analyze political, economic, social, technological, environmental, and legal forces. Use when external market shifts could materially affect a product, roadmap, or strategy.

FileKindSize
SKILL.mdskill md14.1 KB
examples/sample-lifesciences.mdmarkdown5.0 KB
examples/sample.mdmarkdown5.8 KB
template.mdmarkdown1.5 KB

examples/sample-lifesciences.md

View on GitHub
# PESTEL Analysis Example — Life Sciences

**Brightwater Biologics** runs multi-site clinical trials and builds **Trialpath**, the platform its
coordinators, monitors, and CRO partners use.

**Why this domain changes PESTEL:** in most markets, Legal and Political are background conditions.
Here they are the *product constraints* — they determine what can ship, to whom, and after what
documentation. A PESTEL that treats regulation as context rather than as design input has missed
the point.

---

```markdown
## PESTEL Analysis: Trialpath — Clinical Trial Operations Platform

### Political
- Public funding priorities for clinical research shift with administrations, moving trial
  volume between therapeutic areas on a multi-year lag
- Cross-border data movement between trial sites is increasingly politically contested,
  independent of the legal frameworks that formalize it
- **So what:** trial volume by therapeutic area is not something we forecast well. Platform
  design should be therapeutic-area agnostic, and we should resist optimizing for the mix
  we happen to serve today

### Economic
- Small-sponsor funding is rate-sensitive; a tightening cycle thins the segment we identified
  as our best fit
- Site staffing costs rise faster than trial budgets, pushing sponsors toward
  coordinator-efficiency tools
- CRO consolidation concentrates buying power in fewer, larger organizations
- **So what:** our target segment shrinks in exactly the conditions that make our value
  proposition strongest. Plan for a smaller, more motivated market rather than a growing one

### Social
- Coordinator turnover at sites runs high, so institutional knowledge leaves regularly
- Patient expectations around participation convenience are rising, pushing decentralized
  and hybrid trial designs
- Trust in clinical research varies sharply by community, affecting recruitment
- **So what:** high turnover makes "learnable in a day" a durable requirement, not a nice-to-have.
  Any design that assumes an experienced coordinator degrades within a year

### Technological
- Electronic data capture is table stakes; differentiation has moved to workflow and integration
- AI-assisted document review is maturing, with unresolved questions about its acceptability
  in regulated submissions
- Decentralized trial tooling is fragmenting into many point solutions
- **So what:** the AI opportunity is real and the acceptability question is unanswered. Build
  where AI assists a human who remains accountable; avoid anything that would need to be
  defended as an autonomous decision in a submission

### Environmental
- Site travel for monitoring visits is a growing reporting concern for large sponsors
- Sustainability reporting is entering vendor selection for enterprise buyers
- **So what:** remote monitoring capability has a second, non-obvious buyer rationale.
  Low priority for our current segment, rising for the segment above it

### Legal
- Regulatory expectations for computerized systems in trials require validation
  documentation from the vendor, not just the user
- Data protection regimes differ by jurisdiction and by trial, and both apply simultaneously
- Audit trail requirements are non-negotiable and shape data model decisions
- **So what:** **this is the gating category.** Vendor-grade validation documentation is the
  entry ticket to selling at all — it is not a compliance task that follows a product decision,
  it IS the product decision. Audit trail requirements constrain the data model before a
  single feature is designed
```

---

## Assumptions this analysis exposed

- **We assumed our best segment was growing.** Economic analysis says it thins under exactly the
  conditions that make us most valuable. That reframes the opportunity from "growth market" to
  "small motivated market" — which changes what a sensible investment looks like.
- **We assumed AI document review was a roadmap question.** It's an acceptability question first,
  and nobody has answered it. Building AI that assists an accountable human is safe; building AI
  that decides is a bet on a regulatory position that doesn't exist yet.
- **We assumed validation documentation was a compliance workstream.** It's the gate. This single
  finding reordered the roadmap.

---

## Why Legal carries the analysis here

In most PESTEL work, Legal is a paragraph acknowledging that laws exist. Here it produced the
constraint that determined the product's sequencing, its data model, and whether the business is
viable at all.

**The tell that you've done this right in a regulated domain:** at least one "so what" should
change something already on your roadmap. If every conclusion is "keep monitoring," you've written
a description of the industry rather than an analysis of your position in it.

**The trap on the other side:** treating every regulation as a blocker. Environmental here is
honestly low-priority for the current segment, and saying so is more useful than manufacturing
urgency to make the section feel complete. A PESTEL where all six categories are equally critical
is a PESTEL that hasn't prioritized.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall