Your Org Chart Is Your Architecture#14
Merged
superterran merged 2 commits intomainfrom Apr 25, 2026
Merged
Conversation
superterran
approved these changes
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Blog Draft — Wild Card
Hook: Conway's Law is not a metaphor in commerce implementations; it is the literal reason your integration map has gaps where your org chart has gaps.
Angle: In mid-market commerce, the integration architecture between systems mirrors the organizational boundaries between teams. When nobody internally owns the seam between the ERP and the OMS, that integration is the one that breaks in production. When the merchant has no single integration owner, both the SI and the storefront partner assume the other is doing contract management. The architecture problem most teams think is technical is actually an org design problem wearing a technical costume.
Source material: Baseline: Merchant-Side Gap 'integrations-out-of-scope carve-out' and 'the carve-out is clean on the slide and contested in the standup'; Baseline: Constellation 'polyglot integration engagements as the new default'; Baseline: Cross-Cutting 'resourcing resilience as a shared concern'; Rolling view: 'Role Definition in Technical Architecture'; Personal notes: Director-of-Engineering-Jacob.md showing Doug's thinking about org design and role boundaries; Baseline: Merchant-Side Gap 'internal staffing duplication in estimates'.
Draft is in
/home/runner/work/dotcom/dotcom/content/blog/2026-04-25-org-chart-is-your-architecture.md. Edit directly on this branch or merge as-is.To publish: merge this PR. The
blog-publishworkflow will auto-generate a LinkedIn post and cross-post it.To discard: close without merging.