<?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>These Things Matter &#187; work</title>
	<atom:link href="http://www.sgmitch.com/blog/category/work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sgmitch.com/blog</link>
	<description>Encounters with designed experiences</description>
	<lastBuildDate>Sat, 28 Aug 2010 17:04:27 +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>Case Study: Awards Shows</title>
		<link>http://www.sgmitch.com/blog/2010/01/case-study-awards-shows/</link>
		<comments>http://www.sgmitch.com/blog/2010/01/case-study-awards-shows/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 06:51:25 +0000</pubDate>
		<dc:creator>Sarah</dc:creator>
				<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.sgmitch.com/blog/?p=701</guid>
		<description><![CDATA[The 67th annual Golden Globe Awards were just a little over a week ago, and within two days (Sunday and Monday) the Yahoo Golden Globes site served over half a BILLION page views. On that Monday alone, which was Martin Luther King, Jr. Day and a work holiday for many, there were eleven million unique [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>The 67th annual Golden Globe Awards were just a little over a week ago, and within two days (Sunday and Monday) the <a href="http://awards.omg.yahoo.com/">Yahoo Golden Globes site</a> served over half a BILLION page views. On that Monday alone, which was Martin Luther King, Jr. Day and a work holiday for many, there were eleven million unique visitors, each viewing an average of 44 pages and spending almost 8 minutes on the site. I am so proud to have worked on the site that helped make those amazing numbers possible.</p>
<p><a href="http://www.flickr.com/photos/sgmitch/4302377733/"><img alt="Yahoo omg! Golden Globes 2010 site screenshot" src="http://farm5.static.flickr.com/4055/4302377733_230106586d.jpg" title="Yahoo omg! Golden Globes 2010 site screenshot" class="aligncenter frame" width="500" height="449" /></a></p>
<p><strong>Problem:</strong> Prior to this project, Yahoo had some awards show coverage, but the editorial and programming effort involved in each instance was so prohibitive that only the very largest shows were covered. In addition, all of the awards show sites used completely different designs, code, and even editorial tools, which ruled out any chance of efficiency from show to show.</p>
<p><strong>Project: </strong>Design a reusable site template flexible enough to be used for each of the major awards shows during the year—Oscars, Emmys, Grammys, Golden Globes—as well as a low-effort, feature-light version for any of the other smaller awards shows. The site template must also accommodate visual design flexibility, because the different awards shows need to live within different Yahoo sites: <a href="http://awards.tv.yahoo.com/">Emmys in Yahoo TV</a>, <a href="http://awards.omg.yahoo.com/">Globes in omg!</a>, and <a href="http://oscars.movies.yahoo.com/">Oscars in Yahoo Movies</a>.</p>
<p><strong>Research: </strong>We started by mining the traffic data for insight into audience behavior, and then we did a content audit across every awards show site we could find. But our richest sources of information were our in-house experts: the editors. We conducted extensive interviews with editors from all of the Yahoo entertainment sites, and they provided us with a clear understanding of their processes, pain-points, and the opportunities they saw for both themselves and the end-user. </p>
<p><strong>Process: </strong>We began sketching during the research phase, and as we worked we covered the walls and whiteboards in our war room with sketches. Visual design comps and wires were developed and refined in tandem, and the visual designer and I were in constant close communication. We had multiple reviews with the editors, both informal and formal. The most current comps were always taped to the walls.</p>
<p>We focused on a few key things. First, we wanted to make sure we put the <strong>content front and center.</strong> People are looking for the content—photos, nominee and winner info, opinion, and video—and not for site features. We made the photos and videos as large as possible, and tried to make the access to everything as simple as we could. Basically, we tried to keep the site <em>out of the way</em> of the content. </p>
<p>Second, we wanted to <strong>empower the editors</strong> to promote the very best content easily throughout the site. These sites are wholly powered by the editors. They know what is interesting now, and they work hard to elevate and commentate the very best from the photo and news feeds. To take advantage of this we created a highly modular home page and cross-linking right column for content pages. We decided that these promotional areas should not have fixed content placements, and that cross-linking should never be driven by what&#8217;s &#8220;related,&#8221; but rather by what&#8217;s hot right now (as determined by the editors). The editors would have the ability to create content modules of different varieties—photos, videos, blogs, news, and polls—and then place those modules however they liked on the homepage and that right column. This one &#8220;Best of&#8230;&#8221; column would appear on <em>every page</em> but the homepage, helping to simplify the site, keep the editorial workload down, and surface the most enticing content on every page. This modular, editorial-powered approach also meant that the awards show template could be easily modified for lower-profile awards shows. </p>
<p>And lastly, we wanted to <strong>enable user commentary and engagement</strong> wherever possible. We had a lot of scope-intensive ideas like bracket voting and user-created galleries, but at a basic level we wanted to allow people to express their opinions on any piece of content. People have strong opinions about almost everything related to an awards show—<a href="http://awards.omg.yahoo.com/nominees/370-avatar#comments">the nominees</a>, <a href="http://awards.omg.yahoo.com/photos/108-golden-globes-red-carpet-report-card#comments">the dresses</a>, <a href="http://awards.omg.yahoo.com/blog/28-downey-and-monique-surprise-at-golden-globes#comments">the winners</a>, and <a href="http://awards.omg.yahoo.com/blog/26-golden-globes-red-carpet-the-funniest-moments#comments">the show</a>—and we wanted to make sure the site included places to share those opinions. (Clearly, improving spam filtering should be a high priority in improving this experience.)</p>
<p>Of course, there&#8217;s usually a fair amount of hidden complexity in simple-seeming things, so we also spent time stress-testing and spec&#8217;ing the design to make sure it worked for all of the intended host sites and awards show types. </p>
<div class="wp-caption aligncenter" style="width: 500px;"><a href="http://www.flickr.com/photos/sgmitch/4302606551/in/photostream"><img class="frame" title="Yahoo Oscars site screenshot" src="http://farm5.static.flickr.com/4043/4302606551_1f88090852_m.jpg" alt="Yahoo Oscars site screenshot" width="214" height="240" /></a><span style="color:#FFF; ">&#8212;&#8211;</span><a href="http://www.flickr.com/photos/sgmitch/4303356228/in/photostream"><img class="frame" title="Yahoo Emmys site screenshot" src="http://farm5.static.flickr.com/4015/4303356228_4f633d625b_m.jpg" alt="Yahoo Emmys site screenshot" width="214" height="240" /></a></p>
<p class="wp-caption-text">Final <a href="http://oscars.movies.yahoo.com">Oscars</a> and <a href="http://awards.tv.yahoo.com">Emmys</a> site designs</p>
</div>
<div class="wp-caption aligncenter" style="width: 380px;"><a href="http://www.flickr.com/photos/sgmitch/4302559631/sizes/o/in/photostream/"><img class="frame" title="Awards show spec excerpt 1" src="http://farm3.static.flickr.com/2770/4302559631_0d1b6b31cf_m.jpg" alt="Awards show spec excerpt 1" width="155" height="240" /></a><span style="color:#FFF; ">&#8212;&#8211;</span><a href="http://www.flickr.com/photos/sgmitch/4303308922/sizes/o/in/photostream/"><img class="frame" title="Awards show spec excerpt 2" src="http://farm5.static.flickr.com/4029/4303308922_7bc7b45dfc_m.jpg" alt="Awards show spec excerpt 3" width="155" height="240" /></a></p>
<p class="wp-caption-text">2 pages of my functional spec doc</p>
</div>
<p><strong>Successes: </strong> Our efforts to showcase the content and offer enticing cross-links paid off. We saw a 215% jump in page views per unique user over the previous year (from 20 to 45) when we rolled out this design for Oscars. Additionally, the common code, layout, and editorial tools drastically decreased the effort and time involved in building, populating, and releasing sites for new awards shows. </p>
<p><strong>Areas for Improvement: </strong> There are a few pieces of the site I would love to get a chance to revise, like the <a href="http://awards.omg.yahoo.com/nominees/469-sandra-bullock">person/movie/show page</a>, and there were many great features that hit the cutting room floor. But I would say my biggest wish is that I had had more time to work on the design of the editorial tool itself. The engineer who built the tool all by himself in record time did an amazing job, but there are definitely some processes that could have been made easier for the editors.</p>
<p><strong>Final Takeaways</strong> Many factors besides the design of the site contributed to this year&#8217;s fantastic Globes success, Avatar&#8217;s Best Picture win among them. The bulk of the credit goes, without a doubt, to our talented and hardworking staff of editors. Like I said, people want content—photos, opinions, news, and more photos—and our editors crafted an extraordinary set of content that kept the audience engaged and looking for more. After a year of using the new awards show tools, editors from all of Yahoo&#8217;s entertainment sites were able to work together as one large team to support the Globes, which was a huge win for both Yahoo and our audience. I&#8217;d like to salute them for their skill and effort, and I&#8217;m already looking forward to the Oscars!</p>
<p><em>Credits: Interaction Design: Sarah Mitchell (me), Jens Jonason. Visual Design: Megan O&#8217;Toole. Design Manager: Nina Ristani. Engineering: Steve Krutzler, Travis Kuhl, Eric Melkerson. Product Management: Adam Zarlengo. Project Management: Noah Kanter. 2010 Emmys Visual design by Seva Dyakov.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.sgmitch.com/blog/2010/01/case-study-awards-shows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Case Study: Yahoo Entertainment</title>
		<link>http://www.sgmitch.com/blog/2009/12/case-study-yahoo-entertainment/</link>
		<comments>http://www.sgmitch.com/blog/2009/12/case-study-yahoo-entertainment/#comments</comments>
		<pubDate>Mon, 07 Dec 2009 20:06:31 +0000</pubDate>
		<dc:creator>Sarah</dc:creator>
				<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.sgmitch.com/blog/?p=455</guid>
		<description><![CDATA[Project: Redesign this very old page: Background: This project was defined by its constraints. The biggest constraint was that the page, once launched, could not require ANY human effort to update it daily, meaning it could use only pre-existing content feeds and formats. Additionally, we could not build any new feeds or modify the existing [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><strong>Project: </strong>Redesign this <em>very</em> old page:</p>
<p><a href="http://www.flickr.com/photos/sgmitch/4167082431/"><img alt="" src="http://farm3.static.flickr.com/2793/4167082431_0c95a48c38.jpg" title="Yahoo! Entertainment before the redesign" class="frame aligncenter" width="318" height="500" /></a> </p>
<p><strong>Background:</strong> This project was defined by its constraints. The biggest constraint was that the page, once launched, could not require ANY human effort to update it daily, meaning it could use only pre-existing content feeds and formats. Additionally, we could not build any new feeds or modify the existing feeds at all. We had to design, build, and launch the page in 5 weeks. The page had to showcase content from Yahoo&#8217;s five entertainment sites: <a href="http://music.yahoo.com">Music</a>, <a href="http://movies.yahoo.com">Movies</a>, <a href="http://tv.yahoo.com">TV</a>, <a href="http://omg.yahoo.com">omg!</a> (celebrity), and <a href="http://games.yahoo.com">Games</a>.  Our executive client also gave us the directive to make the page customizable and something people would bookmark and come back to daily. </p>
<p><strong>Research:</strong> Prior to the project kickoff, Yahoo had conducted focus groups and participatory design sessions in multiple cities to gather people&#8217;s perceptions and expectations around consuming entertainment content. I was present for all of the sessions in L.A. The findings indicated that people have varied personal definitions of &#8220;entertainment&#8221;—for some it includes things like movie trailers, horoscope, or even sports, while others only care about celebrity gossip and photos. Most people also already have a daily routine of sites they visit to get the kinds of content and information they prefer. The motivations for frequent repeat visits fell into two groups: the desire to find out the very latest noteworthy information (often socially motivated), and the need for practical utilities like the TV listings grid and the movie showtimes finder. </p>
<p><strong>Process:</strong> For the duration of this project the core team (3 designers and 3 engineers) left our cubes and camped out together in a war room. To begin the project we worked together at the whiteboard, analyzing the research and discussing the user and project goals. Then we split up, and the visual designers crafted a creative brief while I worked closely with engineers to determine what content was available. I sketched page after page as we mined the source sites for feeds, teased out the specific content available in each feed, and brainstormed possibilities for the content we couldn&#8217;t access easily. Then the entire team came back together and agreed upon an overall content strategy and creative direction. </p>
<p>We decided that our best bet for encouraging return visits was to focus on the utilities such as the TV listings grid and the movie showtimes and tickets search. Without any additional editorial support, our content feeds simply couldn&#8217;t compete with other sites in terms of surfacing the most important and timely content. Armed with our strategy we reviewed and refined the sketches and began wireframing towards the final solution.</p>
<p><span id="more-455"></span>I presented the strategy and the in-progress wireframe to our executive client, and with his approval the visual designers began working on the final page designs. During this phase we explored options for the detailed in-page interactions, including the video playback and the page customization functionality. Below you can see an exploration of options for drag and drop, which we ultimately decided against, in favor of simpler module up/down controls.</p>
<p><a href="http://www.flickr.com/photos/sgmitch/4179799904/"><img alt="" src="http://farm3.static.flickr.com/2646/4179799904_a5967249aa.jpg" title="Drag and Drop options" class="aligncenter frame" width="500" height="324" /></a></p>
<p>The other interaction designer and I then divided up the modules for functional documentation. (View <a href="http://www.flickr.com/photos/sgmitch/4179058423/">my spec for the TV listings module</a> for an example.) We reviewed and iterated all of the specs with the engineers, and then sat with them as they coded, addressing challenges and opportunities as they came up. Together we fine-tuned the interactions as they came to life. All of the designers contributed to the QA effort, and we launched on schedule. You can view the live site at <a href="http://entertainment.yahoo.com">entertainment.yahoo.com</a>, and below is a video tour of the page highlighting some of the interactive functionality.</p>
<p style="text-align:center"><object width="400" height="300"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=8201063&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=8201063&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=0&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="300"></embed></object></p>
<p>After the launch we conducted a round of usability testing, which was intended to inform changes for the next release version. Unfortunately, shortly after the usability testing was completed, executive priorities shifted, and any future releases were canceled.</p>
<p><strong>Successes:</strong><br />
There are a number of things that I consider successes in the outcome of this project. First of all, it launched on time, exceeded the expectations of our executive client, and has been a clear financial success. The page was also one of the first to embrace Yahoo&#8217;s larger strategy of openness by incorporating external blog and top 10 feeds, iTunes data, and iTunes and Netflix functionality.</p>
<p>Page views went up after launch from an average of 5.5M per month to 10.5+M per month with no additional promotion. (The page views in the first month post-launch jumped to 16M, but I believe it did get some promotion in that month.) Page views held steady at 10-11M per month until July of this year when the redesign of Yahoo.com—which removed the most prominent link to this page—began to roll out. </p>
<p>Aside from those achievements, I am proud of the hard-working and creative team effort that allowed us enhance this fairly basic page with quite a few delightful and refined interactions. I believe we really made the most of every opportunity we had.</p>
<p><strong>Areas for Improvement:</strong><br />
Of course, the page is not perfect. The usability testing uncovered some issues with the module up/down interaction, expectations of content and interaction in the celebrity photos module, and the usability of the top ten drop-down control. Some of the findings were not all that surprising and were related to things we intended to tweak in the next release. However, I think the biggest failing of the page actually was in its overall concept rather than in any individual feature. The research strongly indicated that people are most interested in fresh, engaging, and <em>entertaining</em> content, which generally relies heavily on editorial curation and community engagement. So in the end I think we built a very nice page that misses out on serving the biggest user need.</p>
<p><strong>Final Takeaways:</strong> I am still proud of the work we did on this page. I really enjoy this kind of quick, highly collaborative work, and cherish the respect and affection this project fostered among my team members. The page is visually appealing, contains refined interactivity, is technically solid and responsive, makes easy money for the company, and for two years has been serving (and hopefully delighting) millions of people every month. </p>
<p><a href="http://www.flickr.com/photos/sgmitch/4186052998/"><img alt="" src="http://farm5.static.flickr.com/4048/4186052998_7e9fa30020_b.jpg" title="Screenshot of redesigned Yahoo Entertainment" class="aligncenter frame" width="410" height="1024" /></a></p>
<p><em>Credits: Visual design: Genvieve Garand, Jeff Hurlow. Interaction Design: [me], Ruth Kaufmann. Design Management: Nina Ristani. Engineering: Scott Rocher, William Wetter, Christopher Shattuck. Project Management: Brett Hellman. Product Management: Michael Speigelmann.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.sgmitch.com/blog/2009/12/case-study-yahoo-entertainment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Design Exercise: The New Yahoo.com</title>
		<link>http://www.sgmitch.com/blog/2009/11/design-exercise-yahoo-com/</link>
		<comments>http://www.sgmitch.com/blog/2009/11/design-exercise-yahoo-com/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 06:32:25 +0000</pubDate>
		<dc:creator>Sarah</dc:creator>
				<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://www.sgmitch.com/blog/?p=460</guid>
		<description><![CDATA[Microsoft launched a preview of the new MSN homepage redesign last week. This redesign reminds me in some ways of the recent Yahoo.com redesign. Both homepages are cleaner, with fewer links on the page. Both offer a way to configure the page to view personal content like email and Facebook. I did not have the [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Microsoft launched a preview of the new <a href="http://www.msn.com/preview.aspx">MSN homepage redesign</a> last week. This redesign reminds me in some ways of the recent <a href="http://m.www.yahoo.com/">Yahoo.com</a> redesign. Both homepages are cleaner, with fewer links on the page. Both offer a way to configure the page to view personal content like email and Facebook. </p>
<p>I did not have the privilege of working on the new Yahoo homepage. However, the redesign team did invite my group to contribute some final design thoughts after a fairly long run of <a href="http://en.wikipedia.org/wiki/A/B_testing">A/B testing</a> and iterations. We were given about a day to come back with suggestions for visual design polish. Visual design polish is not my job, but I couldn&#8217;t resist the opportunity to take part in a design exercise on one of the most viewed pages on the entire internet.</p>
<p>I drew up some simple wireframes proposing minor changes to the current design. I didn&#8217;t re-imagine the page from scratch—it was clear that the design was basically final and I didn&#8217;t want to go <em>too</em> far outside of the scope of the exercise. Instead I used the current design as a starting place and made incrementally larger changes. I&#8217;m not sure if the homepage team ever even saw my work, but I thought it would be fun to share a few of them now.</p>
<p><em>(Views expressed below are mine, not Yahoo&#8217;s. All documents are the property of Yahoo.)</em></p>
<div id="attachment_479" class="wp-caption aligncenter" style="width: 540px">
	<a href="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-22.jpg"><img src="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-22-sm.jpg" alt="click to view larger"  class="frame" title="New Yahoo.com 1" width="500" height="561" class="size-full wp-image-479" /></a>
	<p class="wp-caption-text">Version 1 - click to view larger</p>
</div>
<p>I knew that the left column was completely off limits, so for most of my sketches I just used a screenshot of the (then) current version. I also wanted to be sensitive to the editorial input into the current design, so I copied the headlines and text content and used them verbatim. (For comparisons and posterity, <a href="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/yahoo.png">here is a screenshot</a> of the currently live redesign I am referencing.)</p>
<p>This is what I started with, which you can see in the wireframe above: </p>
<ul>
<li>I added more visual hierarchy. I varied size and placement to call out top links and to give the eye a path of focus points. </li>
<li>I increased the number of editorial images. My experience working on entertainment sites has taught me that people love to click on images.</li>
<li>I decreased the amount of hidden content. I chose not to put as much importance in keeping the page very short, and instead tried to reduce the number of carousels and tabs hiding editorial content. </li>
<li>I switched to a serif font. I wanted to embrace the editorial content of the page and give it a more newspaper feel.</li>
<li>I substantially changed the top main feature area. I moved the Popular Searches to elsewhere in the page and stretched the feature area all the way to the right edge. I moved the secondary features to the right of the main feature (instead of below) and simplified the interaction by removing the current rollover behavior. I also<br />
highlighted the feature topic options in prominent tabs instead of the small arrows currently at the bottom of the feature module.</li>
</ul>
<p>I did some more versions like the one below in which I varied the content and feature layout.<br />
<span id="more-460"></span><div id="attachment_487" class="wp-caption aligncenter" style="width: 540px">
	<a href="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-214.jpg"><img class="frame" src="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-214-sm.jpg" alt="click to view larger" title="New Yahoo.com 2" width="500" height="561" class="size-full wp-image-487" /></a>
	<p class="wp-caption-text">Version 2 - click to view larger</p>
</div></p>
<p>In this next version below I did take a little crack at the left app bar after all, despite it being off-limits. Similarly to my earlier efforts, I wanted to add hierarchy and reduce the amount of hidden information. I tried to show some of the information belonging to the top item (email) without requiring a click or rollover, and then I reduced the prominence of the items at the bottom of the list. In order to not break too many rules at once with this design, I also consolidated the page content to create a shorter scroll.</p>
<div id="attachment_481" class="wp-caption aligncenter" style="width: 540px">
	<a href="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-25.jpg"><img class="frame" src="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-25-sm.jpg" alt="click to view larger" title="New Yahoo.com 3" width="500" height="440" class="size-full wp-image-481" /></a>
	<p class="wp-caption-text">Version 3 - click to view larger</p>
</div>
<p>In this last version, I tried moving the app bar to the right. I found it interesting to explore a fairly unconventional page layout, especially with the ad placement in the center of the page. I also thought the username could persist in this upper-right placement through all of Yahoo&#8217;s sites, and rolling over it could trigger the app bar to appear, bringing the utility of its shortcuts and quick-views to the entire Yahoo network.</p>
<div id="attachment_483" class="wp-caption aligncenter" style="width: 540px">
	<a href="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-29.jpg"><img class="frame" src="http://www.sgmitch.com/blog/wp-content/uploads/2009/11/metra-29-sm.jpg" alt="click to view larger" title="New Yahoo.com 4" width="500" height="561" class="size-full wp-image-483" /></a>
	<p class="wp-caption-text">Version 4 - click to view larger</p>
</div>
<p>I&#8217;d like to be clear that these wires do not represent a criticism of the current Yahoo homepage design. The homepage team went through a robust design process that included many rounds of testing and feedback that I was not privy to. Not to mention the fact that the redesign that they launched has been a <a href="http://www.techcrunch.com/2009/10/28/time-spent-on-yahoo-homepage-up-20-percent-since-redesign/">great success</a>. I just really enjoyed getting the chance to lay my hands on the design of this page, and I hope you enjoyed looking at what I came up with.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sgmitch.com/blog/2009/11/design-exercise-yahoo-com/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
