<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Who To Design For?</title>
	<link>http://fadtastic.net/2006/03/02/who-to-design-for/</link>
	<description>thoughts on &#124; comments about &#124; examples of  } web design trends.</description>
	<pubDate>Fri, 08 Aug 2008 21:21:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: P.J. Onori</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-467</link>
		<author>P.J. Onori</author>
		<pubDate>Thu, 02 Mar 2006 18:57:06 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-467</guid>
					<description>Nice article - very good read. 

I think the quintessential difference between art and design is the audience it is created for. If we use a site to be a self-expression of ourselves, with no concern for the outside user, I personally think it's much more a piece of art than design. 

While we obviously need to push visual asthetics, we need to do so within the confines of addressing the end user. Many times, this makes us more of a problem solver than anything else.</description>
		<content:encoded><![CDATA[<p>Nice article - very good read. </p>
<p>I think the quintessential difference between art and design is the audience it is created for. If we use a site to be a self-expression of ourselves, with no concern for the outside user, I personally think it&#8217;s much more a piece of art than design. </p>
<p>While we obviously need to push visual asthetics, we need to do so within the confines of addressing the end user. Many times, this makes us more of a problem solver than anything else.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Peter</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-475</link>
		<author>Peter</author>
		<pubDate>Fri, 03 Mar 2006 19:50:09 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-475</guid>
					<description>I entirely agree and I think most people will also agree. I think we forget though, and get tempted into doing things simply because we like them.</description>
		<content:encoded><![CDATA[<p>I entirely agree and I think most people will also agree. I think we forget though, and get tempted into doing things simply because we like them.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Gustavus Web Services &#187; Blog Archive &#187; Design and Readability &#187; Gustavus Adolphus College</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-476</link>
		<author>Gustavus Web Services &#187; Blog Archive &#187; Design and Readability &#187; Gustavus Adolphus College</author>
		<pubDate>Fri, 03 Mar 2006 21:28:35 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-476</guid>
					<description>[...] fadtastic has two great new articles up about design and readability. The first, Who to Design For? by Steven Teskey, discusses whether designs should focus on users or designers. He writes, &#8220;It all comes down to personal philosophy, but I’d like to possibly open some doors on this issue, that you might not have thought of otherwise.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] fadtastic has two great new articles up about design and readability. The first, Who to Design For? by Steven Teskey, discusses whether designs should focus on users or designers. He writes, &#8220;It all comes down to personal philosophy, but I’d like to possibly open some doors on this issue, that you might not have thought of otherwise.&#8221; [&#8230;]</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Danny Foo</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-478</link>
		<author>Danny Foo</author>
		<pubDate>Sat, 04 Mar 2006 01:56:01 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-478</guid>
					<description>My new philosophy in website design has been to design for the client's clients and not either for me or the client alone. :)

Cheers.</description>
		<content:encoded><![CDATA[<p>My new philosophy in website design has been to design for the client&#8217;s clients and not either for me or the client alone. :)</p>
<p>Cheers.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-539</link>
		<author>Johan</author>
		<pubDate>Mon, 13 Mar 2006 02:50:19 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-539</guid>
					<description>what about design control? When the client is designing alongside you and tries to wave good bye any good design principles?</description>
		<content:encoded><![CDATA[<p>what about design control? When the client is designing alongside you and tries to wave good bye any good design principles?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-541</link>
		<author>Steven Teskey</author>
		<pubDate>Mon, 13 Mar 2006 03:21:18 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-541</guid>
					<description>Johan, I'm not quite sure I understand what you're asking. Are you saying what if your client requests something that you'd normally forgo? If this feature is key to accessibility, I'd try my hardest to convince them of the importance, if not then why not put it in. Remember the client also counts as the designer, even though you're creating the site, you still need to take into account what they want, as well as make it accessible to the users. The design is pretty much your/your clients domain, you must only take into account how easily accessible this is for the end user.</description>
		<content:encoded><![CDATA[<p>Johan, I&#8217;m not quite sure I understand what you&#8217;re asking. Are you saying what if your client requests something that you&#8217;d normally forgo? If this feature is key to accessibility, I&#8217;d try my hardest to convince them of the importance, if not then why not put it in. Remember the client also counts as the designer, even though you&#8217;re creating the site, you still need to take into account what they want, as well as make it accessible to the users. The design is pretty much your/your clients domain, you must only take into account how easily accessible this is for the end user.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-602</link>
		<author>Johan</author>
		<pubDate>Thu, 16 Mar 2006 05:35:10 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-602</guid>
					<description>no what if you design for someone who is a designer, architect that thinks knows how to design a website but you wont hurt their feelings since they want justified text,etc</description>
		<content:encoded><![CDATA[<p>no what if you design for someone who is a designer, architect that thinks knows how to design a website but you wont hurt their feelings since they want justified text,etc</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-604</link>
		<author>Steven Teskey</author>
		<pubDate>Thu, 16 Mar 2006 07:13:55 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-604</guid>
					<description>It then becomes your duty to try and persuade the "designer" to make the site accessible for all, not just themselves. You'll run into people like this, but you must make it known that a site that can be seen the same for everyone is the intention of the site.

I ussually use the line "Not everyone will be able to see the same site, if you decide to do it like that you risk turning users away from the site" something along those lines ussually suffices.</description>
		<content:encoded><![CDATA[<p>It then becomes your duty to try and persuade the &#8220;designer&#8221; to make the site accessible for all, not just themselves. You&#8217;ll run into people like this, but you must make it known that a site that can be seen the same for everyone is the intention of the site.</p>
<p>I ussually use the line &#8220;Not everyone will be able to see the same site, if you decide to do it like that you risk turning users away from the site&#8221; something along those lines ussually suffices.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-642</link>
		<author>Johan</author>
		<pubDate>Tue, 21 Mar 2006 12:18:58 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-642</guid>
					<description>But the problem was the visual aspect of identity, when the clients wants certain visual elements that make a website unatractive   and even hinder accessibility and easy navivagation. The project referred to here was totally accessible/compliant etc ... You miss the point.</description>
		<content:encoded><![CDATA[<p>But the problem was the visual aspect of identity, when the clients wants certain visual elements that make a website unatractive   and even hinder accessibility and easy navivagation. The project referred to here was totally accessible/compliant etc &#8230; You miss the point.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-652</link>
		<author>Steven Teskey</author>
		<pubDate>Wed, 22 Mar 2006 02:39:09 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-652</guid>
					<description>Accessiblity and usability are what the article talks about. If they want to make an ugly site, then so be it. But when they decide to cripple what the user experiences the other end it is the designer's duty to step in. Maybe that will clear up some issues you may have with my article.</description>
		<content:encoded><![CDATA[<p>Accessiblity and usability are what the article talks about. If they want to make an ugly site, then so be it. But when they decide to cripple what the user experiences the other end it is the designer&#8217;s duty to step in. Maybe that will clear up some issues you may have with my article.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Johan</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-655</link>
		<author>Johan</author>
		<pubDate>Wed, 22 Mar 2006 16:34:21 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-655</guid>
					<description>Ugly sites are no good for your portfolio.

That is why a good talk with the client on beforehand can help to clear up a whole lot. You get to know the client and it is up to the designer to communicate back and forth with the client. I talk about  the site structure, make a litle sketch so the client knows what you like to do.</description>
		<content:encoded><![CDATA[<p>Ugly sites are no good for your portfolio.</p>
<p>That is why a good talk with the client on beforehand can help to clear up a whole lot. You get to know the client and it is up to the designer to communicate back and forth with the client. I talk about  the site structure, make a litle sketch so the client knows what you like to do.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Steven Teskey</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-657</link>
		<author>Steven Teskey</author>
		<pubDate>Wed, 22 Mar 2006 22:28:01 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-657</guid>
					<description>So then Johan I ask you this, is it more important to have a good looking site for your portfolio? Or is it better to make the client happy? How do you justify when they won't make a compromise?</description>
		<content:encoded><![CDATA[<p>So then Johan I ask you this, is it more important to have a good looking site for your portfolio? Or is it better to make the client happy? How do you justify when they won&#8217;t make a compromise?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Darius</title>
		<link>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-767</link>
		<author>Darius</author>
		<pubDate>Fri, 07 Apr 2006 07:47:59 +0000</pubDate>
		<guid>http://fadtastic.net/2006/03/02/who-to-design-for/#comment-767</guid>
					<description>well i igree mostly with ideas. especially about making layout first. it works as i do the same with my clients. but sometime they dont what to her about that, they wanna see the designed website already. they dont even talk whithout seeing it. so its not so easy to apply this scheme everytime.</description>
		<content:encoded><![CDATA[<p>well i igree mostly with ideas. especially about making layout first. it works as i do the same with my clients. but sometime they dont what to her about that, they wanna see the designed website already. they dont even talk whithout seeing it. so its not so easy to apply this scheme everytime.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
