<?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>Chapter 42 &#187; inspiration</title>
	<atom:link href="http://chapter42.whitewhale.net/tag/inspiration/feed/" rel="self" type="application/rss+xml" />
	<link>http://chapter42.whitewhale.net</link>
	<description></description>
	<lastBuildDate>Thu, 30 Sep 2010 17:20:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>A great Web site</title>
		<link>http://chapter42.whitewhale.net/2008/08/22/a-great-web-site/</link>
		<comments>http://chapter42.whitewhale.net/2008/08/22/a-great-web-site/#comments</comments>
		<pubDate>Fri, 22 Aug 2008 21:10:14 +0000</pubDate>
		<dc:creator>Tonya</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[IA]]></category>
		<category><![CDATA[inspiration]]></category>
		<category><![CDATA[state fairs]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://chapter42.whaleblogs.net/?p=95</guid>
		<description><![CDATA[Even though I assess, evaluate, critique, and praise Web sites for our clients every day, I don&#8217;t really use that lens in my normal, everyday browsing of the Web.  I mean, don&#8217;t get me wrong, badly designed, poorly organized sites annoy me.  I might even yell to no one (I work at home [...]]]></description>
			<content:encoded><![CDATA[<p>Even though I assess, evaluate, critique, and praise Web sites for our clients every day, I don&#8217;t really use that lens in my normal, everyday browsing of the Web.  I mean, don&#8217;t get me wrong, badly designed, poorly organized sites annoy me.  I might even yell to no one (I work at home most of the time) when I&#8217;m frustrated with a site or see something that&#8217;s particularly garish.  I also note good ideas and generally keep up with best practices. But I don&#8217;t waste my time overthinking or reacting to random sites I like or don&#8217;t like.</p>
<p>So I surprised myself this morning when I came across the <a href="http://www.oregonstatefair.org/">Oregon State Fair</a>&#8217;s Web site and was so impressed with its design, functionality, IA, and writing that I actually wrote a glowing, completely unsolicited email to their marketing director.  (By the way, I found her email quite easily.)</p>
<p>I know the team that developed this site left no rock unturned.  I can tell immediately.  There are no weak links: They spent just as much time making sure the writing was spot-on as they did refining the design.</p>
<p>It’s a complete package:</p>
<ul>
<li>The design &#8211; great, catchy, beautiful, perfect for a state fair</li>
<li>The IA &#8211; clear, easy to navigate, with a touch of unique flair (Big Tomato) that does the double duty of reinforcing brand</li>
<li>The writing &#8211; smart, clever, knowing, funny, succinct</li>
<li>The functionality &#8211; I love My Can&#8217;t-Miss List (such a great use of shopping cart technology) and that the big Purchase Tickets graphic on the top of every page</li>
</ul>
<p>Even when our involvement on a client project is limited to design or strategy, we always emphasize the equal importance of these four elements.  But of the four, writing is often overlooked until well into the project.  As a result energy and resources are in short supply when the time comes to focus on content.  I look forward to the day when all the RFPs we receive include a section on writing; when Web committees allocate a line item in the budget to content development before the project even starts.</p>
<p>I don’t mean to overemphasize writing, but as the lead IA strategist and content developer at White Whale, it’s something I fret about all the time.  I let the other guys worry about <a href="http://chapter42.whaleblogs.net/?p=88">functionality</a> and <a href="http://chapter42.whaleblogs.net/?tag=design">design</a>.  In the end, sites succeed when it all comes together.</p>
<p>I haven&#8217;t been to a state fair since I was in high school but I&#8217;m going to this one.  Amazing what a great Web site can do.</p>
]]></content:encoded>
			<wfw:commentRss>http://chapter42.whitewhale.net/2008/08/22/a-great-web-site/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Make my logo BIGGER</title>
		<link>http://chapter42.whitewhale.net/2008/06/02/make-my-logo-bigger/</link>
		<comments>http://chapter42.whitewhale.net/2008/06/02/make-my-logo-bigger/#comments</comments>
		<pubDate>Mon, 02 Jun 2008 18:41:20 +0000</pubDate>
		<dc:creator>Douglas</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[inspiration]]></category>
		<category><![CDATA[logo]]></category>
		<category><![CDATA[satire]]></category>

		<guid isPermaLink="false">http://chapter42.whaleblogs.net/?p=27</guid>
		<description><![CDATA[During my times as a freelance designer—prior to being captured by White Whale—a majority of my clients were small businesses and entrepreneurial one-(wo)man-shows.  These clients, and thus the functional beauty that I created for them, differed vastly in a myriad of ways and yet they all had nearly the same exact critiques of the [...]]]></description>
			<content:encoded><![CDATA[<p>During my times as a freelance designer—prior to being captured by White Whale—a majority of my clients were small businesses and entrepreneurial one-(wo)man-shows.  These clients, and thus the functional beauty that I created for them, differed vastly in a myriad of ways and yet they all had nearly the same exact critiques of the comps that I would deliver to them.  Those of you who have worked as designers are likely intimately familiar with these exact requests for revision:</p>
<ul>
<li>Even when it is a perfectly acceptable size and is not screaming &#8220;THIS IS THE NAME OF MY COMPANY!!!&#8221;, they ask <strong>&#8220;Can you make my logo BIGGER?&#8221;</strong></li>
<li>After painstakingly designing the whitespace of their design in the interest of facilitating a bit of visual respiration, the client notes that there <strong>&#8220;should be more content because the page feels empty in spots&#8221;</strong>.</li>
<li>And then we have the infamous <strong>&#8220;The headlines need to be brighter and much larger&#8221;</strong></li>
</ul>
<p>In my Saturday morning internet perusing (it is at times sadly amusing that this is what has taken the place of cartoons in my adult life), I stumbled upon <a title="Who Needs Designers?" href="http://www.whoneedsdesigners.com" target="_blank">this</a>; apparently our brethren have taken to satire as a vehicle for alleviating their work-related frustrations.  While its easy to laugh about now, I am truly thankful that White Whale has largely pulled me from disputes over these issues; out of the several WW clients that I&#8217;ve been involved with, I don&#8217;t remember any of these issues being major points of dissent; here&#8217;s to having higher ed. clients!</p>
<p><em>Editor&#8217;s note: Yes, Douglas, but that&#8217;s because we <a title="Duke Law" href="http://law.duke.edu" target="_blank">usually</a> </em><em><a title="Duke.edu" href="http://www.duke.edu" target="_blank">make</a></em><em> <a title="Tulane Admission" href="http://admissiontest.tulane.edu" target="_blank">the logo</a> <a title="Southwestern" href="http://southwestern.babywhale.net/april30/family/homepage.html" target="_blank">really big</a> <a title="White Whale" href="http://www.whitewhale.net" target="_blank">anyway</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://chapter42.whitewhale.net/2008/06/02/make-my-logo-bigger/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

