<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rod Motta - User Experience Visual Designer &#187; customer</title>
	<atom:link href="http://rodmotta.com/blog/tag/customer/feed/" rel="self" type="application/rss+xml" />
	<link>http://rodmotta.com/blog</link>
	<description>Design, Social Media, Business &#38; Everything in Between.</description>
	<lastBuildDate>Mon, 07 May 2012 23:14:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Lean UX: Designing in Agile</title>
		<link>http://rodmotta.com/blog/2012/04/30/lean-ux-designing-in-agile/</link>
		<comments>http://rodmotta.com/blog/2012/04/30/lean-ux-designing-in-agile/#comments</comments>
		<pubDate>Tue, 01 May 2012 05:56:54 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[leanux]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=336</guid>
		<description><![CDATA[I attended the UX Immersion – Agile &#38; Mobile Design Conference in Portland last week, where I had amazing learning sessions (workshops and talks) on Agile and Mobile design. One workshop I especially liked was Jeff Gothelf&#8217;s &#8216;Lean UX: A Seasoned Approach to Designing in Agile&#8217;. What is Lean UX? Lean UX is inspired by [...]]]></description>
			<content:encoded><![CDATA[<p>I attended the <a href="http://www.uie.com/events/ux_immersion/2012/" target="_blank">UX Immersion – Agile &amp; Mobile Design Conference</a> in Portland last week, where I had amazing learning sessions (workshops and talks) on Agile and Mobile design.</p>
<p>One workshop I especially liked was Jeff Gothelf&#8217;s &#8216;Lean UX: A Seasoned Approach to Designing in Agile&#8217;.</p>
<p>What is Lean UX? Lean UX is inspired by Lean Startup and Agile development theories. It&#8217;s about reducing waste: Light faster, collaboration, cross functional, less emphasis on deliverables and more focus on the actual user experience. The more shared understanding we have, the thinner the spec is.</p>
<p>So in essence, our designs are hypotheses; let’s validate or invalidate those hypotheses as quickly as possible so that we can spend time going down the right path and less time going down the wrong paths.</p>
<p>Lean UX brings usability testing to every sprint to validate design hypotheses with customers, and data is used to settle subjective issues.</p>
<p>According to Jeff, when we have the designers, the developers, and the business owners all in the same room sort of working on solving a problem collaboratively, suddenly all that subtly and nuance as to what design is about becomes transparent. The value of the designer becomes even more evident when the collaboration is working at the highest levels. The expertise and the different disciplines that all go into software design and user experience design start to emerge and become very obvious to the team.</p>
<p>I recommend watching this <a href="http://www.youtube.com/watch?v=AW5VpqjpMcc&amp;list=PLC113D08D2D4D78A2&amp;index=3" target="_blank">5 min video</a> where Jeff talks about &#8216;How to do Lean UX in 5 easy steps&#8217;. Or check out his <a href="http://www.slideshare.net/jgothelf/lean-ux-getting-out-of-the-deliverables-business" target="_blank">Lean UX presentation</a> on SlideShare.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2012/04/30/lean-ux-designing-in-agile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Web Accessibility no longer an afterthought</title>
		<link>http://rodmotta.com/blog/2009/12/17/web-accessibility-no-longer-an-afterthought/</link>
		<comments>http://rodmotta.com/blog/2009/12/17/web-accessibility-no-longer-an-afterthought/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 02:36:36 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[Accessibility]]></category>
		<category><![CDATA[business]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[functionality]]></category>
		<category><![CDATA[trends]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=214</guid>
		<description><![CDATA[Yesterday I came across this interesting web accessibility article at CNN.com, talking about how big internet companies such as Yahoo and Google are embracing it. We should all start an accessibility push in our organizations, here&#8217;s why: There are about 60 million people in the U.S. who can&#8217;t use a computer to get on the [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday I came across this interesting <strong><a title="Web Accessibility Article" href="http://www.cnn.com/2009/TECH/12/15/cnet.web.accessibility/index.html" target="_blank">web accessibility article</a></strong> at CNN.com, talking about how big internet companies such as Yahoo and Google are embracing it.</p>
<p>We should all start an accessibility push in our organizations, here&#8217;s why:</p>
<ul>
<li>There are about 60 million people in the U.S. who can&#8217;t use a computer to get on the Internet in the normal fashion. For those people, a mix of screen reader software, keyboards with special buttons, and even motion-sensing Web cameras must take the place of the mouse and QWERTY keyboard.</li>
<p><br/></p>
<li>With a rapidly aging population in many parts of the world &#8212; notably the U.S. &#8212; accessibility requirements will become useful for today&#8217;s crop of baby boomers as they grow older</li>
<p><br/></p>
<li>In order to do business with the U.S. government, companies must comply with Section 508 of the Rehabilitation Act, which insists that electronic and information technology products sold to government agencies be designed with disabled employees in mind, and that government services produced by contractors consider disabled citizens in equal measure.</li>
</ul>
<p>Performance, internationalization, and accessibility are not a feature, they should all be standard.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/12/17/web-accessibility-no-longer-an-afterthought/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Reactions to the imaginary threat of extinction</title>
		<link>http://rodmotta.com/blog/2009/11/06/reactions-to-the-imaginary-threat-of-extinction/</link>
		<comments>http://rodmotta.com/blog/2009/11/06/reactions-to-the-imaginary-threat-of-extinction/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 20:05:03 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[ux]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=199</guid>
		<description><![CDATA[Build every feature any customer would ever want: Apparently, by having all the features anyone can ever imagine, &#8220;eliminate any possible reason that customers might buy a competitors’ product&#8221;. That’s a wrong conclusion and a really bad idea. Software that tries to be everything to everyone generally sucks. It becomes bloated, hard to use, and [...]]]></description>
			<content:encoded><![CDATA[<ol>
<li>Build every feature any customer would ever want: Apparently, by having all the features anyone can ever imagine, &#8220;eliminate any possible reason that customers might buy a competitors’ product&#8221;. That’s a wrong conclusion and a really bad idea. Software that tries to be everything to everyone generally sucks. It becomes bloated, hard to use, and in need of big up-front training, which is probably a  good definition of enterprise software right there.</li>
<p><br/></p>
<li>Become a sales force-driven company: Hire a bunch of sales people and make them convince people to buy your software. Side step the actual users, the developers, and go straight to management. The sales people will invariably promise more than you have and drive you even deeper into &#8220;build everything for everyone&#8221;.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/11/06/reactions-to-the-imaginary-threat-of-extinction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stop and take time to find the direction.</title>
		<link>http://rodmotta.com/blog/2009/10/04/stop-and-take-time-to-find-the-direction/</link>
		<comments>http://rodmotta.com/blog/2009/10/04/stop-and-take-time-to-find-the-direction/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 19:29:19 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[strategy]]></category>
		<category><![CDATA[tactics]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=192</guid>
		<description><![CDATA[A Good Experience blog post by Mark Hurst has an amusing and insightful post on strategy as opposed to tactics: Why is finding direction (or strategy) so rare, so difficult? One reason is that creating the strategy is different from execution. You have to stop and take time to find the direction. You can&#8217;t run [...]]]></description>
			<content:encoded><![CDATA[<p>A <em>Good Experience</em> blog post by Mark Hurst has an amusing and insightful post on <a title="Strategy as opposed to tactics" href="http://goodexperience.com/2009/09/a-lesson-in-strategy.php" target="_blank">strategy as opposed to tactics:</a></p>
<p>Why is finding direction (or strategy) so rare, so difficult? One reason is that creating the strategy is different from execution.</p>
<p>You have to stop and take time to find the direction. You can&#8217;t run while you&#8217;re reading the map.</p>
<p>And this is the potential problem with popular methods such as:</p>
<p>• iterative design<br />
• rapid prototyping<br />
• agile development</p>
<p>&#8230;which are great and all, except when there&#8217;s no well-thought-out direction to go in.</p>
<p>So be forewarned &#8211; it&#8217;s hard to be a strategist. People prefer action. &#8220;Ready-fire-aim&#8221; sounds so much more exciting and appealing. &#8220;<em>Do</em> something!&#8221; they say &#8211; and it can be hard to sit down and say hey, let&#8217;s take at least a couple of days to think about who our customers are and talk to them about what they need.</p>
<p>Speaking with the customers refines and narrows the direction. After all you are fulfilling their needs.</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/10/04/stop-and-take-time-to-find-the-direction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The pleasing paradox phenomenon</title>
		<link>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/</link>
		<comments>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 21:32:18 +0000</pubDate>
		<dc:creator>Rod Motta</dc:creator>
				<category><![CDATA[business]]></category>
		<category><![CDATA[Design Inspirations]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[customer]]></category>
		<category><![CDATA[feedback]]></category>

		<guid isPermaLink="false">http://rodmotta.com/blog/?p=181</guid>
		<description><![CDATA[We try so hard to please our client(s) that we fail to do what would be truly pleasing. That includes also giving our client critical feedback. The challenge is to be of service without becoming servile. We shouldn’t elevate any customer to the role of superior being, but treat each with human respect. The key [...]]]></description>
			<content:encoded><![CDATA[<p>We try so hard to please our client(s) that we fail to do what would be truly pleasing. That includes also giving our client critical feedback.</p>
<p><span>The challenge is to be of service without becoming servile. We shouldn’t elevate any customer to the role of superior being, but treat each with human respect.</span></p>
<p><span>The key to becoming a stellar service provider lies in making only responsible commitments. This requires not simply being knowledgeable about what must be done but “no-legible” about how preferences resolve into satisfying results. We must know how and when to say, “No,” because no one can know what will finally emerge as best. Client and designer will have to discover what constitutes best, and this always means stumbling through some uncomfortable territory together.</span></p>
<p>It’s crazy how much more satisfying to it is when you are able to present an even better solution to the problem they were really hoping for when they were offering suggestions or ideas.</p>
<p>Of course you’ve heard this Henry Ford quote a hundred times:<br />
&#8220;If I had asked my customers what they wanted, they would have said a faster horse.”</p>
<p>Or Tom Kelley&#8217;s (IDEO&#8217;s general manager) translation of that:<br />
&#8220;Customers don’t envision the future, they inform the present.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://rodmotta.com/blog/2009/08/07/the-pleasing-paradox-phenomenon/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

