borghei/Claude-Skills / project-management/strategy-frameworks/swot-analysis
swot-analysis
VerifiedBuilds and audits an evidence-backed SWOT with TOWS actions for one explicit strategic question. Use when assessing a market entry, pivot, competitive response or restructure, or as input to annual planning.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.8 KB |
| assets/sample_swot.json | config | 2.8 KB |
| assets/sample_swot_flawed.json | config | 452 B |
| assets/swot_template.md | markdown | 1.9 KB |
| references/swot-anti-patterns.md | markdown | 5.1 KB |
| references/swot-framework.md | markdown | 6.7 KB |
| scripts/swot_scorer.py | script | 9.8 KB |
references/swot-framework.md
View on GitHub# SWOT — Framework Reference
## 1. The 2x2
| | Helpful (positive) | Harmful (negative) |
|--------------|--------------------|--------------------|
| Internal | **Strengths** | **Weaknesses** |
| External | **Opportunities** | **Threats** |
- **Internal** = under our control (people, money, IP, ops, brand, process)
- **External** = outside our control (market, customers, competitors, regulation, tech)
## 2. What goes where — examples
### Strengths (internal + helpful)
- Strong engineering bench in [specific area]
- Established brand in [segment]
- Proprietary dataset of [type]
- Existing customer base of [scale]
- Capital position ([runway])
- Patented IP for [tech]
- Established channel partnerships
- Geographic presence in [region]
### Weaknesses (internal + harmful)
- Tech debt slowing release cycle
- Reliance on a single major customer
- Limited international presence
- Engineering hiring slowed by location
- High churn in segment X
- Lack of enterprise-grade compliance
- Slow product-led growth motion
### Opportunities (external + helpful)
- New regulation requiring product category
- Major competitor exit / acquisition
- Distribution shift (e.g., new app store, channel)
- Technology shift (e.g., LLMs enabling new use cases)
- Customer behavior shift (post-COVID remote work, e.g.)
- Adjacent market opening up
- Currency / interest rate shift favorable
### Threats (external + harmful)
- Well-funded competitor entering
- Regulatory change reducing addressable market
- Technology shift threatening core product
- Customer concentration risk (their industry struggles)
- Geopolitical risk in major market
- Recession reducing budgets
## 3. The miscategorization test
For each item, ask: "Do we own this directly?"
| Item | Internal? | Why |
|------|-----------|-----|
| "Strong brand" | Internal | We built and own the brand |
| "Customers love us" | External | Customer behavior |
| "Talented team" | Internal | We hired them |
| "Hard to find AI talent" | External | Labor market |
| "Cash reserves" | Internal | Our balance sheet |
| "Investor appetite low" | External | Market sentiment |
| "Excellent customer support" | Internal | We operate it |
| "Customers churning to competitor" | External | Their decision (driven by external trigger) |
Common mistake: "We have great customer satisfaction" — that's customer
sentiment (external) caused by your service (internal). Pick the
underlying internal capability as the Strength.
## 4. Evidence standards
Every SWOT item should have:
- **What:** specific description (not generic)
- **Evidence:** data, customer quote, benchmark, document reference
- **Magnitude:** size, scale, or trend
- **Confidence:** how sure are we?
### Good
> "Strength: Engineering velocity 2.5x our top 3 competitors in feature
> shipping cadence — measured via product changelogs Apr 2025-Apr 2026.
> Evidence: comparative analysis (link). Magnitude: 24 features/yr vs
> 9-12. Confidence: high (measured)."
### Weak
> "Strength: Great engineering team."
The weak version could describe any company.
## 5. The TOWS matrix
After SWOT, build TOWS — the action-oriented cross-cut.
| | Opportunities (O) | Threats (T) |
|--------------|-------------------|-------------|
| **Strengths (S)** | **SO strategies** — use strengths to capture opportunities | **ST strategies** — use strengths to defend against threats |
| **Weaknesses (W)** | **WO strategies** — address weaknesses to capture opportunities | **WT strategies** — minimize weaknesses to avoid threats |
### Example TOWS
Scope: "Entering European compliance market"
| | O1: GDPR Article 22 driving demand | T1: EU competitor with EU presence |
|---|---|---|
| **S1: Strong product** | SO: lead with product differentiation in EU marketing campaigns | ST: highlight product depth vs incumbent's older offering |
| **W1: No EU presence** | WO: hire EU-based GDPR specialist + open EU entity | WT: partner with EU systems integrator to reduce time-to-market |
Each cell yields a candidate strategy. Then prioritize.
## 6. Prioritization across TOWS cells
A typical TOWS has 16+ candidate strategies (4 cells × multiple per cell).
You can't pursue all. Apply:
- **Strategic fit:** aligns with overall strategy
- **Materiality:** worth doing (revenue, risk, brand)
- **Feasibility:** can we actually execute?
- **Timing:** does the window matter?
Pick 2-3. Resource the rest at zero or defer.
## 7. SWOT cadence
- **Annual:** at start of strategic planning
- **Quarterly:** light refresh if external environment shifts
- **Pre-strategic-event:** new market entry, fundraise, pivot, major launch
Avoid:
- SWOT every quarter mechanically (becomes ceremony)
- SWOT once + never update (becomes stale)
## 8. SWOT for a function vs company
A SWOT for "Marketing" or "Engineering" works:
- Scope = "Marketing function vs needs of FY27 strategy"
- Strengths = marketing-specific
- External = company external + cross-functional dependencies
Useful for functional planning. Don't conflate with company-level SWOT.
## 9. SWOT with bias
Common biases to surface:
- **CEO bias:** Strengths inflated; weaknesses minimized
- **Sales bias:** Opportunities expanded; threats acknowledged late
- **Engineering bias:** Tech threats over-weighted; market opportunities under-weighted
- **Founder bias:** Personal narrative ("we started this") drives Strengths
- **Recency bias:** Most-recent event dominates
Mitigations:
- External facilitator
- Anonymous input
- Pre-read of customer/competitor data
- Devil's advocate role assigned
- TOWS forces honest cross-cuts
## 10. SWOT alternatives
When SWOT is the wrong tool:
- **VRIO** (Value, Rarity, Imitability, Organization) — for sustainable competitive advantage
- **Porter's Five Forces** — for industry structure
- **PESTLE** — for macro environment
- **BCG Growth-Share Matrix** — for portfolio decisions
- **Blue Ocean Strategy Canvas** — for uncontested market space
Use SWOT for breadth. Use these others for depth on specific questions.
## 11. Internal vs external: the test
If the item depends on something we own (people, money, tech, brand, process, IP), it is internal. If it depends on something we do not own (market, customers, competitors, regulators, technology trends), it is external.
- "Strong brand recognition in segment X": internal (we own it)
- "Customers love our brand": external (customer behaviour)
- "Strong eng team": internal; "Hard to recruit eng talent": external
- "Our cloud bill is high": internal; "Cloud prices rising": external
## 12. From SWOT to strategy
SWOT is input, not a strategy: SWOT (positioning) → TOWS (options) → prioritisation (2-3 options) → resourcing (what we fund and give up) → KPIs (how we will know). Skipping a step produces analysis without action.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |