<?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>Metricology &#187; Portfolio</title>
	<atom:link href="http://metricology.com/category/portfolio/feed/" rel="self" type="application/rss+xml" />
	<link>http://metricology.com</link>
	<description>Make informed decisions about your audience</description>
	<lastBuildDate>Mon, 26 Apr 2010 17:03:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Nokia Accessories</title>
		<link>http://metricology.com/2009/09/25/nokia-accessories/</link>
		<comments>http://metricology.com/2009/09/25/nokia-accessories/#comments</comments>
		<pubDate>Fri, 25 Sep 2009 19:10:37 +0000</pubDate>
		<dc:creator>Bryan J Busch</dc:creator>
				<category><![CDATA[Portfolio]]></category>

		<guid isPermaLink="false">http://metricology.com/?p=43</guid>
		<description><![CDATA[Situation
The detailed information for mobile phone accessories appeared as a sort of &#8220;data dump&#8221;. The information was all there, but it wasn&#8217;t being structured in a useful manner. We ran several groups of usability tests with potential customers and found specific issues with the navigation:

Solution
In particular, people had trouble navigating the different categories of accessories [...]]]></description>
			<content:encoded><![CDATA[<h3>Situation</h3>
<p>The detailed information for mobile phone accessories appeared as a sort of &#8220;data dump&#8221;. The information was all there, but it wasn&#8217;t being structured in a useful manner. We ran several groups of usability tests with potential customers and found specific issues with the navigation:<span id="more-43"></span></p>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/nokia-ck-7w-orginal.png"><img src="http://metricology.com/wp-content/uploads/2009/09/nokia-ck-7w-orginal-532x564.png" alt="nokia-ck-7w-orginal" title="nokia-ck-7w-orginal" width="532" height="564" class="aligncenter size-large wp-image-44" /></a></p>
<h3>Solution</h3>
<p>In particular, people had trouble navigating the different categories of accessories (“what are Imaging Products?”), determining whether their phone would be compatible, and most critically, finding the &#8220;Buy Now&#8221; button.</p>
<p>My visual designer companion and I addressed these and more issues in the following mock up:</p>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/nokia_accessories.jpg"><img src="http://metricology.com/wp-content/uploads/2009/09/nokia_accessories-532x615.jpg" alt="nokia_accessories" title="nokia_accessories" width="532" height="615" class="aligncenter size-large wp-image-45" /></a></p>
<p>We invented the &#8220;Is Your Phone Compatible&#8221; tool, redesigned the category browsing to expose more detail, and included a task-based navigation, as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://metricology.com/2009/09/25/nokia-accessories/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Payment Request Action Screen (Wireframe)</title>
		<link>http://metricology.com/2009/09/25/payment-request-action-screen-wireframe/</link>
		<comments>http://metricology.com/2009/09/25/payment-request-action-screen-wireframe/#comments</comments>
		<pubDate>Fri, 25 Sep 2009 19:04:48 +0000</pubDate>
		<dc:creator>Bryan J Busch</dc:creator>
				<category><![CDATA[Portfolio]]></category>

		<guid isPermaLink="false">http://metricology.com/?p=38</guid>
		<description><![CDATA[A payment processing system, which had been mostly command-line for many years was being re-engineered to make use of a GUI. After analyzing dozens of use cases, I created wire frames to illustrate each unique situation. An example is below (click for larger version):

Particularly noteworthy:

The payments are always running, unless manually overriden, so I invented [...]]]></description>
			<content:encoded><![CDATA[<p>A payment processing system, which had been mostly command-line for many years was being re-engineered to make use of a GUI. After analyzing dozens of use cases, I created wire frames to illustrate each unique situation. <span id="more-38"></span>An example is below (click for larger version):</p>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/payment-request.png"><img src="http://metricology.com/wp-content/uploads/2009/09/payment-request.png" alt="payment-request" title="payment-request" width="502" height="930" class="aligncenter size-full wp-image-39" /></a></p>
<p>Particularly noteworthy:</p>
<ul>
<li>The payments are always running, unless manually overriden, so I invented a &#8220;CD-player style&#8221; control scheme near the top of the page</li>
<li>&#8220;Date of Payment&#8221; was often referred to as the most critical piece of data, so it gets its own special treatment</li>
<li>Comments are separated between System and User messages with a monospaced font for the System messages</li>
<li>Efficiency was a key concern for the system, so I included the option of inserting a comment based on frequently-used comments instead of typing the same thing over and over.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://metricology.com/2009/09/25/payment-request-action-screen-wireframe/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>American Airlines (aa.com)</title>
		<link>http://metricology.com/2009/09/25/american-airlines-aa-com/</link>
		<comments>http://metricology.com/2009/09/25/american-airlines-aa-com/#comments</comments>
		<pubDate>Fri, 25 Sep 2009 18:01:40 +0000</pubDate>
		<dc:creator>Bryan J Busch</dc:creator>
				<category><![CDATA[Portfolio]]></category>

		<guid isPermaLink="false">http://metricology.com/?p=13</guid>
		<description><![CDATA[Situation
The home page of the American Airlines main customer-facing site was suffering from an overabundance of options, confusing displays and inaccessible flyout menus, not to mention numerous front-end coding issues, noted on the screenshot below (click for larger version):

Solutions
I combined options wherever possible, made judicious use of &#8220;more&#8221; links for options that were just as [...]]]></description>
			<content:encoded><![CDATA[<h3>Situation</h3>
<p>The home page of the American Airlines main customer-facing site was suffering from an overabundance of options, confusing displays and inaccessible flyout menus, not to mention numerous front-end coding issues, noted on the screenshot below (click for larger version):</p>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/aacom-01.png"><img src="http://metricology.com/wp-content/uploads/2009/09/aacom-011-532x335.png" alt="Before Analysis" title="aacom-01" width="532" height="335" class="size-large wp-image-16" /></a></p>
<h3>Solutions</h3>
<p>I combined options wherever possible, made judicious use of &#8220;more&#8221; links for options that were just as valid but not as popular, <span id="more-13"></span>used clear displays and labels for ancillary functions, and standardized form input types. The first screenshot below is of the final wire frame made for a new version of the home page, and the second is a designer&#8217;s interpretation of what the final result might look like:</p>
<h4>Finished IA</h4>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/aacom-02.png"><img src="http://metricology.com/wp-content/uploads/2009/09/aacom-02-532x447.png" alt="Finished Information Architecture" title="aacom-02" width="532" height="447" class="size-large wp-image-17" /></a></p>
<h4>Proposed Design</h4>
<p><a href="http://metricology.com/wp-content/uploads/2009/09/aacom-03.png"><img src="http://metricology.com/wp-content/uploads/2009/09/aacom-03-532x502.png" alt="Proposed Design" title="aacom-03" width="532" height="502" class="size-large wp-image-18" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://metricology.com/2009/09/25/american-airlines-aa-com/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
