Two Lenses, One Decision
Wardley Maps and SWOT analysis are not competing frameworks — they answer different questions about the same decision. A Wardley Map answers "What is the landscape and where is it moving?" SWOT answers "Given this landscape, what are our capabilities and risks?"
Here's how to combine them in practice:
Step 1: Draw the Wardley Map. Plot your system's components on the evolution axis. Identify which components are moving (evolving toward commodity) and which are static.
Step 2: Identify the strategic question. The map will reveal tensions — a component you're custom-building that's becoming a commodity, or a Genesis-stage technology that could become your differentiator.
Step 3: Run a SWOT analysis on the specific move. For example, if the map shows your custom monitoring system is now a commodity (Datadog, Grafana Cloud exist), the strategic question becomes: "Should we migrate to a managed monitoring solution?" Now run SWOT on that specific decision.
Step 4: Cross-reference. Does the SWOT reveal that your team lacks the skills to operate the commodity? (Weakness → Threat.) Or does it reveal that migration would free up 3 engineers to work on your actual differentiator? (Strength → Opportunity.)
Example Workflow:
Wardley Map reveals:
→ "Our custom log aggregation system" is in Custom Built
→ Market has moved log aggregation to Product/Commodity (ELK as a service, Datadog Logs)
→ Strategic question: Should we migrate?
SWOT for "Migrate to managed logging":
Strengths: Team already uses Datadog for metrics. Budget approved.
Weaknesses: Custom system has proprietary log format. 200+ dashboards depend on it.
Opportunities: Frees 2 engineers. Reduces on-call burden. Better search capabilities.
Threats: Migration downtime risk. Vendor pricing changes. Compliance team hasn't approved Datadog for log storage.
Decision: Proceed, but mitigate W→T first:
1. Build log format adapter before migration
2. Get compliance approval before committing
3. Migrate in phases (non-critical services first)
Key Point: Neither framework alone is sufficient. Wardley Maps without SWOT tell you what to do but not whether you can do it. SWOT without Wardley Maps tells you what you're capable of but not whether the landscape rewards that capability. Senior engineers and engineering managers who can fluently combine both frameworks make dramatically better strategic decisions.