<?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>Pleasanton Web Design &#187; website planning</title>
	<atom:link href="http://pleasantonwebdesignblog.com/category/website-planning/feed" rel="self" type="application/rss+xml" />
	<link>http://pleasantonwebdesignblog.com</link>
	<description>Information on Web design, technology, and culture from my vantage point here in Pleasanton, California.</description>
	<lastBuildDate>Fri, 04 May 2012 18:22:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>What &#8220;Looks Good&#8221; is Subjective</title>
		<link>http://pleasantonwebdesignblog.com/2012/02/what-looks-good-is-subjective.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=what-looks-good-is-subjective</link>
		<comments>http://pleasantonwebdesignblog.com/2012/02/what-looks-good-is-subjective.html#comments</comments>
		<pubDate>Fri, 03 Feb 2012 04:22:48 +0000</pubDate>
		<dc:creator>Troy Philis</dc:creator>
				<category><![CDATA[usability]]></category>
		<category><![CDATA[user-centered web design]]></category>
		<category><![CDATA[user-centered website design]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[website planning]]></category>
		<category><![CDATA[Website Redesign]]></category>

		<guid isPermaLink="false">http://pleasantonwebdesignblog.com/?p=997</guid>
		<description><![CDATA[We are all aware of the sayings &#8220;Beauty is in the eye of the beholder,&#8221; &#8220;Different strokes for different folks&#8221; and &#8220;There is no accounting for taste.&#8221; Unfortunately, although these sayings are universal, the associated insights don&#8217;t seem to be. This is nowhere more apparent when designing something for someone else. What looks &#8220;professional&#8221; to [...]]]></description>
			<content:encoded><![CDATA[<div class="none"><div class="g-plusone" data-href="http://pleasantonwebdesignblog.com/2012/02/what-looks-good-is-subjective.html" size="small" count="true"></div></div><p><img class="alignright size-medium wp-image-998" title="Tacky Lady" src="http://pleasantonwebdesignblog.com/wp-content/uploads/2012/02/tacky_lady-332x500.jpg" alt="Tacky Lady" width="253" height="380" />We are all aware of the sayings &#8220;Beauty is in the eye of the beholder,&#8221; &#8220;Different strokes for different folks&#8221; and &#8220;There is no accounting for taste.&#8221; Unfortunately, although these sayings are universal, the associated insights don&#8217;t seem to be. This is nowhere more apparent when designing something for someone else.<strong> What looks &#8220;professional&#8221; to one person, can easily be boring, ugly, or even unprofessional to a different person.</strong></p>
<p>As a web designer you learn that almost all descriptive terms are useless in completing the nuts-and-bolts task of creating a design the pleases the client. You need them to show you what they like, and you need to show them how you interpret that, and there the actual dialog begins.</p>
<p>Over and above pleasing the client, the designer&#8217;s task is to make the client realize that their <strong>taste is not universal</strong>, and their target audience may not respond positively to what they think looks good, or cool, or whatever. More important than pleasing themselves  (or their partners, employees, spouse,  friends or mother) is <strong>creating a design that communicates the desired message to the target audience</strong>.</p>
<p>What can be even more of a challenge is the tendency for inexperienced website buyers to be fixated on look-and-feel, or the visual design, to the neglect and expense of useability. The desire to speed through, or skip the boring task of information design and content creation to get to the visual mockups is extremely common and uniformly disastrous. Then, when the website flops, of course it is the visual design that is the problem and needs to be fixed.</p>
<p>
<!-- Begin Google Adsense code -->
<script type="text/javascript"><!--
google_ad_client = "pub-8315023803230274";
/* 468x60, created 1/7/09 */
google_ad_slot = "2170958206";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
<!-- End Google Adsense code -->
</p>
<p>As a web designer, the best thing you can do to save the client from themselves in such cases is to try to explain with examples, and if that doesn&#8217;t work, stick to your process regardless of the pressure to do otherwise.</p>
]]></content:encoded>
			<wfw:commentRss>http://pleasantonwebdesignblog.com/2012/02/what-looks-good-is-subjective.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to Plan a Website</title>
		<link>http://pleasantonwebdesignblog.com/2007/01/how-to-plan-a-website.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-plan-a-website</link>
		<comments>http://pleasantonwebdesignblog.com/2007/01/how-to-plan-a-website.html#comments</comments>
		<pubDate>Wed, 24 Jan 2007 18:37:00 +0000</pubDate>
		<dc:creator>Troy Philis</dc:creator>
				<category><![CDATA[web design]]></category>
		<category><![CDATA[website design]]></category>
		<category><![CDATA[website planning]]></category>

		<guid isPermaLink="false">http://pleasantonwebdesign.tpdevspace.com/?p=106</guid>
		<description><![CDATA[Whether you are a Web designer, or the buyer of Web designservices, the planning phase of the Web design process isthe most important phase. Planning requires a significantamount of effort before there is a visable product, so itis sometimes a hard-sell to business people, especially thosewho are used to &#8220;flying by the seat of their [...]]]></description>
			<content:encoded><![CDATA[<div class="none"><div class="g-plusone" data-href="http://pleasantonwebdesignblog.com/2007/01/how-to-plan-a-website.html" size="small" count="true"></div></div><p>Whether you are a Web designer, or the buyer of Web design<br />services, the planning phase of the Web design process is<br />the most important phase. Planning requires a significant<br />amount of effort before there is a visable product, so it<br />is sometimes a hard-sell to business people, especially those<br />who are used to &#8220;flying by the seat of their pants.&#8221;<br />I often find, however, that once involved in the process,<br />the client gains valuable insights into their business, their<br />market, their clients, and their competitors. Taking time<br />to really plan a Website project, which requires stepping<br />back and thinking, in a systematic way, about how they are<br />approaching their business, gives the Website buyer an unexpected<br />added value, especially if they are in start-up mode.</p>
<p>
<p>The first step in planning a Website is define the project.<br />You want to make sure that you, as Web designer, and the client<br />are on the same page, and remain on the same page throughout<br />the project. The following are questions that need answers:</p>
<ul>
<li><em style="font-weight: bold;">Project Scope</em><span style="font-weight: bold;"> </span>- What will be included in the<br />project and what will not be included?</p>
</li>
<li><em style="font-weight: bold;">Audience</em> &#8211; Who are the main types of people who<br />will be visiting the Website, what are their characteristics,<br />and why will they be visiting the Website. What will the<br />want to do?
</li>
<li><em style="font-weight: bold;">Competition</em> &#8211; Who are the competitors and what<br />do their Websites do and look like?
</li>
<li><em style="font-weight: bold;">Niche</em> &#8211; Specifically what market niche does the<br />business occupy or want to occupy?</li>
<p>
<li><em style="font-weight: bold;">Positioning</em> &#8211; What is the company&#8217;s positioning<br />strategy for their niche? Why buy their product or service<br />over the competition?</p>
</li>
<li><em style="font-weight: bold;">Overall goals</em><span style="font-weight: bold;"> </span>- What does the business want<br />to acheive through the Website? Sell products? Provide online<br />resources? Present a professional image?
</li>
<li><em style="font-weight: bold;">Business processes</em><span style="font-weight: bold;"> </span>- How will the Website fit<br />into the company&#8217;s business processes? How will it integrate<br />into those off-line processes?
</li>
<li><em style="font-weight: bold;">Marketing and branding strategies</em> &#8211; What existing<br />marketing or branding stategies can be leveraged for use<br />on the Website?</li>
<p>
<li><em style="font-weight: bold;">Workflows</em><span style="font-weight: bold;"> </span>- What processes will need to be completed<br />on the Website, described in a step by step fashion?</p>
</li>
<li><em style="font-weight: bold;">Goals for Web site</em> &#8211; What specific, numerically<br />defined goals exist for the Website. What are the expectations?
</li>
<li><em style="font-weight: bold;">Keywords/Search Terms</em> &#8211; What words will people<br />searching for products/services/information use to find<br />the client&#8217;s Website, using the major search engines?
</li>
<li><em><span style="font-weight: bold;">Message</span> </em>- What message should the Website communicate<br />to the user, either explicitly or implicitly?
</li>
<li><em style="font-weight: bold;">Perception</em> &#8211; How should the user percieve the<br />business, based on visiting the Website?
</li>
<li><em style="font-weight: bold;">Action</em><span style="font-weight: bold;"> </span>- What action or actions should the visitor<br />take while on the Website?
</li>
<li><em style="font-weight: bold;">Technology</em> &#8211; What technology should be used in<br />designing and building the Website?
</li>
<li><em style="font-weight: bold;">Marketing</em> &#8211; How will the Website be marketed?<br />How will the business get visitors there?
</li>
<li><em><span style="font-weight: bold;">Administrativ</span>e</em> &#8211; How will the Website be administered<br />and maintained after it is launched?
</li>
<li><em style="font-weight: bold;">Schedule</em> &#8211; When does the Website need to be complete?<br />When will decision makers be available or unavailable to<br />approve deliverables throught the process?
</li>
<li><em style="font-weight: bold;">Budget</em><span style="font-weight: bold;"> </span>- What is the budget for the project?<br />What is the ongoing budget for maintenance and updates?<br />What is the budget for promotion?</li>
</ul>
<p>The answers to these questions should be put into a &#8220;creative<br />brief&#8221; or &#8220;project definition&#8221; document that<br />will be used as a touchstone throughout the design process.<br />The information in the planning documents should be as detailed<br />as possible, and based on as much empiricle evidence as possible.<br />Having someone fill the a questionnaire off the top of their<br />head will be useful, but to the extent it rely&#8217;s on guesses<br />or false assumptions, it will provide flaws in the planning<br />and therefore flaws in the finished Website.</p>
<p><a href="http://www.tpdesigns.net/services/web_design_process.htm">Find out more<br />about TP Designs&#8217; Web design process.</a></p>
<p><a href="http://www.tpdesigns.net/services/web_design_services.htm">Find out more<br />about TP Designs&#8217; Web design services.</a></p>
<p><a href="http://www.tpdesigns.net/rfq.htm">See TP Designs&#8217; Request for Quote (RFQ)<br />Form</a></p>
<div class="tag_list">Tags: <span class="tags"><a href="http://technorati.com/tag/web+design" rel="tag">web design</a>, <a href="http://technorati.com/tag/website+design" rel="tag">website design</a>, <a href="http://technorati.com/tag/website+planning" rel="tag">website planning</a>, <a href="http://technorati.com/tag/how+to+plan+a+website" rel="tag">how to plan a website</a></span></div>
]]></content:encoded>
			<wfw:commentRss>http://pleasantonwebdesignblog.com/2007/01/how-to-plan-a-website.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

