The architecture of the interstice

Our organizations are built for depth. Streams that train specialists, divisions that file specialists into silos, careers that reward whoever digs the same well ever deeper. This is necessary — nothing serious is done without depth. But look at where ruptures are actually born: almost never at the bottom of a well. Almost always between two wells — when a method from physics illuminates a problem in biology, when a logistics intuition resolves a medical deadlock, when an insurer's reasoning transforms an energy trade.

This space between bodies of knowledge, I call the interstice. It has a cruel particularity: it belongs to no one. No department manages it, no budget funds it, no metric measures it. The specialist does not see it — his very excellence turns him away from it, for one does not build a career in the in-between. And when someone crosses it, we call it luck.

Complexity is not noise. It is a signal — heard only by those who listen between the disciplines.

Those who hear it have a recognizable profile. The polymaths, whom our organizations file badly because they tick several boxes instead of one. The translators — those able to explain department A's problem in department B's language, and whom we confine to coordination when they are doing discovery. Those whose CV « lacks coherence » because it crosses three industries — that is, those who carry three cartographies and see the correspondences. I am one: thirty years across consulting, sales and technology, never quite filing-able, always at the exact spot where two worlds touch without speaking. For a long time I took it for a flaw of trajectory. It was the observation post.

But here is the point that changes the scale: the interstice should not depend on the interstitials. If fertile connections exist only when the right polymath passes the right spot at the right moment, they remain biographical accidents. The serious question is architectural: can the interstice be built? Can an organization's knowledge — and beyond it, the world's — be structured such that improbable rapprochements occur systematically, and not by grace? That a researcher's knowledge capsule meets, six months later, the problem of a practitioner they will never know?

It is an architectural problem in the proper sense: each unit of knowledge must carry enough context to be recognizable outside its well of origin, and a mechanism of attraction must connect what corresponds without anyone having asked. Serendipity then ceases to be a laboratory anecdote and becomes a property of the system. To those who manage what is not written, who see the bridges the specialists ignore: this text is for you — and so is this architecture.