{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreign556uxr5gpdw2bla37ngdh3777tpwq5kmi765b4wnslxropkrhu",
    "uri": "at://did:plc:3peywwdnn4jkfvqowpviodbf/app.bsky.feed.post/3mlrv2s47peu2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiawc7pzrovus5qkdkvlpf5v33knibdwttu2r5y72klqmfeud3rngy"
    },
    "mimeType": "image/png",
    "size": 236712
  },
  "path": "/blog/2026/05/13/how-do-i-decode-software-deployments/",
  "publishedAt": "2026-05-13T00:00:00.000Z",
  "site": "https://jeffbailey.us",
  "tags": [
    "Software Engineering",
    "Organization Design",
    "What Is Conway’s Law?"
  ],
  "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  * **Access to the deployed system.** You need to see the service list, runbooks, and on-call rotations.\n  * **Visibility into pipelines and release boundaries.** You need to know which services ship together and which ship separately.\n  * **A blank document or whiteboard.** You will sketch a map as you go.\n\n\n\n## Walk the deployment\n\nTreat deployed software like a fossil record. Every service boundary, API contract, and deployment pipeline carries the imprint of the people who shipped it. Walk the deployment in this order:",
  "title": "How Do I Decode Software Deployments?"
}