<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Why Give Clients More Than One Mockup?</title>
	<atom:link href="http://marcamos.com/why-give-clients-more-than-one-mockup/feed/" rel="self" type="application/rss+xml" />
	<link>http://marcamos.com/why-give-clients-more-than-one-mockup/</link>
	<description>&#60;love&#62;&#60;/love&#62;</description>
	<pubDate>Fri, 21 Nov 2008 02:18:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Marlyse Comte</title>
		<link>http://marcamos.com/why-give-clients-more-than-one-mockup/#comment-26</link>
		<dc:creator>Marlyse Comte</dc:creator>
		<pubDate>Tue, 26 Feb 2008 01:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/why-give-clients-more-than-one-mockup/#comment-26</guid>
		<description>	&lt;p&gt;Yes, I have also come to the viewpoint that usually 1 mockup is fine and the more options I give the client the more confused he usually will get and out of experience, he will always chose the design I like the least and only put in &#8220;for good measures&#8221; (what a stupid thought that &#8216;more is better&#8217; &#8211; must come from the &#8216;Supersize Me&#8217; push in fast food stores).&lt;/p&gt;

	&lt;p&gt;I much rather put more work into 1 good design then split the same time into 3 quickies. Doing my home work first and listening to the client, this has been very successful.&lt;/p&gt;

	&lt;p&gt;The other day when I completely missed the ballpark with a new logo was when from the meeting the clients had said bronze/gold/copper for colors but the reaction to the design idea then was &#8216;oh, nothing spoke to us, I thought we are going to use cobalt blue and bright yellow&#8217;&#8230; :-)&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Yes, I have also come to the viewpoint that usually 1 mockup is fine and the more options I give the client the more confused he usually will get and out of experience, he will always chose the design I like the least and only put in &#8220;for good measures&#8221; (what a stupid thought that &#8216;more is better&#8217; &#8211; must come from the &#8216;Supersize Me&#8217; push in fast food stores).</p>
<p>I much rather put more work into 1 good design then split the same time into 3 quickies. Doing my home work first and listening to the client, this has been very successful.</p>
<p>The other day when I completely missed the ballpark with a new logo was when from the meeting the clients had said bronze/gold/copper for colors but the reaction to the design idea then was &#8216;oh, nothing spoke to us, I thought we are going to use cobalt blue and bright yellow&#8217;&#8230; <img src='http://marcamos.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo</title>
		<link>http://marcamos.com/why-give-clients-more-than-one-mockup/#comment-25</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Mon, 25 Feb 2008 16:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/why-give-clients-more-than-one-mockup/#comment-25</guid>
		<description>	&lt;p&gt;@paul, By giving clients these kind of &#8216;choices&#8217;,  it opens up the floodgates for design disaster. Your dealership analogy likens all web designers to pre-fabricated template shops. This just isn&#8217;t the case.&lt;/p&gt;

	&lt;p&gt;Clients hire designers to carefully establish custom solutions for the client&#8217;s audience. I&#8217;d think of it more as if you were designing your own car from scratch. Sure, you&#8217;re using mostly pre-fabricated parts for functionality (e.g. an engine for search, wheels for navigation) but the design, the body that holds the vehicle is molded by hand, with each design consideration taken into account.&lt;/p&gt;

	&lt;p&gt;I know I&#8217;m idealizing this process quite a bit here, but it&#8217;s to make a point. What we do should be most valuable to the client&#8217;s audience. (That&#8217;s who is making them money and who they should ultimately care about.) We are tasked with the goal of protecting this intimate, complex relationship.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>@paul, By giving clients these kind of &#8216;choices&#8217;,  it opens up the floodgates for design disaster. Your dealership analogy likens all web designers to pre-fabricated template shops. This just isn&#8217;t the case.</p>
<p>Clients hire designers to carefully establish custom solutions for the client&#8217;s audience. I&#8217;d think of it more as if you were designing your own car from scratch. Sure, you&#8217;re using mostly pre-fabricated parts for functionality (e.g. an engine for search, wheels for navigation) but the design, the body that holds the vehicle is molded by hand, with each design consideration taken into account.</p>
<p>I know I&#8217;m idealizing this process quite a bit here, but it&#8217;s to make a point. What we do should be most valuable to the client&#8217;s audience. (That&#8217;s who is making them money and who they should ultimately care about.) We are tasked with the goal of protecting this intimate, complex relationship.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://marcamos.com/why-give-clients-more-than-one-mockup/#comment-24</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 19 Feb 2008 16:25:20 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/why-give-clients-more-than-one-mockup/#comment-24</guid>
		<description>	&lt;p&gt;I think multiple concepts are a must when presenting to a client. The best way I know how to compare it is buying a new car. &lt;/p&gt;

	&lt;p&gt;I know I want a car that has 4 wheels, power everything, cruise control, a sun roof and air conditioning. That&#8217;s what I want. Now I have to figure out what color I want. Do I want a Chevy or an Audi? Am I more like a Impala, or an A6. Different car makes and models are like different concepts presented to a client.&lt;/p&gt;

	&lt;p&gt;Now, is that to say that you should present 5 concepts and have 4 rounds of revisions, NO, not even close. I think 3 concepts are the max you should show, and if you can&#8217;t get a design right in 2 or 3 rounds after the concept is chosen, then there&#8217;s obviously a communication breakdown with the client.&lt;/p&gt;

	&lt;p&gt;As for frankensteining, it&#8217;s just an unfortunate outcome sometimes, but should &lt;span class="caps"&gt;NEVER&lt;/span&gt; apply to function. If one concept has a search and the others don&#8217;t, then somebody didn&#8217;t do their job. Sometimes clients just don&#8217;t like color combinations or image choices. You can do all the research in the world, ask the client 100 times what they want, and when you do it, they might not like it. Design leaves so much room for interpretation, you rarely nail what a client wants with one attempt.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>I think multiple concepts are a must when presenting to a client. The best way I know how to compare it is buying a new car. </p>
