Insight

Friction is Invisible by Design

Failure has a shape an organization already knows how to see. A project cancelled. A system down. A customer gone. Something happened, on a date, and someone can be asked about it.

Friction produces none of that. It produces a week in which everyone worked hard on reasonable things and very little moved, and there is no meeting for that. No incident review is convened because a decision took eleven weeks instead of two, because nobody experienced the eleven weeks as an event. They experienced it as a calendar.

This is why friction is almost always described in the language of effort rather than the language of structure. We’re stretched thin. We’re under-resourced. There’s a lot going on right now. Each of those is a true description of how it feels and a wrong diagnosis of what it is — and each one points toward adding something, which is the response that reliably makes it worse.

The invisibility isn’t accidental, and it isn’t anyone’s fault. It follows from where friction lives. It doesn’t sit inside anyone’s work, where it would show up in their numbers. It sits in the space between people’s work: the handover, the wait, the question that had to travel. Those spaces appear on no org chart, belong to no budget line, and have no owner — which means nobody is measured on them, and nobody is failing when they get worse.

The practical consequence is that friction has to be looked for on purpose. It will never surface on its own, because nothing about it triggers the mechanisms an organization uses to notice trouble. By the time it’s visible as a result, it has usually been the cause for years.