<?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>Ash Young &#187; Graphic Design</title>
	<atom:link href="http://www.ashyoung.org/category/graphic-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ashyoung.org</link>
	<description>Web development &#38; design at its best</description>
	<lastBuildDate>Tue, 06 Apr 2010 14:56:19 +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>Website Wireframing with Balsamiq</title>
		<link>http://www.ashyoung.org/2009/06/website-wireframing-with-balsamiq/</link>
		<comments>http://www.ashyoung.org/2009/06/website-wireframing-with-balsamiq/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 20:06:19 +0000</pubDate>
		<dc:creator>Ash</dc:creator>
				<category><![CDATA[Evoluted]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Balsamiq]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[wireframes]]></category>

		<guid isPermaLink="false">http://www.ashyoung.org/?p=43</guid>
		<description><![CDATA[Prior to this month our standard design approach at Evoluted didn&#8217;t include wireframing. We occasionally drew some rough sketches with the client whilst having our initial meetings but nothing formal ever took place. Overtime we&#8217;ve come to see the error our ways and we have now started to include wireframes as part of our design [...]]]></description>
			<content:encoded><![CDATA[<p>Prior to this month our standard design approach at Evoluted didn&#8217;t include wireframing. We occasionally drew some rough sketches with the client whilst having our initial meetings but nothing formal ever took place. Overtime we&#8217;ve come to see the error our ways and we have now started to include wireframes as part of our design process. </p>
<p>The motivating factor for us was the time spent in the design stage. Often we&#8217;d send over an initial set of ideas to the client who&#8217;d like the look and feel but request that a handful of new elements were added to the page. This led to a design bursting at the seams with elements crammed in until the original design stopped working. In these situations it would be better to throw the initial design away and start from scratch but due to time and budget restraints this didn&#8217;t always happen.</p>
<p>Wireframing sites has been a revelation, it&#8217;s such a quick process. Wireframing moves the burden of ensuring all the required elements are in the page from the designer who isn&#8217;t always in client meetings to the project manager. The speed at which we can create wireframes means that we now wireframe far more pages that we actually design in Photoshop. This helps the programmers as they no longer have to worry about layout on the additional pages. The wireframes also act as a sort of functional specification; the site’s functionality must include everything that is on the wireframes. Wireframes are also far easier to comprehend meaning our developers spend less timing trawling through long written specifications.</p>
<p>The outcome of this is that we&#8217;ve started to use a program called <a href="http://www.balsamiq.com/products/mockups">Balsamiq Mockups</a> to create wireframes for every project we&#8217;re involved in on the design side. Balsamiq Mockups is a great little tool that makes wireframing effortless, and the best part is that it shows the wireframes for what they really are &#8211; sketches to show layout not design style.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ashyoung.org/2009/06/website-wireframing-with-balsamiq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why you shouldn&#8217;t use another site as your specification</title>
		<link>http://www.ashyoung.org/2009/05/why-you-shouldnt-use-another-site-as-your-specification/</link>
		<comments>http://www.ashyoung.org/2009/05/why-you-shouldnt-use-another-site-as-your-specification/#comments</comments>
		<pubDate>Tue, 05 May 2009 19:51:50 +0000</pubDate>
		<dc:creator>Ash</dc:creator>
				<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Web Sites]]></category>
		<category><![CDATA[copying websites]]></category>
		<category><![CDATA[specification]]></category>

		<guid isPermaLink="false">http://www.ashyoung.org/?p=32</guid>
		<description><![CDATA[Previously I wrote about what happens when a client wants to copy the look and feel of another website for their latest project. Ripping off another website is obviously wrong but it doesn’t lead to any issues in the development process, in fact it might well speed it up.
Imagine the scenario when a potential client [...]]]></description>
			<content:encoded><![CDATA[<p>Previously I wrote about what happens when a client wants to copy the look and feel of another website for their latest project. Ripping off another website is obviously wrong but it doesn’t lead to any issues in the development process, in fact it might well speed it up.</p>
<p>Imagine the scenario when a potential client gets in touch and asks “I want an e-commerce site like Amazon.com, how much will it cost?”</p>
<p>Now I’m sure you’ve spotted the issue here, unless you know the client works for a massive blue chip company then it’s unlikely they are after Amazon.com. You have to read into the client’s requirements, and in this case they are likely after a fairly standard e-commerce setup.</p>
<p>In these situations it is tempting to go with your gut and quote the client for a standard e-commerce platform, following up as usual in a few days to see if the client is interested. It’s at this point that everything can start to go wrong.</p>
<p>On your follow up phone call you discover that the client wishes to go ahead with their Amazon.com clone. At this point you really need to be clear with the client and confirm the functionality that you’ll be supplying for this project. If you haven’t already sent the client a specification, then send one now and get them to sign it!</p>
<p>If you don’t clarify your position with the client you may run into the follow 3 issues:</p>
<ol>
<li>The client only sees a fraction of the functionality on Amazon.com, probably searching or browsing for a product and the checkout process. They don’t see any of the backend or any of the “clever” stuff.</li>
<li>The development team working on the project sees a separate set of functionality and envisages the backend functionality, plus some of the “clever” stuff.</li>
<li>The user doesn’t see certain functionality they require but assumes that Amazon.com must have it somewhere and that the development team will code this into the system.</li>
</ol>
<p><img src="http://chart.apis.google.com/chart?cht=v&amp;chs=520x260&amp;chd=t:80,40,40,15,15,0,0&amp;chdl=Developer Envisaged Functionality|Client Seen Functioanlity|Client Envisiaged Functionality&amp;chtt=Functionality overlap" alt="Functionality overlap" /></p>
<p>If this void between the client and the development team isn’t resolved then your project is doomed to fail, overrun, go over budget and perhaps even get cancelled.</p>
<p>For jobs such as these it is worth the time spent writing a specification upfront to accompany your quote to make sure the client understands the exact functionality they are getting. Once you’ve done a few quotes they’ll take next to no time to knock up. If you don’t write a specification you run the risk of the project going seriously wrong and costing you time, money and potentially worse of all &#8211; reputation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ashyoung.org/2009/05/why-you-shouldnt-use-another-site-as-your-specification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>It’s dead easy, I want it just like that!</title>
		<link>http://www.ashyoung.org/2009/04/it%e2%80%99s-dead-easy-i-want-it-just-like-that/</link>
		<comments>http://www.ashyoung.org/2009/04/it%e2%80%99s-dead-easy-i-want-it-just-like-that/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 19:55:17 +0000</pubDate>
		<dc:creator>Ash</dc:creator>
				<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Web Sites]]></category>
		<category><![CDATA[clone sites]]></category>
		<category><![CDATA[Evoluted]]></category>
		<category><![CDATA[graphic designers]]></category>

		<guid isPermaLink="false">http://www.ashyoung.org/?p=35</guid>
		<description><![CDATA[How many times have you heard that particular phrase? Whether you’re a designer, account manager or developer either your boss or a client will have uttered those words to you whilst pointing at an example they’d like to ‘borrow inspiration’ from.
If you’re a designer this could have just made your job really easy, the client [...]]]></description>
			<content:encoded><![CDATA[<p>How many times have you heard that particular phrase? Whether you’re a designer, account manager or developer either your boss or a client will have uttered those words to you whilst pointing at an example they’d like to ‘borrow inspiration’ from.</p>
<p>If you’re a designer this could have just made your job really easy, the client has given you an exact idea of the style that they like. Or they’ve made it really hard and they won’t be happy unless their website or artwork looks <em>identical</em> to the example provided. Who can tell? From where I’m sitting it doesn’t matter, there is only one choice, the right one.</p>
<p>If you’re sat there thinking that you’d rip off the example provided then I’m afraid you’ve just lost a potential client.</p>
<p>In these situations you can really tell designers who take pride in their work apart from those who just knock designs out on production line. A good designer who is worth anything won’t mindlessly rip off someone else’s hard work and talent, they’ll refuse. Deep down all designers crave the warm fuzzy feeling provided by a client’s love of your design. Ripping off another design doesn’t provide this, it just makes you feel cheap, dirty and used.</p>
<p>Copying designs is something that we never do at Evoluted so if you’re a designer that loves creating unique work then why not get in touch.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ashyoung.org/2009/04/it%e2%80%99s-dead-easy-i-want-it-just-like-that/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
