Most people are either high maintenance or no maintenance. Clay looks for something rarer: negative maintenance — teammates who make life easier for everyone around them.
This goes beyond doing your job well. Negative maintenance means spotting ambiguity and killing it before it slows others down. It means solving problems upstream, quietly improving systems without being asked — an engineer who fixes bugs before they generate support tickets, a teammate who mentors others now so they need less help later.
The operating question is simple: “What can I do today that will reduce future work for others?”
This connects to Systems that prevent bad behavior beat moral appeals — design the cash register, not the sermon — both are about structural prevention rather than reactive correction. The cash register principle applies to organizational friction: design the system so problems can’t propagate, don’t just ask people to try harder.
It also echoes Compound engineering makes each unit of work improve all future work — negative maintenance is the human-organizational equivalent of compound engineering. Each investment in reducing friction pays forward across every future interaction, not just the current one.
Negative maintenance also means focus: doing 1-2 things at 100% rather than juggling 5 things at 80%. This prevents the hidden cost of context-switching and half-finished work that creates drag for others downstream.