<?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>eri on the interweb &#187; process</title>
	<atom:link href="http://www.eriontheinterweb.com/tag/process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eriontheinterweb.com</link>
	<description>Thoughts on the internet, design and user experience.</description>
	<lastBuildDate>Thu, 02 Feb 2012 01:54:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Presenting Design</title>
		<link>http://www.eriontheinterweb.com/2009/05/presenting-design/</link>
		<comments>http://www.eriontheinterweb.com/2009/05/presenting-design/#comments</comments>
		<pubDate>Sun, 10 May 2009 10:31:29 +0000</pubDate>
		<dc:creator>Erietta Sapounakis</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://www.eriontheinterweb.com/?p=55</guid>
		<description><![CDATA[The design process can be gruelling and clients, particularly internal clients rarely take responsibility for mistakes. Colour, pretty pictures, fancy fonts, all get in the way of proofing the actual content. Test the content, verify the feedback and hopefully reduce the risk and angst of the design process. Here are my six steps to the design process.]]></description>
			<content:encoded><![CDATA[<p>I was chatting to a friend recently. She works in house as a marketer and is also responsible for the production of graphic materials — ads, posters, business cards, brochures and the like. What has happened, rarely, but disastrously, is incorrect phone numbers appearing on print material that was proofed and approved by the internal client.</p>
<p>I don’t know about you but I know the client rarely takes responsibility for their part, and I think this is much worse when you are an internal supplier. So what to do?</p>
<p><strong>Step 1. Don’t start with the design<br />
</strong>Take a leaf out of the web development process and instead present a &#8220;wireframe&#8221;, a black and white blue print of the information only. The client, in this step need only focus on proofing the copy.</p>
<p><strong>Step 2. Prepare a design presentation<br />
</strong>Show and explain your creative process. This is something I learned from <a href="http://www.webdu.com.au/go/speaker-profile/pete-ottery-sydney-australia">Pete Ottery</a> (of News Digital) who gave a presentation called &#8220;<a href="http://www.webdu.com.au/go/session/so-you-think-you-can-design"><em>So You Think You Can Design</em></a>&#8221; at <a href="http://www.webdu.com.au">webDU</a> 2008. Pete&#8217;s talk was on the principles of good web design, but he also made the point of how important the presentation of a design is. Pete’s design presentations include the process by which he comes to the final design. In the margin of each page important aspects of the design are explained in friendly, plain language. He shows the rejects from the design process; and how he justifies and changes creative decisions based on the success or failure of designs in user testing.</p>
<p>Showing how you arrived at your final design will help justify your design decisions, and in my experience can shorten the iteration process. It wil lessen the internal client micro-managing the design — <em>make the logo bigger, move that over to the  left</em> sorta thing. Importantly, it will also show the effort you have put in to your client&#8217;s project.</p>
<p><strong>Step 3. Avoid email</strong><br />
It&#8217;s a necessary evil but inboxes are time sinks. Your internal client will view your email with that all important design or design presentation attached, give it a quick once over and say &#8220;looks fab&#8221; and then go on to the next item in the inbox.</p>
<p>Send your designs in an email but also arrange a time for a quick meeting about the design — so you can present it!</p>
<p>If you can&#8217;t be face to face with your client, as is the case with my friend, I would recommend online presentations of some sort and a good ol&#8217; conference call. There are cool online conferencing tools like <a href="http://www.adobe.com/products/acrobatconnectpro/">Adobe Connect</a> but you can just as easily use Google Docs, <a href="http://www.slideshare.net/">Slideshare</a> or the prettier <a href="http://www.sliderocket.com/">Slide Rocket</a> to show off your wares, or simply, walk through each page of a PDF.</p>
<p><strong>Step 4. Proof the feedback</strong><br />
If you are lucky your client may be an Acrobat pro and annotate your PDF so you know exactly what text to change and what to move where. But usually people are lazy and will spill out their feedback on the phone or in an email. I always scored highly in comprehension tasks at school but I would need the added skill of mental telepathy to understand the intent of some of the feedback I have received.</p>
<p>Collate all the feedback and annotate your design with the comments. Get the client to verify that your notes are what they intended by their comments and represent what they want changed.</p>
<p><strong>Step 5. Incorporate feedback<br />
</strong><br />
<strong>Step 6. Rinse and repeat.<br />
</strong><br />
Of course these steps may be overkill if your client is in the next room, or if you are presenting a business card based on a set template, but you get the point. Colour, pretty pictures, fancy fonts, all get in the way of proofing the actual content. Test the content, verify the feedback and hopefully reduce the risk and angst of the design process.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.eriontheinterweb.com/2009/05/presenting-design/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

