The pothole is not the problem

The video above is four minutes of me walking one stretch of road in HSR. Ninety seconds in, you can see where last year’s patch has lifted at the seam.

Here is the thing about that seam. It is not evidence that someone did a bad job patching. It is evidence that the patch was applied in the second week of August.

Three problems in a trenchcoat

When people complain about potholes — and I have filed my share — the complaint bundles three genuinely separate failures together:

1. The hole exists. Water got under the surface, traffic did the rest.
2. The hole is not fixed. Someone has to notice, log it, assign it, fund it.
3. The fix does not last. Asphalt laid onto a wet base fails, reliably, in one season.

These have almost nothing to do with each other. The first is physics. The second is a complaint-routing problem. The third is a calendar problem — road budgets get released late in the financial year, tendering eats weeks, and the actual laying lands squarely inside the monsoon, which is the one window where the work cannot cure properly.

Fixing #2 harder — more apps, more escalation, more tagging of official handles on social media — does nothing at all for #3. We have spent a decade optimising the complaint layer of a problem whose bottleneck is a procurement timetable.

What I actually want to know

I want the dates. Not the complaint counts — the tender award dates against the work completion dates, per ward, for three years. If the distribution of completion dates piles up in July and August, then the entire pothole discourse is arguing about the wrong end of the pipe, and it would be visible in one chart.

That data is at least partly RTI-accessible. It is on my list, and when I have it this becomes a Gutte Reports piece with a tier on it instead of a Gutte Speaks piece with a theory on it.

Until then, this is a theory. A confident one, but a theory. See Why this exists for why I am bothering to mark the difference.