<?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"
	>
<channel>
	<title>Comments on: Good UI or New Web Hubris?</title>
	<atom:link href="http://theappslab.com/2008/04/18/good-ui-or-new-web-hubris/feed/" rel="self" type="application/rss+xml" />
	<link>http://theappslab.com/2008/04/18/good-ui-or-new-web-hubris/</link>
	<description>Driving Innovation</description>
	<pubDate>Sat, 22 Nov 2008 21:57:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jake</title>
		<link>http://theappslab.com/2008/04/18/good-ui-or-new-web-hubris/#comment-3725</link>
		<dc:creator>Jake</dc:creator>
		<pubDate>Sat, 19 Apr 2008 16:17:31 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/?p=809#comment-3725</guid>
		<description>@Ted: Thanks for sharing your experiences. Did you know Paul used to run PeopleSoft Portal? I think Rich was a developer on that product too.

UI is an 80/20 problem. There are so many types and levels of users that it's virtually impossible to please everyone. I used to do technical consulting, which included Form design/build in R11 EBS. It was surprisingly tough to please even a handful of users with a Form built totally to their specs.

That's UI for you. We did keep the pen, albeit within a button.</description>
		<content:encoded><![CDATA[<p>@Ted: Thanks for sharing your experiences. Did you know Paul used to run PeopleSoft Portal? I think Rich was a developer on that product too.</p>
<p>UI is an 80/20 problem. There are so many types and levels of users that it&#8217;s virtually impossible to please everyone. I used to do technical consulting, which included Form design/build in R11 EBS. It was surprisingly tough to please even a handful of users with a Form built totally to their specs.</p>
<p>That&#8217;s UI for you. We did keep the pen, albeit within a button.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Simpson</title>
		<link>http://theappslab.com/2008/04/18/good-ui-or-new-web-hubris/#comment-3717</link>
		<dc:creator>Ted Simpson</dc:creator>
		<pubDate>Sat, 19 Apr 2008 11:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/?p=809#comment-3717</guid>
		<description>Usability testing seems a slippery thing to me; I sat in on a usability testing session recently on some new web apps we are building. The pros running the session seemed to have 2 responses: if the testing results were positive, they high-fived each other because their UI design was great; if the testing results were negative, they explained that the UI features would be adopted by "learned behavior" in time. Either way, the testing did not prompt changes to the UI. I asked them why they did testing at all if the results weren't actionable. They told me I "didn't get it". 

It takes discipline and nerve to put something new out; when we rolled out our PeopleSoft Portal 9.0 last fall, we did not make dramatic changes based on individual user comments -- reasoning instead that the research we did with our user base to develop the new UI and IA was solid and trustworthy. Now those UI and IA features have been adopted.

Another example of UI gone wild is PeopleSoft Campus Solutions 9.0. This is the best UI yet in ERP applications (I say); but, we had complaints from users when we first rolled it out that there were too many ways to navigate (enterprise menu navigation, embedded links, contextual search, and contextual navigation all on the same page). We noted that these were the same users who complained that navigation in prior version used to be too basic for their sophisticated needs and moved on.  

I suppose it is a balance. The AppsLab experiences and blog are helpful and instructive to us who are moving into the NEW world, so thanks.

For what it is worth -- I liked the pen icon ;)

-Ted</description>
		<content:encoded><![CDATA[<p>Usability testing seems a slippery thing to me; I sat in on a usability testing session recently on some new web apps we are building. The pros running the session seemed to have 2 responses: if the testing results were positive, they high-fived each other because their UI design was great; if the testing results were negative, they explained that the UI features would be adopted by &#8220;learned behavior&#8221; in time. Either way, the testing did not prompt changes to the UI. I asked them why they did testing at all if the results weren&#8217;t actionable. They told me I &#8220;didn&#8217;t get it&#8221;. </p>
<p>It takes discipline and nerve to put something new out; when we rolled out our PeopleSoft Portal 9.0 last fall, we did not make dramatic changes based on individual user comments &#8212; reasoning instead that the research we did with our user base to develop the new UI and IA was solid and trustworthy. Now those UI and IA features have been adopted.</p>
<p>Another example of UI gone wild is PeopleSoft Campus Solutions 9.0. This is the best UI yet in ERP applications (I say); but, we had complaints from users when we first rolled it out that there were too many ways to navigate (enterprise menu navigation, embedded links, contextual search, and contextual navigation all on the same page). We noted that these were the same users who complained that navigation in prior version used to be too basic for their sophisticated needs and moved on.  </p>
<p>I suppose it is a balance. The AppsLab experiences and blog are helpful and instructive to us who are moving into the NEW world, so thanks.</p>
<p>For what it is worth &#8212; I liked the pen icon <img src='http://theappslab.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>-Ted</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Pedrazzi</title>
		<link>http://theappslab.com/2008/04/18/good-ui-or-new-web-hubris/#comment-3700</link>
		<dc:creator>Paul Pedrazzi</dc:creator>
		<pubDate>Fri, 18 Apr 2008 18:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://oracleappslab.com/?p=809#comment-3700</guid>
		<description>Yes the icon was a change that didn't work.  The great thing is that the nature of how we work and the ability of the web to connect us, told us immediately.  We didn't have to wait months to find out.  I would also stress that it's the participatory model that is different now - not so much the UI.  Personally, I have always felt that icons were a bit more 1.0 in the sense of what you'd see on a typical client app.  The simple links as buttons (ie. click to save) I find very clean, simple, and intuitive.  

That said, there is another lesson here.  One that anyone who deals with customers knows.  If you hear a complaint from one person, there are 10 more that didn't bother to say anything, but were unhappy nonetheless.  This goes for restaurants, dentists, and yes even software.  So when we heard quickly from 5 or 10 people, we jumped, and jumped high.

Paul</description>
		<content:encoded><![CDATA[<p>Yes the icon was a change that didn&#8217;t work.  The great thing is that the nature of how we work and the ability of the web to connect us, told us immediately.  We didn&#8217;t have to wait months to find out.  I would also stress that it&#8217;s the participatory model that is different now - not so much the UI.  Personally, I have always felt that icons were a bit more 1.0 in the sense of what you&#8217;d see on a typical client app.  The simple links as buttons (ie. click to save) I find very clean, simple, and intuitive.  </p>
<p>That said, there is another lesson here.  One that anyone who deals with customers knows.  If you hear a complaint from one person, there are 10 more that didn&#8217;t bother to say anything, but were unhappy nonetheless.  This goes for restaurants, dentists, and yes even software.  So when we heard quickly from 5 or 10 people, we jumped, and jumped high.</p>
<p>Paul</p>
]]></content:encoded>
	</item>
</channel>
</rss>
