Integrated Meta Model for Enterprise Modelling including Strategy, Business Architecture, Risk and Change

How can a single integrated meta model support strategy, business architecture, risk, and change across multiple EA frameworks — and why do existing approaches fall short?

These slides accompany the paper: Integrated Meta Model for Enterprise Modelling including Strategy, Business Architecture, Risk and Change

The major enterprise architecture frameworks each bring something valuable, but none are sufficient on their own. TOGAF covers IT domains reasonably well but lacks the contextual concepts — competitors, legislation, market forces, ecology — essential for genuine strategic planning. ArchiMate is more rigorous and consistent but weak on data modelling and context. BizBOK is focused but narrow. None of them, individually or together, provide a single coherent foundation for the full scope of strategy, business architecture, risk, change, and programme management that large transformation efforts demand.

This paper describes the development of HAL2023, the latest iteration of the Inspired Holistic Architecture Language — built by systematically analysing and synthesising TOGAF 10th Edition, ArchiMate 3.2, BizBOK 11, SABSA, MEMO, DODAF, and the accumulated Inspired consulting models. The result is a large but well-structured integrated meta model, expressed at three levels — rich pictures for executives, conceptual models for architects, and fully attributed models for tooling — and validated across projects in banking, telecommunications, assurance, retail, healthcare, and government. Notable enhancements in this revision include richer contextual coverage, rationalised relationship types, financial aspects, customer journeys, architecture scenarios, and improved integration with risk, governance, and initiative management.

Crucially, the paper is practical as well as theoretical: it explains how the model should be used incrementally rather than exhaustively, with teams populating only what is relevant to current goals — progressively expanding coverage as new questions arise, much like the way an ERP system delivers increasing value as more modules are adopted.

Originally published as a conference paper by Graham McLeod in the PoEM 2023 Companion Proceedings (16th IFIP Working Conference on the Practice of Enterprise Modeling), Vienna, 2023.

Extending and Automating Maturity Models for More Value

How can maturity models be extended beyond a simple rating to deliver recommendations, prioritised actions, and a path forward — and automated to remove the friction of doing so?

These slides accompany the paper: Extending and Automating Maturity Models for More Value

Maturity models are a staple diagnostic tool in enterprise architecture and information systems — but in practice, their value is often squandered. Organisations complete an assessment, receive a score, and are left to figure out what to do next. The friction of collecting data, calculating ratings, and managing results over time further discourages repeated use. This paper tackles both problems: how to extend the model itself to provide genuine guidance, and how to automate the process so that the effort of running an assessment becomes trivial.

The paper presents a generic domain model for maturity assessment, developed and validated at Inspired.org, which supports not just scoring across multiple dimensions but also recommendations tied to each gap between maturity levels, with relative effort ratings and dependency relationships between recommended actions. An algorithm prioritises recommendations by combining score gaps, effort, and dependency order — producing a ranked, actionable improvement plan rather than a list of observations. The domain model was implemented in the EVA platform in approximately two hours, with the full online assessment flow — including Kiviat chart scoring, recommendation presentation, action selection, and Gantt chart export — delivered in under a week. APIs were subsequently added to support integration with partner systems, adding around three days of effort.

The paper concludes with a reflection on Return on Modelling Effort (ROME): working at the domain concept level, rather than writing custom application code, enabled rapid delivery, easy adaptation, and high reuse — making this a compelling case for meta model-driven, low-code approaches to enterprise tooling.

Originally published as a journal article by Graham McLeod in the EMISA Journal (Enterprise Modelling and Information Systems Architectures), with a companion presentation at the Models at Work stream, PoEM 2022.

AI Goes Mainstream: What Business Architects Need to Know

What is AI, how did it get here, and what does it mean for business architecture?

Artificial intelligence moved from research curiosity to mainstream business tool with remarkable speed, and this 2022 presentation — delivered at the Inspired Business Architecture Forum — captures that inflection point. Graham McLeod and Dr Jay van Zyl trace the history of AI and machine learning from the 1940s to the early 2020s, building a working vocabulary and mapping the rapidly evolving ecosystem of models, frameworks, and platforms. The presentation examines who the major players are — Google DeepMind, Microsoft/OpenAI, Meta, Apple, and Tesla — and how the market is layering from large foundation models down to end-user applications. Crucially for practitioners, it identifies the direct implications of AI for business architecture: product and service design, business intelligence, process automation, customer experience, and the ethical and governance questions that follow. The closing message is unambiguous — business architects who ignore AI do so at their peril.

Originally presented by Graham McLeod and Dr Jay van Zyl at the Inspired Business Architecture Forum, 2022.

New Technology Creates Architecture Opportunity

How should enterprise architects respond when exponential technology change reshapes what's possible?

