<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Talance Friendly Web Tools Blog &#187; Web strategy</title>
	<atom:link href="http://talance.com/blog/tag/web-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://talance.com/blog</link>
	<description>Advice, tips and tricks that help non-profits and small businesses have a stronger web presence</description>
	<lastBuildDate>Wed, 01 Sep 2010 16:57:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Recipe for Disaster: Too Many Website Cooks</title>
		<link>http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/</link>
		<comments>http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/#comments</comments>
		<pubDate>Thu, 20 Aug 2009 14:56:26 +0000</pubDate>
		<dc:creator>Talance</dc:creator>
				<category><![CDATA[design]]></category>
		<category><![CDATA[marketing]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[Web strategy]]></category>

		<guid isPermaLink="false">http://talance.com/blog/?p=613</guid>
		<description><![CDATA[
[Photo credit: Spaghetti and Meatballs (explore) by jshj, on Flickr]
Inclusiveness is always nice to have in any project, Web-related or otherwise. Give everybody a voice, and everybody’s happy, right? 
Wrong. 
In fact, having too many voices feeding into your website can create chaos for your users. The problem is that everybody has their own ideas [...]


You may also enjoy the following related articles:<ol><li><a href='http://talance.com/blog/2009/06/25/assembling-a-web-dream-team/' rel='bookmark' title='Permanent Link: Assembling a Web Dream Team'>Assembling a Web Dream Team</a></li><li><a href='http://talance.com/blog/2008/02/14/importance-of-needs-assessment/' rel='bookmark' title='Permanent Link: Importance of Needs Assessment'>Importance of Needs Assessment</a></li><li><a href='http://talance.com/blog/2009/08/17/how-to-write-really-helpful-web-development-rfps/' rel='bookmark' title='Permanent Link: How To Write Really Helpful Web Development RFPs'>How To Write Really Helpful Web Development RFPs</a></li></ol>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flickr.com/photos/jshj/824608884/" title="Spaghetti and Meatballs (explore) by jshj, on Flickr" onclick="urchinTracker('/outgoing/www.flickr.com/photos/jshj/824608884/?referer=');"><img src="http://farm2.static.flickr.com/1243/824608884_c02e6978bd.jpg" width="500" height="375" alt="Spaghetti and Meatballs (explore)" /></a></p>
<h6>[Photo credit: <a href="http://www.flickr.com/photos/jshj/824608884/" title="Spaghetti and Meatballs (explore) by jshj, on Flickr" onclick="urchinTracker('/outgoing/www.flickr.com/photos/jshj/824608884/?referer=');">Spaghetti and Meatballs (explore) by jshj</a>, on Flickr]</h6>
<p>Inclusiveness is always nice to have in any project, Web-related or otherwise. Give everybody a voice, and everybody’s happy, right? </p>
<p>Wrong. </p>
<p>In fact, having too many voices feeding into your website can create chaos for your users. The problem is that everybody has their own ideas about what belongs on a website, and those ideas might compete with one another. Plus, there’s only so much room on a homepage. You can’t cram everything on.</p>
<p>Add to this the fact that some of those people jockeying for their ideas to appear on your website know absolutely nothing about creating a manageable experience for Web visitors, and you’ve got one snarled, political plate of website spaghetti.</p>
<p>If you’re at a non-profit, there’s a good chance a little light bulb is going on over your head right now. You’ve been there. Too many people trying to take control of the site. Sadly, this is a problem non-profits frequently have, since many organizations are managed by committee. That might (or might not) make sense for day-to-day operations, but it never works with websites.</p>
<p>Nip this problem in the bud. Take these steps to make sure your Web project starts off with a clear vision and a clean outcome.</p>
<h3>Include everybody &#8211; at the start.</h3>
<p>Our solution is to send out a “needs assessment” at the very beginning of a project. This survey, distributed to a whole bunch of people, gives everybody a chance to say what they think is important to have on the website and makes everyone feel included.</p>
<h3>Form a small committee.</h3>
<p>Hand those surveys over to the core website team to scan for insights, ideas and important issues. And, of course, to sort out the muck. But importantly, this body is <em>small</em>, and has only one head.</p>
<h3>Appoint a strategist.</h3>
<p>It’s helpful that the leader of that team be uniformly concerned with the experience your website visitors have, the marketing and business message of your organization and have some idea of the way technology works. If this isn’t possible, at least choose a person humble enough to take direction from a hired Web strategy consultant. That&#8217;s money well spent.</p>
	<p></p>
	<hr noshade style="margin:0;height:1px" />
	<small><p>&copy; Talance for <a href="http://talance.com/blog">Talance Friendly Web Tools Blog</a>, 2009. |
	<a href="http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/">Permalink</a> |
	<a href="http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/#comments">No comment</a> |
	Add to
	<a href="http://del.icio.us/post?url=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/&amp;title=Recipe for Disaster: Too Many Website Cooks" onclick="urchinTracker('/outgoing/del.icio.us/post?url=http_//talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/_amp_title=Recipe_for_Disaster_Too_Many_Website_Cooks&referer=');"><img src="http://talance.com/blog/images/delicious.png" border="0"> del.icio.us</a>
	<a href="http://www.digg.com/submit?phase=2&url=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/&amp;title=Recipe for Disaster: Too Many Website Cooks" onclick="urchinTracker('/outgoing/www.digg.com/submit?phase=2_url=http_//talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/_amp_title=Recipe_for_Disaster_Too_Many_Website_Cooks&referer=');"><img src="http://talance.com/blog/images/digg.png" border="0"> digg</a> 
	<a href="http://reddit.com/submit?url=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/&amp;title=Recipe for Disaster: Too Many Website Cooks" onclick="urchinTracker('/outgoing/reddit.com/submit?url=http_//talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/_amp_title=Recipe_for_Disaster_Too_Many_Website_Cooks&referer=');"><img src="http://talance.com/blog/images/reddit.png" border="0"> reddit</a> 
	<a href="mailto:?subject=Recipe for Disaster: Too Many Website Cooks&body=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/"><img src="http://talance.com/blog/images/email_link.png" border="0"> email</a>
	<a href="http://www.facebook.com/sharer.php?u=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/&amp;t=Recipe for Disaster: Too Many Website Cooks" onclick="urchinTracker('/outgoing/www.facebook.com/sharer.php?u=http_//talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/_amp_t=Recipe_for_Disaster_Too_Many_Website_Cooks&referer=');"><img src="http://talance.com/blog/images/facebook.png" border="0"> facebook</a><br/>
	
	Who's linking ?
	<a href="http://google.com/blogsearch?q=http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/" title="Search on Google Blog Search" onclick="urchinTracker('/outgoing/google.com/blogsearch?q=http_//talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/&referer=');"><img src="http://talance.com/blog/images/googlebookmark.png" border="0">Google</a><br/>
	Want more on these topics ? Browse the archive of posts filed under <a href="http://talance.com/blog/category/design/" title="View all posts in design" rel="category tag">design</a>,  <a href="http://talance.com/blog/category/marketing/" title="View all posts in marketing" rel="category tag">marketing</a>.</small></p>

<p>You may also enjoy the following related articles:<ol><li><a href='http://talance.com/blog/2009/06/25/assembling-a-web-dream-team/' rel='bookmark' title='Permanent Link: Assembling a Web Dream Team'>Assembling a Web Dream Team</a></li><li><a href='http://talance.com/blog/2008/02/14/importance-of-needs-assessment/' rel='bookmark' title='Permanent Link: Importance of Needs Assessment'>Importance of Needs Assessment</a></li><li><a href='http://talance.com/blog/2009/08/17/how-to-write-really-helpful-web-development-rfps/' rel='bookmark' title='Permanent Link: How To Write Really Helpful Web Development RFPs'>How To Write Really Helpful Web Development RFPs</a></li></ol></p>]]></content:encoded>
			<wfw:commentRss>http://talance.com/blog/2009/08/20/recipe-for-disaster-too-many-website-cooks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
