The Observation

I’ve been keeping notes in this vault for two years. Hundreds of calls, meetings, emails, references, thought cards. All wiki-linked, all tagged, all searchable. I thought the value was in the search. Find the note, read the context, prepare for the call.

Then we added community detection. A clustering algorithm that groups nodes by edge density. Nothing fancy. Runs in 50 milliseconds. And suddenly I could see that my vault has 32 natural communities. Association operations is one cluster. State chapters are another. Client work is a third. Thought cards live in their own world, almost entirely disconnected from the operational clusters where the ideas actually apply.

That’s information I didn’t have yesterday. Not because the data was missing, but because the structure was invisible.

What Changes When Structure Is Visible

The first thing we computed was “god nodes,” the most structurally central entities in the graph. The trade association I chair scored 1.0. My own company scored less than half that. That ratio says something I wouldn’t have articulated on my own: the association is more than twice as central to my vault as the company I own. Whether that’s a problem or a feature depends on the season, but I wouldn’t have seen it without the number.

The second thing was multipliers. People whose connections span three or more communities. One contact bridges a dozen. Another bridges eight. I knew both were important. I didn’t know the quieter one was structurally more connected than the association’s CEO, who’s the person I talk to most. One is a connector. The other is a hub. Those are different roles, and they need different kinds of investment.

The third thing was emerging contacts. People I’m talking to a lot right now who aren’t structurally integrated yet. One consulting client has ten notes in 30 days and a community reach of two. I’ve been deep in strategy work with him, generating thought cards and essays from those conversations, but almost none of it connects back to the rest of the vault. The ideas are flowing. The structural integration isn’t.

That’s a signal I would have missed for months.

The Principle

We default to managing relationships by feel. Who called recently, who’s top of mind, who asked for something. Feel is fast but it’s biased toward whatever happened last and whoever’s loudest in your head. The person who emailed you yesterday feels more important than the person who bridges a dozen communities but hasn’t emailed in a week.

Structure doesn’t replace feel. It corrects for the blind spots. The graph doesn’t tell you who to care about. It tells you where your time is actually building something, and where it isn’t.

The auction industry runs on relationships. Everyone knows that. But knowing that your relationship investment is concentrated in one cluster while another cluster has zero multipliers, that’s operational. That changes what you do on Monday morning.

What’s Open

  • The ROI metric combines structural importance with velocity. The top contact scores 0.96. But ROI assumes the current structure is the one you want. What if the right strategic move is to deliberately build bridges into an underconnected community? The metric rewards maintaining the existing network shape. It doesn’t reward reshaping it.
  • The ideas cluster and the operations cluster are separate worlds. My thinking about the industry and my operational work in the industry don’t cross-pollinate in the graph. Is that a documentation gap, or is the separation real? If it’s real, what does it mean that the ideas aren’t grounded in the operations?
  • The emerging contacts signal catches people with high recent velocity but low reach. It doesn’t catch people with low velocity who should have high reach. The person you’re not talking to but should be. That’s the harder question, and the graph can’t answer it alone.