Wardley Maps in Enterprise Architecture

How can Wardley Maps be integrated with Enterprise Architecture frameworks to improve strategic planning?

These slides accompany the paper: Wardley Maps in Enterprise Architecture

Most Enterprise Architecture frameworks — including TOGAF, ArchiMate, and Zachman — address business and technology change effectively, but few formally account for the broader context in which an organisation operates: where it sits in its competitive landscape, how its components are evolving, and what strategic options that evolution creates. This paper argues that Wardley Mapping fills precisely that gap, and proposes a concrete approach for integrating it with EA practice. Drawing on the Inspired Holistic Architecture Language (HAL), Graham McLeod shows that nearly all the concepts required for Wardley Maps — stakeholders, capabilities, value chains, maturity levels — are already present in a well-constructed EA meta model, making integration more straightforward than it might appear. The paper introduces a stratified Wardley Map format that aligns visual layers with EA meta model types, and reports on early use of the integrated approach in client workshops and a Business Architecture Mastery Programme. For enterprise architects and business architects, this integration offers a practical way to add dynamic, evolution-aware thinking to existing EA models without starting from scratch.

Originally published as a conference paper in the PoEM 2025 Companion Proceedings (18th IFIP Working Conference on the Practice of Enterprise Modeling), Geneva, 2025.

The Power of Principles

Why are architecture principles the highest-return activity in enterprise architecture — and how do you define good ones?

Architecture principles are among the most powerful tools available to enterprise architects — yet they are frequently underdefined, poorly worded, or neglected altogether. This 2014 presentation by Graham McLeod makes the case that well-crafted principles, spanning business, application, information, and technology domains, represent the highest return on effort of almost any EA activity: a relatively small investment that shapes decisions across the entire organisation for years. Drawing on experience across banking, assurance, and telecommunications, the presentation covers what distinguishes a principle from a rule, how to structure principles effectively using the short name, statement, rationale, and implications format, and how to engage stakeholders in the definition process. A particularly useful concept is the "stealth payload" — the idea that while principle statements tend to be irrefutable, the implications are where the real architectural direction is embedded. The presentation also addresses compliance monitoring, showing how architecture assets can be mapped against principles and tracked over time to drive meaningful governance.

Originally presented by Graham McLeod at the Enterprise Architecture Conference Europe 2014 & Business Process Management Conference Europe 2014, June 2014.

Engaging Real Business People in Real Business Architecture

Why do business executives avoid enterprise architecture — and how do you get them genuinely engaged?

The complaint is common among IT architects: business executives won't engage with enterprise architecture, leaving the whole effort directionless. But as this 2009 presentation by Graham McLeod argues, the real problem lies with what is typically presented to business people as "business architecture" — a technically framed, detail-heavy, IT-grown discipline that offers little of immediate relevance to the executives who actually own the business. Delivered at The Open Group EA Practitioners Conference in London, the presentation sets out both a diagnosis and a remedy. The diagnosis: most EA has grown upward from IT rather than downward from business strategy, and neither TOGAF nor most frameworks at the time adequately captured the full scope of genuine business architecture — context, markets, products, channels, customers, scenarios, and cross-cutting concerns like cost, risk, quality, and governance. The remedy: a comprehensive business architecture meta model, drawn from Inspired and PROMIS experience across banking, healthcare, assurance, telecommunications, and government, that gives executives models they recognise as their own. A particularly practical section addresses how architects must shift their role — from technical experts presenting conclusions to skilled facilitators asking good questions, holding up a mirror, and ensuring that models and content belong to the business rather than the architecture team. The presentation closes with specific suggestions for how TOGAF should expand its treatment of business architecture.

Originally presented by Graham McLeod at The Open Group EA Practitioners Conference (EAPC), London, UK, April 2009.

Meta Meta Model Extensions for Managing Large-Scale Collaborative EA Modelling

How do you extend enterprise architecture meta models to keep large-scale collaborative modelling manageable?

