ticket punching

I recently sent off another report through FixMyStreet, pointing at the horrible state of the roads round here. (I am more than a little disappointed with the Android client app, by the way.) Within a week, some of the worse potholes had been tar’n’gravelled. Meanwhile, even more seem to have appeared or worsened. What it needs is someone to have a look down the street and think about resurfacing, or at least for some sort of statistical alert to fire showing an unusually high level of potholes based on the incoming reports.

I’m not aware that any of the councils are doing anything clever with the stats, which is itself disappointing. All the cool kids, meanwhile, are fascinated by people like Adam Greenfield and his “walkshops on networked urbanism”. He likes the idea of using a ticketing paradigm for things like FMS; I’m not so sure. (More here. First, as friend of the blog Duane Griffin pointed out, geeks love trouble-ticketing and nobody else does.

In fact, Duane’s exact words were that every young programmer eventually decides to design their own ticketing system. (What he didn’t say is that once they have wasted their time and failed, they are no longer young.) I suspect that this is simply a case of the face growing to match the mask – a hell of a lot of IT people spend significant chunks of their time in symbiosis with either a ticketing application, a distributed version control system, or both, and as a result they come to imagine that all the world’s problems are soluble in a typical Sourceforge project page.

Secondly, there is a more fundamental problem with this – it requires problems to be discrete, atomic, and transactional. In fact, as our keen and agile minds will no doubt have noticed, these characteristics are also intrinsic to the MySQL or SQLite databases that underpin these applications. You open a ticket, it gets assigned, it gets updated, it gets closed. But how do you model a persistent or repeating task, or one that involves a relationship rather than a truck-roll? I don’t, in fact, want potholes patching; I would like the road surface to be maintained, which implies changes in Islington Council’s budgeting and management procedures.

And I suspect that an unintended consequence of ticket-based support in general is that it trains everyone involved to prioritise cancelling the noise. Do the minimum necessary to outprocess the ticket. It requires a further, meta-level of analysis to recognise any root causes – there’s a kind of old fashioned Taylorist view of organisation embedded here. If change is needed, it has to come from some sort of management layer analysing the stats. Further, and more subtly, it models the user, customer, or citizen as an entity that is either silent, or whining. You are expected to shut up, until your environment becomes intolerable, at which point you squawk.

Now, Daniel Davies would probably say that negativity is useful. It is harder to contribute positively than it is to oppose stupidity, so you’re more likely to do some good to society by flinging poo than by drafting a manifesto on the future of the Left. He has a point. And Stafford Beer’s Cybersyn actually worked on this principle – enterprises were silent while they could deal with their own problems, and only escalated issues in the system when they encountered something they couldn’t fix themselves. But I can’t help being sceptical that this is any way of organising a city. By the time you get significant numbers of tickets for cracks in a viaduct, your problems are well advanced.


  1. dsquared

    I’m not sure that the negative/positive model is all that applicable to a problem like this – I think your first point is right. Maintaining a road surface is something that there’s a right and wrong way to do, and a ticket system is the sort of thing that could only be of any help if you’re already doing it the wrong way. The trouble is that there probably isn’t a way of solving this problem (not all problems have solutions), in that unless you’re going to be a single-issue voter there isn’t a way of sending a ticket about the entire road-maintenance system.

  2. Cian

    Well there is a solution and its for Islington council to change its priorities. But that becomes a political problem, something almost all geeks seem incapable of understanding, probably because its a social rather than a technical problem. Aaron Swartz is an interesting exception to this.

    Oh, and its github these days, not sourceforge.

  3. AG

    “But that becomes a political problem, something almost all geeks seem incapable of understanding, probably because its a social rather than a technical problem.”

    Well, “geeks” may be incapable of understanding that, Cian, but that happens to be where we start. I mean, you guys’d know this if you actually bothered to look into what happens at a walkshop instead of taking the lazy way out and slagging it as a “kool kids” thing. The whole point, as far as I’m concerned, is to take a good close materialist look at how communities, institutions and individuals contest public space and the public sphere.

    In this case, sure, the lens we’re using is technological. But the concerns predominantly have to do with accountability, agency and control, and the language is everyday. Come join us on a walkshop sometime and contribute your insight, and I think you’d be hard pressed to come away with any other conclusion.

  1. 1 oppression in software « Alternate Seat of TYR

    […] 27, 2010 in architecture, civil service, class, socialism Adam Greenfield responds, and anyone who uses the BOAC speedbird as their avatar is probably worth listening to: “But that […]

  2. 2 Cities and citizenship; fake security and the real thing « Adam Greenfield’s Speedbird

    […] last aspect of the mission is particularly important to me. I’ve seen one or two responses to my recent work suggesting that people understand me to be arguing for the very thing […]




Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s



%d bloggers like this: