wardley-mapping

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Wardley Mapping

A strategic mapping technique created by Simon Wardley for understanding competitive landscape, technology evolution, and making informed architectural decisions. A Wardley Map visualizes four dimensions: the value chain (components needed to meet user needs), evolution (how components mature over time), the landscape (competitive environment), and movement (how the landscape changes).

这是Simon Wardley创立的一种战略映射技术，用于理解竞争格局、技术演进并做出明智的架构决策。Wardley Map可视化四个维度：价值链（满足用户需求所需的组件）、演进（组件随时间成熟的过程）、格局（竞争环境）以及动态（格局的变化方式）。

Map Structure

地图结构

The following diagram illustrates the conceptual axes of a Wardley Map. For the generation template with placeholders, see the Map Template section below.

text

                    EVOLUTION

        Genesis    Custom     Product    Commodity
           ↓          ↓          ↓          ↓
        ┌──────────────────────────────────────────┐
        │                                          │
Visible │   User Need ●                            │  ← Anchor
        │       │                                  │
        │       ↓                                  │
        │   Component A ●──────────→ ●             │
        │       │                                  │
        │       ↓                                  │
        │   Component B    ●                       │
        │       │                                  │
Hidden  │       ↓                                  │
        │   Component C              ●             │
        │       │                                  │
        │       ↓                                  │
        │   Component D                       ●    │  ← Commodity
        │                                          │
        └──────────────────────────────────────────┘

        Y-axis: Visibility (to user)
        X-axis: Evolution (certainty)

下图展示了Wardley Map的概念轴。如需带占位符的生成模板，请查看下方的“地图模板”部分。

text

                    EVOLUTION

        Genesis    Custom     Product    Commodity
           ↓          ↓          ↓          ↓
        ┌──────────────────────────────────────────┐
        │                                          │
Visible │   User Need ●                            │  ← Anchor
        │       │                                  │
        │       ↓                                  │
        │   Component A ●──────────→ ●             │
        │       │                                  │
        │       ↓                                  │
        │   Component B    ●                       │
        │       │                                  │
Hidden  │       ↓                                  │
        │   Component C              ●             │
        │       │                                  │
        │       ↓                                  │
        │   Component D                       ●    │  ← Commodity
        │                                          │
        └──────────────────────────────────────────┘

        Y-axis: Visibility (to user)
        X-axis: Evolution (certainty)

Evolution Stages (Summary)

演进阶段（摘要）

Stage	Position	Key Trait	Sourcing	Example
Genesis	Far left (0.0-0.25)	Novel, uncertain, high failure	Build (R&D)	Novel AI architectures
Custom-Built	Center-left (0.25-0.50)	Understood but bespoke, differentiating	Build (custom dev)	Bespoke trading platform
Product	Center-right (0.50-0.75)	Multiple vendors, feature competition	Buy (configure)	CRM systems
Commodity	Far right (0.75-1.0)	Well understood, essential, utility	Outsource (consume)	Cloud compute (IaaS)

For detailed stage characteristics, indicators, and positioning criteria, see references/evolution-stages.md.

阶段	位置	核心特征	获取方式	示例
Genesis	最左侧（0.0-0.25）	新颖、不确定性高、失败风险大	自建（研发）	新型AI架构
Custom-Built	左中区域（0.25-0.50）	已被理解但为定制化，具备差异化	自建（定制开发）	定制化交易平台
Product	右中区域（0.50-0.75）	多供应商、功能竞争	采购（配置）	CRM系统
Commodity	最右侧（0.75-1.0）	已被充分理解、不可或缺、实用化	外包（使用）	云计算（IaaS）

如需详细的阶段特征、指标和定位标准，请查看references/evolution-stages.md。

How to Create a Wardley Map

如何创建Wardley Map

Follow these steps in order when the user asks to create or analyze a Wardley Map.

当用户要求创建或分析Wardley Map时，请按以下步骤操作。

Step 1: Gather Context

步骤1：收集上下文信息

Use the AskUserQuestion tool to interactively gather the information needed to create the map. Ask up to 3 questions at a time.

First, identify the anchor and scope:

Use AskUserQuestion to ask:

