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.

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.