I really enjoyed this post, and that's a great set of questions. I've been doing a lot of similar thinking while developing Poblish - my attempt to create a crowdsourced policy-making platform - so I thought I'd share some of my thoughts and experiences.

My take is that because politics is complicated, and because there are conflicts, constraints, and trade-offs, any system that conceals these inevitable facts of life from users risks producing results that are useless to policymakers. That discredits distributed decision-making - I'm sure online polls and petitions aren't held in high regard - and simply shifts the hard decisions back to bureaucrats, to be made behind the scenes. So I think the challenge has to be to appreciate that people's time is valuable, but to raise expectations about how constructively we can use 30 minutes of it, rather than going for the false economy of trying to reduce political issues down to a 5-second attention-span. Perhaps the idea can be sold to voters along the lines that it's a lot cheaper to spend the time thinking now than to have to unravel a policy that had disastrous unintended consequences?

As for factoring these conflicts and constraints into the policymaking process, what Poblish does is to maintain a political knowledge base - comprising blog posts, wiki pages, Debategraph-style maps, etc. - so that all participants have access to content that is closely related to the issue at hand, updating as they type. So rather than forcing users to think entirely afresh, give them access to a mass of - potentially supporting or opposing - evidence, argument, and experience. Hopefully if that can be done in a seamless-enough kind of way, people might be more likely to read around.

Essentially we take a MixedInk-style approach to policy design: a collaboratively-edited document, with each version weighted by the amount of activity, and the ratings it gets. Because each document itself becomes part of the knowledge base, related policy exercises will have access to its content, hopefully giving a greater chance of producing policies that are consistent. I'm not sure if that's enough to solve the consistency problem, but it's a start.

Yes, "reputation" is a tricky concept: while we want to value constructive contributions, the last thing we want to do is allow the contributions of the 1% of "activists" - the kind of people who will already be well plugged-in, in real-life, and especially online - to crowd out others. The bottom 90% are the people we hear least from, and so I think it's their insights that we really want to capture. Perhaps a solution is to *acknowledge* contributions, but to stick to the idea of non-excludability, i.e. ensure that content-matching is done purely on the basis of relevance, not on the basis of reputation, and don't allow a contribution from a highly "reputable" contributor to trump one from someone else. Do you reckon that's plausible?

As you say, Google just isn't geared up to tracking policy debates, and it's no substitute for having a proper API of structured political content. That's something I had to solve, so that even people who don't use Poblish directly could nonetheless follow the course of a debate in a feed reader, view the activities of an elected representative on a timeline, or hook into the aggregated knowledge base for their own projects. It feels like all this content needs to be easily accessible.

Anyway, lots of food for thought!

posted about 1 year ago