Who is the primary user? — Options might include: "External customers", "Internal developers", "Business analysts", or let the user specify
What is the user need? — e.g., "Purchase products online", "Deploy applications reliably", "Generate analytical reports"
What is the scope? — Options: "Single product/service", "Business unit", "Entire organization", "Specific capability"

Then, gather strategic context:

Use AskUserQuestion to ask:

What is the primary goal? — Options: "Identify investment priorities", "Evaluate build vs. buy", "Assess competitive position", "Plan technology evolution"
What industry/domain? — Let the user specify (affects how components are positioned on the evolution axis)
What depth of analysis? — Options: "Quick overview (5-10 components)", "Standard map (10-20 components)", "Deep analysis (20+ components with gameplay)"

使用AskUserQuestion工具交互式收集创建地图所需的信息，每次最多提出3个问题。

首先，确定锚点和范围：

使用AskUserQuestion工具询问：

主要用户是谁？ — 选项包括：“外部客户”、“内部开发人员”、“业务分析师”，或让用户自行指定
用户需求是什么？ — 例如：“在线购买产品”、“可靠部署应用”、“生成分析报告”
范围是什么？ — 选项：“单一产品/服务”、“业务单元”、“整个组织”、“特定能力”

然后，收集战略上下文：

使用AskUserQuestion工具询问：

主要目标是什么？ — 选项：“确定投资优先级”、“评估自建vs采购”、“评估竞争地位”、“规划技术演进”
所属行业/领域？ — 让用户自行指定（会影响组件在演进轴上的定位）
分析深度？ — 选项：“快速概述（5-10个组件）”、“标准地图（10-20个组件）”、“深度分析（20个以上组件含玩法模式）”

Step 2: Build the Value Chain

步骤2：构建价值链

Work backwards from the user need. List every component required to deliver it, then arrange them by visibility (user-facing at top, infrastructure at bottom). For each component, identify what it depends on — dependencies flow downward.

List capabilities, not just technologies
Include people, practices, and data alongside technical components
Map both technical and business components
Ask: "What components are needed?", "What does each depend on?", "What is hidden from the user?"

If component identification is uncertain, use AskUserQuestion to ask the user about key capabilities, technologies, and processes in their domain.

从用户需求倒推，列出交付该需求所需的所有组件，然后按可见性排列（用户可见的在顶部，基础设施在底部）。对于每个组件，确定其依赖关系——依赖关系向下流动。

列出能力，而非仅技术
除技术组件外，还需包含人员、实践和数据
同时映射技术和业务组件
询问：“需要哪些组件？”、“每个组件依赖什么？”、“哪些内容对用户隐藏？”

如果组件识别存在不确定性，使用AskUserQuestion工具询问用户其领域内的关键能力、技术和流程。

Step 3: Position on Evolution

步骤3：在演进轴上定位

For each component, assess its evolution stage using the indicators in references/evolution-stages.md. Place it on the X-axis accordingly.

Key questions for each component:

How well understood is it in the market?
How many alternatives exist?
Is it commoditized or unique?
What's the market maturity?

Avoid common mistakes: don't position based on age (use market maturity), don't confuse internal unfamiliarity with market-wide genesis, and always consider industry context.

If positioning is ambiguous for key components, use AskUserQuestion to clarify with the user — e.g., "Is your recommendation engine a custom differentiator or are you using an off-the-shelf product?"

对于每个组件，使用references/evolution-stages.md中的指标评估其演进阶段，并相应地放置在X轴上。

每个组件的核心问题：

它在市场中的被理解程度如何？
存在多少替代方案？
它是商品化的还是独特的？
市场成熟度如何？

避免常见错误：不要根据年限定位（使用市场成熟度），不要将内部不熟悉与市场层面的Genesis阶段混淆，始终考虑行业上下文。

如果关键组件的定位不明确，使用AskUserQuestion工具向用户澄清——例如：“您的推荐引擎是定制化差异化组件，还是使用现成产品？”

Step 4: Add Movement

步骤4：添加动态箭头

Add arrows showing how components are evolving. All components naturally drift rightward over time, but some move faster or slower.

```
→
```
Natural evolution (component moving right over time)
```
×
```
Inertia (resistance to movement from past success, skills, or politics)
```
>>
```
Acceleration (forced rapid evolution from competition or disruption)

添加箭头显示组件的演进方向。所有组件自然会随时间向右漂移，但有些移动速度更快或更慢。

