Strategy Map

Most strategy work conflates tactics with strategy. Organizations produce detailed plans for what they will do without first establishing why it matters or who it serves. The result is strategic activity disconnected from any coherent understanding of the problem being addressed. This is not a failure of execution; it is a failure of structure.

Strategy Map is a four-layer framework that structures strategic thinking inside-out: from a contextual understanding of a problem, outward through success criteria, concrete tactics, and observable artifacts. Visualized as concentric rings radiating outward from a central problem context, with sectors represented as angular arcs sharing that core, the map makes strategic structure legible across multiple parties simultaneously. The framework originated from applying the journalist’s fundamental inquiry (the five Ws and one H) to strategic planning. The contextual core asks: what is the problem? Why does it matter? Who cares? From these questions, everything else follows.

What makes the Strategy Map distinct is its problem-first core that keeps strategy grounded in context rather than aspiration. It supports bidirectional traversal and incorporates temporal evolution:

• Problem-first core: keeps strategy grounded in context rather than aspiration
• Bidirectional traversal: build inside-out or diagnose outside-in
• Temporal evolution: reveals how strategy changes across time

Predecessors like the Balanced Scorecard introduced multiple perspectives but remained metric-driven and static. Mintzberg distinguished deliberate from emergent strategy but provided no visual architecture. The Strategy Map addresses these omissions by rooting everything in problem understanding and making the layer transitions explicit and navigable.

The Four Layers

Context Layer: What, Why, Who Cares

This is the gravitational centre. It begins with the 5W1H inquiry applied to a problem space:

• What is it? Define the problem domain precisely. What phenomenon are we addressing? This requires describing symptoms, patterns, and boundaries without jumping to causes or solutions.
• Why does it matter? Evidence of impact, urgency, scale. What happens if nothing changes? This layer requires quantifying or qualitatively documenting consequences of inaction.
• Who cares? Stakeholders affected, audiences served, interests at play. This includes both direct and indirect parties whose well-being or goals are influenced by the problem and potential responses.

The Context Layer stays entirely in the problem space. No solutioning occurs here. This is what Problem-First Research produces at depth: a rich understanding of a problem that grounds everything downstream. The layer should capture complexity without confusion — multiple perspectives, historical roots, interconnections with other problems, and evidence of persistence or escalation.

The Context Layer provides the gravitational centre from which all other layers emanate. Without it, strategy floats free of reality. With it, every tactical choice can be traced back to a specific understanding of what matters and for whom. When a new initiative enters your organisation, ask first: where is its Context Layer? If none exists or if it is merely an assumption, the initiative lacks grounding.

Strategy Layer: Metrics, Parameters, Success Criteria

From the contextual understanding, we derive measurements of success. This layer answers: how will we know we are making progress? What are the parameters and constraints? What does good look like?

This is strategy in the proper sense: direction and guardrails arising from problem understanding. The Strategy Layer includes:

• Success metrics: quantifiable indicators, thresholds, benchmarks
• Parameters: boundaries of acceptable action, trade-offs between competing values, rules of engagement
• Strategic priorities: which aspects of the problem receive focus first, sequencing decisions, resource allocation guidelines

The Strategy Layer changes infrequently and deliberately. When it changes often, either the context understanding was shallow or the metrics were poorly derived. Stability here provides the reference frame against which faster-moving layers are evaluated. A strategy that shifts with every new data point indicates metric instability or context volatility. A strategy that never shifts despite changing circumstances indicates inflexibility or fossilization.

The Strategy Layer is dual-sided. Beyond desired outcomes, it tracks derailment signals: the constraints and avoidances that indicate strategy is going wrong. This mirrors the structure of a Compelling Question, which fuses bold ambition with significant constraints. Desired metrics answer “how do we know we are succeeding?” Derailment metrics answer “how do we know we are failing before it is too late?” In visualisation, these two sides can be colour-coded on the same concentric ring, making both aspirational direction and protective boundaries simultaneously visible. The Strategy Layer functions as both compass (where to go) and guardrail (where not to go).

Tactics Layer: Who, Where, How

From the strategy, arise specifics. The remaining Ws and the H find their home here:

• Who will do the work? (actors, teams, partners, decision rights, accountability structures)
• Where will it happen? (domains, geographies, platforms, physical or digital spaces, coordination mechanisms)
• How will it be accomplished? (methods, tools, processes, routines, capabilities required, decision protocols)

Tactics are concrete, observable, and adaptive. They respond to shifts in context while maintaining alignment with strategic parameters. Tactics should be traceable to specific strategic metrics. When a tactic cannot be traced back to a specific strategic metric, it is either misplaced or reveals a gap in the strategy layer.

Effective tactics exhibit three qualities:

• Implementable: realistic given available resources and constraints
• Measurable: their contribution to strategic metrics can be observed
• Reversible: allowing for learning and course correction

Complex tactics often break down into sequences or combinations of simpler ones. The Tactics Layer captures the rhythm of execution.

Artifacts Layer: Evidence and Outputs

Artifacts are directly caused by tactics. They are the tangible evidence that strategy is executing (or failing to execute). Artifacts include:

• Writings (reports, publications, content, code, documentation)
• Projects (initiatives, products, services, infrastructure)
• Real-life case studies (documented outcomes, implementation records, impact assessments)
• Hypothetical future scenarios (design fiction, speculative outputs, anticipatory prototypes)

