Communication Patterns for Architects and Engineers with Jacqui Read

Communication Patterns for Software Architects

• Jacqui Read, an internationally recognized solution Enterprise architect and author of "Communication Patterns: A Guide for Developers and Architects," believes that every software problem can be traced back to a communication problem.
• Read argues that effective communication is crucial for software to function well, as it enables teams to collaborate effectively.

Importance of Communication Skills for Architects

• She emphasizes the importance of communication skills for individuals in architecture roles, as they often act as bridges between different groups within a company, including highly technical teams, less technical individuals, and business stakeholders.
• Read highlights the significance of communication skills for career advancement, stating that individuals who can communicate effectively are more likely to be promoted to leadership positions.

Communication Patterns as a Framework

• She advocates for the use of "communication patterns" as a framework for improving communication skills, drawing a parallel to software and architecture patterns.
• Read explains that communication patterns provide a structured approach to communication, offering templates and guidelines that can be adapted to specific situations.

Practical Application of Communication Patterns

• Read's book, "Communication Patterns," is designed to be accessible and practical, allowing readers to focus on specific patterns as needed.
• The speaker discusses communication patterns for architects and engineers, emphasizing the importance of context-specific application.

Types of Communication Patterns

• The speaker divides communication patterns into four sections: visual, multimodal, remote work, and knowledge.
• The speaker highlights the importance of considering synchronous versus asynchronous communication, suggesting that announcements are often better suited for asynchronous communication unless immediate feedback is required.

Challenges of Remote Communication

• The speaker notes that remote work presents unique challenges for communication, as it can be difficult to read body language and facial expressions through a screen.
• The speaker suggests that presenters should be mindful of their gestures and energy levels when communicating remotely, as these can be harder to convey through a camera.

Addressing Zoom Fatigue

• The speaker acknowledges the phenomenon of "Zoom fatigue" and suggests that turning off one's own video and taking breaks from staring at a screen can help mitigate this.
• The text discusses the importance of being mindful of communication patterns, especially in virtual settings, and how they can lead to "Zoom fatigue."

Visual Communication Patterns

• It highlights the need for visual communication patterns in architecture and engineering, particularly in the creation of diagrams.
• The text identifies a common anti-pattern in visual communication, referred to as a "spiders web," where diagrams are cluttered with boxes, lines, and labels, making them difficult to understand.

Improving Visual Communication

• It suggests solutions for improving such diagrams, including:
  • Moving boxes around to improve layout.
  • Removing unnecessary information or moving it to separate diagrams.
  • Using orthogonal lines (right angles) for better control and clarity.
  • Standardizing label placement for easier readability.

Principles of Effective Diagram Design

• The text emphasizes the importance of considering audience, context, and purpose when creating diagrams, and the need to avoid over-communication.
• It suggests decomposing large diagrams into logical sections for better understanding.

Organizing Diagrams with the C4 Model

• When creating diagrams, it is important to break down information into different levels to avoid overwhelming the reader.
• The C4 model is a useful tool for organizing diagrams into levels, starting with a context level that shows the system, users, and external systems.

Using Layers in Diagram Software

• Using layers in software like draw.io allows for hiding or showing specific information based on the audience or purpose of the diagram.
• Consistency in color and semantic information is crucial for easy understanding.

Color and Accessibility in Diagrams

• While blue is often a good choice for printing and colorblind accessibility, relying solely on color for communication can be problematic.
• Using color only when it has a specific meaning and avoiding excessive colors can improve comprehension.

Enhancing Accessibility for Colorblind Individuals

• Black and white can be effective for highlighting specific elements in a diagram.
• To ensure accessibility for colorblind individuals, using symbols, labels, and patterns in addition to color can enhance understanding.

Communication Beyond Drawings

• The speaker discusses the importance of accessibility in design, highlighting the need to consider color blindness and contrast levels. They use the example of Excel's grid lines, which are a lighter shade of gray to avoid being as visually prominent as the text.
• The speaker emphasizes that communication in architecture extends beyond drawings, requiring effective written and verbal communication with various stakeholders, including business people, security personnel, and executives.

Communicating Knowledge

• The speaker introduces the concept of "communicating knowledge" as opposed to simply documentation. They argue that knowledge is not always explicitly documented and that implicit knowledge held by individuals needs to be made explicit.
• The speaker suggests treating information as "products" rather than "projects" to avoid losing or duplicating information. They explain that projects may be temporary, but the product they work on may have a longer lifespan and require ongoing development.

Perspective-Driven Documentation

• The speaker advocates for "perspective-driven documentation," which focuses on tailoring information to specific stakeholders' needs. They suggest using a wiki to create one-page views for each stakeholder, addressing their specific requirements.
• The speaker highlights the applicability of coding principles, such as the DRY (Don't Repeat Yourself) principle, to architecture and business. They also mention the single responsibility principle, which can be applied to diagrams.

Understanding Software Through Teaching

• The speaker emphasizes the importance of understanding software to improve it, particularly when dealing with legacy software. They suggest that teaching a subject can deepen one's understanding, as it requires thorough research and preparation.

Architecture Decision Records (ADRs)

• Architecture Decision Records (ADRs) are a valuable tool for documenting decisions made by architects and other stakeholders.
• ADRs should include not only the decision itself but also the reasoning behind it.

Benefits of Using ADRs

• This documentation helps to ensure that decisions are understood and can be revisited in the future.
• ADRs can be used to facilitate discussions and collaboration among stakeholders, including those who are not architects.

ADRs for Business Stakeholders

• ADRs can be used to justify decisions to business stakeholders, particularly when it comes to decisions that involve significant costs, such as re-architecting a system.
• ADRs can be used to help make decisions by bringing stakeholders together early in the process to discuss the context, priorities, and options.

Decision-Making Process

• It is better to involve everyone in the decision-making process rather than trying to convince them after a decision has been made.
• Consensus is not always necessary for a decision to be made.

Commitment to Decisions

• Individuals can commit to a decision even if they do not agree with it.
• Decision owners should work with individuals who believe a decision is unsafe.

Business Decision Records

• Business decision records can be used to document the rationale, context, and options considered for a decision.
• Business decision records can be helpful for various business functions, including strategy setting, procurement, contract renewals, and policy reviews.

Structure of Business Decision Records

• The basic structure of a business decision record should include the options considered, the importance of each option, the decision made, and the rationale for the decision.
• Business decision records can help businesses function more effectively by providing a clear record of decisions and their rationale.