The Org Chart Is the Real Architecture Diagram

There's a party trick I can do. Give me admin access to your marketing automation instance and twenty minutes, and I'll tell you which of your teams don't talk to each other — and roughly when they stopped. I've done this enough times that it's stopped being impressive to me and started being slightly sad, like a fortune teller who's only ever right.

It's not magic, and it's not experience exactly. It's that everything in a marketing stack is a fossilized decision, and decisions have fingerprints. The architecture diagram in your wiki shows what the system was supposed to be. The instance shows what the organization actually did. Only one of these documents is honest.

An old law with new evidence

In 1967, a programmer named Mel Conway observed that organizations design systems that mirror their own communication structures. It got named Conway's Law, and it's been quietly true about everything from compilers to microservices ever since. Conway was writing before marketing automation existed, which I consider evidence of real foresight — because I've never seen a domain prove him harder.

Here's why martech is Conway's Law in its most concentrated form: a marketing stack isn't just built by the organization, it's where the organization's agreements get executed. Lead routing is an agreement between marketing and sales. Lifecycle stages are an agreement about what words mean. Send frequency is an agreement about who owns the customer's attention. When those agreements exist, the automation encodes them. When they don't, the automation encodes the argument instead — workaround by workaround, each one a small monument to a meeting that ended without a decision.

That's the mechanism, and it's worth saying plainly: automation is where unresolved arguments go to become permanent. A dispute that doesn't get settled in a conference room gets settled in production, unilaterally, by whoever had admin rights and a deadline. The stack is the minutes of every meeting that didn't happen.

A field guide to reading the fossils

Some artifacts and their diagnoses, from a decade of doing this:

Three routing campaigns with overlapping logic. A territory dispute nobody won. Each version was built by a different owner who didn't trust — or didn't know about — the previous one. The leads that fall between them aren't a bug; they're the disputed border.

Two fields for one concept — Lead Source, Original Source, Source Detail v2. Marketing and sales each keeping their own books. This is a trust problem wearing a schema. Somewhere in the past, one team's numbers got challenged, and instead of agreeing on a definition, everyone built their own field where their truth could live safely.

Regional workarounds around a global process. Headquarters shipped a standard nobody local believed in. The workarounds are votes. Count them and you have a referendum result on the global template, conducted entirely in smart campaigns.

A wall of exemptions on the communication limits. Nobody owns the recipient's inbox; every team owns its own KPI. The exemption list is the org chart of who was senior enough to escalate.

Everything named _v2_FINAL. Turnover without a handover ritual. Each suffix is a small headstone marking where documented knowledge ended and archaeology began.

Three systems that disagree on one number. Three departments, reporting to three executives, who meet quarterly and politely. The data can't reconcile because the owners never had to.

None of these are technology problems. All of them will be handed to a technologist.

Why cleanup without diplomacy re-haunts

I learned this the expensive way, which I've written about before: I once cleaned an instance beautifully — renamed, restructured, documented, admired — and watched it re-haunt itself inside a year. The ghosts came back because I'd exorcised the symptoms and left the séance running. The two teams still disagreed about routing; they just expressed it in freshly named campaigns.

This is the practical consequence of Conway's Law that most fix-it projects miss: every technical proposal is secretly an organizational proposal, and pretending otherwise just postpones the negotiation. A lifecycle redesign is a treaty between marketing and sales with field mappings attached. A dedupe project is a ruling on whose records win, which is a political question with a merge button. A migration — the big one — is a constitutional convention: the rare moment when every encoded agreement gets re-examined, which is exactly why migrations run long. The hard part was never the data mapping. The hard part is that the data mapping forces decade-old ambiguities to finally pick an answer.

So when I scope any structural change now, I do the boring bilateral work first: get the two owning teams to sign one page of definitions before anything gets built. Signed is the operative word — not "aligned," not "socialized," signed, with names. Then the automation enforces the treaty instead of continuing the war. It's slower by two weeks at the start and faster by two quarters at the end, which regular readers will recognize as the only trade I ever make.

The diagnostic shortcut

All of this yields one genuinely useful habit. When you find something weird in a stack, don't ask "what is this?" first. Ask: "which two teams stopped talking, and when?" Then date the artifact — this is where ISO-dated naming conventions quietly pay for themselves — and check it against the company's history. A workaround dated March 2023 next to a reorg dated February 2023 isn't a coincidence; it's a citation.

This reframe changes what fixing means. The junior instinct is to correct the artifact. The senior move is to trace it to the conversation that never happened, and either have that conversation — belatedly, with better snacks — or document why it can't be had, so the next operator inherits an explanation instead of a mystery.

The diagram with names in it

I still draw boxes and arrows. Systems on the left, integrations in the middle, warehouse on the right — the diagram looks like the tools are the architecture, and clients find it soothing. But after ten years, the diagram I actually trust has names in it: who owns this definition, who signs off on that routing, which two people need to be in the room before this field changes meaning. The tools are where the architecture is stored. The org chart is where it's decided.

Which means the real job — the one no certification covers — is part engineer, part diplomat, part historian of arguments. The title says marketing technology. On the honest days, I'd estimate it's forty percent technology, and the rest is helping organizations say things out loud before the automation says it for them.