<?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: The Hidden UX We Miss</title>
	<atom:link href="http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/feed/" rel="self" type="application/rss+xml" />
	<link>http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/</link>
	<description>Gary Barber rants on user experience, information architecture and the web industry.</description>
	<pubDate>Thu, 24 Jul 2008 14:01:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Gary Barber</title>
		<link>http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/#comment-7794</link>
		<dc:creator>Gary Barber</dc:creator>
		<pubDate>Mon, 14 Apr 2008 05:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=172#comment-7794</guid>
		<description>@dean that's where you need to call in the famous UX consultant to weave their magic and solve all the worlds problems before 11:00.  :)  

Seriously the use of externals often plugs the gap.  Sadly budget and some IT manager egos tend to stop this process.</description>
		<content:encoded><![CDATA[<p>@dean that&#8217;s where you need to call in the famous UX consultant to weave their magic and solve all the worlds problems before 11:00.  <img src='http://manwithnoblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  </p>
<p>Seriously the use of externals often plugs the gap.  Sadly budget and some IT manager egos tend to stop this process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Groom</title>
		<link>http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/#comment-7793</link>
		<dc:creator>Dean Groom</dc:creator>
		<pubDate>Mon, 14 Apr 2008 04:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=172#comment-7793</guid>
		<description>The problem for IT (I head the dept) is that everyone who should be involved are too 'busy' to get involved, but more than happy to comment after. The people who need to be involved are all too often happy to watch it sail south to IT, at least they dont have to do MORE work, and then they can moan about it later ... the IT folk are not suprised by this, it's par for the course!</description>
		<content:encoded><![CDATA[<p>The problem for IT (I head the dept) is that everyone who should be involved are too &#8216;busy&#8217; to get involved, but more than happy to comment after. The people who need to be involved are all too often happy to watch it sail south to IT, at least they dont have to do MORE work, and then they can moan about it later &#8230; the IT folk are not suprised by this, it&#8217;s par for the course!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Winter-Giles</title>
		<link>http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/#comment-7791</link>
		<dc:creator>Ben Winter-Giles</dc:creator>
		<pubDate>Mon, 14 Apr 2008 03:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=172#comment-7791</guid>
		<description>Thanks Gary,
UX. always a hard pill for the accountants to swallow.

I once did a very quick survey about how long it took an organisation to publish an 'average' web page, and to make an 'average' web page change / update. (surveyed across a wide selection of web authors I might add, to provide a nice supportive average)

And then I took to them a prototype which we used to measure the time taken to complete the same tasks.

Now barring the foibles of the prototype at the time, we were able to demonstrate a significant time saving.

That said, they still went with a 'low investment' tune of the administrative area, because the benefits gained simply were still not in the favour of investing more on the admin side.

They did however invest more heavily in the client side, which I guess was a decent-ish trade off.

Sadly, unless the developers take the intitive to invest in the administrative sides of sites, then Business are not likely to take any heed of our pain (as authors and what not).

But like many things in other industries (automotive, manufacturing, building construction), as time passes, and globally our ability to easily and repeatedly deliver improved background tools, we shall start to see better and better admin sides.

They still try to make better hammers, despite they all do much the same thing.</description>
		<content:encoded><![CDATA[<p>Thanks Gary,<br />
UX. always a hard pill for the accountants to swallow.</p>
<p>I once did a very quick survey about how long it took an organisation to publish an &#8216;average&#8217; web page, and to make an &#8216;average&#8217; web page change / update. (surveyed across a wide selection of web authors I might add, to provide a nice supportive average)</p>
<p>And then I took to them a prototype which we used to measure the time taken to complete the same tasks.</p>
<p>Now barring the foibles of the prototype at the time, we were able to demonstrate a significant time saving.</p>
<p>That said, they still went with a &#8216;low investment&#8217; tune of the administrative area, because the benefits gained simply were still not in the favour of investing more on the admin side.</p>
<p>They did however invest more heavily in the client side, which I guess was a decent-ish trade off.</p>
<p>Sadly, unless the developers take the intitive to invest in the administrative sides of sites, then Business are not likely to take any heed of our pain (as authors and what not).</p>
<p>But like many things in other industries (automotive, manufacturing, building construction), as time passes, and globally our ability to easily and repeatedly deliver improved background tools, we shall start to see better and better admin sides.</p>
<p>They still try to make better hammers, despite they all do much the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Buchanan</title>
		<link>http://manwithnoblog.com/2008/04/14/the-hidden-ux-we-miss/#comment-7790</link>
		<dc:creator>Ben Buchanan</dc:creator>
		<pubDate>Mon, 14 Apr 2008 02:02:38 +0000</pubDate>
		<guid isPermaLink="false">http://manwithnoblog.com/?p=172#comment-7790</guid>
		<description>I think a lot of this problem is that the cost of a bad intranet is a bit of a hidden cost. 

How do you quantify the amount of money lost because someone struggled with the interface? How do you prove that the fault is with the system and not the user? How do you prove that better UX would lead to bottom-line cost savings?

It's made harder by the fact that, due to their very nature, companies with good intranets can't/don't show them off! I've seen many articles written about top intranets, but they're pretty useless articles most of the time since you can't see what you're talking about.

Companies also cling to the idea that they can simply mandate "use the intranet!" as if staff can't find a way around them. 

Can't use the arcane calendar system? Switch everyone to Google Calendar or some hosted groupware solution. Can't share documents through the impenetrable document sharing bohemoth? Screw it, use Pownce.

The mob is very definitely stronger and faster than the organisation it works for.</description>
		<content:encoded><![CDATA[<p>I think a lot of this problem is that the cost of a bad intranet is a bit of a hidden cost. </p>
<p>How do you quantify the amount of money lost because someone struggled with the interface? How do you prove that the fault is with the system and not the user? How do you prove that better UX would lead to bottom-line cost savings?</p>
<p>It&#8217;s made harder by the fact that, due to their very nature, companies with good intranets can&#8217;t/don&#8217;t show them off! I&#8217;ve seen many articles written about top intranets, but they&#8217;re pretty useless articles most of the time since you can&#8217;t see what you&#8217;re talking about.</p>
<p>Companies also cling to the idea that they can simply mandate &#8220;use the intranet!&#8221; as if staff can&#8217;t find a way around them. </p>
<p>Can&#8217;t use the arcane calendar system? Switch everyone to Google Calendar or some hosted groupware solution. Can&#8217;t share documents through the impenetrable document sharing bohemoth? Screw it, use Pownce.</p>
<p>The mob is very definitely stronger and faster than the organisation it works for.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
