<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Improving Your Process: Maintaining Product Quality</title>
	<atom:link href="http://mondaybynoon.com/2008/04/14/improving-your-process-maintaining-product-quality/feed/" rel="self" type="application/rss+xml" />
	<link>http://mondaybynoon.com/2008/04/14/improving-your-process-maintaining-product-quality/</link>
	<description>A resource for Web designers and developers to read about and discuss their craft.</description>
	<lastBuildDate>Wed, 28 Jul 2010 19:29:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Nathan Smith</title>
		<link>http://mondaybynoon.com/2008/04/14/improving-your-process-maintaining-product-quality/#comment-1705</link>
		<dc:creator>Nathan Smith</dc:creator>
		<pubDate>Tue, 15 Apr 2008 19:51:09 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/?p=137#comment-1705</guid>
		<description>Jonathan: Well spoken, sir. I&#039;ve seen the monkey-see, monkey-do problem far too often, especially with churches and ministries. For instance, with COR.org, since it&#039;s the largest in its denomination, many smaller churches just ripped off their ideas (and graphics) whole-sale. But, such is life, I suppose. We just have to keep fighting the good fight, advocating quality vs. a quick-fix (which is often quite broken).</description>
		<content:encoded><![CDATA[<p>Jonathan: Well spoken, sir. I&#8217;ve seen the monkey-see, monkey-do problem far too often, especially with churches and ministries. For instance, with COR.org, since it&#8217;s the largest in its denomination, many smaller churches just ripped off their ideas (and graphics) whole-sale. But, such is life, I suppose. We just have to keep fighting the good fight, advocating quality vs. a quick-fix (which is often quite broken).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Christopher</title>
		<link>http://mondaybynoon.com/2008/04/14/improving-your-process-maintaining-product-quality/#comment-1706</link>
		<dc:creator>Jonathan Christopher</dc:creator>
		<pubDate>Mon, 14 Apr 2008 19:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/?p=137#comment-1706</guid>
		<description>@Nate Klaiber: Thanks very much for your thoughtful response. Convincing yourself that a successful competitor is doing something wrong is no easy task. Try to convince a client of that is even more tough. There are definitely times where you&#039;re literally forced to do something, and in all honestly I believe it&#039;s unavoidable when you&#039;re being paid to build websites. At the end of the day, you can&#039;t outright refuse to do things and expect to retain clients. Much of the time, however, clients are more than willing to listen to your suggestions for alternatives, as well as your explanation of the fault(s) behind their idea. You bringing up a situation in which the problem is completely internal is one which escaped me while writing this piece. When the &#039;orders&#039; are coming from higher up the ladder, there really isn&#039;t much you can do other than bite the bullet and implement. In a more hostile job scenario there&#039;s always a threat of repercussions as a result of voicing your opinion when marketing is trying to do their part. Thanks again for providing your experience!</description>
		<content:encoded><![CDATA[<p>@Nate Klaiber: Thanks very much for your thoughtful response. Convincing yourself that a successful competitor is doing something wrong is no easy task. Try to convince a client of that is even more tough. There are definitely times where you&#8217;re literally forced to do something, and in all honestly I believe it&#8217;s unavoidable when you&#8217;re being paid to build websites. At the end of the day, you can&#8217;t outright refuse to do things and expect to retain clients. Much of the time, however, clients are more than willing to listen to your suggestions for alternatives, as well as your explanation of the fault(s) behind their idea. You bringing up a situation in which the problem is completely internal is one which escaped me while writing this piece. When the &#8216;orders&#8217; are coming from higher up the ladder, there really isn&#8217;t much you can do other than bite the bullet and implement. In a more hostile job scenario there&#8217;s always a threat of repercussions as a result of voicing your opinion when marketing is trying to do their part. Thanks again for providing your experience!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Klaiber</title>
		<link>http://mondaybynoon.com/2008/04/14/improving-your-process-maintaining-product-quality/#comment-1707</link>
		<dc:creator>Nate Klaiber</dc:creator>
		<pubDate>Mon, 14 Apr 2008 15:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://mondaybynoon.com/?p=137#comment-1707</guid>
		<description>&quot;Just because a (possibly successful) competitor has done one thing, it doesn’t mean it was a good choice.&quot;

That is one of the biggest things I have had to re-inforce in the past. Just because a competitor is doing something, doesn&#039;t mean it is a de-facto standard (in some cases it could be just plain stupid).

I think one of our biggest challenges is what you stated at the end:

&quot;We work in an industry saturated with establishments trying to make a quick buck anywhere they can, which degrades our surface value. &quot;

Agencies like this are all around us, and will say &#039;yes&#039; to anything - without really knowing how to make things a cohesive whole.

I have had to succumb to some stupid things in the past, but that was mostly because I was in house and it entailed requests from CEO/Marketing - even though I may have battled.

It was harder when I worked in house, as the CEO would always say &#039;our competitor site has XYZ, why don&#039;t we?&#039; - when I knew full well it wouldn&#039;t fit our business model and goals of our website. However, he was the CEO - and as such thought he had all the right answers. This made it tough on my position as he didn&#039;t respect my opinion (backed by research) - and just assumed I should do what he said. It was poor leadership.</description>
		<content:encoded><![CDATA[<p>&#8220;Just because a (possibly successful) competitor has done one thing, it doesn’t mean it was a good choice.&#8221;</p>
<p>That is one of the biggest things I have had to re-inforce in the past. Just because a competitor is doing something, doesn&#8217;t mean it is a de-facto standard (in some cases it could be just plain stupid).</p>
<p>I think one of our biggest challenges is what you stated at the end:</p>
<p>&#8220;We work in an industry saturated with establishments trying to make a quick buck anywhere they can, which degrades our surface value. &#8221;</p>
<p>Agencies like this are all around us, and will say &#8216;yes&#8217; to anything &#8211; without really knowing how to make things a cohesive whole.</p>
<p>I have had to succumb to some stupid things in the past, but that was mostly because I was in house and it entailed requests from CEO/Marketing &#8211; even though I may have battled.</p>
<p>It was harder when I worked in house, as the CEO would always say &#8216;our competitor site has XYZ, why don&#8217;t we?&#8217; &#8211; when I knew full well it wouldn&#8217;t fit our business model and goals of our website. However, he was the CEO &#8211; and as such thought he had all the right answers. This made it tough on my position as he didn&#8217;t respect my opinion (backed by research) &#8211; and just assumed I should do what he said. It was poor leadership.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using xcache (user agent is rejected)
Database Caching using xcache

Served from: mondaybynoon.com @ 2010-07-30 22:14:09 -->