<?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"
	>
<channel>
	<title>Comments on: Learning About User Expectations &#8212; The Hard Way</title>
	<atom:link href="http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/</link>
	<description>dissecting the craft of online politics and online advocacy</description>
	<pubDate>Sun, 23 Nov 2008 00:12:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Michael</title>
		<link>http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/#comment-49633</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 27 Mar 2007 00:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/#comment-49633</guid>
		<description>&lt;blockquote&gt;We also sent out an immediate message to our list explaining what had gone wrong and asking people to be patient with us. &lt;/blockquote&gt;

I'm somewhat surprised that sent another email to your list - why did you decide to do this?  Did you have to direct them to another petition page?

&lt;i&gt;&lt;p&gt;No, it was simply courtesy -- as soon as we got rid of that little piece of default text, people were going to start getting an error message when they hit the button as they were used to doing.  This way, they at least had some warning that things were different.  It definitely seems to have helped -- we got several thank-yous and, it was also a good starting point for people who DID write in to complain.  I'd definitely recommend in the future that if you screw something up like that, let the list know!  They're adults and will usually understand the problem and appreciate the communication. -- cpd&lt;/p&gt;&lt;/i&gt;</description>
		<content:encoded><![CDATA[<blockquote><p>We also sent out an immediate message to our list explaining what had gone wrong and asking people to be patient with us. </p></blockquote>
<p>I&#8217;m somewhat surprised that sent another email to your list - why did you decide to do this?  Did you have to direct them to another petition page?</p>
<p><i>
<p>No, it was simply courtesy &#8212; as soon as we got rid of that little piece of default text, people were going to start getting an error message when they hit the button as they were used to doing.  This way, they at least had some warning that things were different.  It definitely seems to have helped &#8212; we got several thank-yous and, it was also a good starting point for people who DID write in to complain.  I&#8217;d definitely recommend in the future that if you screw something up like that, let the list know!  They&#8217;re adults and will usually understand the problem and appreciate the communication. &#8212; cpd</p>
<p></i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Leuthner</title>
		<link>http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/#comment-49624</link>
		<dc:creator>Michael Leuthner</dc:creator>
		<pubDate>Mon, 26 Mar 2007 23:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.epolitics.com/2007/03/26/learning-about-user-expectations-the-hard-way/#comment-49624</guid>
		<description>&lt;blockquote&gt;Turns out, activist groups like ours have trained people to send advocacy messages without a second thought (I doubt many of them even read what theyâ€™re signing). So, when our folks got our alert last week, many of them clicked the â€œsendâ€? button without even scrolling down to see what the message said, just as they always do.&lt;/blockquote&gt;

This is one of the biggest concerns that I've heard from people working on the hill who receive our messages - that when so many messages come in saying the same thing, they are unsure people know, and really support what they are signing.

Without meaning to, this does give a little insite into the number of people this is true of. It must also be said, however, that this doesn't mean that these people didn't read the message sent to them and beleive 100% in the action, and in taking action.

And of course the big take away is, as the author says, we have to be very careful when we are changing the experience for our readers. 

It's a bummer that it happened, but I do appreciate you sharing it. We definately all need the reminder!</description>
		<content:encoded><![CDATA[<blockquote><p>Turns out, activist groups like ours have trained people to send advocacy messages without a second thought (I doubt many of them even read what theyâ€™re signing). So, when our folks got our alert last week, many of them clicked the â€œsendâ€? button without even scrolling down to see what the message said, just as they always do.</p></blockquote>
<p>This is one of the biggest concerns that I&#8217;ve heard from people working on the hill who receive our messages - that when so many messages come in saying the same thing, they are unsure people know, and really support what they are signing.</p>
<p>Without meaning to, this does give a little insite into the number of people this is true of. It must also be said, however, that this doesn&#8217;t mean that these people didn&#8217;t read the message sent to them and beleive 100% in the action, and in taking action.</p>
<p>And of course the big take away is, as the author says, we have to be very careful when we are changing the experience for our readers. </p>
<p>It&#8217;s a bummer that it happened, but I do appreciate you sharing it. We definately all need the reminder!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
