Wardley Mapping for Operators
Source-grounded pack with Strategic Landscape Map Builder, Value Chain Dependency Mapper, and Evolution Operating Model Fit Check, plus 1 more.
Get this packGrounded in the complete Wardley Mapping for Operators series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 4 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches Wardley Mapping for Operators and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
4 source-grounded skills. Load one workflow at a time.
Strategic Landscape Map Builder
Use this workflow when a team needs to see the strategic landscape before committing to a roadmap, platform choice, AI adoption move, vendor decision, staffing model, or operating cadence. Its distinct job inside the Wardley Mapping Pack is to produce a first-pass user-anchored map; use the neighboring skills for deeper dependency mapping, operating-model fit, and doctrine/gameplay choices.
Output specification
Return a strategic landscape map brief with this schema: - purpose: user, need, decision, owner, deadline, and cost of delay. - user_anchor: primary user and the need that anchors the map. - map_components: capabilities with visibility, dependencies, suspected evolution stage, owner, and evidence link. - strategic_observations: position, movement, climate signals, inertia, and AI-era commoditization pressures. - unknowns: assumptions, missing evidence, disputed facts, and tests to run. - decision_implications: what the map suggests about build, buy, platform, vendor, staffing, or cadence choices. - review_gates: human approvals required before the map changes plans, budgets, records, or external commitments. - next_move: one evidence-gathering or alignment step due in the next operating cadence.
Value Chain Dependency Mapper
Use this workflow when a user outcome depends on many hidden capabilities and the team needs to understand what actually has to work before changing process, platform, staffing, vendor, AI agent, or operating cadence decisions. Its distinct job inside the Wardley Mapping Pack is to map value-chain dependencies; use the neighboring skills for landscape framing, evolution fit, and doctrine/gameplay choices.
Output specification
Return a value chain dependency map with this schema: - user_outcome: user, need, success measure, failure moment, and decision owner. - dependency_chain: ordered capabilities with owner, source of truth, evidence, visibility, and dependency type. - critical_links: dependencies that most affect reliability, speed, cost, trust, customer experience, or regulatory exposure. - ai_agent_dependencies: model, context, data rights, tool access, human review, evaluation, and governance dependencies. - risk_register: weak link, likely consequence, evidence, owner, severity, and mitigation. - strategic_implications: what to simplify, standardize, build, buy, instrument, govern, or retire. - review_gates: approvals required before changing systems, contracts, controls, or customer commitments. - next_move: one dependency to verify or instrument next.
Evolution Operating Model Fit Check
Use this workflow when a team may be using the wrong operating model for the evolution stage of a capability. It is especially useful for AI-era decisions where model access, tooling, data infrastructure, workflow orchestration, governance, or customer experience may be moving at different speeds. Its distinct job inside the Wardley Mapping Pack is to test evolution-stage fit; use the neighboring skills for map building,...
Output specification
Return an evolution operating-model fit check with this schema: - capability_stage_table: capability, suspected stage, evidence, confidence, owner, and review date. - fit_assessment: current operating model, fit or mismatch, symptoms, and consequence. - inertia_sources: what the old model protects and who experiences the cost of changing it. - ai_commoditization_scan: capabilities moving toward commodity, contested layers, and strategic control points. - recommended_changes: method, cadence, budget, staffing, platform, vendor, governance, or quality changes with rationale. - risks_and_tradeoffs: blast radius, reversibility, timing, and second-order effects. - review_gates: approvals required before changing operating model or commitments. - next_move: one experiment, review, or evidence check to validate the fit assessment.
Doctrine Gameplay Decision Brief
Use this workflow when a team has a map and needs to decide what to do next without mistaking basic operating discipline for clever strategy. Its distinct job inside the Wardley Mapping Pack is to separate doctrine fixes from gameplay choices such as build, buy, commoditize, differentiate, partner, constrain, migrate, wait, or exit.
Output specification
Return a doctrine gameplay decision brief with this schema: - decision: user need, map position, decision owner, deadline, and cost of no action. - doctrine_check: doctrine strengths, gaps, required fixes, owners, and due dates. - gameplay_options: options with fit to evolution stage, control point, evidence, tradeoffs, reversibility, and blast radius. - inertia_analysis: protected old model, affected stakeholders, resistance signals, and evidence required to move. - recommendation: chosen doctrine fixes and gameplay move, sequencing, rationale, acceptance criteria, and stop conditions. - operating_cadence: how the map changes planning, reviews, resource allocation, platform governance, AI adoption, or vendor management. - review_gates: approvals required before commitments or record changes. - next_move: one decision or evidence action due before the next review.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.