<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Organizational Design on shriker.ca</title>
    <link>/tags/organizational-design/</link>
    <description>Recent content in Organizational Design on shriker.ca</description>
    <generator>shriker.ca</generator>
    <language>en-CA</language>
    <lastBuildDate>Thu, 17 Oct 2024 10:09:00 -0600</lastBuildDate><atom:link href="/tags/organizational-design/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Don&#39;t Expect the Codebases to fall in Love</title>
      <link>/dont-expect-codebases-to-fall-in-love/</link>
      <pubDate>Thu, 17 Oct 2024 10:09:00 -0600</pubDate>
      
      <guid>/dont-expect-codebases-to-fall-in-love/</guid>
      <description>&lt;p&gt;The silly creatures are at it again. They have merged two companies and expected the codebases to fall in love. They expected the databases to hold hands and the APIs to understand each other because the marketing department said &amp;ldquo;synergy.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;They are wrong.&lt;/p&gt;
&lt;p&gt;Welcome to Mergers, Acquisitions, and the Art of the Unplanned API.&lt;/p&gt;
&lt;h2 id=&#34;conways-law-is-the-ghost-in-the-machine&#34;&gt;Conway&amp;rsquo;s Law is the ghost in the machine&lt;/h2&gt;
&lt;p&gt;You cannot merge two organizations and keep the old architecture. It does not work that way. The system&amp;rsquo;s architecture reflects the communication patterns of the organization that built it. Structure is not an accident. It is a direct output of how teams interact.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
