How I organise a civic problem

This is the method I keep reaching for, written down properly for once so I can stop re-deriving it.

Every civic complaint I have ever looked at falls apart into four columns the moment you push on it. The mistake is trying to act before you have separated them.

The four columns

Symptom — what a person actually experiences. “The water comes at 5am for forty minutes.” Not a problem statement, a sensation. Write it in the complainant’s words, not yours.

Mechanism — the physical or procedural chain that produces the symptom. Pressure in the zonal main is only sufficient for the tail end of the line during a narrow window. This is where most people stop reading and start proposing solutions.

Owner — who can actually change the mechanism. Not who is blamed, who has the authority and the budget line. This column is empty far more often than anyone admits, and an empty owner column is itself the finding.

Lever — the smallest thing that moves the mechanism. Usually unglamorous. Usually a schedule, a threshold, or a form.

Why bother

Because a complaint with all four columns filled is actionable by a stranger, and a complaint with only the first column is a feeling. Most civic advocacy runs on column one at very high volume and wonders why nothing shifts.

It also tells you honestly when you are stuck. If I can fill Symptom and Mechanism but Owner comes out empty, then no amount of escalation helps — the work is to establish who owns it, which is a completely different task from fixing the thing.

Applied to roads, this is exactly the argument in The pothole is not the problem — the symptom is a hole, the mechanism is a curing window, and almost everyone spends their energy on a lever attached to neither.

I want to run this properly against water supply in Indore next. That will need actual data, which means it will be a Reports piece, not this kind of piece.