<?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: Band-Aids Only Hide Boo-boos</title>
	<atom:link href="http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/feed" rel="self" type="application/rss+xml" />
	<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos</link>
	<description>Adam DuVander’s thoughts on keeping things simple.</description>
	<lastBuildDate>Mon, 09 Jan 2012 07:03:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1974</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 27 May 2008 18:15:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1974</guid>
		<description>Thanks for your comments, Hari. I think we agree: MySpace has to require a login for some things, but the way they did it is a band-aid. I like what you said about the flow. That login screen is a flow stopper. They don&#039;t even do a good job of getting you to what you were trying to look at before they interrupted your flow.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Hari. I think we agree: MySpace has to require a login for some things, but the way they did it is a band-aid. I like what you said about the flow. That login screen is a flow stopper. They don&#8217;t even do a good job of getting you to what you were trying to look at before they interrupted your flow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hari</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1973</link>
		<dc:creator>Hari</dc:creator>
		<pubDate>Thu, 22 May 2008 20:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1973</guid>
		<description>First, I don&#039;t see the problem here,

&quot;The red box is a band-aid for a broken login process.&quot;

Isn&#039;t it typical to allow a user to view certain information without having to login and if the user chooses to engage at a deeper level, prompt for login?

The problem I see is that the &quot;flow&quot; is broken by taking the user to a different context (in this case, the login page)
which is my solution to your problem question
&quot;As someone who loves simplicity, how can I advocate the additional time to get a better solution?&quot;

Simplicity is all about creating and maintaining the &quot;Flow&quot;.

So from a developer&#039;s perspective,
time and effort may be the factors for simplicity as in
&quot;It is a one line change in the code.&quot;
whereas,
from a user&#039;s perspective, being able to engage with the content, experience different pages/sections of the site seamlessly and getting what he/she wants quickly would count towards simplicity. The result being more sales, more comments, loyalty etc.

Hence, it is not really &quot;extra work&quot; to make this happen but is &quot;the actual work&quot; required.</description>
		<content:encoded><![CDATA[<p>First, I don&#8217;t see the problem here,</p>
<p>&#8220;The red box is a band-aid for a broken login process.&#8221;</p>
<p>Isn&#8217;t it typical to allow a user to view certain information without having to login and if the user chooses to engage at a deeper level, prompt for login?</p>
<p>The problem I see is that the &#8220;flow&#8221; is broken by taking the user to a different context (in this case, the login page)<br />
which is my solution to your problem question<br />
&#8220;As someone who loves simplicity, how can I advocate the additional time to get a better solution?&#8221;</p>
<p>Simplicity is all about creating and maintaining the &#8220;Flow&#8221;.</p>
<p>So from a developer&#8217;s perspective,<br />
time and effort may be the factors for simplicity as in<br />
&#8220;It is a one line change in the code.&#8221;<br />
whereas,<br />
from a user&#8217;s perspective, being able to engage with the content, experience different pages/sections of the site seamlessly and getting what he/she wants quickly would count towards simplicity. The result being more sales, more comments, loyalty etc.</p>
<p>Hence, it is not really &#8220;extra work&#8221; to make this happen but is &#8220;the actual work&#8221; required.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jmartens</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1972</link>
		<dc:creator>Jmartens</dc:creator>
		<pubDate>Sat, 03 May 2008 05:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1972</guid>
		<description>I just had a crazy experience at UrbanDictionary.com and had to come right to this post and leave a comment!

I tried to add a new word to the popular urban dictionary (wantrepreneur) and after 4 attempts, I left the site.

They asked for my name and location. However, they said my name was all ready being used. So I used my middle name, no luck. I used a nick name, still no luck. I made up a name, no luck!

If they wanted me to create a unique user ID, why not just say so? And if I am being asked to do that, make it easy for me to know if the username is available (like real time checking or suggestions of available names).

Perfect example of a site not doing things right.</description>
		<content:encoded><![CDATA[<p>I just had a crazy experience at UrbanDictionary.com and had to come right to this post and leave a comment!</p>
<p>I tried to add a new word to the popular urban dictionary (wantrepreneur) and after 4 attempts, I left the site.</p>
<p>They asked for my name and location. However, they said my name was all ready being used. So I used my middle name, no luck. I used a nick name, still no luck. I made up a name, no luck!</p>
<p>If they wanted me to create a unique user ID, why not just say so? And if I am being asked to do that, make it easy for me to know if the username is available (like real time checking or suggestions of available names).</p>
<p>Perfect example of a site not doing things right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toby Lucich</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1971</link>
		<dc:creator>Toby Lucich</dc:creator>
		<pubDate>Fri, 02 May 2008 18:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1971</guid>
		<description>Well put.

Like user interfaces, I deal with the same issue inside client companies with their employee-facing processes. From getting transactions authorized to on-boarding a new employee or the annual budgeting processes - setting a repeatable processes of any type in motion usually has a series of ludicrious steps (a likely result of excessive navel-gazing).

The answer is rarely another form to supplement the stack, or requiring your employees (users) to learn every nuance of your process. Inspiring is that rare company that is as concerned about employee user experience as much as they are about customer service.</description>
		<content:encoded><![CDATA[<p>Well put.</p>
<p>Like user interfaces, I deal with the same issue inside client companies with their employee-facing processes. From getting transactions authorized to on-boarding a new employee or the annual budgeting processes &#8211; setting a repeatable processes of any type in motion usually has a series of ludicrious steps (a likely result of excessive navel-gazing).</p>
<p>The answer is rarely another form to supplement the stack, or requiring your employees (users) to learn every nuance of your process. Inspiring is that rare company that is as concerned about employee user experience as much as they are about customer service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron B. Hockley</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1970</link>
		<dc:creator>Aaron B. Hockley</dc:creator>
		<pubDate>Thu, 01 May 2008 20:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1970</guid>
		<description>True, perhaps the Band-Aid is the simple solution for you as a designer.

But for most situations, it&#039;s what&#039;s simpler for the &lt;b&gt;end user&lt;/b&gt; that matters.</description>
		<content:encoded><![CDATA[<p>True, perhaps the Band-Aid is the simple solution for you as a designer.</p>
<p>But for most situations, it&#8217;s what&#8217;s simpler for the <b>end user</b> that matters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simplicity Rules &#38;#187; Designing the Obvious is my new best friend</title>
		<link>http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos/comment-page-1#comment-1969</link>
		<dc:creator>Simplicity Rules &#38;#187; Designing the Obvious is my new best friend</dc:creator>
		<pubDate>Thu, 01 May 2008 19:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamduvander.com/simple/band-aids-only-hide-boo-boos#comment-1969</guid>
		<description>[...] Band-Aids Only Hide Boo-boos [...]</description>
		<content:encoded><![CDATA[<p>[...] Band-Aids Only Hide Boo-boos [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

