In this episode of the #AzureEnablementShow, our #ArmchairArchitects—Uli and Eric (https://www.youtube.com/channel/UCbQ5FSOvQ311EM3v_e7QwlQ)—discuss Melvin Conway’s law, which states that organizations will often design a system that mirrors their organizational structure. Can good leadership and clearly defined goals mitigate the effects of Conway’s Law? Resources • Melvin Conway https://www.melconway.com/ • Conway’s Law https://en.wikipedia.org/wiki/Conway%27s_law To watch more episodes in the Well-Architected series, check out our playlist: https://aka.ms/azenable/yt/wa-playlist To watch more episodes in the Armchair Architects series, check out this playlist! https://aka.ms/armchairarchitects Chapters 0:00 Introduction 1:22 What is Conway’s Law? 2:22 How does Conway’s Law intersect with software architecture? 3:15 Shipping your org chart is bad architecture and zero leadership 5:40 Is it bad to build an organization that mirrors your architecture? 6:45 When should you consider a re-org vs. creating virtual teams? 10:00 Conway’s Law is real, but architecture and leadership can help 11:23 Re-orgs are expensive and painful, and not always successful 12:52 Clearly-defined outcomes and guardrails can minimize the effects of Conway’s Law 14:23 Does your organizational structure support or denigrate your outcomes? 14:55 Individuals need to understand their role in an organization #AzureEnablementShow #ArmchairArchitects #Azure