<?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: Why Not Just Try Designing? &#8211; Trusting the Ability and Conviction of Experienced Designers</title>
	<atom:link href="http://danielmckenzie.com/blog/2010/02/why-not-just-try-designing-trusting-the-ability-and-conviction-of-experienced-designers/feed/" rel="self" type="application/rss+xml" />
	<link>http://danielmckenzie.com/blog/2010/02/why-not-just-try-designing-trusting-the-ability-and-conviction-of-experienced-designers/</link>
	<description>Musings on design matters, technology and culture.</description>
	<lastBuildDate>Wed, 25 Jan 2012 17:24:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Jim Washok</title>
		<link>http://danielmckenzie.com/blog/2010/02/why-not-just-try-designing-trusting-the-ability-and-conviction-of-experienced-designers/comment-page-1/#comment-241</link>
		<dc:creator>Jim Washok</dc:creator>
		<pubDate>Wed, 24 Feb 2010 23:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://danielmckenzie.com/blog/?p=363#comment-241</guid>
		<description>I can see your interpretations of the actions of both companies. Perhaps their actions are reflective of design laziness or fear. On the other hand, the actions of Company A in releasing updates to a subset of users for &quot;testing&quot; may be more reflective of the nature of their software offering such that inaccuracies are not tolerated (such as an online stock trading firm). They may have such a large user base that 100% rollout could result in infrastructure issues or a flood of support requests. The approach may be to simply empower users with the choice of when to switch from an interface they are comfortable with to a new one. You use Apple as an example and I agree that they are fearless in their designs, but they don&#039;t force you to upgrade to their latest OS or buy newest generation of iPhone... the consumer has that choice. The user of a SaaS product is at the company&#039;s mercy. In other words, the company may be just as comfortable as Apple with their designs, but also cognizant of the issues with forcing their users to change.

I&#039;m with you on Company B. While they may think they are being considerate by involving mass users in interface design, most users don&#039;t know what they want. If they want some user input, it would be more appropriate to identify a few select users that they know from past interactions are appropriate to participate in UI design.

@Ben I had an original iPhone and did not experience any glaring problems... not saying there weren&#039;t any. It would be beneficial for you to identify a few rather than using generalizations without evidence. Though you did not specifically state the &quot;problems&quot; were actually a lack of features, such as multitasking or syncing to-dos, if it may be the case, I suggest refraining from equating &quot;problems&quot; with purposeful withholding of features. Apple does not design around features, they design around the user and ease of use; yet, they somehow manage to make the device/software work just as well, if not better, than competing products. I think Apple&#039;s reputation and confidence are such that they wouldn&#039;t risk testing a product with a first version to users. I think it&#039;s just natural for companies, like individuals, to learn more and appropriately adapt when in the &quot;real world&quot;.

In light of both of your comments, I&#039;m hopeful that increased interest among companies for user / interactive experience designers will help improve the condition of product and software design... with the welcome side effect of improved customer service.</description>
		<content:encoded><![CDATA[<p>I can see your interpretations of the actions of both companies. Perhaps their actions are reflective of design laziness or fear. On the other hand, the actions of Company A in releasing updates to a subset of users for &#8220;testing&#8221; may be more reflective of the nature of their software offering such that inaccuracies are not tolerated (such as an online stock trading firm). They may have such a large user base that 100% rollout could result in infrastructure issues or a flood of support requests. The approach may be to simply empower users with the choice of when to switch from an interface they are comfortable with to a new one. You use Apple as an example and I agree that they are fearless in their designs, but they don&#8217;t force you to upgrade to their latest OS or buy newest generation of iPhone&#8230; the consumer has that choice. The user of a SaaS product is at the company&#8217;s mercy. In other words, the company may be just as comfortable as Apple with their designs, but also cognizant of the issues with forcing their users to change.</p>
<p>I&#8217;m with you on Company B. While they may think they are being considerate by involving mass users in interface design, most users don&#8217;t know what they want. If they want some user input, it would be more appropriate to identify a few select users that they know from past interactions are appropriate to participate in UI design.</p>
<p>@Ben I had an original iPhone and did not experience any glaring problems&#8230; not saying there weren&#8217;t any. It would be beneficial for you to identify a few rather than using generalizations without evidence. Though you did not specifically state the &#8220;problems&#8221; were actually a lack of features, such as multitasking or syncing to-dos, if it may be the case, I suggest refraining from equating &#8220;problems&#8221; with purposeful withholding of features. Apple does not design around features, they design around the user and ease of use; yet, they somehow manage to make the device/software work just as well, if not better, than competing products. I think Apple&#8217;s reputation and confidence are such that they wouldn&#8217;t risk testing a product with a first version to users. I think it&#8217;s just natural for companies, like individuals, to learn more and appropriately adapt when in the &#8220;real world&#8221;.</p>
<p>In light of both of your comments, I&#8217;m hopeful that increased interest among companies for user / interactive experience designers will help improve the condition of product and software design&#8230; with the welcome side effect of improved customer service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Liyanage</title>
		<link>http://danielmckenzie.com/blog/2010/02/why-not-just-try-designing-trusting-the-ability-and-conviction-of-experienced-designers/comment-page-1/#comment-240</link>
		<dc:creator>Ben Liyanage</dc:creator>
		<pubDate>Wed, 24 Feb 2010 17:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://danielmckenzie.com/blog/?p=363#comment-240</guid>
		<description>I have to say, Apple is not a great example.  I bought a first generation iphone.  Sure it was innovative, but the product had a lot of problems, and plenty more innovation needed.  My experiences with the device changed my opinion on Apple.  

When they came out with the first iPhone, I told everyone I knew not to buy a first generation iPhone.  Apple was testing the waters on their consumers just like they did with the iPod.  I recommended to people to wait one year while Apple ironed out the problems and release a new and better version.

I recommend patience with the iPad as well.</description>
		<content:encoded><![CDATA[<p>I have to say, Apple is not a great example.  I bought a first generation iphone.  Sure it was innovative, but the product had a lot of problems, and plenty more innovation needed.  My experiences with the device changed my opinion on Apple.  </p>
<p>When they came out with the first iPhone, I told everyone I knew not to buy a first generation iPhone.  Apple was testing the waters on their consumers just like they did with the iPod.  I recommended to people to wait one year while Apple ironed out the problems and release a new and better version.</p>
<p>I recommend patience with the iPad as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

