deanpeters/Product-Manager-Skills / skills/swot-analysis
swot-analysis
VerifiedBuild an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.0 KB |
| examples/sample-industrial.md | markdown | 5.9 KB |
| examples/sample.md | markdown | 5.8 KB |
| template.md | markdown | 2.2 KB |
examples/sample-industrial.md
View on GitHub# Evidence-Cited SWOT — Worked Example (Industrial)
All companies, products, URLs, and figures are **fictional**. Industrial sibling of
[`sample.md`](sample.md): Northfield Automation SWOTs **Helix Motion Systems** ahead of the 2027
channel-strategy decision. The industrial evidence base differs from the SaaS sibling's — filings
and registries carry the weight that review sites carry in SaaS, and the "customer voice" for
weaknesses comes from distributor and integrator channels rather than app stores.
**Invocation:** `Evidence-cited SWOT on Helix Motion Systems, whole company, from Northfield's
perspective — supports the 2027 integrator-channel strategy. Snapshot and watch report in session.`
---
# SWOT: Helix Motion Systems (whole company)
**As-of date:** 2026-11-12
**Decision supported:** Northfield's 2027 integrator-channel strategy
**Perspective:** Northfield Automation, competing with them
## 1. Strengths (internal, evidenced)
- Installed base as a moat: their components sit in a majority of target plants, per market-share disclosures — **Fact** ([annual filing](https://example.com/helix/10k)) — ranked #1: it's the asset Foresight monetizes and the reason every retrofit conversation starts with their nameplate
- Distributor and certified-service network built over decades — **Fact** ([partner directory](https://example.com/helix/partners)); service attach praised in trade-press plant profiles — **Fact** ([trade article](https://example.com/tradepress/helix-service))
- Aftermarket & services margin engine — segment reporting shows it outearning new-equipment sales — **Fact** (segment tables, same filing)
- Century-old brand trust with corporate engineering buyers — **Inference** (spec-sheet incumbency in public capital-project bid documents)
## 2. Weaknesses (internal, evidenced)
- Digital execution gap: Foresight re-scoped to aftermarket-only, sponsoring VP departed, digital hiring down ~85% — **Fact** ([Q3 transcript](https://example.com/helix/q3-transcript); [departure](https://example.com/news/helix-vp); job boards) — ranked #1 by exploitability
- Single-vendor coverage: Foresight's own compatibility docs exclude third-party equipment — **Fact** ([docs](https://example.com/helix/foresight-docs))
- Slowing product velocity outside aftermarket: new-product release cadence roughly flat-to-down across two years of catalogs — **Inference** (catalog edition comparison)
- Segment-P&L structure resists horizontal plays — the org repeatedly localizes cross-cutting programs (Foresight is the second digital program fenced into a segment) — **Inference** (pattern across two programs, public record)
## 3. Opportunities (external)
- Aging-plant modernization demand is structural: average equipment age at record highs per census data — **Fact** ([census equipment-age series](https://example.com/census/equipment-age)) — strong fit to their installed base
- Machinery-safety documentation burden creates a compliance-automation market — **Fact** ([regulatory register](https://example.com/regs/machinery)) — moderate fit: their services arm could sell it tomorrow
- Integrator consolidation produces bigger partners who prefer fewer, deeper vendor relationships — **Fact** ([roll-up coverage](https://example.com/news/integrator-rollups)) — fits their channel depth
## 4. Threats (external)
- Vendor-agnostic monitoring software (Northfield's play) valuing exactly what they can't cover — mixed floors — **Fact** (category motion, our own launch)
- Meridian-class platform entrants with certification filings in progress — **Fact** ([registry](https://example.com/certregistry/meridian))
- Talent drain from their digital org into software-led rivals — **Fact** (two tracked departures landed at platform companies)
## 5. The Crossings (the "so what")
- **S-O (attack):** installed base (S1) × aging-plant demand (O1) is their natural fortress move — deepen aftermarket monetization without fighting anyone. Their filings say they're already taking it — **Inference**. Expect them to be *harder* to displace in Helix-majority plants, not easier.
- **W-T (exposure):** the digital execution gap (W1) plus single-vendor coverage (W2) is exactly what vendor-agnostic software (T1) finds first — and the org-structure pattern (W4) says the fix requires a reorg, not a feature. This exposure is durable — **Inference**.
- **For your decision:** don't contest Helix-majority plants in 2027 — their S-O fortress is real. Point the integrator channel at mixed-vendor plants where W1/W2 meet T1, and sign integrators *before* the consolidation wave (O3) makes the big ones choose sides.
### Assumptions to Validate
- The org-structure inference (two fenced programs = durable pattern) survives a third data point
- Integrator roll-ups haven't already signed exclusive Helix arrangements (check partner-program terms)
- Equipment-age data translates to monitoring budget, not just deferred replacement
---
## Why this example works
- **Weakness #1 is a fused signal, not a single fact.** Transcript language + a departure + a
hiring collapse — three independent channels — is what earns "digital execution gap" its rank.
One signal alone would have been a watch item, and the SaaS sibling's review-cluster method
wouldn't work here: industrial weaknesses hide in filings and org moves, not app stores.
- **The W-T crossing includes durability reasoning.** It doesn't just name the exposure — it
argues *why the fix is slow* (org structure, evidenced by a repeated pattern), which is what
makes the exposure worth building a 2027 strategy on.
- **The S-O crossing warns rather than gloats.** Honest SWOTs of competitors identify where they
will get *stronger* — the fortress move — so your plan avoids it instead of walking into it.
- **Both universes, one method:** compare with the SaaS sibling to see the same quadrant
discipline and label rigor running on a completely different evidence diet.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |