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.

What Should an EA Management Tool Actually Do?

What are the requirements for a truly effective enterprise architecture management tool — and how should one be designed?

The tools most organisations use to manage enterprise architecture — spreadsheets, presentation software, drawing tools — were built for entirely different purposes, and the gap shows. This 2005 presentation by Graham McLeod takes a rigorous look at what a purpose-built EA management tool actually needs to do, synthesising requirements from Zachman, Spewak, Schekkerman, TOGAF, and real-world RFPs into a comprehensive checklist spanning repository design, meta-modelling, collaboration, security, reporting, and governance support. The presentation then describes the design of Archi/WebModeler, Inspired's own web-based EA repository, and how its architecture addresses these requirements — including a runtime-extensible meta model, rich content types, inferencing and computation capabilities, visual modelling, and scenario management. Particularly notable is the emphasis on making the tool useful not just to enterprise architects but to the full range of stakeholders involved in EA: strategic planners, programme managers, risk managers, sponsors, and domain architects. For practitioners evaluating EA tooling or building the case for a dedicated repository, this presentation remains a clear-eyed benchmark of what good looks like.

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.