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.

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.

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.