Technology does not advance linearly — and enterprise architects who plan as if it does will consistently underestimate what is both possible and necessary. This 2013 presentation by Graham McLeod surveys the wave of exponential technologies then reshaping the landscape: mobile and internet connectivity, big data and analytics, semantic technology and linked data, social networks, nanotechnology, robotics, and 3D printing. For each, the presentation draws out not just what the technology does, but what it makes architecturally possible — from radically compressed value chains enabled by 3D printing, to "world processing" application architectures that collect, merge, analyse, and visualise data at scale. A particularly striking section examines network effects and the speed at which new platforms achieve mass adoption, underscoring the pace at which architectural assumptions can be overtaken. The closing message is clear: technology advances are not background noise for enterprise architects — they are the signal.

Originally presented by Graham McLeod at an Inspired event, October 2013.

A Business and Solution Building Block Approach to EA Project Planning

How can enterprise architects bring clarity to project scope, release planning, and stakeholder communication across complex, interdependent programmes?

These slides accompany the paper: A Business and Solution Building Block Approach to EA Project Planning

When multiple projects are running in parallel — each with its own business analyst, development team, and agile backlog — it becomes surprisingly easy for scope, dependencies, and release content to become invisible to the people who most need to understand them: sponsors, stakeholders, and programme managers. This paper documents exactly that problem at a rapidly expanding South African telecoms company, where two major projects (Quoting and Billing) were underway with little consensus on scope, no agreed release breakdown, and a growing disconnect between business expectations and development plans.

The solution was a structured building block approach, distinguishing Business Building Blocks (BBBs) — capability-level components independent of technology choices — from Solution Building Blocks (SBBs), representing the actual systems, data sources, and infrastructure chosen to implement them. A facilitated workshop produced a BBB diagram showing capabilities, dependencies, and release groupings at a glance; a release matrix then mapped capability and content coverage to delivery timelines. Both were formalised in a meta model and implemented in the EVA Netmodeler repository, enabling traceability from business requirements through to agile backlogs and programme milestones.

The approach was well received across all stakeholder groups — sponsors, strategists, and programme managers reported that they finally had a clear, shared picture of what each project would deliver and when. The paper includes the full meta model, visual examples, and an honest reflection on adoption challenges, making it a practical reference for any EA function working to improve programme visibility and stakeholder alignment.

Originally published as a conference paper by Graham McLeod, Inspired.org / University of Cape Town, circa 2013–2014.

Real Business Architecture: Strategy, Design Thinking, and the Bigger Picture

How does business architecture go beyond conventional scope to become a genuine driver of business transformation?

Most treatments of business architecture focus on functions, processes, and capabilities — important, but incomplete. This 2012 presentation by Graham McLeod, delivered at The Open Group Enterprise Transformation Conference in Cannes, makes the case that the true scope of business architecture is much broader: encompassing innovation and design thinking, customer value and emotion, external context, emerging technology, and the full range of strategic concerns that drive organisational change. Drawing on TOGAF 9, Archimate 2, and the Inspired framework, the presentation maps out an expanded meta model that integrates motivation, functional, process, service, and capability perspectives — and shows how these are not competing views but complementary lenses that can be reconciled. A compelling section examines the transformative forces reshaping business in 2012 — cloud, big data, social media, additive manufacturing, and the rise of design-driven companies — and asks what business architects must do to stay relevant. Case examples from Apple, Volkswagen, and others illustrate how architectural thinking at the right level of abstraction enables the kind of strategic clarity that transforms organisations. The closing argument is unambiguous: business architecture practised at its full scope is a board-level strategic capability, not a documentation exercise.

Originally presented by Graham McLeod at The Open Group Enterprise Transformation Conference, Cannes, France, April 2012.

From Chief Information Officer to Chief Innovation Officer

How should enterprise architects and CIOs reframe their role in a world where innovation has become a survival issue?

Business models that were sound five years ago are already obsolete, and the pace of change is only accelerating. This 2011 presentation by Graham McLeod — delivered under the provocative subtitle "Get out of your cubicle and into the future!" — challenges CIOs and enterprise architects to fundamentally reframe their role in response to a world being reshaped by exponential forces. Drawing on Ray Kurzweil's computing power curves, the explosive growth of social media, the collapse of traditional value chains through 3D printing and digital distribution, and the rise of semantic and AI-driven applications, the presentation paints a vivid picture of the environment in which organisations must now compete. The central argument is that staying where you are is itself a risk — and that the architects and technology leaders best placed to lead are those who can connect these broad external change themes to the structure of the enterprise: its business architecture, processes, applications, information, and technology. A particularly compelling section examines innovation as a managed capability, drawing on examples from Procter & Gamble and Cisco to show how structured innovation processes, social tools, and external networks can be embedded in the operating model. The closing message is direct: design thinking, innovation models, and an outward-facing perspective are no longer optional extras for enterprise architects — they are core competencies.

Originally presented by Graham McLeod at an Inspired event, March 2011.

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.

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.