Vigneshwar’s blog

Exactly enough

Too much traction is friction. Too little is slippage. Every organization eventually picks a side, and it rarely picks on purpose.


Control is the easiest to feel. Add a checkpoint, add a review, add a second sign-off, and the machine visibly slows down. Most operators read that slowdown as proof the process is working. It isn't proof of anything except that traction increased. Whether that traction was needed is a separate question, and it's the one nobody asks, because asking it means admitting the checkpoint might be theater. Organizations default to control not because control works but because control is legible. You can point to it in a postmortem. You cannot point to the incident that didn't happen because someone was trusted to move without it.


Communication fails in the opposite direction, and for the same reason. Under-communicating doesn't look like a decision — it looks like nothing, which is exactly why it survives. Nobody built a system that produces silence on purpose. Silence is just what's left when nobody owns the job of narrating the work. The org chart assigns who does the work. It rarely assigns who explains it. So the explaining defaults to whoever has the least to lose from staying quiet, which is usually everyone, which is how a team ships something real and the rest of the company finds out three weeks later, from someone else.


Follow-up is where the calibration question gets hardest, because follow-up is not one thing. There's follow-up that closes a loop and follow-up that just performs concern. The first one is traction doing its job — it converts an open item into a closed one. The second is friction wearing traction's clothes: the same email, the same tone, sent again not because the situation changed but because checking in felt like doing something. The tell is whether the follow-up carries new information. If it doesn't, it isn't follow-up. It's a status update on your own anxiety.


Hustle is the pair everyone claims to want more of, so it's the one most often mistaken for the answer. Too little hustle is a real failure mode — work sits, decisions drift, nothing closes. But the fix isn't more motion. It's the same calibration question as the other three: does this increment of effort convert into outcome, or does it just look like commitment? An organization that rewards visible hustle over closed loops will get exactly what it measures — people moving fast in front of each other, slippage everywhere it isn't being watched.


None of these four are really about control, communication, follow-up, or hustle. They're about the same underlying failure, worn four different ways: mistaking the presence of traction for the correctness of its amount. Systems default to whichever side is easier to defend after the fact — control and follow-up because they're visible, communication and hustle because their absence is invisible until it isn't. The operator's actual job was never to pick a side. It's to keep asking, pair by pair, decision by decision, whether this is friction, or slippage, or exactly enough.