<?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 for InContext</title>
	<atom:link href="http://incontextdesign.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://incontextdesign.com</link>
	<description>Putting data to work for you</description>
	<pubDate>Thu, 11 Mar 2010 09:08:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Don&#8217;t Ask Your Customer—Use Contextual Inquiry by Fahied</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-article/comment-page-1/#comment-3426</link>
		<dc:creator>Fahied</dc:creator>
		<pubDate>Mon, 01 Mar 2010 17:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2739#comment-3426</guid>
		<description>That is really cool, provided me inspiration about this tool, especially in case of designing everyday life user experience.</description>
		<content:encoded><![CDATA[<p>That is really cool, provided me inspiration about this tool, especially in case of designing everyday life user experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer by David Locke</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-comic/comment-page-1/#comment-2670</link>
		<dc:creator>David Locke</dc:creator>
		<pubDate>Thu, 31 Dec 2009 00:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2735#comment-2670</guid>
		<description>The users in one market phase differ greatly from users in another market phase. Typically, this gets ignored. Our users are a collection of nearly random people. We aggregate their feedback, and smudge distinctions.</description>
		<content:encoded><![CDATA[<p>The users in one market phase differ greatly from users in another market phase. Typically, this gets ignored. Our users are a collection of nearly random people. We aggregate their feedback, and smudge distinctions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer—Use Contextual Inquiry by Jason Robb</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-article/comment-page-1/#comment-2306</link>
		<dc:creator>Jason Robb</dc:creator>
		<pubDate>Thu, 26 Nov 2009 01:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2739#comment-2306</guid>
		<description>Wow, Karen--this is an outstanding article. Well done! I don't know where to start, but everything was forehead-slapping-ly awesome. Thank you for taking the time to write this.

David R. - Your comic was stellar. Very nice. :-)</description>
		<content:encoded><![CDATA[<p>Wow, Karen&#8211;this is an outstanding article. Well done! I don&#8217;t know where to start, but everything was forehead-slapping-ly awesome. Thank you for taking the time to write this.</p>
<p>David R. - Your comic was stellar. Very nice. <img src='http://incontextdesign.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Organizational Empathy by Valerie Shuman</title>
		<link>http://incontextdesign.com/blog/organizational-empathy/comment-page-1/#comment-2218</link>
		<dc:creator>Valerie Shuman</dc:creator>
		<pubDate>Wed, 18 Nov 2009 14:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2716#comment-2218</guid>
		<description>Hello Larry

Nice post!  This certainly rings true from my experience.  It sure would help if we more often recognized, trained, and staffed projects with this key Cross-Discipline Translation skillset... 

Valerie</description>
		<content:encoded><![CDATA[<p>Hello Larry</p>
<p>Nice post!  This certainly rings true from my experience.  It sure would help if we more often recognized, trained, and staffed projects with this key Cross-Discipline Translation skillset&#8230; </p>
<p>Valerie</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is Friendship Relationship Management Our Future by Shoshana Holtzblatt</title>
		<link>http://incontextdesign.com/articles/is_friendship_relationship_management_our_future/comment-page-1/#comment-1812</link>
		<dc:creator>Shoshana Holtzblatt</dc:creator>
		<pubDate>Fri, 30 Oct 2009 11:41:50 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/articles/is_friendship_relationship_management_our_future/#comment-1812</guid>
		<description>Dear Karen,

I don't think social networking sites are just about maintaining loose social connections. I have found that social networking sites can help strengthen my relationships with the people that are already in my social network in the "real" world.  By seeing the profiles of acquaintances in my social network I was able to find people that I had things in common with and the site fostered a deeper relationship.  This is especially good when entering new social networks.  It can be overwhelming to meet new people in a new place.  It is hard enough trying to remember all the names of the new people let alone what activities they are interested in.  By being able to connect online after meeting someone, you are able to view their interests on their profile and find the people who will make the best friends.  I think this use of these sites probably comes more naturally to the younger generation.    

But I do see you point about how this may hinder the natural pruning 
process.  While sites like this do let me connect with my old friends and see who is still in town, it also forces me into awkward situations about trying to figure out who to confirm as "my friend". 

Also, I'm sure it has caused many issues for people after breaking up.  I mean if you are connected to your ex then you find out when they find someone else. That is not something you have to deal with usually.  

I actually did end up leaving one site for another when I left one social group for another.  I guess that is still one way of enabling social pruning. 

But it should be interesting to see what happens with the generation that grew up with these sites and already have anywhere from 300 - 3000 connections.  I wonder if they will end up feeling overwhelmed by all their connections when they become successful business men and women.


Shoshana</description>
		<content:encoded><![CDATA[<p>Dear Karen,</p>
<p>I don&#8217;t think social networking sites are just about maintaining loose social connections. I have found that social networking sites can help strengthen my relationships with the people that are already in my social network in the &#8220;real&#8221; world.  By seeing the profiles of acquaintances in my social network I was able to find people that I had things in common with and the site fostered a deeper relationship.  This is especially good when entering new social networks.  It can be overwhelming to meet new people in a new place.  It is hard enough trying to remember all the names of the new people let alone what activities they are interested in.  By being able to connect online after meeting someone, you are able to view their interests on their profile and find the people who will make the best friends.  I think this use of these sites probably comes more naturally to the younger generation.    </p>
<p>But I do see you point about how this may hinder the natural pruning<br />
process.  While sites like this do let me connect with my old friends and see who is still in town, it also forces me into awkward situations about trying to figure out who to confirm as &#8220;my friend&#8221;. </p>
<p>Also, I&#8217;m sure it has caused many issues for people after breaking up.  I mean if you are connected to your ex then you find out when they find someone else. That is not something you have to deal with usually.  </p>
<p>I actually did end up leaving one site for another when I left one social group for another.  I guess that is still one way of enabling social pruning. </p>
<p>But it should be interesting to see what happens with the generation that grew up with these sites and already have anywhere from 300 - 3000 connections.  I wonder if they will end up feeling overwhelmed by all their connections when they become successful business men and women.</p>
<p>Shoshana</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer by Ron</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-comic/comment-page-1/#comment-1748</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Wed, 28 Oct 2009 21:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2735#comment-1748</guid>
		<description>Nice comic, true story. Features are added or built out until a tipping point is reached and everyone cries "The customers can't use it and we can't maintain it. We have to simplify the product." 

Developers and designers can't forget that users are doing a job. Their product is a tool to do the job and not the job itself.</description>
		<content:encoded><![CDATA[<p>Nice comic, true story. Features are added or built out until a tipping point is reached and everyone cries &#8220;The customers can&#8217;t use it and we can&#8217;t maintain it. We have to simplify the product.&#8221; </p>
<p>Developers and designers can&#8217;t forget that users are doing a job. Their product is a tool to do the job and not the job itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creativity from the Ground Up by Timothy J. Leahy</title>
		<link>http://incontextdesign.com/blog/creativity-from-the-ground-up/comment-page-1/#comment-1699</link>
		<dc:creator>Timothy J. Leahy</dc:creator>
		<pubDate>Tue, 27 Oct 2009 14:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2659#comment-1699</guid>
		<description>Larry:
Thanks for sharing the Incontext E - Newsletter. I enjoyed your article. Your honesty and self reflection is refreshing. Reframing is nothing new. I think Copernicus experienced this when he reasoned that the sun does not revolve around the earth; rather its the other way around!

Cheers -Tim</description>
		<content:encoded><![CDATA[<p>Larry:<br />
Thanks for sharing the Incontext E - Newsletter. I enjoyed your article. Your honesty and self reflection is refreshing. Reframing is nothing new. I think Copernicus experienced this when he reasoned that the sun does not revolve around the earth; rather its the other way around!</p>
<p>Cheers -Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer by Paul Oord</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-comic/comment-page-1/#comment-1632</link>
		<dc:creator>Paul Oord</dc:creator>
		<pubDate>Mon, 26 Oct 2009 09:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2735#comment-1632</guid>
		<description>Karen,
I think contextual design is one thing, but the next logical step would be involving users and customers in the design of a product. This is more than playing with prototypes and screenshots. 
To develop a common language, both engineers and users will understand better the problems at hand and develop solutions. This also leads to more acceptance and mutual responsibility. Participatory design methods are often neglected in education for software engineers. Educators often think that user centered design garantees user involvement, but this is severe a misconception.</description>
		<content:encoded><![CDATA[<p>Karen,<br />
I think contextual design is one thing, but the next logical step would be involving users and customers in the design of a product. This is more than playing with prototypes and screenshots.<br />
To develop a common language, both engineers and users will understand better the problems at hand and develop solutions. This also leads to more acceptance and mutual responsibility. Participatory design methods are often neglected in education for software engineers. Educators often think that user centered design garantees user involvement, but this is severe a misconception.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer by Brian</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-comic/comment-page-1/#comment-1592</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Wed, 21 Oct 2009 02:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2735#comment-1592</guid>
		<description>Karen, great entry, and great way to get a concept across - love the comic.  It's so true that too often people listen to what their customers say without actually taking the time to observe what they do.  What's interesting to me - maybe something you can comment about in another post (or comic), is people who misconstrue the reasoning presented here to entirely ignore their customers.  More frequently I hear people use the excuse "customers never really know what they want" to just go ahead and build what they want to build, entirely ignoring good user centered design.  It’s interesting because I’ve seen some very talented people use that excuse.  But I've also seen products with great potential flop that way.</description>
		<content:encoded><![CDATA[<p>Karen, great entry, and great way to get a concept across - love the comic.  It&#8217;s so true that too often people listen to what their customers say without actually taking the time to observe what they do.  What&#8217;s interesting to me - maybe something you can comment about in another post (or comic), is people who misconstrue the reasoning presented here to entirely ignore their customers.  More frequently I hear people use the excuse &#8220;customers never really know what they want&#8221; to just go ahead and build what they want to build, entirely ignoring good user centered design.  It’s interesting because I’ve seen some very talented people use that excuse.  But I&#8217;ve also seen products with great potential flop that way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Don&#8217;t Ask Your Customer by Sylvia Barnard</title>
		<link>http://incontextdesign.com/articles/dont-ask-your-customer-comic/comment-page-1/#comment-1591</link>
		<dc:creator>Sylvia Barnard</dc:creator>
		<pubDate>Tue, 20 Oct 2009 09:06:30 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2735#comment-1591</guid>
		<description>Dear Karen,
Wow, your comic story is great! I really had a good laugh, but I am known for my morbid humour...The story explains exactely what you have to do and how, and what is not helpful at all. This is why it is so important to have usability experts on board when going to the customer and interviewing and OBSERVING users. But we are still struggeling to getting the right message into the heads if the big guys! ...And can I get that cool cap you are wearing??? 
Cheers, Sylvia</description>
		<content:encoded><![CDATA[<p>Dear Karen,<br />
Wow, your comic story is great! I really had a good laugh, but I am known for my morbid humour&#8230;The story explains exactely what you have to do and how, and what is not helpful at all. This is why it is so important to have usability experts on board when going to the customer and interviewing and OBSERVING users. But we are still struggeling to getting the right message into the heads if the big guys! &#8230;And can I get that cool cap you are wearing???<br />
Cheers, Sylvia</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Creativity from the Ground Up by Thomas Sutrina</title>
		<link>http://incontextdesign.com/blog/creativity-from-the-ground-up/comment-page-1/#comment-1194</link>
		<dc:creator>Thomas Sutrina</dc:creator>
		<pubDate>Mon, 21 Sep 2009 21:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2659#comment-1194</guid>
		<description>Larry, you make reframing paradigm very positive,but to most of the engineering world and business world it is very scary.  I mean scary enough to continue making a product when all the signals tell you to stop.  Scary enough to go bankrupt.  Scary enough to accept solutions you would never consider.

Reality of the market is like a dragon blasting their hot breath at your castle.  Making pass after pass scaring the people including the leaders in your castle and starting fires.  You need a solution, any solution.  You welcome knight that will face the dragon and withstand the hot breath of the dragon against his shield like we see in the pictures from a fairy tale.  You do not care if he reframes your problem.  You only want a solution.  But unlike the fairy tale that same knight is a threat to the castle leaders unless he came from their ranks. 
 
One examples is the Longitude Prize offered by the British government through an Act of Parliament in 1714 for a simple and practical method for the precise determination of a ship's longitude.  The British navy felt the dragon's breath of inaccurate location.  John Harrison a young clock builder, a knight not from the ranks, had a solution and developed an unusual method based on an accurate clock, chronometer.  In 1737 he received a payment by meeting the requirement, but the board dragged its feet so he finally received the a big chuck completing the full prize in 1765.  He died three years later.

Larry, I have been reframing problems from my first three patents at Dow Chemical on Ziploc Sandwich bag extrusion process that has been used to make every bag sold.  And reframed the paradigm marketing and industrial design image of the Freestyle breast pump shields that was launched in February 2008 resulting in two patents.  A few dozen patents fill the time between them.  Most because a dragon shadow swept over the castle.  Clouds or a real dragon no one knew.

Larry I have always been the scary outsider, the knight capable of facing the dragon, to be kept in reserve in a silo to wait for the next dragon, or to be set from the castle because the next dragon will not occur on my watch.</description>
		<content:encoded><![CDATA[<p>Larry, you make reframing paradigm very positive,but to most of the engineering world and business world it is very scary.  I mean scary enough to continue making a product when all the signals tell you to stop.  Scary enough to go bankrupt.  Scary enough to accept solutions you would never consider.</p>
<p>Reality of the market is like a dragon blasting their hot breath at your castle.  Making pass after pass scaring the people including the leaders in your castle and starting fires.  You need a solution, any solution.  You welcome knight that will face the dragon and withstand the hot breath of the dragon against his shield like we see in the pictures from a fairy tale.  You do not care if he reframes your problem.  You only want a solution.  But unlike the fairy tale that same knight is a threat to the castle leaders unless he came from their ranks. </p>
<p>One examples is the Longitude Prize offered by the British government through an Act of Parliament in 1714 for a simple and practical method for the precise determination of a ship&#8217;s longitude.  The British navy felt the dragon&#8217;s breath of inaccurate location.  John Harrison a young clock builder, a knight not from the ranks, had a solution and developed an unusual method based on an accurate clock, chronometer.  In 1737 he received a payment by meeting the requirement, but the board dragged its feet so he finally received the a big chuck completing the full prize in 1765.  He died three years later.</p>
<p>Larry, I have been reframing problems from my first three patents at Dow Chemical on Ziploc Sandwich bag extrusion process that has been used to make every bag sold.  And reframed the paradigm marketing and industrial design image of the Freestyle breast pump shields that was launched in February 2008 resulting in two patents.  A few dozen patents fill the time between them.  Most because a dragon shadow swept over the castle.  Clouds or a real dragon no one knew.</p>
<p>Larry I have always been the scary outsider, the knight capable of facing the dragon, to be kept in reserve in a silo to wait for the next dragon, or to be set from the castle because the next dragon will not occur on my watch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interaction Design and the Boston Subway by Dave Flotree</title>
		<link>http://incontextdesign.com/blog/interaction-design-and-the-boston-subway/comment-page-1/#comment-237</link>
		<dc:creator>Dave Flotree</dc:creator>
		<pubDate>Thu, 13 Aug 2009 15:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://69.89.31.90/~incontex/?p=1292#comment-237</guid>
		<description>David, here in Seattle the new light rail system just went into service and rest assured that the Bostin T is not alone in the problems you describe.  Watch this video and see a transit employee fumble with the new system and ask for help:  http://seattletimes.nwsource.com/flatpages/video/seattletimesvideo.html?bcpid=25685749001&amp;bctid=33425048001

Why oh why didn't the designers of the system use proper user-centered design to prevent the obvious user interaction problems before going online??</description>
		<content:encoded><![CDATA[<p>David, here in Seattle the new light rail system just went into service and rest assured that the Bostin T is not alone in the problems you describe.  Watch this video and see a transit employee fumble with the new system and ask for help:  <a href="http://seattletimes.nwsource.com/flatpages/video/seattletimesvideo.html?bcpid=25685749001&amp;bctid=33425048001" rel="nofollow">http://seattletimes.nwsource.com/flatpages/video/seattletimesvideo.html?bcpid=25685749001&amp;bctid=33425048001</a></p>
<p>Why oh why didn&#8217;t the designers of the system use proper user-centered design to prevent the obvious user interaction problems before going online??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Is Friendship Relationship Management Our Future by brian huang</title>
		<link>http://incontextdesign.com/articles/is_friendship_relationship_management_our_future/comment-page-1/#comment-98</link>
		<dc:creator>brian huang</dc:creator>
		<pubDate>Tue, 28 Jul 2009 07:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/articles/is_friendship_relationship_management_our_future/#comment-98</guid>
		<description>Dear Karen,

I like your eye. 
I miss your eye. :)

This is a great story that illustrates looking beyond the obvious.

Best wishes.

Brian</description>
		<content:encoded><![CDATA[<p>Dear Karen,</p>
<p>I like your eye.<br />
I miss your eye. <img src='http://incontextdesign.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>This is a great story that illustrates looking beyond the obvious.</p>
<p>Best wishes.</p>
<p>Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Innovation is Easy by brian huang</title>
		<link>http://incontextdesign.com/blog/innovation-is-easy/comment-page-1/#comment-97</link>
		<dc:creator>brian huang</dc:creator>
		<pubDate>Tue, 28 Jul 2009 07:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/?p=2674#comment-97</guid>
		<description>well-said, Hugh!

The new website looks great  :)</description>
		<content:encoded><![CDATA[<p>well-said, Hugh!</p>
<p>The new website looks great  <img src='http://incontextdesign.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interaction Design and the Boston Subway by Jamie Ciocco</title>
		<link>http://incontextdesign.com/blog/interaction-design-and-the-boston-subway/comment-page-1/#comment-72</link>
		<dc:creator>Jamie Ciocco</dc:creator>
		<pubDate>Thu, 09 Jul 2009 18:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://69.89.31.90/~incontex/?p=1292#comment-72</guid>
		<description>Hey Dave!

Excellent article! I just discovered kids could ride free this week when my nephews visited -- and I've been riding the T since college. It might be nice if they posted that info somewhere obvious, like maybe on the fare kiosks.

I remember the first time I used one of those kiosks, just after they were installed. The person in front of me only had T tokens, which of course were no longer accepted. An impatient T employee was helping him through the process and laying on the ol' Boston charm. an excerpt:
-----
Surly T Employee: Click the 'Cash' button. CLICK THE 'CASH' BUTTON. DO YOU SPEAK ENGLISH?
Befuddled Passenger: But I only have tokens...
Surly T Employee: CLICK THE 'CASH' BUTTON!! ... Now click 'Other Amount' ... now drop your tokens in the slot.
-----

I was appalled. How the heck was someone supposed to know to press "Cash" and then drop in T tokens? They certainly aren't cash, and the icons next to the coin slot indicate that the machine only accepts nickels, dimes, quarters, and dollar coins. 

And yet they rolled out this system at a time when hundreds of thousands of users had millions of T tokens in their possession. Not taking ten seconds to change the text on that button to say "Cash or T Tokens" cost tens of thousands of hours or more in lost productivity for T riders: add just 30 seconds to the time it takes one person to complete a transaction, and that one transaction has added a total of five minutes in wait time for the 10 people in line behind him. 

Working with you guys in the late 90s was a defining experience for me as a programmer -- whenever I wanted to cut corners, you kept me honest, and that's something that's stuck with me ever since. These kiosks were definitely designed by programmers who'd never worked with Dave Rondeau.</description>
		<content:encoded><![CDATA[<p>Hey Dave!</p>
<p>Excellent article! I just discovered kids could ride free this week when my nephews visited &#8212; and I&#8217;ve been riding the T since college. It might be nice if they posted that info somewhere obvious, like maybe on the fare kiosks.</p>
<p>I remember the first time I used one of those kiosks, just after they were installed. The person in front of me only had T tokens, which of course were no longer accepted. An impatient T employee was helping him through the process and laying on the ol&#8217; Boston charm. an excerpt:<br />
&#8212;&#8211;<br />
Surly T Employee: Click the &#8216;Cash&#8217; button. CLICK THE &#8216;CASH&#8217; BUTTON. DO YOU SPEAK ENGLISH?<br />
Befuddled Passenger: But I only have tokens&#8230;<br />
Surly T Employee: CLICK THE &#8216;CASH&#8217; BUTTON!! &#8230; Now click &#8216;Other Amount&#8217; &#8230; now drop your tokens in the slot.<br />
&#8212;&#8211;</p>
<p>I was appalled. How the heck was someone supposed to know to press &#8220;Cash&#8221; and then drop in T tokens? They certainly aren&#8217;t cash, and the icons next to the coin slot indicate that the machine only accepts nickels, dimes, quarters, and dollar coins. </p>
<p>And yet they rolled out this system at a time when hundreds of thousands of users had millions of T tokens in their possession. Not taking ten seconds to change the text on that button to say &#8220;Cash or T Tokens&#8221; cost tens of thousands of hours or more in lost productivity for T riders: add just 30 seconds to the time it takes one person to complete a transaction, and that one transaction has added a total of five minutes in wait time for the 10 people in line behind him. </p>
<p>Working with you guys in the late 90s was a defining experience for me as a programmer &#8212; whenever I wanted to cut corners, you kept me honest, and that&#8217;s something that&#8217;s stuck with me ever since. These kiosks were definitely designed by programmers who&#8217;d never worked with Dave Rondeau.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interaction Design and the Boston Subway by Harlan</title>
		<link>http://incontextdesign.com/blog/interaction-design-and-the-boston-subway/comment-page-1/#comment-11</link>
		<dc:creator>Harlan</dc:creator>
		<pubDate>Tue, 07 Jul 2009 22:57:21 +0000</pubDate>
		<guid isPermaLink="false">http://69.89.31.90/~incontex/?p=1292#comment-11</guid>
		<description>It's definitely interesting - when considering the T kiosk, you have to consider all the service touchpoints implied by that single interface. 

For example, the acquisition of one of the core elements of the system, the CharlieCard, is completely divorced from the kiosk itself - neither a description of what it is or where to get one is present in the kiosk UI or surrounding documentation. 

Similarly, the underlying structure of the system doesn't take user behavior into account - since you cannot buy monthly passes for a given month before the 1st of each month, the system often collapses under the weight of every commuter in the Boston area trying to obtain their passes between 8-9am.

The CharlieCard system has been in place for a year or so now, you'd think they would have addressed some of these obvious issues by now!</description>
		<content:encoded><![CDATA[<p>It&#8217;s definitely interesting - when considering the T kiosk, you have to consider all the service touchpoints implied by that single interface. </p>
<p>For example, the acquisition of one of the core elements of the system, the CharlieCard, is completely divorced from the kiosk itself - neither a description of what it is or where to get one is present in the kiosk UI or surrounding documentation. </p>
<p>Similarly, the underlying structure of the system doesn&#8217;t take user behavior into account - since you cannot buy monthly passes for a given month before the 1st of each month, the system often collapses under the weight of every commuter in the Boston area trying to obtain their passes between 8-9am.</p>
<p>The CharlieCard system has been in place for a year or so now, you&#8217;d think they would have addressed some of these obvious issues by now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interaction Design and the Boston Subway by Jason Robb</title>
		<link>http://incontextdesign.com/blog/interaction-design-and-the-boston-subway/comment-page-1/#comment-10</link>
		<dc:creator>Jason Robb</dc:creator>
		<pubDate>Mon, 06 Jul 2009 17:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://69.89.31.90/~incontex/?p=1292#comment-10</guid>
		<description>David,

Great write-up! I especially like the part when you find out your son rides for free. Haha, that must have made you laugh, too. Shesh...

I wonder who was on the design team when they thought it up?

They should have prototyped and tested it. Wouldn't have taken many people to identify those issues.

Thanks for sharing!

Jason R.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Great write-up! I especially like the part when you find out your son rides for free. Haha, that must have made you laugh, too. Shesh&#8230;</p>
<p>I wonder who was on the design team when they thought it up?</p>
<p>They should have prototyped and tested it. Wouldn&#8217;t have taken many people to identify those issues.</p>
<p>Thanks for sharing!</p>
<p>Jason R.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Irreverence of Users by Hugh Beyer</title>
		<link>http://incontextdesign.com/blog/the-irreverence-of-users/comment-page-1/#comment-8</link>
		<dc:creator>Hugh Beyer</dc:creator>
		<pubDate>Wed, 24 Jun 2009 13:06:41 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/blog/the-irreverence-of-users/#comment-8</guid>
		<description>See how "this video" in the last paragraph is blue? Point at it and you'll see it's a link.</description>
		<content:encoded><![CDATA[<p>See how &#8220;this video&#8221; in the last paragraph is blue? Point at it and you&#8217;ll see it&#8217;s a link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Irreverence of Users by Don Mitchell</title>
		<link>http://incontextdesign.com/blog/the-irreverence-of-users/comment-page-1/#comment-7</link>
		<dc:creator>Don Mitchell</dc:creator>
		<pubDate>Wed, 24 Jun 2009 12:33:30 +0000</pubDate>
		<guid isPermaLink="false">http://incontextdesign.com/blog/the-irreverence-of-users/#comment-7</guid>
		<description>Where is the link for the video?</description>
		<content:encoded><![CDATA[<p>Where is the link for the video?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
