<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.6" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: What not to do when building your website</title>
	<link>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/</link>
	<description>Simple. Measurable. Powerful.</description>
	<pubDate>Tue, 07 Feb 2012 18:08:01 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.6</generator>

	<item>
		<title>by: Jay</title>
		<link>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-15</link>
		<pubDate>Wed, 04 Apr 2007 20:21:09 +0000</pubDate>
		<guid>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-15</guid>
					<description>"That’s not to say I won’t make recommendations or tell them what I think they should do or that I’m just a monkey, it’s that it’s ultimately up to the client."

That was my main point, I wasn't saying I just roll over and do 'whatever', just that it's important to do what the client wants. And honestly, it's often much harder on a design than a technical level to justify why something may be a bad idea.</description>
		<content:encoded><![CDATA[<p>&#8220;That’s not to say I won’t make recommendations or tell them what I think they should do or that I’m just a monkey, it’s that it’s ultimately up to the client.&#8221;</p>
<p>That was my main point, I wasn&#8217;t saying I just roll over and do &#8216;whatever&#8217;, just that it&#8217;s important to do what the client wants. And honestly, it&#8217;s often much harder on a design than a technical level to justify why something may be a bad idea.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jason</title>
		<link>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-14</link>
		<pubDate>Wed, 04 Apr 2007 20:14:45 +0000</pubDate>
		<guid>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-14</guid>
					<description>@Jay: It goes both ways. Sure, the client signs the check, but you're the professional. You have a responsibility to protect them from obvious errors deviant to their cause. If its to make money or deliver an effective message, the majority of the items in Josiah's list are not just helpful, but serious concerns.

Now, if you can't seem to counter the "I want a fancy flash intro with music and bells and whistles" request from a client with an effective argument -- you need to beef up your reasoning. Disagreeing with them cordially in these situations should work out better for them in the end.</description>
		<content:encoded><![CDATA[<p>@Jay: It goes both ways. Sure, the client signs the check, but you&#8217;re the professional. You have a responsibility to protect them from obvious errors deviant to their cause. If its to make money or deliver an effective message, the majority of the items in Josiah&#8217;s list are not just helpful, but serious concerns.</p>
<p>Now, if you can&#8217;t seem to counter the &#8220;I want a fancy flash intro with music and bells and whistles&#8221; request from a client with an effective argument &#8212; you need to beef up your reasoning. Disagreeing with them cordially in these situations should work out better for them in the end.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Gene</title>
		<link>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-13</link>
		<pubDate>Wed, 04 Apr 2007 03:46:18 +0000</pubDate>
		<guid>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-13</guid>
					<description>Yeah, Yeah, but you've really got to fight hard against this kind of stuff, even if your client begs and pleads for it.  If they want their website to have any realized business impact (like make money) making these mistakes can hurt the bottom line...</description>
		<content:encoded><![CDATA[<p>Yeah, Yeah, but you&#8217;ve really got to fight hard against this kind of stuff, even if your client begs and pleads for it.  If they want their website to have any realized business impact (like make money) making these mistakes can hurt the bottom line&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jay</title>
		<link>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-11</link>
		<pubDate>Tue, 03 Apr 2007 20:03:06 +0000</pubDate>
		<guid>http://blog.period-three.com/2007/04/02/what-not-to-do-when-building-your-website/#comment-11</guid>
					<description>I'm going to play contrarian here, cause, well, that's what I do. While these are valid points and I agree in principle to most of them, it's important to remember not to bite the hand that feeds. I may have a personal dislike or even solid reasons for not doing certain things, but it's not my website I'm building, 99% of the time at least. If someone wants something, it's my job to give it to them. That's not to say I won't make recommendations or tell them what I think they should do or that I'm just a monkey, it's that it's ultimately up to the client. So it's easy to get snide and say 'Fire your web designer!' but who does that help? Making your client happy should be the main goal.</description>
		<content:encoded><![CDATA[<p>I&#8217;m going to play contrarian here, cause, well, that&#8217;s what I do. While these are valid points and I agree in principle to most of them, it&#8217;s important to remember not to bite the hand that feeds. I may have a personal dislike or even solid reasons for not doing certain things, but it&#8217;s not my website I&#8217;m building, 99% of the time at least. If someone wants something, it&#8217;s my job to give it to them. That&#8217;s not to say I won&#8217;t make recommendations or tell them what I think they should do or that I&#8217;m just a monkey, it&#8217;s that it&#8217;s ultimately up to the client. So it&#8217;s easy to get snide and say &#8216;Fire your web designer!&#8217; but who does that help? Making your client happy should be the main goal.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

