A Caution Before Anything Else
This is the most delicate chapter in the book, and it has to begin with a warning, because the systems language that has served every other chapter can turn ugly here if it is pointed the wrong way. A relationship system is not a machine for extracting value from people. It is not a way to optimize humans, to manage your contacts like inventory, or to automate warmth you do not feel. If that is what systematizing relationships meant, the right move would be to refuse it, and you should refuse any version of this that starts to feel like running a con on the people who matter to you.
good relationships decay through neglect, not malice
What a relationship system actually is, done right, is the opposite of cold. It is a way to protect attention for the people and communities you care about, so that the connections you value do not quietly starve while you are busy. The problem it solves is real and human: good relationships decay through neglect, not malice, and the neglect usually comes not from indifference but from a life full of systems and obligations that crowd the relationships out. The point of bringing system design to this is not to make your relationships efficient. It is to make sure the people who matter actually get your attention rather than losing it by default to whatever is loudest that week. Hold that framing through everything that follows, and the moment it slips toward transaction, stop.
Protect attention for the people who matter, before a busy life quietly starves them.
Connection as a Compounding Asset
With that guard in place, look at what relationships have in common with every other system in this book: they compound, or they decay, depending on whether anything tends them. Trust is the clearest example of a compounding asset. It builds slowly, through many small positive contacts over time, and once built it pays out for years, opening doors, smoothing work, deepening life. Left untended it does the reverse, eroding so gradually that you do not notice until a once-close relationship has gone cold and reconnecting feels awkward and effortful.
That decay is the same entropy from the maintenance chapter, working on human connection. And it points at the same solution: not a grand gesture but light, regular tending, the relational equivalent of maintenance that keeps a system from rotting. The reason connections cool is almost never a decision to let them; it is the absence of any regular contact, so months pass, then a year, and the relationship that mattered is now a name you feel slightly guilty about. A small, steady cadence of genuine contact prevents that entirely, and it costs far less than the heroic reconnection required once a relationship has gone fully cold. The asset compounds when tended and decays when ignored, exactly like every other system, and the tending is cheap while the neglect is expensive.
The Loop and How It Fails
The loop here is simple and should stay simple: genuine contact, which builds trust, which deepens the relationship, which makes the next contact more natural, around again. The cadence is what keeps it alive, a light rhythm of reaching out and showing up, not because a system told you to but because the rhythm ensures the people you care about do not fall through the cracks of a busy life.
The failure modes are easy to recognize. The first is no cadence at all, pure reactivity, where you only contact people when you need something or when an occasion forces it, which is precisely the pattern that makes connection feel transactional, because functionally it is. The second is the opposite danger, the one the whole chapter guards against: cadence that has become mechanical, contact that is technically regular but hollow, the automated birthday message that fools no one and signals that the person has been moved into a system rather than held in mind. The third is letting the relational loop be crowded out entirely by your productive systems, so that the very efficiency you have built ends up costing you the relationships it was supposed to free time for. That last one is the cruelest, because it means the systems worked and you still lost what mattered, having optimized everything except the thing you were optimizing for.
A Quick Audit and One Change
Audit gently here, because the questions are about people, not throughput. The outcome it should produce: the people and communities you care about staying genuinely connected to you over years. The cadence: is there any regular tending, or only reactive contact when something forces it. The feedback: are you noticing which relationships are warming and which are cooling, or only finding out when it is late. For most people the honest finding is that connection runs on pure reactivity, with no tending at all, so relationships survive only if circumstance keeps throwing the people in front of them.
The single change is small and entirely under the warning above: install a light cadence of genuine contact, and keep it genuine. Not a CRM for your friendships, not scripted messages, but a simple, regular prompt to actually reach out to people you would otherwise lose to busyness, with the contact itself remaining real. The system’s only job is to make sure the reaching-out happens; what you reach out with must stay human, or you have built exactly the cold machine this chapter warns against. The structure protects the attention; you still have to actually pay it. Done this way, the cadence does not make your relationships mechanical. It rescues them from the neglect that a systematized, busy life would otherwise impose, which is the whole point.
Keeping the Network Warm
Tie it to the work, carefully. Around your course is a web of real people: students who came through it, collaborators you have worked with, alumni who once cared and have drifted. In the reactive default, all of them cool the moment a term ends, and you only reconnect when you need something, a launch to promote, a favor to ask, which is exactly the transactional pattern that makes people feel used. A light connection loop changes that without making it false. A modest cadence of genuine contact, checking in on how a past student is doing, sharing something useful with no ask attached, staying actually present to the people around the work, keeps the network warm between terms instead of letting it go cold and then trying to reheat it when you want something.
The difference this makes is large and not primarily commercial, though the warmth does pay off in every practical way. Past students return and refer others, collaborators stay glad to work with you, the community around your work stays alive rather than resetting to strangers each term. But the reason to do it is that these are real relationships worth keeping for their own sake, and a busy life full of running systems will starve them by default unless something deliberately protects the attention they need. That is the entire case for this chapter, and the line it must never cross. The systems exist to give you back time and attention; the relationship system exists to make sure some of that reclaimed attention actually reaches the people it was for. Use it to protect connection, never to manufacture it, and it earns its place among the systems that make a life rather than just a body of work.