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.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
npx agent-skills-cli listSkill Instructions
name: wardley description: 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. user-invocable: true
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:
- [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
More by NeverSight
View all从多个文献内容中系统化提取并生成结构化课程。支持 1-100+ 个文献文件,智能识别内容类型(转录/文献/混合),自动进行主题识别、课程大纲生成、总览与章节内容撰写。采用可选模块架构,适应不同类型内容(理论/实践/案例/历史等)。本技能应在用户需要将多个文献整理为系统化课程、生成学习材料、处理转录内容、或从复杂文稿中提取结构化内容时使用。
Planning for React web UI implementation with component design focus
Install ADBC (Arrow Database Connectivity) drivers with dbc. Use when the user wants to install database drivers and connect to databases.
Vue 3 debugging and error handling for runtime errors, warnings, async failures, and SSR/hydration issues. Use when diagnosing or fixing Vue issues.
