A communication pattern is a repeatable organizational practice for sharing information, decisions, and progress among relevant participants. It shapes how teams coordinate and can influence software architecture, delivery flow, and support for change. section 11.1.6 section 15.1.5
Treat communication as part of socio-technical design rather than as an afterthought. Align organizational boundaries, software boundaries, and team interactions so that coordination does not create friction or obstruct independent value streams. section 11.1.6
Making modernization visible
During modernization, technology leaders can establish monthly progress sessions and help teams share updates through text and video. Internal conferences, communities of practice, and office hours provide additional ways to build understanding and enthusiasm without making the enabling team the permanent voice of the initiative. section 15.1.5
Use communication patterns to inspect organizational and delivery friction:
- Compare team responsibilities with software and domain boundaries; mismatches can force teams into shared codebases and repeated coordination. section 11.1.6
- Make progress visible through recurring sessions and varied formats, while gradually distributing communication responsibility across leaders and teams. section 15.1.5