Artifacts serve a dual function: they demonstrate execution and they provide feedback. When artifacts consistently fail to produce expected outcomes, the signal propagates upward: either tactics are misaligned, strategy metrics are wrong, or the contextual understanding was incomplete.

The Artifacts Layer is where strategy becomes visible to external audiences. These outputs may circulate independently of their origin, so clarity in tracing artifacts back to their generating tactics and underlying strategy matters for credibility and learning. A single artifact may serve multiple purposes — a publication may be both an output of a project and a tool for shaping stakeholder understanding.

Bidirectional Traversal

The Strategy Map supports two modes of use:

Design mode (inside-out): Start from a problem understanding (Context), derive success criteria (Strategy), determine concrete actions (Tactics), and specify expected outputs (Artifacts). This is how you build a new strategy from scratch.

Diagnosis mode (outside-in): Start from observable artifacts and reverse-engineer backward. What tactics produced these artifacts? What strategic objectives do those tactics imply? What problem understanding (or lack thereof) sits beneath?

Diagnosis mode is particularly revealing for organizations whose stated strategy contradicts their observable behaviour. By mapping artifacts backward through tactics to inferred strategy, gaps between rhetoric and reality become structural rather than anecdotal.

For example, the World Economic Forum states a strategy of stakeholder capitalism and inclusive growth. Artifact analysis (closed-door member meetings, selective invitation policies, partnership structures favouring large multinationals) reveals tactics optimised for elite network maintenance. Reverse-engineering through the Strategy Map layers: the inferred Context Layer assumption is that global governance requires elite coordination, not broad participation. The gap between stated and inferred context is where strategic incoherence lives. The framework makes this visible and precise rather than merely rhetorical.

Bidirectional traversal also supports learning across time. When a strategy succeeds, reverse-engineering explains why. When it fails, reverse-engineering identifies where the breakdown occurred. This turn-taking — design, execute, diagnose, redesign — creates a feedback loop for strategic development.

Temporal Dimension

The four layers do not exist as a static snapshot. They evolve, and understanding that evolution enriches the tool considerably.

The four layers evolve at different paces:

• Different paces: Context shifts continuously; Strategy shifts rarely and deliberately; Tactics adapt responsively; Artifacts reflect execution rhythm.

• Linear time: Mapping how the four layers have changed historically reveals patterns. Which context shifts prompted strategic pivots? Which tactical changes produced (or failed to produce) the expected artifacts? The historical record of a Strategy Map is itself a diagnostic tool. Comparing the Context Layer of an organisation at two points in time reveals whether assumptions were tested and revised or merely repeated. Comparing Artifacts across periods reveals whether output volume correlates with strategy adherence or merely activity.

• Expansive time: The framework extends into alternative scenarios. What if a specific historical context assumption had been different? What artifacts would have resulted? Projecting forward: under different future context scenarios, which strategic metrics remain valid and which require revision? This connects the Strategy Map to scenario planning and foresight methodology, where the contextual core is stress-tested against multiple possible futures rather than a single expected one.

The temporal dimension transforms the Strategy Map from a planning document into a living instrument for understanding how strategy actually evolves. It acknowledges that strategy is not a one-time exercise but an ongoing process of adaptation governed by the relative stability and volatility of each layer.

Cross-Sector Coordination

The Strategy Map is circular in visualisation. The Context core sits at the centre (the bullseye), with Strategy, Tactics, and Artifacts as concentric rings radiating outward. Sectors are defined as angular arcs on this circle: distinct disciplines, interests, or organisations each occupying their own slice of the map.

The key structural property: multiple sectors can share the same Context core. When several parties organise around the same problem (the same “what, why, who cares”), their strategies, tactics, and artifacts radiate outward from the same gravitational centre. They need not agree on method. They need only share the problem understanding at the centre.

This creates a coalition model. Shared context enables coordinated action without requiring homogenized tactics. An innovation ecosystem, a cross-sector partnership, or a multi-stakeholder initiative can map each participant as a separate arc on the same circle. Where arcs align at the Strategy ring (shared success metrics), coordination is natural. Where arcs diverge at the Tactics ring (different methods), that divergence is visible and can be evaluated: does it strengthen the overall response through diversity, or does it fragment effort?

The framework provides a way to audit strategic correlation between parties. Two organizations claiming to work on the same problem can map their respective arcs and compare: do their Strategy-layer metrics align? Do their Tactics point in compatible directions? Are their Artifacts complementary or contradictory? This turns vague “partnership” language into structural analysis.

Figure: An implementation of the Strategy Map framework. Source: FW.VISION

References

• Kaplan, Robert S., and David P. Norton. “Having Trouble with Your Strategy? Then Map It.” Harvard Business Review 78, no. 5 (2000): 167-176. The Balanced Scorecard introduced layered strategic perspectives; the Strategy Map presented here replaces metric-driven statics with problem-first dynamics.
• Mintzberg, Henry. “Patterns in Strategy Formation.” Management Science 24, no. 9 (1978): 934-948. Mintzberg’s distinction between deliberate and emergent strategy informs the bidirectional traversal model.
• Schwartz, Peter. The Art of the Long View: Planning for the Future in an Uncertain World. Currency, 1996. Scenario planning methodology provides the foundation for temporal integration.

Cross-links

• Compelling Question
• Innovation Challenge
• Problem-First Research