```
→
```
自然演进（组件随时间向右移动）
```
×
```
惯性（因过往成功、技能或政治因素导致的移动阻力）
```
>>
```
加速（因竞争或颠覆而被迫快速演进）

Step 5: Analyze and Recommend

步骤5：分析并给出建议

After drawing the map, apply the analysis checklist below, then review gameplay patterns in references/gameplay-patterns.md and climatic patterns in references/climatic-patterns.md to identify strategic moves.

Use AskUserQuestion to confirm priorities with the user before finalizing recommendations — e.g., "The map suggests these three strategic moves. Which areas are most important to your organization right now?"

绘制完成地图后，应用下方的分析清单，然后查看references/gameplay-patterns.md中的玩法模式和references/climatic-patterns.md中的气候模式，以确定战略举措。

在最终确定建议之前，使用AskUserQuestion工具与用户确认优先级——例如：“地图显示了这三项战略举措。您的组织目前最关注哪些领域？”

Step 6: Quantitative Analysis (Optional)

步骤6：量化分析（可选）

When the user asks for numeric precision, scoring, or data-driven positioning, apply the mathematical models from references/mathematical-models.md:

Evolution Scoring — Calculate precise X-axis positions using Ubiquity and Certainty scores
Decision Metrics — Differentiation Pressure, Commodity Leverage, and Dependency Risk
Weak Signal Detection — Assess readiness factors to predict stage transitions

Present results as a table alongside the qualitative analysis — the numbers should confirm or challenge the intuitive positioning, not replace it.

当用户要求数值精度、评分或数据驱动的定位时，应用references/mathematical-models.md中的数学模型：

演进评分 — 使用普及度和确定性分数计算X轴上的精确位置
决策指标 — 差异化压力、商品杠杆和依赖风险
弱信号检测 — 评估就绪因素以预测阶段转换

将结果与定性分析一起以表格形式呈现——数值应确认或挑战直观定位，而非替代它。

Analysis Checklist

分析清单

Apply this checklist to every completed map:

yaml

analysis_checklist:
  completeness:
    - "Is the anchor (user need) clearly defined?"
    - "Are all components necessary to meet the need included?"
    - "Are dependencies shown?"
    - "Are movement arrows present?"

  positioning:
    - "Is each component positioned based on market evolution, not internal capability?"
    - "Are commodity components on the right?"
    - "Are genuinely novel components on the left?"

  insights:
    - "What components have inertia?"
    - "Where are there opportunities to commoditize?"
    - "What genesis activities could become differentiators?"
    - "Where is there technical debt (building custom where products exist)?"

  strategic:
    - "What gameplay patterns apply?"
    - "Where should we invest vs. outsource?"
    - "What climatic patterns affect our landscape?"
    - "What doctrine weaknesses exist?"

For deeper strategic analysis, consult:

Gameplay Patterns for offensive/defensive moves and build vs. buy guidance
Climatic Patterns for external forces affecting the landscape
Doctrine for organizational maturity weaknesses

对每个已完成的地图应用以下清单：

yaml

analysis_checklist:
  completeness:
    - "Is the anchor (user need) clearly defined?"
    - "Are all components necessary to meet the need included?"
    - "Are dependencies shown?"
    - "Are movement arrows present?"

  positioning:
    - "Is each component positioned based on market evolution, not internal capability?"
    - "Are commodity components on the right?"
    - "Are genuinely novel components on the left?"

  insights:
    - "What components have inertia?"
    - "Where are there opportunities to commoditize?"
    - "What genesis activities could become differentiators?"
    - "Where is there technical debt (building custom where products exist)?"

  strategic:
    - "What gameplay patterns apply?"
    - "Where should we invest vs. outsource?"
    - "What climatic patterns affect our landscape?"
    - "What doctrine weaknesses exist?"

如需更深入的战略分析，请参考：

玩法模式，获取进攻/防御举措以及自建vs采购的指导
气候模式，了解影响格局的外部力量
准则，评估组织成熟度的薄弱环节

Map Template

地图模板

Always produce the visual map using the template below. Also produce the structured YAML output (using the Output Format section) when writing the map to a file; for conversational responses, the visual map alone is sufficient.

Use this template when generating a visual Wardley Map:

