Linking Strategy and Execution: Using Archimate Motivation Elements for Enterprise Architecture
The article explains how strategy development and execution are interdependent, outlines why executives often prioritize execution, and demonstrates how Archimate 3.1's motivation layer can model strategic intent, capabilities, and feedback loops to bridge strategy with actionable enterprise architecture practices.
Strategic practice consists of two parts: the development of strategy—what you must do to win—and the execution of strategy—actually carrying out the work to ensure the plan is implemented.
“I would rather have first‑class execution and second‑class strategy than brilliant ideas and mediocre management.”
In recent years many CEOs have believed execution is more important than strategy, for reasons such as self‑protection, the hidden nature of strategic change, and the perception of strategy as a top‑down effort.
In reality strategy and execution are intrinsically linked; both are essential. Enterprise architecture can add value by providing traceability from strategy to execution and by deriving strategic insight from execution analysis.
The relationship between strategy and execution can be expressed in four steps:
Associate strategy with required capabilities.
Build a capability roadmap that reflects dependencies and resource availability.
Link capabilities to the technology needed to fill gaps.
Create a technology roadmap that respects budgets, dependencies, and resource schedules.
Execution feedback that informs strategy must consider external factors (market shifts, consumer tastes, world events, disruptive technologies) and internal factors (new CEO, team capability, cost changes).
Archimate 3.1’s motivation layer offers a meta‑model for capturing the reasons behind change. Its elements include Stakeholder, Driver, Assessment, Goal, Requirement, Constraint, and Principle.
These elements help shape a strategy by defining capabilities, resources, and action plans, and they enable analysis of how changes in drivers affect the strategy.
Tools such as the open‑source Archi visualizer, Avolution Abacus, and other EA tools provide varying degrees of query and visualization capability, but most struggle with representing the temporal dimension of strategic change.
Future articles will explore capability maturity assessments, capability and technology road‑mapping exercises, and value‑stream mapping.
The motivational elements in Archimate 3.
An example of strategy (tan) and motivation (violet) elements and their relationships.
Architects Research Society
A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.