Renetwork

Draw the problem as nodes and connections, because indirect paths, hubs, and bridges explain behavior that straight-line thinking cannot.

Your friend group is fraying and you can't work out why. You think in pairs: you and Dana are fine, Dana and Marcus are fine, so what's the problem? But groups aren't lists of pairs. One person turns out to be the bridge holding two clusters together, and she just moved away. The straight-line explanations can't see that.

RENETWORK means drawing the situation as nodes and connections, because indirect paths and hubs explain behavior that pairwise thinking cannot. The cue: your one-to-one explanations keep missing something that only shows up through shared nodes. Sketch it: people as nodes, and typed edges between them (organizes, confides in, invites, mediates). Then inspect the topology: who's a hub everything routes through, who's a bridge between clusters, who's become an isolate, where redundancy exists and where a single connection carries everything. Keep the graph small; the spec says to use the smallest graph whose shape changes a prediction or intervention. It works when a structural feature, like the departed bridge, explains what no individual relationship could, and points to a fix: build one new cross-cluster tie. Avoid hairball diagrams with untyped edges; more nodes is not more understanding.