text

Title: {Map Name}
Anchor: {User Need}
Date: {ISO-8601}

                    Genesis    Custom     Product    Commodity
                       │          │          │          │
Visible            ┌───┼──────────┼──────────┼──────────┼───┐
                   │   │          │          │          │   │
                   │   │  {User Need}                       │
                   │   │      │                             │
                   │   │      ↓                             │
                   │   │  {Component 1}    ●──────→         │
                   │   │      │                             │
                   │   │      ├───────────────┐             │
                   │   │      ↓               ↓             │
                   │   │  {Component 2}  {Component 3}      │
                   │   │      ●               ●             │
                   │   │      │               │             │
                   │   │      ↓               │             │
                   │   │  {Component 4}       │             │
                   │   │           ●          │             │
Hidden             │   │           │          │             │
                   │   │           ↓          ↓             │
                   │   │  {Component 5}───────┘             │
                   │   │                  ●                 │
                   │   │                                    │
                   └───┴────────────────────────────────────┘

Legend: ● Current position, → Evolution direction, × Inertia

始终使用以下模板生成可视化地图。当将地图写入文件时，还需生成结构化YAML输出（使用“输出格式”部分）；对于对话式回复，仅可视化地图即可。

生成可视化Wardley Map时使用此模板：

text

Title: {Map Name}
Anchor: {User Need}
Date: {ISO-8601}

                    Genesis    Custom     Product    Commodity
                       │          │          │          │
Visible            ┌───┼──────────┼──────────┼──────────┼───┐
                   │   │          │          │          │   │
                   │   │  {User Need}                       │
                   │   │      │                             │
                   │   │      ↓                             │
                   │   │  {Component 1}    ●──────→         │
                   │   │      │                             │
                   │   │      ├───────────────┐             │
                   │   │      ↓               ↓             │
                   │   │  {Component 2}  {Component 3}      │
                   │   │      ●               ●             │
                   │   │      │               │             │
                   │   │      ↓               │             │
                   │   │  {Component 4}       │             │
                   │   │           ●          │             │
Hidden             │   │           │          │             │
                   │   │           ↓          ↓             │
                   │   │  {Component 5}───────┘             │
                   │   │                  ●                 │
                   │   │                                    │
                   └───┴────────────────────────────────────┘

Legend: ● Current position, → Evolution direction, × Inertia

Output Format

输出格式

When generating a Wardley Map document, use this structure:

yaml

wardley_map:
  metadata:
    title: "{Map Name}"
    author: "{Author}"
    date: "{ISO-8601}"
    version: "1.0"
    scope: "{What this map covers}"

  anchor:
    user: "{User description}"
    need: "{User need statement}"

  components:
    - name: "{Component Name}"
      evolution: "{Genesis/Custom/Product/Commodity}"
      position: "{0.0-1.0}"
      visibility: "{0.0-1.0}"
      depends_on:
        - "{Dependency 1}"
        - "{Dependency 2}"
      notes: "{Strategic notes}"
      movement: "{evolving/accelerating/inertia/none}"

  analysis:
    opportunities:
      - "{Opportunity 1}"
      - "{Opportunity 2}"

    threats:
      - "{Threat 1}"
      - "{Threat 2}"

    inertia_points:
      - component: "{Component}"
        reason: "{Why inertia exists}"

  recommendations:
    immediate:
      - "{Action with rationale}"
    short_term:
      - "{Action with rationale}"
    long_term:
      - "{Action with rationale}"

生成Wardley Map文档时，使用以下结构：

yaml

wardley_map:
  metadata:
    title: "{Map Name}"
    author: "{Author}"
    date: "{ISO-8601}"
    version: "1.0"
    scope: "{What this map covers}"

  anchor:
    user: "{User description}"
    need: "{User need statement}"

  components:
    - name: "{Component Name}"
      evolution: "{Genesis/Custom/Product/Commodity}"
      position: "{0.0-1.0}"
      visibility: "{0.0-1.0}"
      depends_on:
        - "{Dependency 1}"
        - "{Dependency 2}"
      notes: "{Strategic notes}"
      movement: "{evolving/accelerating/inertia/none}"

  analysis:
    opportunities:
      - "{Opportunity 1}"
      - "{Opportunity 2}"

    threats:
      - "{Threat 1}"
      - "{Threat 2}"

    inertia_points:
      - component: "{Component}"
        reason: "{Why inertia exists}"

  recommendations:
    immediate:
      - "{Action with rationale}"
    short_term:
      - "{Action with rationale}"
    long_term:
      - "{Action with rationale}"

