wardley

Wardley Mapping strategic analysis—map value chains against evolution to reveal build vs buy decisions and competitive dynamics. Use for technology strategy or investment decisions.

General

What this skill does


# Wardley Map

Create a strategic map showing components positioned by their evolution stage and visibility in the value chain.

## Instructions

Identify the user need, map the value chain of components required to meet it, and position each component on the evolution axis.

### Output Format

**Context**: [What situation we're mapping]
**User**: [Who the user is]
**User Need**: [What they're trying to accomplish]

---

## Value Chain Identification

**Working backward from user need:**

| Component | Depends On | Visibility |
|-----------|------------|------------|
| [User Need] | [what it requires] | High (User-facing) |
| [Component A] | [what it requires] | High/Med/Low |
| [Component B] | [what it requires] | High/Med/Low |
| [Infrastructure] | [base requirements] | Low (Hidden) |

---

## Evolution Assessment

| Component | Evolution Stage | Evidence |
|-----------|-----------------|----------|
| [Component A] | Genesis / Custom / Product / Commodity | [Why at this stage] |
| [Component B] | Genesis / Custom / Product / Commodity | [Why at this stage] |

**Evolution Indicators**:
- Genesis: Novel, poorly understood, no standard, high uncertainty
- Custom: Emerging practices, divergent approaches, experimentation
- Product: Feature differentiation, rental/purchase models, scalable
- Commodity: Standardized, utility pricing, essential but undifferentiated

---

## The Map

```
VISIBLE │
   TO   │  [User Need]
  USER  │       │
        │       ▼
        │  [Component A]
        │       │
        │       ▼
INVISIBLE│  [Component B]
        │
        └──────┬──────┬──────┬──────┬──────►
            GENESIS  CUSTOM PRODUCT COMMODITY
              I        II     III      IV
```

---

## Movement Analysis

**What's evolving rightward?**
| Component | Current Stage | Evolving Toward |
|-----------|---------------|-----------------|
| [component] | [stage] | [next stage] |

**Inertia Points**
- [Component with inertia] — [why we might resist]

---

## Strategic Analysis

### Build vs. Buy

| Component | Recommendation | Rationale |
|-----------|----------------|-----------|
| [Genesis/Custom] | **Build** | Differentiator |
| [Commodity] | **Buy** | Commodity, not differentiating |

### Competitive Dynamics

**Our differentiators** (left side of map):
- [Component we do differently]

**Commoditization threats**:
- [Component becoming commodity]

---

## Recommendations

**Short-term actions**:
1. [Action based on map insights]

**What to stop doing**:
- [Component to outsource/buy instead of build]

---

**Key Insight**:
> [Main strategic takeaway from the mapping exercise]

## Guidelines

- Always start with user need
- Everything evolves left to right (genesis → commodity)
- Build on the left (differentiation), buy on the right (commodity)
- Watch for inertia—past success creates resistance to change

$ARGUMENTS

Files: 1

Size: 3.1 KB

Complexity: 12/100

Category: General

Source: https://github.com/neurofoo/agent-skills/tree/main/wardley

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts