We’re fast approaching the time of year where, for those of us in an IT-adjacent role, we can be sure of a good few hours engaged in family-related technology support. I’ve already been asked a couple of questions about backups and how to keep data safe. As usual with this topic, I head for my favourite explainer page on the principles of backups. I find this a useful prop to discussions on the topic, as it outlines well the underlying reasons why I make specific recommendations.
Many of us make decisions and present recommendations on technology to less-technical audiences throughout the year. These technical support conversations of mine outline the importance of clear, non-conflicting and well-publicised Enterprise Architecture principles to an effective Enterprise Architecture practice. To note for the TOGAF world, I include both Enterprise principles and Architecture principles here.
Some Government departments publish very clear documentation on their decision processes, and with that in mind I turn to the Department for Education’s GitHub: “Enterprise Architecture principles are general rules and guidelines that inform and support decisions in how DfE should deliver services, to align with its vision and objectives” i. As a definition, it’s pretty clear. It highlights the core elements: generality, their use to support decisions, and the core goal being to align with the organisational vision and objectives. It is one thing having a well-defined set of principles; their value comes from how well they are used.
Enterprise Architecture principles need to be clear and understandable by all. Having principles that are digestible by all audiences brings transparency to the decision-making process, reduces ambiguity in the approach taken and allows stakeholders to remain informed.
Enterprise Architecture principles must not conflict with one another and must apply equally across the enterprise. If application of one principle conflicts with the spirit of another, an environment is created where individuals or teams can selectively apply principles based on individual use-cases. Principles should be applied equally to every decision, and so selectivity in application must be avoided. Exceptions should be rare, reviewed and documented. Similarly, to allow for a specific business unit to less closely apply the principles to its technology decisions only serves to undermine the application of the principles across the enterprise. This ‘divisional’ approach to enterprise architecture in general increases complexity across the estate, reduces the ability to fully exploit tools where functionality is required in different units, and serves to create an environment with siloed data and processes.
Finally, Enterprise Architecture principles must be evangelised across every engagement. Repetition (of the right things) is the key to success here – when every business sponsor knows about the principles and has seen them used explicitly to underpin decision-making, they will become more aware of the sorts of decisions and recommendations that you may produce, and will anticipate their alignment with the organisation’s goals and values.
Back to my family’s technological troubles, and I’m excluding details as I’m not keen to be the first to initiate a Christmas quarrel! When the principles behind a recommendation are understood, the recommendations are more readily accepted. The stakeholder is empowered to ask questions around the framework of principles, deepening understanding. The stakeholder is aware of the decision-making process and the justifications behind it, aligning business and technology rather than pitting them against one another. Finally, and importantly, the stakeholder is more likely to spend money on the best solution, rather than selecting for price above all other factors.
