{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiairdebpogbrv2yhxzwoew27xypx3wtzzy7rpwz2dlcrvaz6xryte",
    "uri": "at://did:plc:3peywwdnn4jkfvqowpviodbf/app.bsky.feed.post/3mlrv2iti2lt2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreig7mhftzfihjbg4xysisupwopoaadslts6pleicbwom5esn76jhea"
    },
    "mimeType": "image/png",
    "size": 183835
  },
  "path": "/blog/2026/05/13/how-do-i-pitch-org-design-for-better-architecture/",
  "publishedAt": "2026-05-13T00:00:00.000Z",
  "site": "https://jeffbailey.us",
  "tags": [
    "Software Engineering",
    "Organization Design",
    "What Is Conway’s Law?",
    "How Do I Diagnose Delivery Friction?",
    "How Do I Decode a Deployment?"
  ],
  "textContent": "## Prerequisites\n\nThis guide assumes:\n\n  * **Familiarity with Conway’s Law.** Read What Is Conway’s Law? first if “communication structure shapes system structure” sounds new.\n  * **Concrete evidence from your own org.** A diagnosis from How Do I Diagnose Delivery Friction? or a deployment decode from How Do I Decode a Deployment? gives you the artifacts to point at. Without evidence, the pitch sounds like opinion. Start there if you have not yet.\n  * **An audience.** Architects, product leaders, your own team, an open-source community, or conference attendees. The pitch shifts with each.\n\n\n\n## Bring both halves to every conversation\n\nMost conversations about software architecture skip the organizational layer entirely. Engineers debate microservices versus monoliths. Leaders debate team structure in isolation. The two conversations rarely connect. Use Conway’s Law to make the connection explicit.",
  "title": "How Do I Pitch Org Design for Better Architecture?"
}