When enterprise architecture modelling moves beyond a single expert working alone — across teams, organisations, time zones, and languages — the meta model that was perfectly adequate for small-scale work begins to break down. Ownership conflicts, information overload, incompatible versions, and variable data quality all emerge as serious practical obstacles. This 2008 presentation by Graham McLeod, delivered at EMMSAD 2008 (Exploring Modelling Methods for Systems Analysis and Design), addresses these challenges head-on with a set of formal but pragmatic extensions to EA meta models and meta meta models, developed through real-world experience building and operating the EVA collaborative repository. The core constructs introduced include context — a powerful, reusable mechanism that operates at the meta meta level and addresses domain, ownership, authority, timeframe, status, and language in a unified way; relationship typing, which brings precision to how model elements connect; and a model type abstraction that subsumes graphical models, documents, reports, and user interfaces under a single coherent concept. A three-layer object architecture — implemented in Smalltalk — is shown to be essential for the flexibility required, with filters implemented as a specialisation of model type and time, version, and baseline tracking unified through relationships. The resulting conceptual model is notably compact given the range of challenges it addresses, and the presentation is candid about both the expressiveness achieved and the performance challenges encountered in implementation. For practitioners building or evaluating EA repository tooling, this is a rare account of what the meta model level actually needs to look like in production.

Originally presented by Graham McLeod at EMMSAD 2008 (Exploring Modelling Methods for Systems Analysis and Design), Montpellier, France, June 2008.

Service Orientation in Enterprise Architecture: Beyond Surface-Level Support

How should enterprise architecture frameworks and meta models be extended to provide genuine, deep support for service orientation?

Service orientation reshapes how applications are conceived, how systems are integrated, and ultimately how value is delivered to customers — yet most enterprise architecture frameworks treat it as a technical implementation detail rather than an architectural concern that spans the full enterprise stack. This 2008 presentation by Graham McLeod, delivered in his role as CTO of PROMIS Solutions AG, argues that achieving deep support for service orientation in EA requires rethinking frameworks and meta models from the ground up. The presentation distinguishes carefully between technical, application, information, and business services, and between logical service definitions — independent of technology and implementation — and their physical realisation, insisting that the mapping between these two levels is essential for meaningful planning and governance. A key architectural insight is the treatment of modern applications not as monolithic systems but as malleable bundles of functions exposed as services, where components can be replaced without impacting overall service delivery — a view that has significant implications for how application architecture is modelled. The presentation also addresses what it calls "enrichment": the additional concepts needed to govern services effectively, including intent (benchmarks, goals, objectives), responsibility and ownership, cross-cutting concerns (risk, cost, quality), and built-in computation and analysis. Archimate is proposed as a candidate notation for distinguishing domains and logical versus physical layers, with worked examples showing how service cross-referencing and traceability can be achieved in practice.

Originally presented by Graham McLeod at an Inspired/PROMIS event, December 2008.

The Central Role of Business Analysis in Enterprise Architecture

What role does business analysis play in enterprise architecture — and why is it central rather than peripheral?

Business analysis is frequently treated as a project-level discipline — something that happens within initiatives, not above them. This 2007 presentation by Graham McLeod challenges that view, arguing that business analysts have a central and irreplaceable role in enterprise architecture, particularly across the business and process architecture dimensions. Delivered to the IIBA Western Cape Chapter, the presentation walks through the components of EA using the Inspired frameworks, with detailed coverage of business architecture, business process architecture, and the relationship between strategy, architecture, and programme management. A key theme is requirements traceability — the clear linkage from business goals and events through to system and technology services — which demands the kind of domain knowledge and analytical rigour that experienced business analysts bring. The presentation concludes that EA represents a natural career growth path for analysts, and that organisations which keep the two disciplines separate are missing a significant opportunity.

Originally presented by Graham McLeod to the IIBA Western Cape Chapter, November 2007.

Breaking the EA Bottleneck: Collaborative and Distributed Enterprise Modelling

