<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for BARcamp Chicago</title>
	<atom:link href="http://barcampchicago.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://barcampchicago.org</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Thu, 07 Jul 2011 17:53:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Some Ideas To Hack On at BARcamp This Year by Bill Scheurer</title>
		<link>http://barcampchicago.org/2011/07/some-ideas-to-hack-on-at-barcamp-this-year/#comment-15</link>
		<dc:creator>Bill Scheurer</dc:creator>
		<pubDate>Thu, 07 Jul 2011 17:53:40 +0000</pubDate>
		<guid isPermaLink="false">http://barcampchicago.org/?p=131#comment-15</guid>
		<description>KarmaKorn is looking for hackers and designers who want to help build a #GoodSpotting game to help take the existing cash-for-causes contest model to the next level.

Contests like Pepsi Refresh and Chase the Good have donated a lot of money to the winning nonprofits, but they suffer from 3 fundamental design flaws: 

1) Their system of voting for nonprofits is meaningless. An empty vote does nothing to advance the mission of the cause except for trying to help them win. What a wasted opportunity. Instead, we can have some kind of meaningful action count as a &quot;vote&quot; in the contest. 

2) Their winner-takes-all system for awarding the cash prizes distorts nonprofit behavior and creates a poorly engineered incentive-disincentive dilemma for participating nonprofits: Do we think we can win? If so, go all out. If not, stop participating. 

3) The combination of 1) &amp; 2) results in an erosion of social capital for participating nonprofits, instead of an increase in their social capital. They relentlessly flog their lists trying to scour meaningless votes to win the cash prize -- basically, a spam-like activity. This wears on the good will, patience and attention span of their fans and supporters, while doing nothing for these key people or for the nonprofits themselves.

We have conceived a better way to run these contests/games, and would like to find hackers and designers to help us build the first one.</description>
		<content:encoded><![CDATA[<p>KarmaKorn is looking for hackers and designers who want to help build a #GoodSpotting game to help take the existing cash-for-causes contest model to the next level.</p>
<p>Contests like Pepsi Refresh and Chase the Good have donated a lot of money to the winning nonprofits, but they suffer from 3 fundamental design flaws: </p>
<p>1) Their system of voting for nonprofits is meaningless. An empty vote does nothing to advance the mission of the cause except for trying to help them win. What a wasted opportunity. Instead, we can have some kind of meaningful action count as a &#8220;vote&#8221; in the contest. </p>
<p>2) Their winner-takes-all system for awarding the cash prizes distorts nonprofit behavior and creates a poorly engineered incentive-disincentive dilemma for participating nonprofits: Do we think we can win? If so, go all out. If not, stop participating. </p>
<p>3) The combination of 1) &amp; 2) results in an erosion of social capital for participating nonprofits, instead of an increase in their social capital. They relentlessly flog their lists trying to scour meaningless votes to win the cash prize &#8212; basically, a spam-like activity. This wears on the good will, patience and attention span of their fans and supporters, while doing nothing for these key people or for the nonprofits themselves.</p>
<p>We have conceived a better way to run these contests/games, and would like to find hackers and designers to help us build the first one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

