Many eons before the advent of computers and sophisticated spoken languages, the conveyance of ideas among individuals relied on pictures. The use of visual representations for communication has persisted throughout history. In contemporary times, especially within the realm of IT Architecture, a picture or diagram remains an extraordinarily potent tool. It possesses the capacity to abstract vast complexities, facilitating the sharing of business information.
A pivotal skill for an Architect, irrespective of their designation—be it Technical, Solution, Enterprise, or otherwise—is the proficiency to communicate effectively with business user groups. Achieving this demands the ability to structure, simplify, and abstract copious amounts of information, rendering it comprehensible to the intended audience.
Simplifying the blueprint diagram is often recommended, especially for effective communication with executives who are accustomed to receiving information in a concise format. When more detailed information is necessary, employing multiple diagrams, each illustrating a higher level of detail, is advisable. This approach ensures that communication remains accessible and tailored to the specific needs of the audience.
The IT Architect also needs to contemplate the long-term maintenance of the diagrams, accounting for the resources required to keep multiple diagrams current, especially when each diagram encompasses a substantial amount of information.
Blueprints serve as a potent tool for abstracting and disseminating information. They establish a foundation for effective engagement with business and other audience groups, constituting a crucial skill that every IT Architect should possess and refine.
The diagram below is something a created for a global organisation with a highly complex IT landscape that had organically developed into Frankenstein’s monster due to lack of governance and many years of uncontrollable customisations.
