How can you make system architecture reviews more inclusive?

1 Define the goals and scope

Before you start a system architecture review, you need to have a clear and shared understanding of what you want to achieve and what you want to focus on. A system architecture review can have different goals, such as validating the feasibility and suitability of a design, identifying and resolving issues and gaps, or finding opportunities for improvement and innovation. You also need to define the scope of the review, such as the level of detail, the components and interfaces, and the criteria and metrics. By defining the goals and scope, you can align the expectations and priorities of the reviewers and the architects, and avoid confusion and ambiguity.

2 Choose the right format and tools

The format and tools of a system architecture review can have a significant impact on how inclusive and productive it is. Depending on the size and complexity of the system, the number and location of the reviewers, and the time and budget constraints, you can choose between different formats, such as formal or informal, synchronous or asynchronous, or document-based or presentation-based. You also need to select the appropriate tools that support the communication, collaboration, and feedback of the review, such as video conferencing, chat, document sharing, or diagramming. By choosing the right format and tools, you can ensure that the review is accessible, interactive, and engaging for everyone.

3 Invite diverse and relevant stakeholders

A system architecture review can benefit from the input and feedback of different stakeholders, such as developers, testers, users, managers, or customers. By inviting diverse and relevant stakeholders, you can leverage their expertise, experience, and perspectives, and gain a more comprehensive and holistic view of the system. However, you also need to balance the diversity and relevance of the stakeholders with the manageability and effectiveness of the review. You don't want to have too many or too few reviewers, or reviewers who are not familiar or interested in the system. By inviting diverse and relevant stakeholders, you can foster a culture of inclusion and learning.

5 Provide and solicit feedback

The core of a system architecture review is the feedback that the reviewers provide to the architects, and the feedback that the architects solicit from the reviewers. Feedback is essential for improving the quality and performance of the system, as well as for enhancing the skills and knowledge of the reviewers and the architects. However, feedback can also be challenging, especially when it is vague, inconsistent, or irrelevant. To provide and solicit feedback effectively, you need to follow some best practices, such as being specific, objective, and actionable, using examples and evidence, asking open-ended and probing questions, or acknowledging and appreciating the efforts and contributions of the reviewers and the architects. By providing and soliciting feedback effectively, you can make the review more informative and valuable.

6 Follow up and iterate

A system architecture review is not a one-time event, but a continuous and iterative process. After the review, you need to follow up and iterate on the feedback and the design, and ensure that the actions and outcomes are documented, communicated, and implemented. You also need to evaluate the effectiveness and efficiency of the review, and identify and address any issues or challenges that emerged during the review. By following up and iterating, you can ensure that the review is not a waste of time and resources, but a catalyst for improvement and innovation.

7 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?