Embedded Files
In the practice of organizational management, communication is not a side activity — it is the essence of how decisions are made and change is executed. Nowhere is this more evident than in the work of solution and enterprise architects. While architecture is often associated with models, diagrams, and frameworks, at its core it is about making complex ideas understandable to diverse stakeholders and guiding organizations through transformation.
In the practice of organizational management, communication is not a side activity — it is the essence of how decisions are made and change is executed. Nowhere is this more evident than in the work of solution and enterprise architects. While architecture is often associated with models, diagrams, and frameworks, at its core it is about making complex ideas understandable to diverse stakeholders and guiding organizations through transformation.
Communication as a Strategic Capability
Communication as a Strategic Capability
Enterprise Architecture (EA) frameworks such as ISO/IEC/IEEE 42010 define architecture description as a communication artifact: a way to represent systems through views and viewpoints that address specific stakeholder concerns. The Zachman Framework organizes this into perspectives (“what,” “how,” “who,” “where,” “when,” “why”), while ArchiMate offers a standardized modeling language for showing dependencies across business, application, and technology layers.
But these are not ends in themselves. Models and frameworks are instruments to communicate about change: to explain why a system must evolve, what the target should be, and how the path to that target might unfold.
Models as Shared Language
Models as Shared Language
Architectural models provide a shared vocabulary. Capability maps, process flows, application landscapes, or data lineage diagrams allow decision-makers to “see” abstractions that would otherwise remain invisible. The act of modeling enables analysis and experimentation, but its primary function is communication: making trade-offs explicit, highlighting dependencies, and giving leaders a structured way to evaluate options.
Without communication, models risk becoming shelf-ware. With effective communication, they become decision accelerators.
Bridging Stakeholder Worlds
Bridging Stakeholder Worlds
An architect rarely designs for themselves. They design with and through others: executives, product owners, engineers, compliance officers, and end users. Each group brings its own language and priorities.
Here lies the unique responsibility of the architect:
Translate strategy into technology so that business leaders see opportunities rather than just costs.
Translate technology into business impact so that engineers understand why their work matters beyond code.
Mediate between abstract and concrete, ensuring that strategic goals can be executed in real-world systems.
Effective communication here is not only verbal but also visual and structural. Diagrams, roadmaps, and capability heatmaps all function as cognitive bridges.
Communication as Risk Management
Communication as Risk Management
Change in large systems is inherently risky. Misaligned expectations or misunderstood dependencies can derail multi-million-dollar programs. Clear communication is therefore a form of risk mitigation. By articulating assumptions, dependencies, and decision rationales in a structured way, architects create transparency and build trust.
In practice, this means:
Documenting architecture decisions and their rationale.
Showing alternative scenarios and the trade-offs involved.
Keeping a consistent “line of sight” from strategic objectives down to technical design.
Beyond Methods: The Human Side
Beyond Methods: The Human Side
Frameworks like TOGAF or ArchiMate provide structure, but successful communication depends equally on soft skills: listening, empathy, storytelling. Architects must sense where stakeholders are in their understanding, and adjust the narrative accordingly. A board-level presentation may require metaphor and storytelling, while a design review with engineers demands precision and technical clarity.
Good communication also means courage to challenge. Architects often need to surface blind spots — risks, gaps, or unrealistic assumptions — in ways that are constructive and actionable.
Toward a Communicative Architecture Practice
Toward a Communicative Architecture Practice
In an era of cloud, AI, and rapid transformation, technical knowledge alone is not enough. The most effective architects are those who can:
Build models that invite dialogue rather than dictate answers.
Create visualizations that help leaders grasp complexity without drowning in detail.
Communicate across silos and disciplines, making architecture a shared practice instead of an ivory tower.
As enterprise systems grow more interconnected, the role of the architect is less about producing static blueprints and more about orchestrating communication. In this sense, architecture is a living conversation — and the architect, above all, is its translator.
References
References
ISO/IEC/IEEE 42010:2011 – Systems and software engineering — Architecture description. International Organization for Standardization.
Zachman, J. A. (1987). A Framework for Information Systems Architecture. IBM Systems Journal, 26(3), 276–292.
The Open Group (2017). TOGAF® Version 9.2. The Open Group Architecture Framework (TOGAF®) Standard.
The Open Group (2023). ArchiMate® 3.2 Specification. The Open Group.
Lankhorst, M. (2017). Enterprise Architecture at Work: Modelling, Communication and Analysis. Springer.
Ross, J. W., Weill, P., & Robertson, D. (2006). Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press.
Page updated
Report abuse