Linking Strategy and Execution: Using Archimate for Motivation Modeling

Strategic practice is a two‑part exercise: strategy development (what to do to win) and strategy execution (the work needed to implement the plan). Many CEOs view execution as more important, as illustrated by Jamie Dimon’s quote preferring top‑class execution over second‑class strategy.

The belief stems from self‑protection (CEOs see themselves as strategists), the hidden nature of rapid strategic change, and a top‑down perception of strategy. Real‑world examples, such as the retail sector’s delayed response to the pandemic, show that strategy must evolve quickly.

In fact, strategy and execution are intrinsically linked; enterprise architecture adds value by providing traceability from strategy to execution and deriving strategic insights from execution analysis.

The link can be built through four steps: (1) associate strategy with required capabilities, (2) create a capability roadmap that assesses current maturity and dependencies, (3) map capabilities to the technology gaps they expose, and (4) develop a technology roadmap that schedules implementations based on budget, dependencies, and resources.

Execution feedback challenges strategy by introducing external factors (market shifts, consumer tastes, disruptive technologies) and internal factors (new CEOs, team capability, cost changes), requiring strategic adjustments.

Archimate 3.1, a meta‑modelling standard, offers a motivation layer that models why changes occur. Its elements—stakeholders, drivers, assessments, goals, requirements, constraints, and principles—help architects capture the reasons behind strategic shifts.

These motivation elements combine with strategic nodes such as capabilities, resources, and action plans to form a complete view of strategy and its execution.

An illustrative diagram (shown in the article) depicts the relationships between strategy (tan) and motivation (violet) elements.

Action processes must be tied to goals; without this link, ideas remain unimplemented. Linking goals to action plans ensures that strategic intent translates into operational work.

Additional connections can be made to other architecture elements (applications, data objects, infrastructure). Queries can identify impacted resources when goals change, affected goals when resources are disrupted, or revised action plans when personnel changes occur.

Tools such as the open‑source Archi visualizer, Avolution Abacus, and other EA platforms provide varying levels of query capability, but many struggle with handling the temporal dimension of strategic change and simulating future scenarios.

Other meta‑cognitive toolsets—capability maturity assessments, capability and technology roadmaps, and value‑stream mapping—also support strategy‑execution alignment and will be explored in future articles.