<?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: Focus Groups, Meh</title>
	<atom:link href="http://buzzpressure.com/2009/09/09/focus-groups-meh/feed/" rel="self" type="application/rss+xml" />
	<link>http://buzzpressure.com/2009/09/09/focus-groups-meh/</link>
	<description>Now with 100% more Carbon</description>
	<lastBuildDate>Tue, 17 Aug 2010 12:56:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: alexblack</title>
		<link>http://buzzpressure.com/2009/09/09/focus-groups-meh/comment-page-1/#comment-501</link>
		<dc:creator>alexblack</dc:creator>
		<pubDate>Mon, 05 Oct 2009 02:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=195#comment-501</guid>
		<description>Hey Jeff, great post, sounds like a page out of Customer Development: &lt;a href=&quot;http://www.startuplessonslearned.com/2008/11/what...&quot; target=&quot;_blank&quot;&gt;http://www.startuplessonslearned.com/2008/11/what...&lt;/a&gt; 
 
This reminds me of a similar situation we experienced at Booksoft years ago. We&#039;d developed a speakers-corner type video kiosk system for high school students to use to collect video messages for the yearbook, using a laptop and camcorder etc. I designed us a fancy looking wizard for people to use to collect a person&#039;s name and grade and photo. Phil, our lead developer at the time told me this was not a very usable interface, but I was in love with wizards... 
 
One day we visited a school using the system, and within 5 minutes I was embarrassed about how slow and hard to use the system was... I felt pain for the guy running the system, having to keep hitting next, noticing the student giving the information out of order, and our rigid software making things difficult. 
 
We wrote some new code as soon as we were back at the office. We should have got in front of people much sooner!  </description>
		<content:encoded><![CDATA[<p>Hey Jeff, great post, sounds like a page out of Customer Development: <a href="http://www.startuplessonslearned.com/2008/11/what..." target="_blank"></a><a href="http://www.startuplessonslearned.com/2008/11/what.." rel="nofollow">http://www.startuplessonslearned.com/2008/11/what..</a>. </p>
<p>This reminds me of a similar situation we experienced at Booksoft years ago. We&#039;d developed a speakers-corner type video kiosk system for high school students to use to collect video messages for the yearbook, using a laptop and camcorder etc. I designed us a fancy looking wizard for people to use to collect a person&#039;s name and grade and photo. Phil, our lead developer at the time told me this was not a very usable interface, but I was in love with wizards&#8230; </p>
<p>One day we visited a school using the system, and within 5 minutes I was embarrassed about how slow and hard to use the system was&#8230; I felt pain for the guy running the system, having to keep hitting next, noticing the student giving the information out of order, and our rigid software making things difficult. </p>
<p>We wrote some new code as soon as we were back at the office. We should have got in front of people much sooner!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noirs</title>
		<link>http://buzzpressure.com/2009/09/09/focus-groups-meh/comment-page-1/#comment-500</link>
		<dc:creator>noirs</dc:creator>
		<pubDate>Mon, 05 Oct 2009 02:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://buzzpressure.com/?p=195#comment-500</guid>
		<description>Hey Jeff, great post, sounds like a page out of Customer Development: &lt;a href=&quot;http://www.startuplessonslearned.com/2008/11/what-is-customer-development.html&quot; target=&quot;_blank&quot;&gt;http://www.startuplessonslearned.com/2008/11/what...&lt;/a&gt;  
 
This reminds me of a similar situation we experienced at Booksoft years ago.  We&#039;d developed a speakers-corner type video kiosk system for high school students to use to collect video messages for the yearbook, using a laptop and camcorder etc.  I designed us a fancy looking wizard for people to use to collect a person&#039;s name and grade and photo.  Phil, our lead developer at the time told me this was not a very usable interface, but I was in love with wizards...  
 
One day we visited a school using the system, and within 5 minutes I was embarrassed about how slow and hard to use the system was... I felt pain for the guy running the system, having to keep hitting next, noticing the student giving the information out of order, and our rigid software making things difficult.   
 
We wrote some new code as soon as we were back at the office.  We should have got in front of people much sooner! </description>
		<content:encoded><![CDATA[<p>Hey Jeff, great post, sounds like a page out of Customer Development: <a href="http://www.startuplessonslearned.com/2008/11/what-is-customer-development.html" target="_blank"></a><a href="http://www.startuplessonslearned.com/2008/11/what.." rel="nofollow">http://www.startuplessonslearned.com/2008/11/what..</a>.  </p>
<p>This reminds me of a similar situation we experienced at Booksoft years ago.  We&#039;d developed a speakers-corner type video kiosk system for high school students to use to collect video messages for the yearbook, using a laptop and camcorder etc.  I designed us a fancy looking wizard for people to use to collect a person&#039;s name and grade and photo.  Phil, our lead developer at the time told me this was not a very usable interface, but I was in love with wizards&#8230; </p>
<p>One day we visited a school using the system, and within 5 minutes I was embarrassed about how slow and hard to use the system was&#8230; I felt pain for the guy running the system, having to keep hitting next, noticing the student giving the information out of order, and our rigid software making things difficult.  </p>
<p>We wrote some new code as soon as we were back at the office.  We should have got in front of people much sooner!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
