<?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: Rawnet on web usability</title>
	<atom:link href="http://www.brelson.com/2008/09/rawnet-on-web-usability/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brelson.com/2008/09/rawnet-on-web-usability/</link>
	<description>the long-form thoughts of brendan nelson</description>
	<lastBuildDate>Sat, 21 Jan 2012 02:35:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: brelson</title>
		<link>http://www.brelson.com/2008/09/rawnet-on-web-usability/comment-page-1/#comment-21</link>
		<dc:creator>brelson</dc:creator>
		<pubDate>Thu, 11 Sep 2008 15:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.brelson.com/blog/?p=84#comment-21</guid>
		<description>Hi Adam,

Thanks for responding to my post, you&#039;ve raised some good points. 

Projects that harness what I described as a &quot;productive synthesis&quot; between client and agency are best-case scenarios. In the worst cases, this synthesis is far from productive and the end result doesn&#039;t work for anyone - agency, client or (most importantly) the customer who has to interact with the result.

I&#039;ve got to admit that I myself have, at times, decided to take the easy option and not challenge the client hard enough on projects where I&#039;ve led the design process. But those days are behind me - those of us on the agency side need to assert ourselves.

One positive trend I&#039;ve noticed in the last few years is that clients are increasingly willing to see agencies as &#039;advisers&#039; and not just practitioners. The best clients expect to be challenged and are disappointed when agencies kow-tow too much.

The key to success in any client/agency relationship is for it to foster impassioned, creative discussions that don&#039;t become fractious or personalised. Ideally the client/agency distinction should only be a contractual one, and people working on a project should view themselves as a single team with a common goal, that shares the credit when things go well—but also shares responsibility when things go badly...

Brendan</description>
		<content:encoded><![CDATA[<p>Hi Adam,</p>
<p>Thanks for responding to my post, you&#8217;ve raised some good points. </p>
<p>Projects that harness what I described as a &#8220;productive synthesis&#8221; between client and agency are best-case scenarios. In the worst cases, this synthesis is far from productive and the end result doesn&#8217;t work for anyone &#8211; agency, client or (most importantly) the customer who has to interact with the result.</p>
<p>I&#8217;ve got to admit that I myself have, at times, decided to take the easy option and not challenge the client hard enough on projects where I&#8217;ve led the design process. But those days are behind me &#8211; those of us on the agency side need to assert ourselves.</p>
<p>One positive trend I&#8217;ve noticed in the last few years is that clients are increasingly willing to see agencies as &#8216;advisers&#8217; and not just practitioners. The best clients expect to be challenged and are disappointed when agencies kow-tow too much.</p>
<p>The key to success in any client/agency relationship is for it to foster impassioned, creative discussions that don&#8217;t become fractious or personalised. Ideally the client/agency distinction should only be a contractual one, and people working on a project should view themselves as a single team with a common goal, that shares the credit when things go well—but also shares responsibility when things go badly&#8230;</p>
<p>Brendan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.brelson.com/2008/09/rawnet-on-web-usability/comment-page-1/#comment-20</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Tue, 09 Sep 2008 16:53:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.brelson.com/blog/?p=84#comment-20</guid>
		<description>Hi Brendan, 

You raise a very interesting point, the final website is very much a joint responsibility between the client and the agency. 

To further clarify the point I was making about agencies ‘focusing too much on design or non-essential technical features’, I’m refereeing to some agencies taking the easier route of designing the website for their client, not their client’s customers.

It’s an agency’s job to challenge the client, let them know that the websites goal is to drive business, designing it for their customers, not them directly. What the client thinks is great design or a must have technical feature, isn’t necessary great for the end user or usability. 

The easy route is to just take on all the feedback from the client which may or may not improve the look of the site, but it may impact the usability, something a client may not have a huge amount of experience in. How many times has a client said ‘make my logo bigger’?  They say it all the time, that’s a classic example of designing for the client, and not necessary for the users of the website. 

Another classic example, a client may ask ‘I want all text above the fold, if there’s too much, add a scrollbar so that my logo and contact details are always on screen’.  Maybe this ‘could’ looks nice, but bad usability. 

So yes, Clients are indeed ultimately responsible for a website’s success, but it’s the agency’s role to reign in the client if required. While they may understand their brand and clients better – the agency will have much more experience in usability. That’s what they’re buying, the added value of an agency’s experience. 

I guess to summarize, companies are losing out on potential business because their web agency hasn’t challenged their ideas enough - focused too much on pleasing the client, which in some cases is not always delivering the best solution. 

Adam</description>
		<content:encoded><![CDATA[<p>Hi Brendan, </p>
<p>You raise a very interesting point, the final website is very much a joint responsibility between the client and the agency. </p>
<p>To further clarify the point I was making about agencies ‘focusing too much on design or non-essential technical features’, I’m refereeing to some agencies taking the easier route of designing the website for their client, not their client’s customers.</p>
<p>It’s an agency’s job to challenge the client, let them know that the websites goal is to drive business, designing it for their customers, not them directly. What the client thinks is great design or a must have technical feature, isn’t necessary great for the end user or usability. </p>
<p>The easy route is to just take on all the feedback from the client which may or may not improve the look of the site, but it may impact the usability, something a client may not have a huge amount of experience in. How many times has a client said ‘make my logo bigger’?  They say it all the time, that’s a classic example of designing for the client, and not necessary for the users of the website. </p>
<p>Another classic example, a client may ask ‘I want all text above the fold, if there’s too much, add a scrollbar so that my logo and contact details are always on screen’.  Maybe this ‘could’ looks nice, but bad usability. </p>
<p>So yes, Clients are indeed ultimately responsible for a website’s success, but it’s the agency’s role to reign in the client if required. While they may understand their brand and clients better – the agency will have much more experience in usability. That’s what they’re buying, the added value of an agency’s experience. </p>
<p>I guess to summarize, companies are losing out on potential business because their web agency hasn’t challenged their ideas enough &#8211; focused too much on pleasing the client, which in some cases is not always delivering the best solution. </p>
<p>Adam</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.673 seconds -->

