value-chain-mapping

# Value Chain Mapping Skill

Map value chains from user needs to underlying components as the foundation for Wardley Maps.

## When to Use This Skill

Use this skill when:

- **Value Chain Mapping tasks** - Working on map value chains from user needs to underlying components
- **Planning or design** - Need guidance on Value Chain Mapping approaches
- **Best practices** - Want to follow established patterns and standards

## MANDATORY: Documentation-First Approach

Before mapping value chains:

1. **Invoke `docs-management` skill** for value chain patterns
2. **Verify mapping methodology** via MCP servers (perplexity)
3. **Base guidance on Wardley's value chain decomposition**

## Value Chain Fundamentals

```text
Value Chain = Components Linked by Dependencies

User Need
    │
    ▼
┌─────────────────┐
│ Component A     │ ◄── Visible to user
└────────┬────────┘
         │ depends on
         ▼
┌─────────────────┐
│ Component B     │ ◄── Less visible
└────────┬────────┘
         │ depends on
         ▼
┌─────────────────┐
│ Component C     │ ◄── Invisible to user
└─────────────────┘

Key Principles:
- Start with user need (anchor)
- Work backwards to dependencies
- Higher = more visible to user
- Lower = more invisible (infrastructure)
```

## Step 1: Identify the Anchor (User Need)

### Good vs Bad Anchors

```text
GOOD ANCHORS (Needs):
✓ "I need to communicate with my team"
✓ "I need to process customer payments"
✓ "I need to deploy software reliably"
✓ "I need to understand customer behavior"
✓ "I need to manage my finances"

BAD ANCHORS (Solutions):
✗ "I need Slack"
✗ "I need Stripe"
✗ "I need Kubernetes"
✗ "I need Google Analytics"
✗ "I need QuickBooks"

Test: Can the need be satisfied multiple ways?
If tied to specific solution, you have a solution, not a need.
```

### Anchor Identification Questions

```text
Finding User Needs:

WHO Questions:
- Who is the user?
- Who benefits from this?
- Who are we serving?

WHAT Questions:
- What outcome do they want?
- Wh