ARCHITECTURE IS THE VEHICLE FOR STAKEHOLDER COMMUNICATION:

Each stakeholder of a software system-customer, user, project manager, coder, tester, and so on-is concerned with different system characteristics that are affected by the architecture. For example, the user is concerned that the system is reliable and available when needed; the customer is concerned that the architecture can be implemented on schedule and to budget; the manager is worried (as well as about cost and schedule) that the architecture will allow teams to work largely independently, interacting in disciplined and controlled ways. The architect is worried about strategies to achieve all of those goals.

Architecture provides a common language in which different concerns can be expressed, negotiated, and resolved at a level that is intellectually manageable even for large, complex systems .Without such a language, it is difficult to understand large systems sufficiently to make the early decisions that influence both quality and usefulness.

Communication architecture defines the frequency and fidelity of information flow between individuals in your organization. It helps structure how and when you communicate, both within a team and cross-functionally. Having a well-understood communication architecture can help you diagnose trouble spots, so you’re always iterating and improving.

For example, does your engineering team understand your customers’ problems so they can build the right solution? If not, perhaps there’s a breakdown in communication between your sales and engineering teams. Perhaps a monthly meeting between the teams, an email, or some other medium will help. Three months in, does a new hire understand the company’s mission and where it’s going? If not, perhaps your onboarding process could use some work. The specific tactics are unique to each organization, but it requires proactive thought and investment.

Creating a communication architecture starts with understanding your company’s current goals and people. Are you an early-stage startup in a rapidly changing environment with competitors breathing down your neck? Or do you already have a solid foundation, product, and team, and are now focusing on adding structure and scaling?