<?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>Paper to Pixel &#187; dealing with clients</title>
	<atom:link href="http://www.papertopixel.org/category/dealing-with-clients/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.papertopixel.org</link>
	<description>web design tips for graphic designers</description>
	<lastBuildDate>Sun, 08 Aug 2010 09:05:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The most important thing you should do when meeting a client for the first time</title>
		<link>http://www.papertopixel.org/2009/the-most-important-thing-you-should-do-when-meeting-a-client-for-the-first-time/</link>
		<comments>http://www.papertopixel.org/2009/the-most-important-thing-you-should-do-when-meeting-a-client-for-the-first-time/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 08:05:11 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[dealing with clients]]></category>
		<category><![CDATA[general web design]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=520</guid>
		<description><![CDATA[Shut up and let your client speak. 
It is a natural instinct that tells us: talking about yourself shows how professional you are. Especially talking about how you know and understand technology, internet, social networking, insert your favorite latest internet sensation here. In reality, nothing is further from the truth. The only thing your prospect [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Shut up and let your client speak. </strong></p>
<p><strong>It is a natural instinct that tells us: talking about yourself shows how professional you are. </strong>Especially talking about how you know and understand technology, internet, social networking, insert your favorite latest internet sensation here. <strong>In reality, nothing is further from the truth.</strong> The only thing your prospect wants to find out is whether you understand his needs. And unless you convince him of that your fate is doomed.</p>
<p><span id="more-520"></span><strong>Why do I write this in a design blog though? </strong>Actually the impulse for this post came to me after a meeting between a web designer and a prospective client that I witnessed the other day. During over an hour that I was there the designer hasn&#8217;t stopped talking. I imagine the client must have been delighted when given a chance to throw &#8220;ahah&#8221; into the &#8220;conversation&#8221;.</p>
<p>Instead of finding out important information about clients plans for the site the designer kept on bragging about himself and all the internet crap you can think of.</p>
<p>Was the client happy? I pretty much doubt it.</p>
<p>Was the designer happy? I suppose he was actually proud of himself. In his mind he showed professionalism. Mainly by shifting between javascript, twitter and all the stuff his client doesn&#8217;t care about, very often in a single sentence.</p>
<p>Was the client interested in all that? Possibly, but I imagine he was more interested in telling the designer why he needs a website and what aim it is supposed to achieve.</p>
<p><strong>So what was the designer supposed to do?</strong><br />
<strong>Shut up and let the client speak. </strong>He should have sit there and find out about clients plans. What his company does, what expectations does the client have for his website. He should have gathered links to clients direct competition, also links to sites that the client likes.</p>
<p>Initial meeting is not about you, it is not about how well you know the latest internet/social networking trends either. It is about convincing the client that you understand his plans and needs. And that you can deliver those.</p>
<p>And the best way to achieve that is to shut up, listen and ask questions only if you don&#8217;t know something.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/the-most-important-thing-you-should-do-when-meeting-a-client-for-the-first-time/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>When would you say no to a project and why what you know might be a reason</title>
		<link>http://www.papertopixel.org/2009/when-would-you-say-no-to-a-project-and-why-what-you-know-might-be-a-reason/</link>
		<comments>http://www.papertopixel.org/2009/when-would-you-say-no-to-a-project-and-why-what-you-know-might-be-a-reason/#comments</comments>
		<pubDate>Fri, 18 Sep 2009 19:06:22 +0000</pubDate>
		<dc:creator>pawel</dc:creator>
				<category><![CDATA[dealing with clients]]></category>

		<guid isPermaLink="false">http://www.papertopixel.org/?p=496</guid>
		<description><![CDATA[Let me ask you a quick question, would you reject a project these days if it came your way? I mean would you definitely say no to it? I guess not. But let’s assume this one time that you would. What would be your reasons for doing so?

Some of them might be obvious, I suppose. [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Let me ask you a quick question, would you reject a project these days if it came your way? I mean would you definitely say no to it? I guess not. But let’s assume this one time that you would. What would be your reasons for doing so?<br />
</strong><br />
Some of them might be obvious, I suppose. They would most likely revolve around clients not having any budget for the work. Or offering something else than money in return for your service. Others might include clients having unrealistic expectations over what they are getting for their money. Or their bad reputation, if they have one may play a significant role here as well. </p>
<p><strong>Did you notice that they all involve a client?</strong> It seems that a client seems to always be in the center. I wonder though if there is any non-client related reason that would make you to say no to a project.<br />
<span id="more-496"></span></p>
<p><strong>Thinking of that I ran a simple test last week. I asked some of our clients and friends when would they reject a project.</strong> And most of the answers I got were pretty much in line with those already mentioned. But I got some interesting ones as well with one reason that really stood out. A very simple, yet a very powerful one at the same time.<br />
<strong><br />
A friend of mine said that she would simply say no to a project that she could not deliver.</strong><br />
<strong><br />
And when you think of it the reason pretty much obvious. So, what was so powerful about it then?</strong><br />
Well, think of the last project you rejected for that reason. Many of us tend to fiddle with things, hoping that we can make them work and  still deliver the project. And in general many designers would not even consider such a “silly reason” to be good enough to reject a project and a potential income.<br />
<strong><br />
Let’s face it, no one likes to loose a potential income, especially in this economic situation. And of course no one likes to admit to a client that they can not deliver the work. We all like our clients to consider us experts. </strong><br />
<strong><br />
The problem is that to a client you are not a quick solution.</strong> They consider you someone they can trust a major aspect of their business with. And they not only expect it to be looked after to a highest standard but also deserve that too. </p>
<p><strong>So what can you do to ensure that?</strong><br />
Since rejecting a project is not really an option you can try various other ones. Outsourcing, hiring a contractor and many others. In fairness you may also earn some extra money from that and that is never a bad thing. </p>
<p>You may also consider referring a client to someone else and still look after that part of the job you can deliver. Not only you will help your client but possibly help a fellow business. And in business world this almost always pays back.</p>
<p>One thing is important here, to your client you are an expert indeed. Otherwise I doubt they would be working with you in the first place. But you are an expert in your field. And clients will be more than happy to hear that you can not deliver those aspects of the project that are outside of what you do but rather ask someone’s help or assistance. And they will very easily accept that. </p>
<p>And you? By doing this you most likely will look even more professional in the eyes of your client. And that’s what it’s all about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.papertopixel.org/2009/when-would-you-say-no-to-a-project-and-why-what-you-know-might-be-a-reason/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
