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.

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.

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.