<?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 on: How does your web form flow?</title>
	<atom:link href="http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/</link>
	<description></description>
	<lastBuildDate>Sat, 14 Aug 2010 11:08:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Micah</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2555</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Thu, 18 Mar 2010 14:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2555</guid>
		<description>Although this will obviously vary from site to site, and form to form, would it be helpful to assume a few things about the user&#039;s input to help them along? For example, if most people ended up checking the box so the same phone number was entered in both fields, perhaps have it checked by default. As Bennett said, forms have been using the &quot;if different&quot; setup for quite some time. Taking that a step further, do you think it would be helpful/usable to allow the user to uncheck that box to reveal another field for Evening Phone?</description>
		<content:encoded><![CDATA[<p>Although this will obviously vary from site to site, and form to form, would it be helpful to assume a few things about the user&#8217;s input to help them along? For example, if most people ended up checking the box so the same phone number was entered in both fields, perhaps have it checked by default. As Bennett said, forms have been using the &#8220;if different&#8221; setup for quite some time. Taking that a step further, do you think it would be helpful/usable to allow the user to uncheck that box to reveal another field for Evening Phone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Jessop</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2526</link>
		<dc:creator>Kevin Jessop</dc:creator>
		<pubDate>Fri, 26 Feb 2010 21:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2526</guid>
		<description>Very good article, Dave.  Flow is very important.  I like how you tackle and differentiate between the considered and immediate response and how that impacts flow.

The rest of the solutions posted by readers are valid too.  I love how there is flexibility in usability...well, sometimes.  

We had a similar issue in a recent test.  The form was a typical credit card detail thing - name on card, expirations date, etc.  

However, the boxes were out of order.  The credit card number box was last and at the bottom of the page.  The format of the credit card number was displayed below the box but most people missed it.  They saw the input box at the end of the field an immediately entered the details without looking at the example below.  Wonky flow.

Great article, sir.</description>
		<content:encoded><![CDATA[<p>Very good article, Dave.  Flow is very important.  I like how you tackle and differentiate between the considered and immediate response and how that impacts flow.</p>
<p>The rest of the solutions posted by readers are valid too.  I love how there is flexibility in usability&#8230;well, sometimes.  </p>
<p>We had a similar issue in a recent test.  The form was a typical credit card detail thing &#8211; name on card, expirations date, etc.  </p>
<p>However, the boxes were out of order.  The credit card number box was last and at the bottom of the page.  The format of the credit card number was displayed below the box but most people missed it.  They saw the input box at the end of the field an immediately entered the details without looking at the example below.  Wonky flow.</p>
<p>Great article, sir.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2521</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Wed, 24 Feb 2010 09:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2521</guid>
		<description>Hi Bennet, thanks for the comment. As I said in the comment above yours, there are a number of ways it could be resolved. I didn&#039;t want to include a thesis on the client&#039;s situation in order to make the point. Your example would work well too.</description>
		<content:encoded><![CDATA[<p>Hi Bennet, thanks for the comment. As I said in the comment above yours, there are a number of ways it could be resolved. I didn&#8217;t want to include a thesis on the client&#8217;s situation in order to make the point. Your example would work well too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bennett McElwee</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2520</link>
		<dc:creator>Bennett McElwee</dc:creator>
		<pubDate>Tue, 23 Feb 2010 23:11:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2520</guid>
		<description>Why not do the same thing as you suggested for the invite number? Just add an explanation to the label:

Evening phone (if different from daytime phone)

This flows perfectly, without the repetition.

My suggestion is not original, of course. It&#039;s been used in order forms (paper and online) for years. They ask for your billing address, and &quot;Delivery address (if different)&quot;.</description>
		<content:encoded><![CDATA[<p>Why not do the same thing as you suggested for the invite number? Just add an explanation to the label:</p>
<p>Evening phone (if different from daytime phone)</p>
<p>This flows perfectly, without the repetition.</p>
<p>My suggestion is not original, of course. It&#8217;s been used in order forms (paper and online) for years. They ask for your billing address, and &#8220;Delivery address (if different)&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2517</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Tue, 23 Feb 2010 08:59:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2517</guid>
		<description>Hi Yoav. There are many ways that the problem could be resolved. Your method would work if the labels were changed from daytime and evening to preferred and alternative numbers. However clients aren&#039;t always able to be so flexible. Having made such a change would have apparently cost a lot of money. What seems like a simple change to a website can actually be quite difficult for some large businesses.</description>
		<content:encoded><![CDATA[<p>Hi Yoav. There are many ways that the problem could be resolved. Your method would work if the labels were changed from daytime and evening to preferred and alternative numbers. However clients aren&#8217;t always able to be so flexible. Having made such a change would have apparently cost a lot of money. What seems like a simple change to a website can actually be quite difficult for some large businesses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoav M.</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2516</link>
		<dc:creator>Yoav M.</dc:creator>
		<pubDate>Tue, 23 Feb 2010 08:49:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2516</guid>
		<description>Great article indeed.
I didn&#039;t understand something: why not simply remove the &quot;mandatory&quot; asterisk from the evening phone? As a user filling many forms in my past - I encountered many cases where only one of the phones were mandatory and the other weren&#039;t - meaning only the first one is the one to be used.</description>
		<content:encoded><![CDATA[<p>Great article indeed.<br />
I didn&#8217;t understand something: why not simply remove the &#8220;mandatory&#8221; asterisk from the evening phone? As a user filling many forms in my past &#8211; I encountered many cases where only one of the phones were mandatory and the other weren&#8217;t &#8211; meaning only the first one is the one to be used.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2518</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2518</guid>
		<description>Hi Lizzie, thanks I did publish your comment despite it being picked up as spam. I just took out the keywords out and replaced it with the name you provided.</description>
		<content:encoded><![CDATA[<p>Hi Lizzie, thanks I did publish your comment despite it being picked up as spam. I just took out the keywords out and replaced it with the name you provided.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lizzie Soul</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2512</link>
		<dc:creator>Lizzie Soul</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:50:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2512</guid>
		<description>Today I have found what I have been looking for and that is a very big day for me! Thank you for this blog and this post (del.icio.us poetry)and I hope you will publish my comment as this is a great site and worthy of congratulations. Lizzie Soul</description>
		<content:encoded><![CDATA[<p>Today I have found what I have been looking for and that is a very big day for me! Thank you for this blog and this post (del.icio.us poetry)and I hope you will publish my comment as this is a great site and worthy of congratulations. Lizzie Soul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aye Moah</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2511</link>
		<dc:creator>Aye Moah</dc:creator>
		<pubDate>Mon, 22 Feb 2010 20:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2511</guid>
		<description>Your last point about treating the form as a conversational piece seems to be the new trend of form design. I&#039;m noticing more and more of informal conversational tone in form labels. 

This reminds me of this particular sign up form at Huffduffer where the entire form is a dialog.

http://huffduffer.com/signup/

I&#039;m not certain this will test well in terms of completion speed or ease of scanning.</description>
		<content:encoded><![CDATA[<p>Your last point about treating the form as a conversational piece seems to be the new trend of form design. I&#8217;m noticing more and more of informal conversational tone in form labels. </p>
<p>This reminds me of this particular sign up form at Huffduffer where the entire form is a dialog.</p>
<p><a href="http://huffduffer.com/signup/">http://huffduffer.com/signup/</a></p>
<p>I&#8217;m not certain this will test well in terms of completion speed or ease of scanning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hamill</title>
		<link>http://www.goodusability.co.uk/2010/02/how-does-your-web-form-flow/comment-page-1/#comment-2510</link>
		<dc:creator>David Hamill</dc:creator>
		<pubDate>Mon, 22 Feb 2010 19:24:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.goodusability.co.uk/?p=2151#comment-2510</guid>
		<description>Hi Artem. The example is very simple I agree. That&#039;s why I chose it. I try to choose examples that illustrate a principle. In this one I&#039;m talking about how people behave differently when dealing with questions of varying difficulty. Hopefully a simple example helps to communicate the point.</description>
		<content:encoded><![CDATA[<p>Hi Artem. The example is very simple I agree. That&#8217;s why I chose it. I try to choose examples that illustrate a principle. In this one I&#8217;m talking about how people behave differently when dealing with questions of varying difficulty. Hopefully a simple example helps to communicate the point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
