<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Fellows Friday with Gerry Douglas</title>
	<atom:link href="http://blog.ted.com/2011/04/29/fellows-friday-with-gerry-douglas/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ted.com/2011/04/29/fellows-friday-with-gerry-douglas/</link>
	<description>The TED Blog shares interesting news about TED, TED Talks video, the TED Prize and more.</description>
	<lastBuildDate>Tue, 18 Jun 2013 21:15:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dan Andreescu</title>
		<link>http://blog.ted.com/2011/04/29/fellows-friday-with-gerry-douglas/comment-page-1/#comment-7216</link>
		<dc:creator><![CDATA[Dan Andreescu]]></dc:creator>
		<pubDate>Sun, 01 May 2011 13:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ted.com/?p=49649#comment-7216</guid>
		<description><![CDATA[My favorite user interfaces have three things in common:

1. They ask the absolute minimum of me.  For example, a drop-down with three choices should be a radio button list.  That&#039;s because the drop-down requires me to click twice and the radio button list only once.

2. They&#039;re fun to figure out, and a tiny bit challenging.  The user interface doesn&#039;t have to be so dumb that you literally require 0 thought process to figure it out.  If a part of a repetitive form gets used very infrequently, it can be hidden.  The user will find it and be happy .  Or, if a todo list has a due date for each item, don&#039;t rely on a simple date and time.  Try using &quot;today, tomorrow, a week, custom&quot; as a radio button list if the first three choices cover most of the situations.  It takes a second to understand that you&#039;re not keying in a date like everywhere else, but the shortcut you learn is more valuable than that second.

3. Incredibly readable font.  BIG buttons.  HUGE.  Associate labels with checkboxes and radio buttons so that I can click on the label and not have to aim at the teeny tiny little box.  There&#039;s no shame in huge buttons.  If you have so many that you can&#039;t afford to make them huge, then you have too many buttons.  If you don&#039;t have a lot of them, then there&#039;s no reason to keep them small (::cough:: I&#039;m looking at you Submit-button-on-this-form).]]></description>
		<content:encoded><![CDATA[<p>My favorite user interfaces have three things in common:</p>
<p>1. They ask the absolute minimum of me.  For example, a drop-down with three choices should be a radio button list.  That&#8217;s because the drop-down requires me to click twice and the radio button list only once.</p>
<p>2. They&#8217;re fun to figure out, and a tiny bit challenging.  The user interface doesn&#8217;t have to be so dumb that you literally require 0 thought process to figure it out.  If a part of a repetitive form gets used very infrequently, it can be hidden.  The user will find it and be happy .  Or, if a todo list has a due date for each item, don&#8217;t rely on a simple date and time.  Try using &#8220;today, tomorrow, a week, custom&#8221; as a radio button list if the first three choices cover most of the situations.  It takes a second to understand that you&#8217;re not keying in a date like everywhere else, but the shortcut you learn is more valuable than that second.</p>
<p>3. Incredibly readable font.  BIG buttons.  HUGE.  Associate labels with checkboxes and radio buttons so that I can click on the label and not have to aim at the teeny tiny little box.  There&#8217;s no shame in huge buttons.  If you have so many that you can&#8217;t afford to make them huge, then you have too many buttons.  If you don&#8217;t have a lot of them, then there&#8217;s no reason to keep them small (::cough:: I&#8217;m looking at you Submit-button-on-this-form).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Badami</title>
		<link>http://blog.ted.com/2011/04/29/fellows-friday-with-gerry-douglas/comment-page-1/#comment-7214</link>
		<dc:creator><![CDATA[Ted Badami]]></dc:creator>
		<pubDate>Sun, 01 May 2011 12:20:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ted.com/?p=49649#comment-7214</guid>
		<description><![CDATA[&quot;Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction.&quot; Albert Einstein]]></description>
		<content:encoded><![CDATA[<p>&#8220;Any intelligent fool can make things bigger and more complex&#8230; It takes a touch of genius &#8211; and a lot of courage to move in the opposite direction.&#8221; Albert Einstein</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Healthcare and Technology</title>
		<link>http://blog.ted.com/2011/04/29/fellows-friday-with-gerry-douglas/comment-page-1/#comment-7198</link>
		<dc:creator><![CDATA[Healthcare and Technology]]></dc:creator>
		<pubDate>Sat, 30 Apr 2011 14:10:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ted.com/?p=49649#comment-7198</guid>
		<description><![CDATA[[...] out the rest of the interview here.  Digg this post Share on dzone Recommend on Facebook Share on Posterous share via Reddit Tell a [...]]]></description>
		<content:encoded><![CDATA[<p>[...] out the rest of the interview here.  Digg this post Share on dzone Recommend on Facebook Share on Posterous share via Reddit Tell a [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
