<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Intellitics &#187; innovation</title>
	<atom:link href="http://www.intellitics.com/blog/tag/innovation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intellitics.com/blog</link>
	<description>Experiments in Civic Sensemaking</description>
	<lastBuildDate>Tue, 27 Jul 2010 15:41:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Open Government Dialogue: 26 Tips for Improving Phase 2</title>
		<link>http://www.intellitics.com/blog/2009/06/10/open-government-dialogue-26-tips-for-improving-phase-2/</link>
		<comments>http://www.intellitics.com/blog/2009/06/10/open-government-dialogue-26-tips-for-improving-phase-2/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 15:30:34 +0000</pubDate>
		<dc:creator>Tim</dc:creator>
				<category><![CDATA[Events]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Dialogue]]></category>
		<category><![CDATA[experience]]></category>
		<category><![CDATA[innovation]]></category>
		<category><![CDATA[ogov]]></category>
		<category><![CDATA[opengov]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://www.intellitics.com/blog/?p=342</guid>
		<description><![CDATA[While working on the previous post, I couldn&#8217;t help but think how valuable it would be for participants, researchers and everyone else interested if these high-level participation metrics were readily available in real-time on the site that hosts the discussion, rather than having to dig them up manually and deal with incomplete information, assumptions and more or [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>While working on the <a href="http://www.intellitics.com/blog/2009/06/09/open-government-dialogue-phase-2-metrics-update/">previous post</a>, I couldn&#8217;t help but think how valuable it would be for participants, researchers and everyone else interested if these <em>high-level participation metrics</em> were readily available <em>in real-time</em> on the site that hosts the discussion, rather than having to dig them up manually and deal with incomplete information, assumptions and more or less wild guesses.</p>
<p>Some of the numbers I usually like to track over the course of an e-participation initiative include the following (these are all pretty straightforward and a number of tools recently used by the transition team and the new administration already expose some of them by default):</p>
<ul>
<li>Number or registered users</li>
<li>Number of posts (or ideas, questions etc.)</li>
<li>Number of comments</li>
<li>Number of votes</li>
<li>Number of flags</li>
<li>Total word count</li>
<li>Participation per participant (e.g. average number of comments, median)</li>
<li>Leader boards (where applicable)</li>
</ul>
<p>Others &#8212; both participants and observers &#8212; have pointed out other issues with the site that make it harder to use than necessary.</p>
<p>Based on their feedback and some of my own observations, I&#8217;ve compiled a list of 26 enhancement ideas that would considerably improve the <em>participation experience</em> during phase 2 of the Open Government Dialogue and increase the overall quantity and quality of participant input.</p>
<p>Some of these refer specifically to the tool used for phase 2 (Wordpress blogging engine for threaded discussions and a plug-in for comment rating) but most should be generally applicable across other tools as well.</p>
<p>I&#8217;m sure the list is far from complete. Please leave a comment below if you can think of anything else that could be improved.</p>
<p><strong>Registration</strong></p>
<ol>
<li value="1">Improve the usability of the sign-up process (including a better fall-back solution for CAPTCHA, which a lot of users apparently can&#8217;t seem to figure out).</li>
</ol>
<p><strong>User profile</strong></p>
<ol>
<li value="2">Add a prominent link to the <a href="http://blog.ostp.gov/wp-admin/profile.php">user profile self-management page</a>, where participants can edit their name, contact information, password etc.</li>
<li>Add a public user profile page that allows participants to voluntarily reveal more background on their real identity (e.g. by sharing their name, <a href="http://www.flickr.com/photos/planspark/3602408344/in/set-72157618585823580/">affiliation</a>, a brief bio, photo/avatar, link to their personal blog etc.).</li>
<li>On each participant&#8217;s profile page, list some basic participation metrics for that user and link back to all of her comments (this also makes finding one&#8217;s own comments a lot easier than, say, having to browse the entire archive).</li>
</ol>
<p><strong>Commenting</strong></p>
<ol>
<li value="5">Allow participants to edit or delete their comments for a reasonable time period after posting (e.g. to correct <a href="http://www.flickr.com/photos/planspark/3602330282/in/set-72157618585823580/">typos</a> or remove <a href="http://www.flickr.com/photos/planspark/3601456251/in/set-72157618585823580/">duplicate entries</a>).</li>
<li>Consider imposing smart limits on the maximum number of characters allowed per comment to avoid overly lengthy submissions.</li>
</ol>
<p><strong>Navigation</strong></p>
<ol>
<li value="7">Add <a href="http://en.wikipedia.org/wiki/Permalink">permalinks</a> to comments for easier referencing and sharing across the web (e.g. using email, blogs, Twitter etc.).</li>
<li>Highlight <a href="http://www.flickr.com/photos/planspark/3599691990/in/set-72157618585823580/">staff contributions</a> more prominently.</li>
<li>Display posts and threads in <a href="http://www.flickr.com/photos/planspark/3601633791/in/set-72157618585823580/">chronological order.</a></li>
<li>Provide a more robust tree structure, one that properly associates replies with the comments they refer to (even if one or more comments from a thread have been hidden or removed) and which supports better browsing and sorting of comments and threads (e.g. show most recent posts or most recently active threads).</li>
<li>Highlight recently added comments.</li>
<li>Allow tagging of posts and comments.</li>
<li>Add a tag cloud.</li>
<li>Add a searchable directory of all registered users that supports various filters (e.g. sort by most active users, most recently joined, most highly voted etc.).</li>
</ol>
<p><strong>Notifications</strong></p>
<ol>
<li value="15">Add a prominent link to the general comment RSS feed as an alternative way to follow the discussions: <a href="http://blog.ostp.gov/comments/feed/">http://blog.ostp.gov/comments/feed/</a></li>
<li>Enable email notifications for new or updated blog posts, comments and replies.</li>
</ol>
<p><strong>Comment voting</strong></p>
<ol>
<li value="17">Allow participants to correct (take back or switch) their up or down votes on comments.</li>
<li>In the meantime (and at a minimum), make participants better aware of the fact that votes cannot be changed once submitted.</li>
<li>In addition, improve the usability of the voting (vote up, vote down), flagging and reply buttons: the icons aren&#8217;t clear enough and the buttons are fairly small, both factors that can lead to accidental <a href="http://www.flickr.com/photos/planspark/3595659391/in/set-72157618585823580/">mis-voting</a>).</li>
<li>In addition to net number of votes, expose the total number of positive and negative notes for each comment.</li>
<li>Expose <em>controversiality</em> (the ratio of negative to positive votes).</li>
</ol>
<p><strong>Moderation</strong></p>
<ol>
<li value="22">For comments that have to be removed due to a violation of the terms of participation, leave a note that references the type of violation.</li>
<li>In case a comment is removed, notify the original poster of her offense (we don&#8217;t know for sure if this is done consistently but judging from user feedback it&#8217;s not).</li>
</ol>
<p><strong>General</strong></p>
<ol>
<li value="24">Add an FAQ or help page.</li>
<li>Add a statistics page that shows the number of registered users, number of comments, number of votes and number of flags over time.</li>
<li>Add site-wide search (currently comments don&#8217;t seem to show up in search).</li>
</ol>
<p>That&#8217;s all I could find over the past week. Please expand on this list as you come across other stumbling blocks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.intellitics.com/blog/2009/06/10/open-government-dialogue-26-tips-for-improving-phase-2/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>
