<?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>erikgibb.com Blog</title>
	<atom:link href="http://erikgibb.com/blog/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://erikgibb.com/blog</link>
	<description>A clean, well-lighted place for me to blather</description>
	<lastBuildDate>Sat, 08 Jan 2011 00:42:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Kink.com: Fapatars</title>
		<link>http://erikgibb.com/blog/2011/01/01/kink-com-fapatars/</link>
		<comments>http://erikgibb.com/blog/2011/01/01/kink-com-fapatars/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 08:00:41 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[Kink.com (2008-Present)]]></category>
		<category><![CDATA[NSFW]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/?p=152</guid>
		<description><![CDATA[view larger You gotta have a sense of humor when you&#8217;re looking at flesh 9 hours a day, right? User experience means focusing on the user. In a non-adult company, you would think about where the user has been and where they want to go, like &#8220;The user just read some e-mail, and is now [...]]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2011/01/fapatars2.png" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/fap-thumb1.jpg" width="250" height="250" alt="fap-thumb.jpg" name="fap-thumb1.jpg" /><br />view larger</a></div>
<p>You gotta have a sense of humor when you&#8217;re looking at flesh 9 hours a day, right?</p>
<p>User experience means focusing on the user. In a non-adult company, you would think about where the user has been and where they want to go, like &#8220;The user just read some e-mail, and is now checking his stock portfolio.&#8221; In the adult world, you have to think about the user&#8217;s state too &#8211; Is he aroused? Is he naked? Does he have his credit card out? Can he get to his credit with only one hand?</p>
<p>To help everyone remember who we were building the product for, and the state of mind he might be in, I created a series of humorous avatars which I occasionally used in documentation.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2011/01/01/kink-com-fapatars/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kink.com: Mobile</title>
		<link>http://erikgibb.com/blog/2011/01/01/kink-com-mobile/</link>
		<comments>http://erikgibb.com/blog/2011/01/01/kink-com-mobile/#comments</comments>
		<pubDate>Sat, 01 Jan 2011 08:00:40 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[Kink.com (2008-Present)]]></category>
		<category><![CDATA[NSFW]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2011/01/05/kink-com-mobile/</guid>
		<description><![CDATA[view pdf I created a set of extremely simple yet high fidelity wireframes to use in discussion with the front end engineering team who were tasked with making our sites mobile friendly. Rather than convert the entire site, and armed with member survey data, we chose to focus on an extremely easy login/registration process and [...]]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2011/01/kmobile1.pdf" title="kmobile.pdf" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/kmobile-thumb.jpg" width="250" height="250" alt="kmobile-thumb.jpg" /><br />view pdf</a></div>
<p>I created a set of extremely simple yet high fidelity wireframes to use in discussion with the front end engineering team who were tasked with making our sites mobile friendly. Rather than convert the entire site, and armed with member survey data, we chose to focus on an extremely easy login/registration process and making the smallest possible video files available.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2011/01/01/kink-com-mobile/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo: Selling the work to a busy executive</title>
		<link>http://erikgibb.com/blog/2008/01/01/yahoo-selling-the-work-to-a-busy-executive/</link>
		<comments>http://erikgibb.com/blog/2008/01/01/yahoo-selling-the-work-to-a-busy-executive/#comments</comments>
		<pubDate>Tue, 01 Jan 2008 08:00:56 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[Yahoo (2005-2008)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/?p=146</guid>
		<description><![CDATA[view pdf Attached is a deck I created to help the busy VP of our group quickly grasp the work. The simple line art helped draw attention to all the right areas of the proposed experience. An interface spec, which would normally take 60 minutes to describe in detail, was condensed to a 7 minute [...]]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2011/01/Clickthrough_v1.1.pdf" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/Clickthrough_v1.1.graffle_-OCP_SDS-Feed-Recommendations....-300x215.jpg" alt="preso" width="250" height="200" /><br />view pdf</a></div>
<p>Attached is a deck I created to help the busy VP of our group quickly grasp the work. The simple line art helped draw attention to all the right areas of the proposed experience. An interface spec, which would normally take 60 minutes to describe in detail, was condensed to a 7 minute presentation which helped highlight the areas which she could provide guidance on.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2008/01/01/yahoo-selling-the-work-to-a-busy-executive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo: RSS Feed Discovery Interface</title>
		<link>http://erikgibb.com/blog/2008/01/01/yahoo-rss-feed-discovery-interface/</link>
		<comments>http://erikgibb.com/blog/2008/01/01/yahoo-rss-feed-discovery-interface/#comments</comments>
		<pubDate>Tue, 01 Jan 2008 08:00:32 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[Yahoo (2005-2008)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/?p=118</guid>
		<description><![CDATA[view pdf The Yahoo Mail interface allowed users to subscribe to RSS feeds, but the legacy interface was an after thought: It allowed users to subscribe to known feeds, but provided no discovery experience. I worked with the RSS team to understand how feeds were discovered, consumed, cached, and updated by the network then created [...]]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2011/01/RSSDiscovery_WF_v1.4.pdf" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/0.-Primary-Interface-Conventions-300x190.png" alt="0. Primary Interface Conventions" title="0. Primary Interface Conventions" width="250" height="170" /><br />view pdf</a></div>
<p>The Yahoo Mail interface allowed users to subscribe to RSS feeds, but the legacy interface was an after thought: It allowed users to subscribe to known feeds, but provided no discovery experience.</p>
<p>I worked with the RSS team to understand how feeds were discovered, consumed, cached, and updated by the network then created an interface which would work not only with Mail. but any Yahoo property which wanted users to add RSS feeds.</p>
<p>Finished product</p>
<p><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/YHOO09_072.jpg" width="437" height="331" alt="YHOO09_07.jpg" /></p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2008/01/01/yahoo-rss-feed-discovery-interface/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo: Yahoo Application Platform</title>
		<link>http://erikgibb.com/blog/2008/01/01/yahoo-application-platform-2/</link>
		<comments>http://erikgibb.com/blog/2008/01/01/yahoo-application-platform-2/#comments</comments>
		<pubDate>Tue, 01 Jan 2008 08:00:30 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[Yahoo (2005-2008)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2011/01/05/yahoo-application-platform-2/</guid>
		<description><![CDATA[view larger The Yahoo Application Platform was a framework we piloted enabling Yahoo properties to open their pages to 3rd party developer applications. Example use case: Users can add an OpenID permissioned Mint.com personal finance module to Yahoo Finance, or any other enabled property. My team provided experience and visual design options for the consumer [...]]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2011/01/yap_map.portfolio.png" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2011/01/yap-thumb2.jpg" width="250" height="94" alt="yap-thumb2.jpg" /><br />view larger</a></div>
<p>The Yahoo Application Platform was a framework we piloted enabling Yahoo properties to open their pages to 3rd party developer applications. Example use case: <i>Users can add an OpenID permissioned Mint.com personal finance module to Yahoo Finance, or any other enabled property</i>.</p>
<p>My team provided experience and visual design options for the consumer experience: primarily the application gallery that allowed used to discover interesting apps on any page, and the &#8220;chrome&#8221; around each app which included a menu of standard options and settings.</p>
<p>test.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2008/01/01/yahoo-application-platform-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlanetOut: Example flow</title>
		<link>http://erikgibb.com/blog/2004/01/01/planetout-example-flow/</link>
		<comments>http://erikgibb.com/blog/2004/01/01/planetout-example-flow/#comments</comments>
		<pubDate>Thu, 01 Jan 2004 20:00:54 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[PlanetOut (2003-2004)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2007/05/19/planetout-example-flow/</guid>
		<description><![CDATA[view larger This flow diagram incorporated interface detail hints which allowed people outside the development group to follow the process.]]></description>
			<content:encoded><![CDATA[<div class="item"><a href="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191652.jpg" target="_blank"><img width="198" height="109" border="1" alt="200705191652" src="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191652-tm.jpg" name="200705191652-tm.jpg" /><br />view larger</a>
</div>
<p>This flow diagram incorporated interface detail hints which allowed people outside the development group to follow the process.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2004/01/01/planetout-example-flow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlanetOut: Member Browser Widget</title>
		<link>http://erikgibb.com/blog/2004/01/01/planetout-member-browser-widget/</link>
		<comments>http://erikgibb.com/blog/2004/01/01/planetout-member-browser-widget/#comments</comments>
		<pubDate>Thu, 01 Jan 2004 20:00:44 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[PlanetOut (2003-2004)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2007/05/19/planetout-member-browser-widget/</guid>
		<description><![CDATA[view larger As part of a major redesign I created a compact, AJAX member browser widget, enabling the user to quickly browse through a list of &#8220;featured members&#8221; without having to reload the page.]]></description>
			<content:encoded><![CDATA[<div class="item">
  <a href="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191640.jpg" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191640-tm.jpg" alt="200705191640" width="178" height="86" /><br />
  view larger</a>
</div>
<p>As part of a major redesign I created a compact, AJAX member browser widget, enabling the user to quickly browse through a list of &#8220;featured members&#8221; without having to reload the page.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2004/01/01/planetout-member-browser-widget/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlanetOut: Buddy List Window</title>
		<link>http://erikgibb.com/blog/2004/01/01/planetout-buddy-list-window/</link>
		<comments>http://erikgibb.com/blog/2004/01/01/planetout-buddy-list-window/#comments</comments>
		<pubDate>Thu, 01 Jan 2004 20:00:37 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[PlanetOut (2003-2004)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2007/05/19/planetout-buddy-list-window/</guid>
		<description><![CDATA[view larger A system architecture quirk at PlanetOut/Gay.com required a small persistent floating window to fully utilize the site—If the user closed this nearly pointless window, instant messaging and chat would be disabled. I added the user&#8217;s buddy list and a mini-profile browser, turning this annoying window (and perennial customer service complaint) into a useful [...]]]></description>
			<content:encoded><![CDATA[<div class="item">
  <a href="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191634.jpg" target="_blank"><img width="71" height="188" alt="200705191634" src="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191634-tm.jpg" /><br />
  view larger</a>
</div>
<p>A system architecture quirk at PlanetOut/Gay.com required a small persistent floating window to fully utilize the site—If the user closed this nearly pointless window, instant messaging and chat would be disabled. I added the user&#8217;s buddy list and a mini-profile browser, turning this annoying window (and perennial customer service complaint) into a useful asset for the user.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2004/01/01/planetout-buddy-list-window/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlanetOut: Search and Refine</title>
		<link>http://erikgibb.com/blog/2004/01/01/planetout-search-and-refine/</link>
		<comments>http://erikgibb.com/blog/2004/01/01/planetout-search-and-refine/#comments</comments>
		<pubDate>Thu, 01 Jan 2004 20:00:22 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[PlanetOut (2003-2004)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2007/05/19/planetout-search-and-refine/</guid>
		<description><![CDATA[view larger During the PlanetOut/Gay.com redesign I proposed adding different layout options to search results pages, in addition to surfacing the refine function in a handy minimizable tray.]]></description>
			<content:encoded><![CDATA[<div class="item">
  <a href="http://erikgibb.com/blog/wp-content/uploads/2007/06/search.png" target="_blank"><img src="http://erikgibb.com/blog/wp-content/uploads/2007/06/search-tm.jpg" height="152" width="163" alt="Search" /><br />
  view larger</a>
</div>
<p>During the PlanetOut/Gay.com redesign I proposed adding different layout options to search results pages, in addition to surfacing the refine function in a handy minimizable tray.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2004/01/01/planetout-search-and-refine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PlanetOut: Example Wireframe and UI Spec</title>
		<link>http://erikgibb.com/blog/2004/01/01/planetout-example-wireframe-and-ui-spec/</link>
		<comments>http://erikgibb.com/blog/2004/01/01/planetout-example-wireframe-and-ui-spec/#comments</comments>
		<pubDate>Thu, 01 Jan 2004 20:00:18 +0000</pubDate>
		<dc:creator>erik</dc:creator>
				<category><![CDATA[PlanetOut (2003-2004)]]></category>

		<guid isPermaLink="false">http://erikgibb.com/blog/2007/05/19/planetout-example-wireframe-and-ui-spec/</guid>
		<description><![CDATA[view larger My Planetout specs vary between high and low fidelity. In this hifi wireframe, I numbered every element with attention to system generated text and localized strings. The behaviors of each numbered element is described in the UI Spec.]]></description>
			<content:encoded><![CDATA[<div class="item">
  <a href="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191649.jpg" target="_blank"><img width="163" height="123" alt="200705191650" src="http://erikgibb.com/blog/wp-content/uploads/2007/05/200705191650-tm.jpg" /><br />
  view larger</a>
</div>
<p>My Planetout specs vary between high and low fidelity. In this hifi wireframe, I numbered every element with attention to system generated text and localized strings. The behaviors of each numbered element is described in the UI Spec.</p>
]]></content:encoded>
			<wfw:commentRss>http://erikgibb.com/blog/2004/01/01/planetout-example-wireframe-and-ui-spec/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

