Communication

Practice · Chapter 15

Communication

Possibly the most important soft skill for an architect, who must communicate with a wide range of technical and non-technical stakeholders. It is not only what you say but how you say it — understand your message, know your audience, and pick a style that fits.

• More communication across everyone involved raises the odds a project succeeds.
• Stakeholders include developers, testers, business analysts, customers, management, and others.
• Tailor communication to the audience’s technical level.

What an architect must communicate

• The architecture itself — communicate structures, elements, and their interactions to the dev team so they can implement functionality. The architecture imposes constraints that prevent incorrect design decisions; developers must understand them to avoid building non-conforming components.
• Quality attributes — explain how design decisions affect quality attributes (maintainability, availability, performance, security). Discussing tradeoffs with product owners, business analysts, and stakeholders drives these decisions.
• Expectations — feed technical input into project scheduling/resource planning, report status to management, and keep customers in the loop. Goal: eliminate surprises so clients stay satisfied. A project that misses client expectations is not a success.

The 7 Cs of communication

A set of tips for effective communication (the count varies by source; some list five).

C	Meaning
Clarity	Message must be understandable to the receiver; consider audience and purpose; define unfamiliar terms.
Conciseness	Use only necessary words; cut the unnecessary to emphasize what matters; saves time/cost; avoid repetition.
Concreteness	Be specific, not vague; use facts, figures, vivid language, and active voice to reduce misinterpretation.
Courteousness	Be respectful, polite, tactful; be aware of cultural differences; use nondiscriminatory language.
Consideration	Keep the recipient in mind; emphasize “you” over “I/we”; be empathetic to their views and emotions.
Correctness	Information, grammar, spelling, and punctuation must be accurate; builds audience confidence.
Completeness	Include everything needed to act; check the five Ws (who, what, where, when, why); answer questions honestly.

Listening skills

Communication flows both ways — receiving and understanding a message is as important as sending one.

• Hearing is not listening — hearing is an automatic physical process; listening requires deliberate, focused effort.
• Showing empathy — understand another person’s viewpoint; listen more, talk less; ask questions to grasp what they feel, think, or need. Empathy helps motivate the team and build better products.

Tips for effective listening

• Face the speaker and maintain eye contact; be present and attentive.
• Do not get distracted (including by planning your reply while they talk).
• Do not interrupt; defer judgment; wait for a natural pause to respond or ask questions.
• Give verbal/physical feedback (nodding, expressions) so the speaker knows you are engaged.
• Confirm your understanding by asking clarifying questions.

Giving presentations

Architects present to varied audiences — technical talks to dev teams, sales pitches to customers, executive updates to management, proof-of-concept demos to domain experts. Public speaking improves with practice.

The 4 Ps of presentations

1. Plan — define subject and purpose (inform, persuade, or motivate); know who attends and what they expect; settle logistics (date/time, location); become familiar with the venue if possible.
2. Prepare — structure into introduction (short, sets topic), body (main content, major points), and conclusion; make visuals legible (font size, resolution, colors); avoid text-heavy slides; set up and rehearse live demos, planning for what could go wrong (e.g. a local DB copy as fallback); create shortcuts to files/software.
3. Practice — rehearse until intimately familiar to boost confidence and cut nerves; practice in front of others; check timing; drill live demos.
4. Present — be prepared, punctual, and keep to time; dress appropriately; make a good first impression with eye contact, enthusiasm, and adequate volume; apply the 7 Cs; if something breaks, do not panic — recover and end on a positive note.

Related

• Leadership — communication is the foundation of effective leadership.
• Negotiation — being a good communicator and listener underpins negotiating.

Citations

• Software Architect’s Handbook (Packt, 2018), Ch.15 “Communication”, pp. 1077-1099.