<?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>Helen Marie: Design and Code &#187; Client Side</title>
	<atom:link href="http://blog.helen-marie.com/index.php/cat/client-side/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.helen-marie.com</link>
	<description>Strategy, design, technology, and how to be our client</description>
	<lastBuildDate>Mon, 27 Jul 2009 20:33:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Agility and the User Experience</title>
		<link>http://blog.helen-marie.com/index.php/2009/04/agility-and-the-user-experience/</link>
		<comments>http://blog.helen-marie.com/index.php/2009/04/agility-and-the-user-experience/#comments</comments>
		<pubDate>Wed, 15 Apr 2009 18:20:09 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[The Craft]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[informationarchitecture]]></category>
		<category><![CDATA[phases]]></category>
		<category><![CDATA[uxd]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=128</guid>
		<description><![CDATA[It&#8217;s easy to think of a web site in terms of the teams who participate in the project: content, design, information architecture, hardware, platform, application development.  But it&#8217;s the user who ties all the parts together: the user experience is the end-product of a web application.
This is why people freak out about user experience [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s easy to think of a web site in terms of the teams who participate in the project: content, design, information architecture, hardware, platform, application development.  But it&#8217;s the user who ties all the parts together: the user experience is the end-product of a web application.</p>
<p>This is why people freak out about user experience design, or UxD, these days.  We can define and justify and normalize everything we do during the course of a web project by referring to the user experience, and we can keep this experience in mind as a theoretical model to help us make decisions along the way.<span id="more-128"></span></p>
<p>But the user experience is only just that &#8212; a theoretical model &#8212; until you get <em>real users</em>.  This is why we can&#8217;t begin a project with all the answers.  The answers to many important questions are provided by the users.  But the users don&#8217;t come until we&#8217;ve actually designed and built something.</p>
<p>Oh, the Catch-22!</p>
<p>The way out, of course, is by agreeing to launch with something that&#8217;s in some important way unfinished.  Knowing that our users will provide us with feedback that will shape the future site &#8212; that we plan and build the site in phases, and that these phases are informed by an ongoing engagement with the user experience.</p>
<p>As an agency, you need to go to great lengths to get your clients to understand this.  They can&#8217;t provide a spec, like a blueprint for a shed, and get a quote and schedule based solely on the blueprint, and then expect the actual shed to look exactly like the blueprint.  This is what they&#8217;ll want, because it&#8217;s easier to plan, and easier to budget for, and just generally easier to think about.  But it doesn&#8217;t comport with reality, so you&#8217;ll have to make a strong case for agility throughout the process.</p>
<p>And as a client, you need to go to equally great lengths to factor this fluidity into your own plans.  Remember the great triangle of software development: one side is budget; the second side is functionality; and the third is schedule.  You can&#8217;t fix all of these sides, because you&#8217;ll end in horrendous failure (the great triangle of pain and disappointment).  If you must, try to fix two; but leave the third one agile.</p>
<p>Say you&#8217;ve got a project with some fairly well-defined requirements, and pegged to a particular real-world date.  You&#8217;ve got your functionality and schedule fixed.  This means you must remain agile with your budget.  In practical terms, you&#8217;ll need to provide the agency with a budget range that is acceptable, and trust them (<em>Trust them!</em> Seriously!) to keep their costs down.</p>
<p>(Side note: if you can&#8217;t trust your agency to keep their costs down, you should find another agency.  This shouldn&#8217;t be an antagonistic process, but one where both sides share common goals.)</p>
<p>A second example, one that we see very often at HM: Say you&#8217;re a not-for-profit institution that secured funding for a particular project proposal from a big foundation.  You may see all three sides of the triangle as fixed: you promised a set of functionality in your proposal.  You also received a fixed amount of funding, and have a delivery date as part of the funding timeline.</p>
<p>In truth, though, one side of the triangle has to be flexible in this situation.  Chances are the foundation won&#8217;t increase the budget, so one of the other sides needs to be subject to change.  This may require some advocacy on your part to get the flexibility you need from the funder, but the big selling point here is the main goal: a beautiful, functional, memorable web experience that users will visit again and again because it was <em>built around their needs</em>.  If you can&#8217;t get it all done in the budget and timeline provided, consider this a first phase.  Phases are good!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2009/04/agility-and-the-user-experience/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Build what you need, not what you want</title>
		<link>http://blog.helen-marie.com/index.php/2009/02/build-what-you-need/</link>
		<comments>http://blog.helen-marie.com/index.php/2009/02/build-what-you-need/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 21:17:18 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[contentmanagement]]></category>
		<category><![CDATA[technologicalpanic]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=72</guid>
		<description><![CDATA[I met a writer the other night who has spent months freelancing for a prominent national magazine.  The magazine had enjoyed a reasonably popular web audience, including a community of frequent posters to its bulletin board.  The community was mostly middle-aged, middle-American women who used the magazine&#8217;s online space to chat and bring up issues [...]]]></description>
			<content:encoded><![CDATA[<p>I met a writer the other night who has spent months freelancing for a prominent national magazine.  The magazine had enjoyed a reasonably popular web audience, including a community of frequent posters to its bulletin board.  The community was mostly middle-aged, middle-American women who used the magazine&#8217;s online space to chat and bring up issues that were loosely related to the magazine&#8217;s content.</p>
<p>It was an open question how best to take advantage of this community to benefit the magazine.  But instead of starting with obvious questions &#8212; Who are these users? What do they care about?  How can we increase their enthusiasm for our brand? &#8212; someone high up in the magazine&#8217;s interactive food chain had a classic <a href="http://blog.helen-marie.com/index.php/tag/technologicalpanic/">technological panic</a>.<span id="more-72"></span> The panic took this form, probably late at night:</p>
<p><em>What about social networks?  What about Facebook?  What about Twitter?  What about blogging?  Everyone&#8217;s doing it but us!  <strong>We need to catch up.</strong></em></p>
<p>So the magazine built a social network.  It probably hired an agency that affirmed the magazine&#8217;s fears of obsolescence and charged them an outsized fee to build every last microblog and Twitter integration, user profile, friend-manager, minifeed, video uploader, and widget that <a href="http://blog.helen-marie.com/index.php/2008/12/dangerous-phrases-wouldnt-it-be-cool-if/">they could imagine</a> in their darkest nightmares of media isolation.</p>
<p>The magazine launched their Spanking New Social Presence and, to their shock, lost all of the users who had made their old bulletin board such a lively place.</p>
<p>That&#8217;s how this writer I met, a young, urban, male Brooklynite, got his job: every day he logs in as five different women and maintains their ghost user profiles.  He simulates social activity on a social network that was conceived in panic, cost the magazine a good deal of increasingly scarce resources, alienated the community it was supposed to engage.</p>
<p>Instead of starting with open questions, this online initiative started in a panic.  And now they have a structure that requires them to lie through their teeth just to present a semblance of activity.</p>
<p>Don&#8217;t let this be you!  Start with the right questions about your situation, and be open to the answers that you&#8217;ll find.  For some organizations, blogging, Twitter, and a Facebook presence are just what the doctor ordered.  Those who are  lucky enough to have an existing online user base need to start with their users.  Users are the lifeblood of a participatory web.</p>
<p>And remember this: the structure you build brings with it a certain infrastructure, and that infrastructure must be maintained.  If you create employee blogs, you better make sure that your employees have something to say, and are trained to publish on a regular basis.  If you push your staff to sign up for Twitter, you need to make sure that they&#8217;re actively writing &#8212; and, I hope it doesn&#8217;t need to be said, that they <em>want</em> to write.  And if you let users create profiles and write blog entries, you need staff to review those profiles and posts on a regular basis.</p>
<p>An empty social network is just like bad standup comedy: nobody wants to be in the same room.  Make sure that your room, regardless of its size, makes your audience want to come back.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2009/02/build-what-you-need/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Web is Expensive</title>
		<link>http://blog.helen-marie.com/index.php/2009/01/the-web-is-expensive/</link>
		<comments>http://blog.helen-marie.com/index.php/2009/01/the-web-is-expensive/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 19:15:37 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[consulting]]></category>
		<category><![CDATA[specialization]]></category>
		<category><![CDATA[technologicalpanic]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=62</guid>
		<description><![CDATA[It&#8217;s easy to forget that we work in a new and strange industry.  We surround ourselves with ourselves, so we take the nature of our product for granted.  But for the majority of web users, we create virtual products &#8212; they take up no space; their size, complexity, and location are indeterminate; they appear and [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s easy to forget that we work in a new and strange industry.  We surround ourselves with ourselves, so we take the nature of our product for granted.  But for the majority of web users, we create virtual products &#8212; they take up no space; their size, complexity, and location are indeterminate; they appear and disappear from the screen in an instant.  So how to value their worth?</p>
<p><span id="more-62"></span></p>
<p>For many of our clients, the worth is apparent, either because of their past experience in this arena or their experience with similar creative services (advertising, brand strategy, business consulting, etc.).  It&#8217;s a relatively straightforward process to translate a strategy into a proposal and budget with clients like these.</p>
<p>For many other clients, though, even those with deep pockets, the web is a hard place to get a grip on.  This could be because <a title="Technological Panic: a continuing study" href="http://blog.helen-marie.com/index.php/tag/technologicalpanic/">technology scares them</a>.  They might equate their IT budget with the kind of work that we do, because of they perceive <a title="Maybe they Know A Guy." href="http://blog.helen-marie.com/index.php/2008/11/dangerous-phrases-i-know-a-guy/">a shared arena of activity</a>.  Or the web to them is <a title="That's wicked cool" href="http://blog.helen-marie.com/index.php/2008/12/dangerous-phrases-wouldnt-it-be-cool-if/">an infinite realm of untold, mind-boggling possibility</a>.  Or, maybe, they&#8217;ve stumbled through every creative project they&#8217;ve ever embarked on in the past, and expect that we operate in the same fashion.</p>
<p>There are myriad ways to get to a common vision of the value of the work that we do.  And keep in mind that we don&#8217;t mean only us; we want to arrive at a common vision of value for our industry, not just ourselves.  We may not be the firm for you, but you&#8217;ll have a much more successful search if you can better quantify the worth of your project.</p>
<p>So, the &#8220;we&#8221; and &#8220;us&#8221; below don&#8217;t refer just to us at Helen Marie; we&#8217;re presumptuously speaking for the industry.</p>
<p><strong>The bottom line</strong></p>
<p>An easy one. You, the client, need us to do something that you estimate will affect your bottom line by X dollars in the next year.  You want to come out ahead, so obviously our work can&#8217;t cost X dollars.  But it shouldn&#8217;t be surprising for it to cost, say, half of X.  Your payment to us is fixed, but the value to you increases beyond the next year.  Our fee, then, decreases over time in relationship to the change in your bottom line.  This is math that you can do in advance of your agency search, and that will help you square your available budget against what you&#8217;re asking an agency to produce.</p>
<p><strong>What it would really cost you</strong></p>
<p>This often comes into play with calculations against your IT budget, because you imagine that the IT team can do work similar to ours.  Our long experience working with (and in) IT departments is that this assumption is always, always wrong.  And your IT team will be happy to disabuse you of the notion that they can magically transmogrify into a group with decades of collective web experience who can give your project the attention and focus it deserves.</p>
<p>If you can&#8217;t square our cost against your IT team, then what other point of reference do you have?  You can look at the job listings for web designers, web developers, information architects, and interactive project managers, and piece together the cost of bringing them on salary for a year or more.</p>
<p><strong>Our experience</strong></p>
<p>If you think a project is expensive, try doing it twice.  Or three times.  This happens often.  As we&#8217;ve said elsewhere on this blog, we&#8217;re often approached to redesign the client&#8217;s current site.  And the current site is often some kind of minor tragedy of wasted time and money.</p>
<p>We don&#8217;t guarantee that we will design and build a product that will answer all your needs for the next ten years.  What we do offer is the experience to make intelligent choices, and the opportunity to educate you on the process and help you to make informed choices.</p>
<p><strong>Peace of mind</strong></p>
<p>There are few experiences more relieving than finding the perfect experts for your problem.  You can&#8217;t quantify the dollar worth of that feeling.  But you can imagine paying for it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2009/01/the-web-is-expensive/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dangerous Phrases: &#8220;Wouldn&#8217;t it be cool if&#8230;&#8221;</title>
		<link>http://blog.helen-marie.com/index.php/2008/12/dangerous-phrases-wouldnt-it-be-cool-if/</link>
		<comments>http://blog.helen-marie.com/index.php/2008/12/dangerous-phrases-wouldnt-it-be-cool-if/#comments</comments>
		<pubDate>Tue, 30 Dec 2008 18:48:31 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[Strategy]]></category>
		<category><![CDATA[dangerousphrases]]></category>
		<category><![CDATA[informationarchitecture]]></category>
		<category><![CDATA[phases]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=25</guid>
		<description><![CDATA[Now, we at Helen Marie think the web is very cool. That&#8217;s why we&#8217;re in this business.  We get excited on a daily basis about all manner of new design and interface ideas and technology.  (Personally, I discover a new way to love jQuery almost every day, and that&#8217;s exciting.)  It&#8217;s this constant fascination that [...]]]></description>
			<content:encoded><![CDATA[<p>Now, we at Helen Marie think the web is <em>very cool.</em> That&#8217;s why we&#8217;re in this business.  We get excited on a daily basis about all manner of new design and interface ideas and technology.  (Personally, I discover a new way to love <a href="http://jquery.com/">jQuery</a> almost every day, and that&#8217;s exciting.)  It&#8217;s this constant fascination that energizes each one of our projects, and that we hope to find reflected in our clients.</p>
<p>Part of our job is to focus this enthusiasm into disciplined decisions about how best to serve a particular client and a particular project.  We have a lot of healthy arguments that start with, &#8220;Wouldn&#8217;t it be cool if&#8230;?&#8221;  The question is often followed by, &#8220;I agree, but we shouldn&#8217;t do that in this case because&#8230;.&#8221;  Or, just as often: &#8220;That&#8217;s great &#8212; but let&#8217;s consider that for phase 2.&#8221;</p>
<p>We go through this in order to avoid three big pitfalls: building more than the client needs or can immediately use, rejecting new approaches or techniques because we&#8217;re unfamiliar, and committing to unreliable approaches or techniques because the coolness factor affects our judgment.  We wrestle with these issues so you don&#8217;t have to.</p>
<p><span id="more-25"></span></p>
<p>(There are a lot of interactive technologies that are the equivalent of a two-seat <a title="Nice" href="http://www.lotuscars.com/exige_s240.html">Lotus Exige</a>: extremely cool, but maybe not what you need.)</p>
<p>You may have done your own research before you even found us, however, and decided that your new site absolutely has to include X, or be built on Y.  We often meet with potential clients who say, &#8220;We want our new site to be built on [insert trendy platform or poorly-understood technology here].&#8221;  Why, we ask? &#8220;We&#8217;ve read about it, and it looks like the best new technology for us.&#8221;</p>
<p>This is an ideal point to ask us what we think of the idea, and whether we have other recommendations.  That&#8217;s the beginning of a great conversation that will help you to educate yourself about your options, learn something about us and our experience, and save money in the long-haul by making the right decisions when you have the most flexibility – i.e., before you start down any road.</p>
<p>You&#8217;ll be able to meet the overwhelming majority of your project&#8217;s critical strategic needs with proven, industry-standard design and interface practices.  Your agency, if they&#8217;re up to snuff, will have a toolbox of information design, user interface, and technology solutions that apply in some manner to almost everything that can come up.</p>
<p>Your first contact with an agency should be a great learning experience.  I know that I love talking to potential and new clients about the broad strokes of planning and building a web application.  I call it <em>Everything You Always Wanted To Know About The Web But Were Afraid To Ask</em>.  For you, the client, it&#8217;s free advice; for us, it&#8217;s a chance to show you how we think and work.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2008/12/dangerous-phrases-wouldnt-it-be-cool-if/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Buddy, You Need an Agent</title>
		<link>http://blog.helen-marie.com/index.php/2008/12/buddy-you-need-an-agent/</link>
		<comments>http://blog.helen-marie.com/index.php/2008/12/buddy-you-need-an-agent/#comments</comments>
		<pubDate>Wed, 03 Dec 2008 19:42:51 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[consulting]]></category>
		<category><![CDATA[creativebroker]]></category>
		<category><![CDATA[services]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=13</guid>
		<description><![CDATA[Let&#8217;s say you enter the real estate market as a first-time buyer.  The process at first seems to be a matter of identifying your budget and wish list (must: open kitchen; maybe: wood-fired brick oven), getting pre-qualified for a mortgage, looking at listings, pursuing your favorites, making an offer, etc.  As you start, though, you [...]]]></description>
			<content:encoded><![CDATA[<p>Let&#8217;s say you enter the real estate market as a first-time buyer.  The process at first seems to be a matter of identifying your budget and wish list (must: open kitchen; maybe: wood-fired brick oven), getting pre-qualified for a mortgage, looking at listings, pursuing your favorites, making an offer, etc.  As you start, though, you realize that with all this money at stake, so many variables in the process, and nobody interested in getting you the best deal, you could use an advocate on your side &#8212; a seasoned hand who can help guide you past serious mistakes, act as a sounding board to your evolving ideas, and help you optimize negotiations with the selling agent.</p>
<p>This is a broker.  The good ones are worth their weight in gold (especially the smaller good ones).  You can get them to clear an enormous amount of brush for you &#8212; weeding out the bad listings, giving you a sales history of any property on the market, speaking the secret language of brokers with the other side.  They save you time and ultimately money.</p>
<p>It occurred to us at Helen Marie, after many years of working with clients of all stripes and sizes, that this is desperately needed in the design and interactive industry: a kind of <strong>creative broker</strong>.  Clients often need to commit large amounts of funding, human capital, and time to a project with an outside agency. Ironically, while this is the stage where they most need expertise, they&#8217;re often unaware of, or resistant to, the option to bring in an outside specialist right from the beginning.  We want to change this.</p>
<p><span id="more-13"></span></p>
<p>The hardest stage is often defining their needs to the point where they can be reflected in a clear, informative &#8220;request for proposal&#8221; (RFP).  To get to this point, a business needs to poll its stakeholders, identify their frustrations with the current system (or lack of system), look at its long-term needs, identify a budget, enunciate its brand values, and actually write the thing &#8212; and then get it approved.  This can be a full-time job (or several!).</p>
<p>There&#8217;s a lot riding on one of these documents.  The clarity with which you communicate your needs will directly affect the quality of the proposals you get back.  We&#8217;ve turned down many potential clients in the past because of bad RFPs &#8212; the logic being, of course, that if you can&#8217;t succinctly tell us what you need and why, then we&#8217;ll have a hard time giving you what you need.</p>
<p>Once the RFP is written and approved, the would-be client needs to distribute their shiny new document to the right agencies.  The world of agencies is crowded with similar offerings and slick marketing.  If you&#8217;ve never done this before, how do you tell an established, successful firm from one that talks a good game?</p>
<p>For instance, here are two pieces of content that you&#8217;ll find on most agency web sites.  Neither will help you determine that agency&#8217;s worth to your business.</p>
<p><strong>Past Client List<br />
</strong></p>
<p>There are some major clients, blue-chip brands, who occasionally hire incompetent agencies.  Even if the resulting project is a disaster, the agency in question can still legimately list that client on its site.  The big clients never have time to double-check these claims, and you, the unseasoned evaluator, will not be able to vet the association yourself without a massive expenditure of time.</p>
<p><strong>Services List</strong></p>
<p>An agency&#8217;s services list can look like an impressive roster of every activity you ever thought you&#8217;d need: Logo design! Hosting! Search engine optimization! Content management systems! Information architecture! It might look like a wonderland.  Truth is, though, that each one of these services requires at least one seasoned, communicative, well-managed specialist on the other side in order to be of any worth to you. Too often, the services list is meant to be scanned as a laundry list, not vetted.  The agency knows that its site&#8217;s audience includes harried executive assistants, product managers, and not-for-profit executive directors who are desperately trying to find the right agency that fits all their needs.  The temptation is to provide an omnibus list of services so a potential client can glance at the list and think, &#8220;Oh, phew &#8212; they do everything we need.&#8221;</p>
<p>On the other hand, an agency might not list a service if it assumes that service as part of another.  For instance, the agency might be skilled at print design and print pre-production, but may list only &#8220;design&#8221; among its services.  Or it may assume that database administration and web server optimization are assumed when it says &#8220;systems administration&#8221;.  It&#8217;s hard, and it shouldn&#8217;t be your job, to tease out these services when you have better things to do with your life.</p>
<p>Helen Marie is not just interested in shepharding work into our own office.  We&#8217;re interested in working with clients to help them through the process of defining and enunciating their needs, and finding the right agency to fulfill those needs.  We can identify where to spend money and where to save it, how to conceive your interactive project in phases to ease funding commitments and provide for more flexibility, how to use the language of the industry in your RFP to maximize the quality of the resulting proposals, and what kinds of agencies to target.  We can save you time and money, and ease the strain on your organization.</p>
<p>Call it what you want &#8212; creative broker, strategic design consultant, interactive strategist, you name it.  We thought of &#8220;institutional heartbreak avoider&#8221;, but it was too dramatic.  We&#8217;re sticking with &#8220;creative broker&#8221; for now.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2008/12/buddy-you-need-an-agent/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dangerous Phrases: &#8220;I Know a Guy&#8221;</title>
		<link>http://blog.helen-marie.com/index.php/2008/11/dangerous-phrases-i-know-a-guy/</link>
		<comments>http://blog.helen-marie.com/index.php/2008/11/dangerous-phrases-i-know-a-guy/#comments</comments>
		<pubDate>Thu, 27 Nov 2008 17:33:35 +0000</pubDate>
		<dc:creator>msh</dc:creator>
				<category><![CDATA[Client Side]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[dangerousphrases]]></category>
		<category><![CDATA[specialization]]></category>
		<category><![CDATA[technologicalpanic]]></category>

		<guid isPermaLink="false">http://blog.helen-marie.com/?p=11</guid>
		<description><![CDATA[This dangerous phrase occurs mostly in the world of development, not in design (although there is a variation: &#8220;My friend is a designer&#8221;).  It could be a woman, of course, but in the world of IT and web development, you&#8217;re usually dealing with men.  This person will have some kind of experience with the web, [...]]]></description>
			<content:encoded><![CDATA[<p>This dangerous phrase occurs mostly in the world of development, not in design (although there is a variation: &#8220;My friend is a designer&#8221;).  It could be a woman, of course, but in the world of IT and web development, <a title="National Center for Women and Technology" href="http://www.ncwit.org/">you&#8217;re usually dealing with men</a>.  This person will have some kind of experience with the web, or web servers, or some technology you associate with the web.  He may configure your email server.  He may be a friend who once had a web site of his own.</p>
<p>In any case, your (limited, possibly anecdotal) understanding of this person&#8217;s skills may lead you to think, &#8220;I don&#8217;t need an overpriced agency to design and build our site.  We&#8217;ll just get <em>him</em> to do it.  We know him, we trust him, we already pay him&#8230;.&#8221;  You might also think, &#8220;Let&#8217;s keep the risk low this first time around by keeping the investment low.  If we need to, we can hire specialists to clean this up later.&#8221;</p>
<p><span id="more-11"></span></p>
<p>This person, your guy, who undoubtedly has skills in some area or other, will not deliver the web site that you need.  Your unfamiliarity with the interactive world may cause you to equate your guy&#8217;s technical skills with a total knowledge of the process of web design and development, but in reality you&#8217;ve hired an electrician to design and build a house.</p>
<p>The &#8220;I know a guy&#8221; phenomenon is an outgrowth of what we call Technological Panic.  You are pressured, either by the higher-ups at your organization or by market forces, to produce a web site.  And your lifelong experience of the web is either of maintaining whatever crusty, old thing you have now, or even just of consuming the web through a browser.</p>
<p>You need to be in control of this project, but you can&#8217;t sense the boundaries or the requirements.  It&#8217;s hard even just to write the first steps down on a piece of paper.  This is the source of Technological Panic: a total, fundamental unfamiliarity with the subject.</p>
<p>For years, Helen Marie&#8217;s business was largely based on clients who approached us after succumbing to Technological Panic.  We were the Second Try.  The organization would approach us after completing the first site, which would barely see the light of day before becoming a symbolic container for every aspect of the company&#8217;s internal politics or strategic confusion.  Finally, someone would say, &#8220;We need to do this right, and we need to put real money into this project &#8212; what we have is useless.&#8221;  That person would find us.</p>
<p>Clients who come to us in this state are humbled by their initial experience.  They have realized, painfully, that the electrician they hired didn&#8217;t build them a house, but instead tried to frame the building from wires and electrical tape.  As it turns out, the place to start is with an architecture firm.  We enjoy working with these clients because they don&#8217;t need us to make the case for proper strategy, planning, research, and information architecture.  But we think there&#8217;s a lot of unnecessary pain out there in Client Land, and we&#8217;d like to warn you ahead of time.</p>
<p>Conclusion: to overcome Technological Panic, call us, or an agency like ours, to talk through your situation.  Call more than one agency.  You&#8217;ll find that these conversations can give you a sense of the real learning curve, and put you on the path to ascending it.  Panic subsides, the real learning begins, and you can come up with a plan that&#8217;s grounded in reality.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.helen-marie.com/index.php/2008/11/dangerous-phrases-i-know-a-guy/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