References

参考资料

Consult these reference files for deeper analysis:

Evolution Stages — Stage characteristics, indicators, positioning criteria, transition heuristics, pioneers/settlers/planners talent model
Climatic Patterns — 32 patterns across 6 categories (component, financial, speed, inertia, competitor, prediction), peace/war/wonder cycle, pattern interactions
Gameplay Patterns — 60+ plays across 11 categories with D&D alignment classification, play-position matrix, play compatibility, case studies (AWS, Netflix, Tesla, Spotify)
Doctrine — 40+ principles across 4 phases and 6 categories, Strategy Cycle framework, implementation journeys, maturity assessment template
Mapping Examples — Worked examples: E-Commerce, DevOps Platform, ML Product, TechnoGadget Smart Home, value chain decomposition walkthrough, case study cross-references
Mathematical Models — Evolution scoring formulas, decision metrics, weak signal detection, play-position scoring, climate pattern impact weighting

如需更深入的分析，请查阅以下参考文件：

演进阶段 — 阶段特征、指标、定位标准、转换启发式、先驱者/定居者/规划者人才模型
气候模式 — 6个类别下的32种模式、和平/战争/奇迹周期、模式交互
玩法模式 — 11个类别下的60余种玩法，含D&D对齐分类、玩法-定位矩阵、玩法兼容性、案例研究（AWS、Netflix、Tesla、Spotify）
准则 — 4个阶段、6个类别下的40余项原则、战略周期框架、实施路径、成熟度评估模板
映射示例 — 实战示例：电子商务、DevOps平台、ML产品、TechnoGadget智能家居、价值链分解演练、案例研究交叉参考
数学模型 — 演进评分公式、决策指标、弱信号检测、玩法-定位评分、气候模式影响权重

ArcKit Integration

ArcKit集成

This skill handles conversational Wardley Mapping — quick questions, evolution stage lookups, doctrine assessments, and interactive map creation.

For formal architecture documents with document control, project integration, UK Government compliance (TCoP, GDS, AI Playbook), and OnlineWardleyMaps syntax for https://create.wardleymaps.ai, use the ArcKit Wardley suite:

```
/arckit.wardley.value-chain
```
— Decompose user needs into value chains (WVCH artifact)
```
/arckit.wardley
```
— Create strategic Wardley Maps (WARD artifact)
```
/arckit.wardley.doctrine
```
— Assess organizational doctrine maturity across 4 phases, 40+ principles (WDOC artifact)
```
/arckit.wardley.gameplay
```
— Analyze strategic plays from 60+ gameplay patterns with D&D alignment (WGAM artifact)
```
/arckit.wardley.climate
```
— Assess 32 climatic patterns across 6 categories with prediction horizons (WCLM artifact)

These generate versioned artifacts saved to your project directory with full traceability to requirements and architecture principles. Each command works standalone but gets richer when sibling artifacts exist.

此技能处理对话式Wardley Mapping——快速问答、演进阶段查询、准则评估和交互式地图创建。

如需具备文档管控、项目集成、英国政府合规（TCoP、GDS、AI Playbook）以及支持https://create.wardleymaps.ai的OnlineWardleyMaps语法的**正式架构文档**，请使用ArcKit Wardley套件：

```
/arckit.wardley.value-chain
```
— 将用户需求分解为价值链（WVCH工件）
```
/arckit.wardley
```
— 创建战略Wardley Map（WARD工件）
```
/arckit.wardley.doctrine
```
— 评估组织准则在4个阶段、40余项原则上的成熟度（WDOC工件）
```
/arckit.wardley.gameplay
```
— 分析60余种玩法模式中的战略玩法，含D&D对齐（WGAM工件）
```
/arckit.wardley.climate
```
— 评估6个类别下的32种气候模式，含预测周期（WCLM工件）

这些命令会生成带版本的工件并保存到您的项目目录，与需求和架构原则完全可追溯。每个命令可独立运行，但当存在关联工件时会提供更丰富的内容。