<?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: Web Development by Committee?</title>
	<atom:link href="http://collegewebguy.com/2007/10/16/web-development-by-committee/feed/" rel="self" type="application/rss+xml" />
	<link>http://collegewebguy.com/2007/10/16/web-development-by-committee/</link>
	<description>He’s employed at a university. He calls himself a web designer. These are his brain droppings.</description>
	<lastBuildDate>Wed, 25 Apr 2012 13:39:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Art for the Conference Room</title>
		<link>http://collegewebguy.com/2007/10/16/web-development-by-committee/comment-page-1/#comment-879</link>
		<dc:creator>Art for the Conference Room</dc:creator>
		<pubDate>Fri, 17 Oct 2008 14:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://collegewebguy.com/2007/10/16/web-development-by-committee/#comment-879</guid>
		<description>[...] Web Development by Committee? [...]</description>
		<content:encoded><![CDATA[<p>[...] Web Development by Committee? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guy Heckman</title>
		<link>http://collegewebguy.com/2007/10/16/web-development-by-committee/comment-page-1/#comment-64</link>
		<dc:creator>Guy Heckman</dc:creator>
		<pubDate>Wed, 28 Nov 2007 11:35:13 +0000</pubDate>
		<guid isPermaLink="false">http://collegewebguy.com/2007/10/16/web-development-by-committee/#comment-64</guid>
		<description>Very well argued.

Design by committee in Higher Ed can work, provided everyone knows their role on that committee. Two scenarios lifted from the real world.

I am lucky to work at a large College in a Big 10 school. Within the College, we are fortunate enough to have a centralized IT group. Everyone knows their role in the bigger picture of the mission of the College. When design decisions are being made I know that our Multimedia section knows what is best visually, and that my job is to evaluate how well that vision will mesh with usability, standards, and SEO. Egos, while still a factor, are much less of an issue due to this strict linearization of roles and responsibilities in the design process. Visual creativity is not sacrificed nor is technical creativity - indeed quite the opposite as we are able to feed off each others ideas and take different approaches than we would have if left on our own. This illustrates Meranda&#039;s committee of &quot;qualified professionals&quot; theory.

A counter-point was recently adopted by another College at our University. When my peer announced that their Marketing Department had decided upon design by committee - a commitee that was not only going to consist of the IT and Marketing groups but also of faculty and staff. Now it should be said that this is an IT-oriented College, so the faculty as a whole is more web design savy than say Liberal Arts. There were no clear roles and responsibilities laid out for the individual committee members. Knowledgeable committee members is a mixed blessing, they understand the web but they also each bring their own agendas and ideology to the table and without a clear understanding of what each member is supposed to bring to that table the project flounders. It has been close to a year and NO progress has been made. This illustrates the &quot;web design by committee is bad&quot; theory.

I will go on to say that I personally am in agreement to the blanket statement that design by committee is bad when you apply it to the visual design aspect. One man&#039;s Van Gosh is another&#039;s refrigerator art. To attempt the visual/graphical design within a committee will totally squash creativity and leave you with a bland final product.

Thoughts?</description>
		<content:encoded><![CDATA[<p>Very well argued.</p>
<p>Design by committee in Higher Ed can work, provided everyone knows their role on that committee. Two scenarios lifted from the real world.</p>
<p>I am lucky to work at a large College in a Big 10 school. Within the College, we are fortunate enough to have a centralized IT group. Everyone knows their role in the bigger picture of the mission of the College. When design decisions are being made I know that our Multimedia section knows what is best visually, and that my job is to evaluate how well that vision will mesh with usability, standards, and SEO. Egos, while still a factor, are much less of an issue due to this strict linearization of roles and responsibilities in the design process. Visual creativity is not sacrificed nor is technical creativity &#8211; indeed quite the opposite as we are able to feed off each others ideas and take different approaches than we would have if left on our own. This illustrates Meranda&#8217;s committee of &#8220;qualified professionals&#8221; theory.</p>
<p>A counter-point was recently adopted by another College at our University. When my peer announced that their Marketing Department had decided upon design by committee &#8211; a commitee that was not only going to consist of the IT and Marketing groups but also of faculty and staff. Now it should be said that this is an IT-oriented College, so the faculty as a whole is more web design savy than say Liberal Arts. There were no clear roles and responsibilities laid out for the individual committee members. Knowledgeable committee members is a mixed blessing, they understand the web but they also each bring their own agendas and ideology to the table and without a clear understanding of what each member is supposed to bring to that table the project flounders. It has been close to a year and NO progress has been made. This illustrates the &#8220;web design by committee is bad&#8221; theory.</p>
<p>I will go on to say that I personally am in agreement to the blanket statement that design by committee is bad when you apply it to the visual design aspect. One man&#8217;s Van Gosh is another&#8217;s refrigerator art. To attempt the visual/graphical design within a committee will totally squash creativity and leave you with a bland final product.</p>
<p>Thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth Meranda</title>
		<link>http://collegewebguy.com/2007/10/16/web-development-by-committee/comment-page-1/#comment-31</link>
		<dc:creator>Seth Meranda</dc:creator>
		<pubDate>Tue, 16 Oct 2007 21:12:17 +0000</pubDate>
		<guid isPermaLink="false">http://collegewebguy.com/2007/10/16/web-development-by-committee/#comment-31</guid>
		<description>Great post!

It think the emphasis needs to be made on the blanket statement, and you did that much better than I. Each situation is different; however after working with the committee I can&#039;t imagine taking on such a project in a University setting alone again. But the distinction is that I worked with &quot;qualified professionals.&quot; It isn&#039;t a group of dreamers; it&#039;s a group of developers that know the latest technologies, design principles, trends and outcomes. If you can create this committee you will be in a better place.</description>
		<content:encoded><![CDATA[<p>Great post!</p>
<p>It think the emphasis needs to be made on the blanket statement, and you did that much better than I. Each situation is different; however after working with the committee I can&#8217;t imagine taking on such a project in a University setting alone again. But the distinction is that I worked with &#8220;qualified professionals.&#8221; It isn&#8217;t a group of dreamers; it&#8217;s a group of developers that know the latest technologies, design principles, trends and outcomes. If you can create this committee you will be in a better place.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

