Near-Decomposability

The same structure that makes a specialist good at their specialty is the structure that makes certain real connections invisible from inside it. That's not a staffing problem. It's a shape problem.

September 3, 2026 6 min read

Strategy's weekly report says the roadmap is on track. Sales says pipeline is healthy. Support says ticket volume is down. Every domain looks fine, because every domain report is accurate. A customer churned the week after a pricing change, and the actual reason lived entirely in the gap between two of those reports, a change strategy made for good reasons, landing on an account sales had flagged as price-sensitive three months earlier in a note nobody in strategy ever had reason to read. Nobody lied. Nobody missed their own job. The thing that mattered was never inside either job to begin with.

Depth in one place is bought with blindness at the edges

This isn't a hiring gap or a communication failure waiting on a better Slack channel. It's closer to a structural fact: the same narrowness that lets a specialist go deep on one domain is what makes the connections between domains invisible from inside any one of them. A strategy team that tracked every downstream sales implication of every roadmap decision wouldn't be a strategy team anymore, it would be doing sales's job too, at the cost of the depth that made its own judgment worth having. Depth requires a boundary. A boundary, by definition, is the place past which you stop tracking things closely.

That trade isn't a design mistake to be corrected. It's closer to the only way specialization can work at all. Every function that gets good at anything does it by narrowing what it pays close attention to, and the price of that narrowing is a set of real connections that cross the boundary and land in nobody's job description. The question isn't how to staff away that gap. It's what kind of thing could actually sit in it.

Where this gets its name

Systems theory has a name for exactly this shape, and a memorable illustration of why it holds up across very different kinds of systems. In 1962, Herbert Simon published "The Architecture of Complexity" (Proceedings of the American Philosophical Society), a few sections into which he introduces a parable about two watchmakers. Hora built watches from subassemblies of about ten parts each, combined into larger and larger units. Tempus built his watches one part at a time, in a single unbroken sequence. Both were interrupted constantly by phone calls. Every interruption cost Tempus everything, an incomplete watch with no fixed subassemblies fell completely apart the moment he set it down, so he rarely finished one. Hora's partial subassemblies held their shape when he set them down, so an interruption cost him at most the piece he was working on, not the whole watch. Simon's point was that complex systems which persist tend to be built the way Hora built watches: organized into subsystems with dense interaction inside each one and comparatively sparse, weak interaction between them, a property he called near-decomposability. It isn't an accident that stable complex systems look this way. It's close to the only shape complexity can survive being built and disrupted in.

The honest limit: the sparse connections are still real connections

This isn't an argument that specialization is a mistake, or that near-decomposability is something to engineer away. Simon's whole point cuts the other direction: a system with no boundaries at all, where everything is tightly coupled to everything, is the Tempus case, fragile, uncoordinated, and unable to make steady progress anywhere, because nothing can be worked on in isolation. The weak coupling between subsystems is what makes each subsystem tractable in the first place, not a flaw sitting alongside the useful part of the structure.

What near-decomposability doesn't promise is that the sparse connections between subsystems are unimportant, only that they're rare and easy to miss precisely because each subsystem is built to be busy with its own dense internal work. A pricing decision landing on a price-sensitive account is exactly this kind of connection: real, consequential, and structurally unlikely to be caught by either side of the boundary it crosses, because catching it was never what either side was built to do.

Where this fits at Brief

This is the shape of the job CPO Agent is described as doing: reading across every domain and surfacing the cross-cutting insight no single agent would catch on its own, in Brief's own words for it. That description matches the boundary problem exactly. A domain-specific agent, whichever one, is doing its job well precisely by staying inside its own dense interior and not trying to track every sparse link running out of it. The insight that only exists in the connection between two domains was never going to come from inside either domain's own reporting, not because either one failed, but because catching it needs something positioned to look at the gap itself.

Somewhere between your team's separate, individually accurate reports this week, is there a connection sitting in the gap that no single one of them was ever built to catch?

Frequently asked questions

What is near-decomposability? A property of complex systems, described by Herbert Simon, where the system is organized into subsystems with dense, frequent interaction inside each one and sparse, weak interaction between them. It's offered as close to a structural necessity for complex systems that have to survive being built up gradually and disrupted along the way, not an incidental design choice.

Where does the term come from? Herbert Simon's 1962 paper "The Architecture of Complexity," which uses a parable about two watchmakers to make the case: one who builds from stable subassemblies and recovers quickly from interruptions, and one who builds in one continuous sequence and loses everything each time he's interrupted. Simon uses it to argue that stable complex systems tend to be organized hierarchically, with weak coupling between subsystems, for exactly this reason.

Doesn't that mean specialized teams or agents are the problem? No. The same weak coupling that creates blind spots between domains is what makes each domain tractable to work in at all. A system with no boundaries, everything tightly coupled to everything, is worse, not better, closer to the watchmaker who loses his whole watch every time he's interrupted. The blind spots are a real cost of a structure that's mostly a benefit.

Why does Brief have a CPO Agent instead of expecting each domain agent to catch cross-cutting issues itself? Because catching a connection that runs between two domains isn't something either domain's own close, dense work is built to do, that's what makes each domain's work effective in the first place. Something has to be positioned to look at the sparse connections between domains rather than inside any one of them, which is the job Brief describes CPO Agent as doing.