<?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>Usability Thoughts &#187; call to action</title>
	<atom:link href="http://usabilitythoughts.com/tag/call-to-action/feed" rel="self" type="application/rss+xml" />
	<link>http://usabilitythoughts.com</link>
	<description>content meets user</description>
	<lastBuildDate>Thu, 12 Jan 2012 09:02:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>So wrong on so many levels</title>
		<link>http://usabilitythoughts.com/so-wrong-on-so-many-levels.html</link>
		<comments>http://usabilitythoughts.com/so-wrong-on-so-many-levels.html#comments</comments>
		<pubDate>Mon, 19 Oct 2009 11:39:31 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[Patterns]]></category>
		<category><![CDATA[Usability fail]]></category>
		<category><![CDATA[buttons]]></category>
		<category><![CDATA[call to action]]></category>
		<category><![CDATA[forms]]></category>

		<guid isPermaLink="false">http://usabilitythoughts.com/?p=175</guid>
		<description><![CDATA[I have update the &#8220;All in one seo pack&#8221; for wordpress and it insisted that i update the configuration page. I went and checked the page an this is what i have found:

It amazes me how awful is this form made, I think it&#8217;s deliberately made so you fuck up. Let&#8217;s see why:
1. the &#8220;Reset&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>I have update the &#8220;All in one seo pack&#8221; for wordpress and it insisted that i update the configuration page. I went and checked the page an this is what i have found:</p>
<p><img src="http://usabilitythoughts.com/wp-content/uploads/2009/10/seopack.png" alt="seopack" title="seopack" width="499" height="363" class="alignnone size-full wp-image-176" /></p>
<p>It amazes me how awful is this form made, I think it&#8217;s deliberately made so you fuck up. Let&#8217;s see why:</p>
<p>1. the &#8220;Reset&#8221; option in on the right. (I&#8217;m not saying the submit must be on the right, but it&#8217;s the most common that way)<br />
2. the &#8220;Reset&#8221; button is bigger and has the same design as the &#8220;Update&#8221; button. That and 1. makes it most likely to be pressed first<br />
3. both buttons have the same design, hence they are equally important? i don&#8217;t think so, the call to action button must be the &#8220;update&#8221; button. Keep in mind that &#8220;Reset&#8221; is a destructive action.<br />
4. what&#8217;s with the &#8220;>>&#8221; ? the arrows on the first button point to the second, which kindda&#8217; makes the second the call to action, but the arrows on the second? there&#8217;s no extra step, there&#8217;s only a form. </p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitythoughts.com/so-wrong-on-so-many-levels.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google Account login over the years</title>
		<link>http://usabilitythoughts.com/google-account-login-over-the-years.html</link>
		<comments>http://usabilitythoughts.com/google-account-login-over-the-years.html#comments</comments>
		<pubDate>Wed, 07 Oct 2009 14:48:57 +0000</pubDate>
		<dc:creator>Adrian</dc:creator>
				<category><![CDATA[Good practices]]></category>
		<category><![CDATA[Patterns]]></category>
		<category><![CDATA[account]]></category>
		<category><![CDATA[call to action]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[login]]></category>

		<guid isPermaLink="false">http://usabilitythoughts.com/?p=158</guid>
		<description><![CDATA[A login account sounds simple but it&#8217;s not. I&#8217;ve been watching Google Account login form for a while and saw the changes they made over time. A login form has to accomplish several things:
- get the registered clients into the system fast
- make unregistered users to register
- convert a visitor into a user
- provide a [...]]]></description>
			<content:encoded><![CDATA[<p>A login account sounds simple but it&#8217;s not. I&#8217;ve been watching Google Account login form for a while and saw the changes they made over time. A login form has to accomplish several things:</p>
<p>- get the registered clients into the system fast<br />
- make unregistered users to register<br />
- convert a visitor into a user<br />
- provide a way to recover an account</p>
<p>In time, the priority  of those things changes, ie: at the beginning of a startup you want more new users, the register process must be the first thing a visitor sees in the page, after a while and a solid client base you want those clients to login fast and without issues.</p>
<p>Let&#8217;s see some of Google&#8217;s login forms now:</p>
<p style="text-align: center;"><img class="size-full wp-image-160 aligncenter" title="google-account-login" src="http://usabilitythoughts.com/wp-content/uploads/2009/10/google-account-login.gif" alt="google-account-login" width="227" height="262" /></p>
<p style="text-align: left;">Size of the font and spacing changed for better focus on the link.</p>
<p style="text-align: center;"><img class="size-full wp-image-159 aligncenter" title="google-docs-login" src="http://usabilitythoughts.com/wp-content/uploads/2009/10/google-docs-login.gif" alt="google-docs-login" width="323" height="359" /></p>
<p style="text-align: left;">Here come the blue buttons.  Call to action all the way. Unfortunately, I personally had problems logging in, I pressed the &#8220;new account&#8221; button instead of &#8220;login&#8221; multiple times.  Wasn&#8217;t very happy with those. The naming on the button changed a lot, &#8220;get started&#8221;, &#8220;pick a name&#8221; or simply &#8220;new account&#8221;</p>
<p style="text-align: center;"><img class="size-full wp-image-161 aligncenter" title="gmail-login-signup" src="http://usabilitythoughts.com/wp-content/uploads/2009/10/gmail-login-signup.bmp" alt="gmail-login-signup" /></p>
<p style="text-align: center;"><img class="size-full wp-image-164 aligncenter" title="Login_Full" src="http://usabilitythoughts.com/wp-content/uploads/2009/10/Login_Full.jpg" alt="Login_Full" width="269" height="364" /></p>
<p>The next one is the one i can see today on my browser, it really doesn&#8217;t have a actual call-to-action button, just a size priority. It&#8217;s better.</p>
<p style="text-align: center;"><img class="size-full wp-image-162 aligncenter" title="2009-10-07_1713" src="http://usabilitythoughts.com/wp-content/uploads/2009/10/2009-10-07_1713.png" alt="2009-10-07_1713" width="407" height="420" /></p>
<p style="text-align: left;">Note: I&#8217;m more than sure it depends on the OS/BROWSER/GOOGLE SERVICE etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://usabilitythoughts.com/google-account-login-over-the-years.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

