Improving Communication between Enterprise Architects and Development Teams

In large enterprises, enterprise architects used to work in a top-down, decree-based manner. However, this approach was often ineffective because there was no shared understanding of what success looked like. Enterprise architects were concerned with the long-term asset value of the IT estate, while development teams were focused on delivering business functionality quickly and efficiently. This lack of shared objectives and context resulted in a disconnect between the teams. To bridge this gap, it is important for development teams to understand the concerns of architects and vice versa. Architects need to communicate what they are worried about, such as log message effectiveness and system recovery, while development teams need to recognize the importance of protecting the IT estate's overall value. Creating awareness in both directions is crucial to enable trade-off conversations and decision-making. It is also essential to change the perception of enterprise architects from being viewed as cost-saving overhead to being seen as value-generating contributors. This can be achieved by demonstrating the outcomes and business value derived from architectural decisions. Additionally, in large enterprises, a shadow architecture organization or other scaling mechanisms may be necessary to support effective communication and collaboration. Ultimately, the goal is to establish a shared context and understanding between enterprise architects and development teams, allowing for productive conversations and successful outcomes.