<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Getting Design Approval: The Single Mockup Theory</title>
	<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 21 Nov 2008 03:22:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Cristiano Rastelli</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379303</link>
		<author>Cristiano Rastelli</author>
		<pubDate>Mon, 26 May 2008 21:17:53 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379303</guid>
					<description>I generally use two approaches: I present or a single mockup (the best one out of a series of grahical attempts) or the early&#160;grahical attempts (through Basecamp) using an agile approach and involving the customer in the decisional process.</description>
		<content:encoded><![CDATA[<p>I generally use two approaches: I present or a single mockup (the best one out of a series of grahical attempts) or the early&nbsp;grahical attempts (through Basecamp) using an agile approach and involving the customer in the decisional process.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steve Rose</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379361</link>
		<author>Steve Rose</author>
		<pubDate>Mon, 26 May 2008 22:16:54 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379361</guid>
					<description>I have come to dislike the idea of showing the client a variety of sites to try to understand their likes and dislikes. I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas. I prefer to ask site owners, &#34;What perception do you want your site users to have regarding your company/service&#34;? Then I try to give them a design that fulfills that goal.</description>
		<content:encoded><![CDATA[<p>I have come to dislike the idea of showing the client a variety of sites to try to understand their likes and dislikes. I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas. I prefer to ask site owners, &quot;What perception do you want your site users to have regarding your company/service&quot;? Then I try to give them a design that fulfills that goal.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darren Hoyt</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379484</link>
		<author>Darren Hoyt</author>
		<pubDate>Tue, 27 May 2008 00:21:08 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379484</guid>
					<description>&lt;em&gt;I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas.&lt;/em&gt;That's a great point. When I broach this with clients, they often suggest that they know their industry very well, thus they are&#160; part of their own audience and can identify with what users need. Sometimes they are projecting these needs on their users and it doesn't work. It's not directly addressed in the article, but yeah, Audience is obviously a major part of the strategy process.</description>
		<content:encoded><![CDATA[<p><em>I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas.</em>That&#8217;s a great point. When I broach this with clients, they often suggest that they know their industry very well, thus they are&nbsp; part of their own audience and can identify with what users need. Sometimes they are projecting these needs on their users and it doesn&#8217;t work. It&#8217;s not directly addressed in the article, but yeah, Audience is obviously a major part of the strategy process.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Tor Løvskogen</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379847</link>
		<author>Tor Løvskogen</author>
		<pubDate>Tue, 27 May 2008 07:25:03 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379847</guid>
					<description>At my job we just present one mock-up with several secondary page mock-ups, because it's just the best way - no Frankenstein :-)</description>
		<content:encoded><![CDATA[<p>At my job we just present one mock-up with several secondary page mock-ups, because it&#8217;s just the best way - no Frankenstein :-)</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Michelle Sullivan</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379998</link>
		<author>Michelle Sullivan</author>
		<pubDate>Tue, 27 May 2008 09:59:40 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-379998</guid>
					<description>It has been my experience that if presented with several different mockups a client will more often than not go for the 'mashup' of designs - a bit of this, a bit of that, much to the frustration of the designer.</description>
		<content:encoded><![CDATA[<p>It has been my experience that if presented with several different mockups a client will more often than not go for the &#8216;mashup&#8217; of designs - a bit of this, a bit of that, much to the frustration of the designer.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Heidi</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380189</link>
		<author>Heidi</author>
		<pubDate>Tue, 27 May 2008 13:43:54 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380189</guid>
					<description>&lt;em&gt;&lt;a href="http://simplyfull.com/" rel="nofollow"&gt;Steve Rose said:&lt;/a&gt;&lt;/em&gt;&lt;em&gt;&#34;I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas.&#34;&lt;/em&gt;Amen! I actually turned down an otherwise attractive position in an agency because the client I would be focusing on could not grasp this concept. The attitude was very much &#34;we know what our visitors want,&#34; and the expectation was that I would merely code what the client asked for, not what they actually needed. </description>
		<content:encoded><![CDATA[<p><em><a href="http://simplyfull.com/" rel="nofollow">Steve Rose said:</a></em><em>&quot;I believe websites should be designed graphically to suit the likes and dislikes of the site users, not the site owners, and too many site owners are unable to separate these two very different ideas.&quot;</em>Amen! I actually turned down an otherwise attractive position in an agency because the client I would be focusing on could not grasp this concept. The attitude was very much &quot;we know what our visitors want,&quot; and the expectation was that I would merely code what the client asked for, not what they actually needed. </p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Aaron Russell</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380407</link>
		<author>Aaron Russell</author>
		<pubDate>Tue, 27 May 2008 19:15:56 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380407</guid>
					<description>I think there's a lot of sense in this article as I'm sure we've all come accross the same situation: you create three mockups - one really creative concept, one really conservative concept, and one middle of the road concept. Sure enough, nine times out of ten the client picks the 'wrong' concept - the middle of the road idea. Why did we even give them the option?However, I think there's more to this. We have to accept that as creative types, we're always going to prefer that slightly more leftfield concept - that's our nature. The client who's expectations are shaped somewhat differently to ours, is probably hoping for something a bit more conventional than we would like - a 'safer' option. Does that mean that we're right and they're wrong? I don't think so.The argument of this article can work the other way too, because if you present only one option and the client doesn't like it, then time and budget can get spent bending the concept to something the client does like. Sometimes providing multiple concepts allows the client to feel involved and have some input into the overall decision, without the project turning into design by committee or some beastly frankenstein. </description>
		<content:encoded><![CDATA[<p>I think there&#8217;s a lot of sense in this article as I&#8217;m sure we&#8217;ve all come accross the same situation: you create three mockups - one really creative concept, one really conservative concept, and one middle of the road concept. Sure enough, nine times out of ten the client picks the &#8216;wrong&#8217; concept - the middle of the road idea. Why did we even give them the option?However, I think there&#8217;s more to this. We have to accept that as creative types, we&#8217;re always going to prefer that slightly more leftfield concept - that&#8217;s our nature. The client who&#8217;s expectations are shaped somewhat differently to ours, is probably hoping for something a bit more conventional than we would like - a &#8217;safer&#8217; option. Does that mean that we&#8217;re right and they&#8217;re wrong? I don&#8217;t think so.The argument of this article can work the other way too, because if you present only one option and the client doesn&#8217;t like it, then time and budget can get spent bending the concept to something the client does like. Sometimes providing multiple concepts allows the client to feel involved and have some input into the overall decision, without the project turning into design by committee or some beastly frankenstein. </p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Naomi Niles</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380816</link>
		<author>Naomi Niles</author>
		<pubDate>Wed, 28 May 2008 07:48:07 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380816</guid>
					<description>Total agreement here, great article! We started offering 1 concept about a year ago. We explain to them that we'd rather give them 1 strong concept rather than several weak ones and they seem to understand that. Often they still request more than 1 and we honor that too, but I agree that almost always, 1 concept gets better restults. Anyhow, when you offer more than one, there's always one you know is better and the client picks the worse one, right? Or the frankenstein mish mash, which is yuck too.I agree with Steve on putting too much importance in what type of site the client likes. This can be helpful depending on the level of knowledge they have about the industry or web in general, but sometimes they don't really know. It's up to you either way to research their industry as much as you can and make something in line with that.Interesting about the Mood Board idea. I never heard of that! We pretty much do wireframes on all sites nowadays, whether the client sees them or not. I think it helps the design process a lot later. &#160;</description>
		<content:encoded><![CDATA[<p>Total agreement here, great article! We started offering 1 concept about a year ago. We explain to them that we&#8217;d rather give them 1 strong concept rather than several weak ones and they seem to understand that. Often they still request more than 1 and we honor that too, but I agree that almost always, 1 concept gets better restults. Anyhow, when you offer more than one, there&#8217;s always one you know is better and the client picks the worse one, right? Or the frankenstein mish mash, which is yuck too.I agree with Steve on putting too much importance in what type of site the client likes. This can be helpful depending on the level of knowledge they have about the industry or web in general, but sometimes they don&#8217;t really know. It&#8217;s up to you either way to research their industry as much as you can and make something in line with that.Interesting about the Mood Board idea. I never heard of that! We pretty much do wireframes on all sites nowadays, whether the client sees them or not. I think it helps the design process a lot later. &nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Harry Roberts</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380822</link>
		<author>Harry Roberts</author>
		<pubDate>Wed, 28 May 2008 08:10:29 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-380822</guid>
					<description>Brilliant article, thanks!&#160;&#160;</description>
		<content:encoded><![CDATA[<p>Brilliant article, thanks!&nbsp;&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: johan</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-381059</link>
		<author>johan</author>
		<pubDate>Wed, 28 May 2008 19:10:40 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-381059</guid>
					<description>Sometimes I dont have to redesign/change anything, though this depends on the client's input and last minute overhaul changes.Usually we have two stages: proposal and&#160; after clients give their opinion changes and refinement go on that what the final website will be.&#160; &#160;&#160;</description>
		<content:encoded><![CDATA[<p>Sometimes I dont have to redesign/change anything, though this depends on the client&#8217;s input and last minute overhaul changes.Usually we have two stages: proposal and&nbsp; after clients give their opinion changes and refinement go on that what the final website will be.&nbsp; &nbsp;&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jennifer</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-382043</link>
		<author>Jennifer</author>
		<pubDate>Thu, 29 May 2008 20:16:58 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-382043</guid>
					<description>Great article and great comments. I've been providing my clients with two design drafts up till now and I think I'm going to change that now to one homepage design and a couple of secondary &#34;inside&#34; pages.&#160; I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me. So I try to take their &#34;likes&#34; and build them what they need and make as many recommendations as possible if they are erring off onto some sort of web monstrosity.&#160; </description>
		<content:encoded><![CDATA[<p>Great article and great comments. I&#8217;ve been providing my clients with two design drafts up till now and I think I&#8217;m going to change that now to one homepage design and a couple of secondary &quot;inside&quot; pages.&nbsp; I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me. So I try to take their &quot;likes&quot; and build them what they need and make as many recommendations as possible if they are erring off onto some sort of web monstrosity.&nbsp; </p>
]]></content:encoded>
				</item>
	<item>
		<title>By: J. Jeffryes</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383189</link>
		<author>J. Jeffryes</author>
		<pubDate>Fri, 30 May 2008 18:17:24 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383189</guid>
					<description>I've been doing this for a few years, the key is to have a very solid process, where the client approves and has input into the requirements list, the site architecture, the wireframes and the color scheme before they see the design. If you've done that, then they already have some idea what the concept will look like, and it's easy to get them to sign off on it. If you just ambush them with a concept from out of nowhere they will resist, and demand changes or new concepts.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been doing this for a few years, the key is to have a very solid process, where the client approves and has input into the requirements list, the site architecture, the wireframes and the color scheme before they see the design. If you&#8217;ve done that, then they already have some idea what the concept will look like, and it&#8217;s easy to get them to sign off on it. If you just ambush them with a concept from out of nowhere they will resist, and demand changes or new concepts.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darren  Hoyt</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383242</link>
		<author>Darren  Hoyt</author>
		<pubDate>Fri, 30 May 2008 19:33:16 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383242</guid>
					<description>&lt;em&gt;because if you present only one option and the client doesn&#8217;t like it, then time and budget can get spent bending the concept to something the client does like.&lt;/em&gt;Our standard contract only provides 3 rounds of design feedback. If by the 3rd round we feel like we've done our best work and are presenting something that represents best design and best practices, but the client is still displeased, we hit the brakes and decide whether to re-cope the budget or to offer the client 'other options' (aka, referring them elsewhere). This almost never happens, FWIW, but if&#160; it's clear the client is going to insist on a piece of work that we don't think is good, we'd rather them work with a firm that suits them better than to prolong a doomed process. &#160;It&#8217;s up to you either way to research their industry as much as you can and make something in line with that.Interesting about the Mood Board idea. I never heard of that! We pretty much do wireframes on all sites nowadays, whether the client sees them or not. I think it helps the design process a lot later.&#160;I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me. &#160;If you&#8217;ve done that, then they already have some idea what the concept will look like, and it&#8217;s easy to get them to sign off on it.&#160;W3c, or sketchpad.&#160;</description>
		<content:encoded><![CDATA[<p><em>because if you present only one option and the client doesn&rsquo;t like it, then time and budget can get spent bending the concept to something the client does like.</em>Our standard contract only provides 3 rounds of design feedback. If by the 3rd round we feel like we&#8217;ve done our best work and are presenting something that represents best design and best practices, but the client is still displeased, we hit the brakes and decide whether to re-cope the budget or to offer the client &#8216;other options&#8217; (aka, referring them elsewhere). This almost never happens, FWIW, but if&nbsp; it&#8217;s clear the client is going to insist on a piece of work that we don&#8217;t think is good, we&#8217;d rather them work with a firm that suits them better than to prolong a doomed process. &nbsp;It&rsquo;s up to you either way to research their industry as much as you can and make something in line with that.Interesting about the Mood Board idea. I never heard of that! We pretty much do wireframes on all sites nowadays, whether the client sees them or not. I think it helps the design process a lot later.&nbsp;I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me. &nbsp;If you&rsquo;ve done that, then they already have some idea what the concept will look like, and it&rsquo;s easy to get them to sign off on it.&nbsp;W3c, or sketchpad.&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darren Hoyt</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383280</link>
		<author>Darren Hoyt</author>
		<pubDate>Fri, 30 May 2008 20:16:58 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-383280</guid>
					<description>&lt;em&gt;The argument of this article can work the other way too, because if you present only one option and the client doesn&#8217;t like it, then time and budget can get spent bending the concept to something the client does like.&lt;/em&gt;

Our standard contract offers up to 3 rounds of design feedback. If after 3 rounds the client is still displeased but we feel like we've done our best design using best practices, we will hit the brakes and re-scope the budget. Or, we offer the client 'alternatives' (aka, refer them elsewhere). FWIW, this almost never happens, but I'd rather them work with someone whose tastes and process suits them better than to prolong a relationship that isn't working. 

&lt;em&gt;It&#8217;s up to you either way to research their industry as much as you can and make something in line with that.&lt;/em&gt;

Exactly. If the client is giving a deer-in-the-headlights look when asked for input, it's up to us to dig deeper to research their industry and competition. Granted, if it's clear the client isn't equipped to offer timely content or feedback, it's sometimes necessary to add additional design hours to the budget for assembling content and experimenting. A more prepared, on-the-ball client always pays less.

&lt;em&gt;I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me.&lt;/em&gt; 

The questionnaire approach can be really helpful. FWIW, I usually give them a copy a couple weeks before the kickoff meeting so that they have some things to discuss in person. Even when the&#160; responses aren't 100% helpful, it's a good conversation-starter, and a reminder that they will need to actively contribute to the project, not passively expect results.&#160; 

&lt;em&gt;If you just ambush them with a concept from out of nowhere they will resist, and demand changes or new concepts. &lt;/em&gt;

Before the end of a kickoff meeting, I try to have something already sketched, either with the Best4c tool or even drawn on paper. If nothing else, a list of homepage modules that we both agree on, so when presented with a mockup later on, they won't feel surprised or ambushed by the layout. </description>
		<content:encoded><![CDATA[<p><em>The argument of this article can work the other way too, because if you present only one option and the client doesn&rsquo;t like it, then time and budget can get spent bending the concept to something the client does like.</em></p>
<p>Our standard contract offers up to 3 rounds of design feedback. If after 3 rounds the client is still displeased but we feel like we&#8217;ve done our best design using best practices, we will hit the brakes and re-scope the budget. Or, we offer the client &#8216;alternatives&#8217; (aka, refer them elsewhere). FWIW, this almost never happens, but I&#8217;d rather them work with someone whose tastes and process suits them better than to prolong a relationship that isn&#8217;t working. </p>
<p><em>It&rsquo;s up to you either way to research their industry as much as you can and make something in line with that.</em></p>
<p>Exactly. If the client is giving a deer-in-the-headlights look when asked for input, it&#8217;s up to us to dig deeper to research their industry and competition. Granted, if it&#8217;s clear the client isn&#8217;t equipped to offer timely content or feedback, it&#8217;s sometimes necessary to add additional design hours to the budget for assembling content and experimenting. A more prepared, on-the-ball client always pays less.</p>
<p><em>I give all my clients questionnaires where I try to dig out as much information about the sites that they like, dislike, colours they like and so on. That often yields a lot more information than when I meet them face to face because they seem to take a bit more time on the questionnaire and are under no pressure to give answers to me.</em> </p>
<p>The questionnaire approach can be really helpful. FWIW, I usually give them a copy a couple weeks before the kickoff meeting so that they have some things to discuss in person. Even when the&nbsp; responses aren&#8217;t 100% helpful, it&#8217;s a good conversation-starter, and a reminder that they will need to actively contribute to the project, not passively expect results.&nbsp; </p>
<p><em>If you just ambush them with a concept from out of nowhere they will resist, and demand changes or new concepts. </em></p>
<p>Before the end of a kickoff meeting, I try to have something already sketched, either with the Best4c tool or even drawn on paper. If nothing else, a list of homepage modules that we both agree on, so when presented with a mockup later on, they won&#8217;t feel surprised or ambushed by the layout. </p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Jon Kokke</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-385349</link>
		<author>Jon Kokke</author>
		<pubDate>Sun, 01 Jun 2008 19:13:52 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-385349</guid>
					<description>We generally use a single mock up&#160;approach&#160;for all our work. We find that using a workflow of a project sheet (either filled in by the client or by us and the client), writing a spec &#38; scope document (usually with wireframes), then presentation of visual (usually 2-3 key pages). We then have a meeting and produce any amendments. Often we can so these in the template / build stage.	</description>
		<content:encoded><![CDATA[<p>We generally use a single mock up&nbsp;approach&nbsp;for all our work. We find that using a workflow of a project sheet (either filled in by the client or by us and the client), writing a spec &amp; scope document (usually with wireframes), then presentation of visual (usually 2-3 key pages). We then have a meeting and produce any amendments. Often we can so these in the template / build stage.	</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Aaron Mills</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-385742</link>
		<author>Aaron Mills</author>
		<pubDate>Mon, 02 Jun 2008 04:32:10 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-385742</guid>
					<description>This is a really great post. I have been so frustrated with offering 3 mockups. I think you are so right to offer one. This also places the finances of the design budget into the slot of &#34;really discovering what the client likes to get it right the first time&#34;&#160;Great ideas, love the blog&#160;</description>
		<content:encoded><![CDATA[<p>This is a really great post. I have been so frustrated with offering 3 mockups. I think you are so right to offer one. This also places the finances of the design budget into the slot of &quot;really discovering what the client likes to get it right the first time&quot;&nbsp;Great ideas, love the blog&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Kirk</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-386623</link>
		<author>Kirk</author>
		<pubDate>Mon, 02 Jun 2008 22:40:58 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-386623</guid>
					<description>I work for an agency as a creative director and have found that very few clients will accept the 1 mock approach. I have tried this idea and when our AE is speaking with the primary stakeholders, rarely will they go for this approach. As the creative director, it is my responsibility to steer them in the right direction and they usually pick the best design. From there we build the interior comps based off of the approved index comp.</description>
		<content:encoded><![CDATA[<p>I work for an agency as a creative director and have found that very few clients will accept the 1 mock approach. I have tried this idea and when our AE is speaking with the primary stakeholders, rarely will they go for this approach. As the creative director, it is my responsibility to steer them in the right direction and they usually pick the best design. From there we build the interior comps based off of the approved index comp.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: MJ</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-387164</link>
		<author>MJ</author>
		<pubDate>Tue, 03 Jun 2008 10:48:14 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-387164</guid>
					<description>It's usually the clients with no artistic taste who are very picky!</description>
		<content:encoded><![CDATA[<p>It&#8217;s usually the clients with no artistic taste who are very picky!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-392534</link>
		<author>Johan</author>
		<pubDate>Mon, 09 Jun 2008 05:21:52 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-392534</guid>
					<description>- Mostly clients set up the wireframe?- Many clients often include references to sites they like. - Without the necessary content a mockup seems sterile? </description>
		<content:encoded><![CDATA[<p>- Mostly clients set up the wireframe?- Many clients often include references to sites they like. - Without the necessary content a mockup seems sterile? </p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Debi K</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-393291</link>
		<author>Debi K</author>
		<pubDate>Mon, 09 Jun 2008 19:09:24 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-393291</guid>
					<description>Great discussion. What about presenting a single mockup, but allow customers to collaborate on the design using a program like Gliffy? This way you can allow them to specifically suggest what types of changes they have in mind (but you still have the option to revert to earlier versions). No matter what trends occur, people always want their opinions heard!debik at gliffy dot com&#160;</description>
		<content:encoded><![CDATA[<p>Great discussion. What about presenting a single mockup, but allow customers to collaborate on the design using a program like Gliffy? This way you can allow them to specifically suggest what types of changes they have in mind (but you still have the option to revert to earlier versions). No matter what trends occur, people always want their opinions heard!debik at gliffy dot com&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: OneHipSista</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-394714</link>
		<author>OneHipSista</author>
		<pubDate>Tue, 10 Jun 2008 17:02:57 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-394714</guid>
					<description>I like this theory. I always thought I was giving clients options by doing several mockups. In reality, I've always produced one really detailed comp; then reproduced the same layout in slightly different color schemes - making the client think they were seeing something different. I actually listen to clients and what they think they want but ultimately, I'm the designer and I know what I'm doing.</description>
		<content:encoded><![CDATA[<p>I like this theory. I always thought I was giving clients options by doing several mockups. In reality, I&#8217;ve always produced one really detailed comp; then reproduced the same layout in slightly different color schemes - making the client think they were seeing something different. I actually listen to clients and what they think they want but ultimately, I&#8217;m the designer and I know what I&#8217;m doing.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Aaron</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-396043</link>
		<author>Aaron</author>
		<pubDate>Thu, 12 Jun 2008 20:25:35 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-396043</guid>
					<description>Absoletely true. Spend as much time and resources in the planning stage, really learn the clients likes and dislikes, and then present them the one. Your pitch should be, this is what we think is the best solution for you. The more versions you give them, the longer it will take and usually overall the worse and more muddled and unfocused it will be.</description>
		<content:encoded><![CDATA[<p>Absoletely true. Spend as much time and resources in the planning stage, really learn the clients likes and dislikes, and then present them the one. Your pitch should be, this is what we think is the best solution for you. The more versions you give them, the longer it will take and usually overall the worse and more muddled and unfocused it will be.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: flashy</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-405055</link>
		<author>flashy</author>
		<pubDate>Thu, 19 Jun 2008 17:32:09 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-405055</guid>
					<description>Nice post, do you have any on how to defend logo designs....I always have pronlems with that :(</description>
		<content:encoded><![CDATA[<p>Nice post, do you have any on how to defend logo designs&#8230;.I always have pronlems with that :(</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: abdul</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-406961</link>
		<author>abdul</author>
		<pubDate>Sat, 21 Jun 2008 07:34:21 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-406961</guid>
					<description>This is a really great post. Excellent atricle...&#160;</description>
		<content:encoded><![CDATA[<p>This is a really great post. Excellent atricle&#8230;&nbsp;</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Sonali Sengupta</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-421944</link>
		<author>Sonali Sengupta</author>
		<pubDate>Fri, 04 Jul 2008 07:00:11 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-421944</guid>
					<description>Brilliant post, thanks for sharing.</description>
		<content:encoded><![CDATA[<p>Brilliant post, thanks for sharing.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Klans</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-438711</link>
		<author>Klans</author>
		<pubDate>Sun, 20 Jul 2008 16:12:21 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-438711</guid>
					<description>Good insight. I normally work on 2 drafts based upon a series of questions, slected reference sites from the client, my own research, and the corporate identity of the company. Generally, people like to have choices and providing 2 well&#160;conceptualized drafts solves this. It also shows that you hae done your homework and is serious enough.&#160;At the end, it's up to the agent to direct a disgruntled client into closing on a concept.</description>
		<content:encoded><![CDATA[<p>Good insight. I normally work on 2 drafts based upon a series of questions, slected reference sites from the client, my own research, and the corporate identity of the company. Generally, people like to have choices and providing 2 well&nbsp;conceptualized drafts solves this. It also shows that you hae done your homework and is serious enough.&nbsp;At the end, it&#8217;s up to the agent to direct a disgruntled client into closing on a concept.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Ryan Battles</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-439869</link>
		<author>Ryan Battles</author>
		<pubDate>Mon, 21 Jul 2008 11:55:38 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-439869</guid>
					<description>I had never thought about suggesting only one markup.&#160; It makes perfect sense though, especially if you do good homework on what they are looking for.&#160; I really liked the idea of projecting a CSS gallery to get feedback.&#160; Thanks for the article.</description>
		<content:encoded><![CDATA[<p>I had never thought about suggesting only one markup.&nbsp; It makes perfect sense though, especially if you do good homework on what they are looking for.&nbsp; I really liked the idea of projecting a CSS gallery to get feedback.&nbsp; Thanks for the article.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: acms</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-448994</link>
		<author>acms</author>
		<pubDate>Mon, 28 Jul 2008 16:39:53 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-448994</guid>
					<description>Great resource for a begginer like me. Thanks.</description>
		<content:encoded><![CDATA[<p>Great resource for a begginer like me. Thanks.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: jhonnight</title>
		<link>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-460397</link>
		<author>jhonnight</author>
		<pubDate>Wed, 06 Aug 2008 09:34:49 +0000</pubDate>
		<guid>http://fadtastic.net/2008/05/26/getting-design-approval-the-single-mockup-theory/#comment-460397</guid>
					<description>go land stone joke speed white water vacant home usa minor mail</description>
		<content:encoded><![CDATA[<p>go land stone joke speed white water vacant home usa minor mail</p>
]]></content:encoded>
				</item>
</channel>
</rss>