How can enterprise architecture move beyond the central "oracle" model to become a truly collaborative, distributed discipline?

The central architect as "oracle" — a single expert who holds all the knowledge and dispenses answers to those willing to make the pilgrimage — is a familiar and dysfunctional pattern in enterprise architecture. It creates bottlenecks, slows delivery, produces models that lack buy-in, and makes it almost impossible to integrate the perspectives of business, process, data, application, and technology teams who each hold a piece of the picture. This 2007 tutorial by Graham McLeod, delivered at the CAiSE conference in Trondheim, tackles this problem head-on with a comprehensive framework for collaborative, distributed enterprise modelling. The tutorial covers the full stack of enablers: shared meta models and naming standards as the foundation for integration; a structured process for identifying participants, educating them, collecting architecture elements, organising hierarchies, and building cross-domain relationships; and tool support that enables distributed teams to capture, relate, model, and share architecture content across geographies and time zones. A particularly useful section distinguishes the roles of framework, meta model, method, and repository tool — clarifying how each contributes to making collaboration work in practice. The benefits are concrete: higher quality inputs, faster results, greater organisational awareness, and significantly higher levels of architectural compliance, precisely because the people who need to act on the architecture helped build it.

Originally presented by Graham McLeod as a tutorial at CAiSE 2007 (19th International Conference on Advanced Information Systems Engineering), Trondheim, Norway, 2007.

Linking Strategy, Enterprise Architecture and Programme Management

How do you create a coherent link between business strategy, enterprise architecture, and programme management — and why does it matter?

Organisations routinely struggle to translate strategic intent into delivered change — not because the strategy is wrong, but because the connections between strategy, architecture, and execution are poorly defined or missing entirely. This presentation by Graham McLeod, drawn from 15 years of cross-industry experience, addresses that gap with a structured framework for integrating strategy, enterprise architecture, and programme management into a coherent whole. Central to the approach is the concept of delta models — architecture views that show the net change required between current and future states, providing accurate scope for projects and a clear communication bridge between strategists, architects, and the project office. The presentation covers the full chain: from understanding current reality and setting architectural principles, through scenario development and filtering, to portfolio selection based on benefit ranking, risk scoring, cost estimation, and dependency mapping. A particularly useful section introduces the concept of organisational APIs — published, stable business service interfaces that facilitate rapid reconfiguration, outsourcing, and partnering, and that bring the discipline of software interface design to the boundary between business units. Case studies from telecommunications, a media group, an international bank, and a major assurer illustrate the approach in practice, showing how the integration of strategy, architecture, and programme management produces better-scoped initiatives, more informed investment decisions, and faster, lower-risk delivery.

Originally presented by Graham McLeod at an Inspired event, 2005.

Enhancing Enterprise Architecture Models with Cost, Quality and Risk Dimensions

How can enterprise architecture models be extended to capture cost, quality, and risk — and why does it matter?

Enterprise architecture models do an excellent job of mapping the structural relationships between business, process, application, information, and technology domains — but they have traditionally said little about cost, quality, and risk, the dimensions most relevant to the executives and managers who need to act on them. This 2003 presentation by Graham McLeod, delivered at the University of Cape Town in collaboration with Promis Solutions AG, makes the case that these dimensions are not separate concerns requiring separate tools — they can be woven directly into existing EA models. Drawing on the Inspired EA framework and its EVA repository, the presentation shows how cost centres can be linked to architecture elements and values derived through declarative formulas, how quality metrics can be attached to products, processes, applications, and platforms, and how risk can be incorporated as a further dimension of the model. A particularly useful insight is that most of the cost elements organisations need are already present in their architecture models — they simply need attributes added and a mechanism for accumulation and apportionment. The result is a single integrated view that allows strategic planners, architects, and business managers to evaluate current positions and future scenarios with proper appreciation for the full implications of their decisions.

Originally presented by Graham McLeod at the University of Cape Town, June 2003.