<p>I know I want a car that has 4 wheels, power everything, cruise control, a sun roof and air conditioning. That&#8217;s what I want. Now I have to figure out what color I want. Do I want a Chevy or an Audi? Am I more like a Impala, or an A6. Different car makes and models are like different concepts presented to a client.</p>
<p>Now, is that to say that you should present 5 concepts and have 4 rounds of revisions, NO, not even close. I think 3 concepts are the max you should show, and if you can&#8217;t get a design right in 2 or 3 rounds after the concept is chosen, then there&#8217;s obviously a communication breakdown with the client.</p>
<p>As for frankensteining, it&#8217;s just an unfortunate outcome sometimes, but should <span class="caps">NEVER</span> apply to function. If one concept has a search and the others don&#8217;t, then somebody didn&#8217;t do their job. Sometimes clients just don&#8217;t like color combinations or image choices. You can do all the research in the world, ask the client 100 times what they want, and when you do it, they might not like it. Design leaves so much room for interpretation, you rarely nail what a client wants with one attempt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo</title>
		<link>http://marcamos.com/why-give-clients-more-than-one-mockup/#comment-23</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Tue, 19 Feb 2008 13:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/why-give-clients-more-than-one-mockup/#comment-23</guid>
		<description>	&lt;p&gt;Clients are not designers. That is &lt;em&gt;presumably&lt;/em&gt; why they have hired us as web professionals. Allowing clients any degree of flexibility in the design process is a slippery slope indeed.&lt;/p&gt;

	&lt;p&gt;That being said, the best compromise I&#8217;ve found is a clear statement of roles at the beginning of the relationship, as well as consistent reminders throughout. Couple this with rapid design iterations in a browser context, and most &#8216;designers&#8217; can be persuaded to allow you the elbow room you need to do the work at hand proper justice.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Clients are not designers. That is <em>presumably</em> why they have hired us as web professionals. Allowing clients any degree of flexibility in the design process is a slippery slope indeed.</p>
<p>That being said, the best compromise I&#8217;ve found is a clear statement of roles at the beginning of the relationship, as well as consistent reminders throughout. Couple this with rapid design iterations in a browser context, and most &#8216;designers&#8217; can be persuaded to allow you the elbow room you need to do the work at hand proper justice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://marcamos.com/why-give-clients-more-than-one-mockup/#comment-22</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 19 Feb 2008 13:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://marcamos.com/blog/why-give-clients-more-than-one-mockup/#comment-22</guid>
		<description>	&lt;p&gt;Unfortunately the solution lies more in the realm of adjusting client expectations than a firm&#8217;s process. Unless the entire industry were to take a unified approach, there&#8217;s always another shop down the road. And there are bills to pay. &lt;/p&gt;

	&lt;p&gt;We recently held our ground on only one design concept. It was due to a really tight timeframe, though. The client went to someone else who agreed to do multiple concepts and asked if we&#8217;d execute the winner. We declined. He probably won&#8217;t make his deadline, which we would have guaranteed. It was more important to him, though, to have 3 concepts.  &lt;/p&gt;

	&lt;p&gt;Frankensteining sucks but it doesn&#8217;t have to be either or. A few concepts can be created &lt;span class="caps"&gt;AND&lt;/span&gt; the client can be educated. Successful outcome hinges upon the relationship and its footing moreso than process.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Unfortunately the solution lies more in the realm of adjusting client expectations than a firm&#8217;s process. Unless the entire industry were to take a unified approach, there&#8217;s always another shop down the road. And there are bills to pay. </p>
<p>We recently held our ground on only one design concept. It was due to a really tight timeframe, though. The client went to someone else who agreed to do multiple concepts and asked if we&#8217;d execute the winner. We declined. He probably won&#8217;t make his deadline, which we would have guaranteed. It was more important to him, though, to have 3 concepts.  </p>
<p>Frankensteining sucks but it doesn&#8217;t have to be either or. A few concepts can be created <span class="caps">AND</span> the client can be educated. Successful outcome hinges upon the relationship and its footing moreso than process.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
