Every Company Has Two Communication Architectures: A Response to Ben Horowitz
A response to Ben Horowitz.
There is a passage in Ben Horowitz's "The Hard Thing About Hard Things" that has been on my desk in some form for the last decade. "Perhaps the CEO's most important operational responsibility is designing and implementing the communication architecture for her company. Absent a well-designed communication architecture, information and ideas will stagnate, and your company will degenerate into a bad place to work."
He is right.
I would add the layer underneath the architecture he describes.
Every company has two communication architectures. The deeper job, the one I learned the hard way, is keeping them aligned.
The architecture you draw
The first architecture is the one the CEO designs. It is what shows up in the operating manual.
The org chart. The weekly business review. The monthly leadership team meeting. The quarterly board prep. The skip-level one-on-ones. The escalation paths. The Slack channels. The email rules. The dashboard cadence. The decision rights matrix that the COO put together over a weekend.
This is the architecture Ben is naming. It is the one you put in the deck for your first 90 days. It is real and it matters.
It is also not the architecture the company actually runs on.
The architecture that operates the company
The second architecture is the one nobody draws. It runs anyway.
Who texts whom at 9pm before the Monday standup. Who decides over coffee before the meeting starts. Who walks past whose desk before posting in Slack. Who has the side conversation that turns into the real call. Who reads whose calendar to figure out who is gaining influence. Who the new hire is told to "really talk to" in their first week.
This is the architecture your company actually runs on. It exists in every organization, large and small. It is not malicious. It is the natural human response to the gaps in the designed architecture.
The designed architecture is the org's intent. The invisible architecture is the org's truth.
When the two are aligned, the company runs cleanly. When they diverge, the company breaks. And the CEO is the last person to find out.
The meeting that was not on my calendar
In my first year as CEO I drew a clean operating manual. Weekly business review with every metric assigned to an owner. Monthly leadership team meeting. Quarterly board prep. Skip-level one-on-ones on a rolling cadence.
I was proud of the architecture. I had spent two weekends on it. I thought I had built what Ben described.
Six months in, I walked past a conference room and noticed two VPs in a meeting that was not on my calendar. I asked my chief of staff what it was. She said, casually, "Oh, they meet every Tuesday at 7:30 AM."
I checked. Yes, every Tuesday for the prior four months. They had been discussing the product roadmap. They had been making decisions. The decisions were not bad. The meeting was not malicious. It was the natural workaround the team had built because the architecture I designed did not give them a clean place to talk.
I had been the CEO of a system I no longer controlled, and I did not know it.
That afternoon I made a rule for myself that I still carry. Walk the floor. Find the meetings that are not on my calendar. Either bring them into the visible architecture, or change the visible architecture to match where the work is actually happening. Both moves are care. Neither move is punishment.
Three principles I learned the hard way
1. Communication architecture is operating cadence, not tools.
Most first-time CEOs respond to communication problems by changing tools. New Slack instance. New email rules. New project management system. New "town hall" format.
Tools are plumbing. They are not architecture.
The actual architecture is the cadence. The weekly review where every number has an owner. The 13-week operating rhythm where every quarter is a complete cycle. The standing meeting where the team brings the bad news first. These are the architecture. The tools are the pipes the architecture flows through.
I have seen CEOs spend a quarter rolling out a new tool and not understand why nothing changed. The cadence was the same. The tool change was theater.
2. The invisible architecture is reading the visible one.
If your visible architecture rewards politicians, the invisible one will too. If your visible architecture rewards the loudest voice in the room, the side conversations will route around the loudest voice. If your visible architecture rewards truth, the invisible architecture will eventually follow.
The two are not independent systems. The invisible architecture is the company's adaptive response to the incentives the visible architecture sets. Change the visible architecture, and the invisible one will, slowly, follow.
This is harder than it sounds because the visible architecture is what the CEO writes down. The invisible architecture is what the company actually does in response. The lag between the change and the response is what makes most first-time CEOs give up too early. The change takes a quarter to land. Sometimes two.
3. The CEO is the last person to find out.
The team knows the invisible architecture by week two. The middle manager knows it by week six. The CEO often does not know until quarter four.
The discipline of walking the floor, asking what is not in the deck, listening for the meeting you were not invited to, is the only way to close the gap. There is no other tool for this. No survey, no all-hands, no anonymous feedback channel reliably surfaces the invisible architecture. The CEO has to go find it.
This is the part of the job Ben does not quite name. The design of the visible architecture is hard. The discovery of the invisible architecture is harder, because the system is built to keep you out of it.
Architecture is care made visible
There is a teaching in the Indian tradition that I came back to in that first year. The CEO is the householder. The home is held together by the daily routines that everyone knows by heart. The household does not run on the chore chart on the fridge. It runs on the unspoken understanding of who does what, when, and how. The chore chart matters. The unspoken understanding matters more.
Communication architecture is the householder's responsibility. It is care made visible. It is how the household tells the truth to itself.
If you build a household where the truth flows easily, where the routines make care explicit, where every voice has a known route to the keeper of the hearth, the household runs healthily. If you build a household where information has to find a side door, where decisions are made in private conversations between people who like each other, where the keeper does not know what is happening on the third floor, the household degrades. Slowly at first, then quickly.
This is not a metaphor for the CEO seat. It is the seat.
The audit you can run on yourself this week
If you are wondering whether your visible and invisible architectures are aligned, three questions to ask yourself.
One: Name the three decisions made in the company last month that you found out about through Slack DM, hallway conversation, or by reading a deliverable. If the number is greater than two, you have an invisible architecture problem.
Two: Ask three different middle managers, in three separate meetings this week, "what is the meeting that everyone goes to that is not on the official calendar." If you get three different answers, the invisible architecture is more diverse than the visible one. If you get the same answer from all three, the invisible architecture is well-established and you do not control it.
Three: Look at your last two months of one-on-one notes. Count the times you were told something by a direct report that you should have already known. If the answer is more than five, your visible architecture is not surfacing what it needs to surface.
The CEO who passes all three is rare. Most of us, on a good week, pass one.
The harder thing about hard things
Ben's book is rightly named. The hard thing about communication architecture is not designing it. The hard thing is keeping the designed architecture and the operating architecture aligned, quarter after quarter, against the natural drift of human systems.
If you cannot name your invisible architecture, you are not running it. It is running you.
People, products, profits, in that order. Truth, underneath all three. Architecture is how truth flows.
That is the operating principle. It is also, I think, what Ben was pointing at without quite saying.
If this resonated, more operating-journal essays at satya.me.