In Edition 3<\/a> I shared the whole book as fifteen sentences. One of them claimed that coherence is a measurable property with five dimensions. A few of you wrote back with a fair question. Which five?<\/p>\n\n\n\n So as the launch nears, I put up a reference page that answers it, and answers the larger question in the title of this edition. What is organizational coherence?<\/p>\n\n\n\n Here is the short version. Coherence is your organization’s capacity to see what its autonomous systems are doing, judge whether they are doing it well, and correct them when they are not.<\/p>\n\n\n\n People sometimes hear coherence as something soft, a feeling of alignment or a good culture. It is neither. It is an operational capability, and you can have a lot of it, very little, or somewhere in between. Put another way, coherence is the integrity of the link between what a local part of the company does and what the whole enterprise intends. When that link holds, the parts serve one purpose. When it breaks, each part can be right on its own terms while the enterprise drifts.<\/p>\n\n\n\n That link can fray in five places, which is why coherence has five dimensions.<\/p>\n\n\n\n Each maps to a specific way organizations fail, and each can be measured and built. The page walks through all five, along with the ideas around them: the Coasian Inversion, complexity debt, agentic slop, and how coherence differs from governance and alignment. Check out the full reference page here: What is organizational coherence?<\/a><\/p>\n\n\n\n Three posts from the past week.<\/p>\n\n\n\n Uninformed Expectations, Five Years Later.<\/a> Five years ago in an interview, I was asked about the single biggest roadblock to AI ROI. I had said back then that it was uninformed expectations, and predicted disillusionment. Here we are today, years into the enterprise AI rush, and my answer to the question is still the same. The reason, however, is completely different. Weigh in on LinkedIn…<\/a><\/p>\n\n\n\n Coding Got Easy, But What Kind?<\/a> I read a passionate post about what makes the profession of writing code human, and the author takes exception to the framing “code was never the hard part.” That statement, read at face value, can be true and false at the same time, depending on what you mean by coding. Producing instructions that run, yes. Building a software system that lasts, no. Weigh in on LinkedIn…<\/a><\/p>\n\n\n\n The Machinery Under Manners.<\/a> Reid Hoffman wrote about a convention people use in professional networking. When asked for an introduction to a contact of yours, you check with the other person first and then make the introduction if they are willing to entertain it. But that “permission check” is not just courtesy, it is a structural mechanism. And agents especially need such structural constraints since they don’t face our social and societal constraints. Weigh in on LinkedIn…<\/a><\/p>\n\n\n\n One thread runs through all three. Each takes a surface we trust, an expectation, a line of code, a courtesy, and shows that what makes it really work sits underneath, out of view. Remove the hidden structure and the surface keeps looking fine right up until it fails. That gap between what shows and what holds is the whole subject of the book.<\/p>\n\n\n\n A reminder about the favor from last week<\/a>, because timing matters. SXSW community voting closes August 23. If the book’s argument has been useful to you, a vote helps carry it to a stage in Austin next March. Vote here.<\/a><\/p>\n\n\n\n\n
The week in ideas<\/h3>\n\n\n\n
Before you go<\/h3>\n\n\n\n