← All posts

The agent doesn't absorb your org chart. It executes it

Listen · 2 min 4 s

Three channels, three teams, three release cycles. Nobody designed the divergence between your website, your app, and your partner listings. It’s just what happens when ownership is split and nothing forces reconciliation.

The website team ships weekly. The app team runs its own backlog on its own cadence. Whoever owns the partner feed updates it whenever they remember it exists. None of them talk to each other about what the customer actually sees, because that conversation isn’t in anyone’s job description.

This is Conway’s Law doing what it always does: your channels mirror your org chart, not your product.

For a decade this cost nothing visible. A human hit the mismatch, shrugged, and picked whichever channel seemed more current — or just called to check. That correction happened silently, inside someone’s head, and never once showed up as a ticket.

An agent doesn’t do that. It reads one channel and treats what it finds as ground truth, confidently. Feed it two channels and it has no basis to prefer one over the other, so it either picks arbitrarily or fails outright — and either way it acts on the result.

The org chart that used to stay safely internal now shows up directly in your product’s behavior. The agent doesn’t absorb the cost of your team structure. It executes it, step by step, as if it were policy.

This isn’t a data sync problem you close out once. The divergence keeps regenerating for as long as separate teams ship on separate schedules with no shared source of truth between them. The fix isn’t reconciling the data. It’s deciding, in advance, which channel is authoritative before an agent has to guess on your behalf.

Pick one fact your company states publicly — a price, a policy, a deadline — and trace who last touched it on every channel where it appears.

Discuss on LinkedIn