<?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: The Difficulty with Articulating Design</title>
	<atom:link href="http://bokardo.com/archives/the-difficulty-with-articulating-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://bokardo.com/archives/the-difficulty-with-articulating-design/</link>
	<description>Interface Design &#38; UX by Joshua Porter</description>
	<lastBuildDate>Wed, 28 Sep 2011 20:28:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Web Hosting News &#187; On Web Standards</title>
		<link>http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-137575</link>
		<dc:creator>Web Hosting News &#187; On Web Standards</dc:creator>
		<pubDate>Thu, 10 May 2007 23:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-137575</guid>
		<description>[...] So instead of tearing down designers whose code doesnâ€™t validate, letâ€™s re-evaluate our work by asking what is the most important thing we can do to make our userâ€™s experience better? Letâ€™s question the questioners, and not view the world in black (does validate) and white (doesnâ€™t validate). Some time ago I wrote a long riff about why we are having trouble articulating design. [...]</description>
		<content:encoded><![CDATA[<p>[...] So instead of tearing down designers whose code doesnâ€™t validate, letâ€™s re-evaluate our work by asking what is the most important thing we can do to make our userâ€™s experience better? Letâ€™s question the questioners, and not view the world in black (does validate) and white (doesnâ€™t validate). Some time ago I wrote a long riff about why we are having trouble articulating design. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francis Wu</title>
		<link>http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-4299</link>
		<dc:creator>Francis Wu</dc:creator>
		<pubDate>Mon, 27 Feb 2006 06:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-4299</guid>
		<description>This brings me back to Adam Greenfield&#039;s &lt;a href=&quot;http://www.alistapart.com/articles/bathingape/&quot; rel=&quot;nofollow&quot;&gt;Designer vs Stylist article&lt;/a&gt;.  In my experience, people tend to lump design with graphic design.  This is doubly so when these people are project decision-makers.  I&#039;ve had the misfortune of working on a design project where my employer was allowing an advertising company to make design decisions for me.

It seems that people just take design at face value and it doesn&#039;t help that we&#039;re saturated with so-called designers who are simply glorified graphic artists equipped with Photoshop and Frontpage. Think of all these traditional print companies that decided to hop onto the Internet wagon. &quot;Yeah, of course we know the Internet... It&#039;s great!  Check out this spinning logo.  Isn&#039;t that amazing?  Yeah, of course you can have that as your email signature.  I can make it blink too so you&#039;ll really get their attention!  We&#039;re pioneers of this information highway, you know.&quot;

I think some of the problem also lies in the fact that other trades have kinda appropriated the word to describe fashion and art, thus removing any functionality or problem-solving meanings that the word once had.  Ironically enough though, when people think of design, not only do they think of fashion and art, but they also think of great product design like the iPod.

It would be rather silly to attempt to reclaim the word at this point -- I don&#039;t think a parade would improve things :P.  However, &lt;a href=&quot;http://developer.yahoo.net/ypatterns/index.php&quot; rel=&quot;nofollow&quot;&gt;Yahoo&#039;s release of design patterns&lt;/a&gt; does fill me with some hope.</description>
		<content:encoded><![CDATA[<p>This brings me back to Adam Greenfield&#8217;s <a href="http://www.alistapart.com/articles/bathingape/" rel="nofollow">Designer vs Stylist article</a>.  In my experience, people tend to lump design with graphic design.  This is doubly so when these people are project decision-makers.  I&#8217;ve had the misfortune of working on a design project where my employer was allowing an advertising company to make design decisions for me.</p>
<p>It seems that people just take design at face value and it doesn&#8217;t help that we&#8217;re saturated with so-called designers who are simply glorified graphic artists equipped with Photoshop and Frontpage. Think of all these traditional print companies that decided to hop onto the Internet wagon. &#8220;Yeah, of course we know the Internet&#8230; It&#8217;s great!  Check out this spinning logo.  Isn&#8217;t that amazing?  Yeah, of course you can have that as your email signature.  I can make it blink too so you&#8217;ll really get their attention!  We&#8217;re pioneers of this information highway, you know.&#8221;</p>
<p>I think some of the problem also lies in the fact that other trades have kinda appropriated the word to describe fashion and art, thus removing any functionality or problem-solving meanings that the word once had.  Ironically enough though, when people think of design, not only do they think of fashion and art, but they also think of great product design like the iPod.</p>
<p>It would be rather silly to attempt to reclaim the word at this point &#8212; I don&#8217;t think a parade would improve things <img src='http://bokardo.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> .  However, <a href="http://developer.yahoo.net/ypatterns/index.php" rel="nofollow">Yahoo&#8217;s release of design patterns</a> does fill me with some hope.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Isaac Almond</title>
		<link>http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-618</link>
		<dc:creator>Michael Isaac Almond</dc:creator>
		<pubDate>Tue, 10 May 2005 15:15:00 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-618</guid>
		<description>Joshua, You are the man!
I enjoyed this post and felt rather vindicated, to be honest. I agree with your key points. Of course, I have my own spin on the issue as well.

Designers, not design, are frustrated; and for good reasons. I say designers for the obvious reason that design hasn&#039;t gone anywhere. It is just fine in it&#039;s skin. What I believe is that designers are looking at and discussion the wrong problem.

Let me explain (your phase I am borrowing). My sense is that designers are craving meaning and voice. We have the difficult task of creating something that is essentially invisible. I was always taught that good design is transparent. Art on the other hand is quite different. It communicates ideas about the inner life of the artist-expression is a better word. While we can&#039;t help but leave some traces of ourselves-a fingerprint-design is not about the designer. So we are essentially transparent and without voice. 

However, this doesn&#039;t have to be the case. If we could force ourselves to look to the past, just for a moment, we would see that much of the history of design involved ideologies and collective action. There where profound and meaningful ideas that were real movements, as we see in Art History. The Bauhaus is the perfect example.

So I am of the opinion that much of this is not our fault. Design education and the professional world have not encouraged nor educated us in other areas and outside disciplines. They have more and more promoted transparency. I also believe that it is our problem to solve, regardless of how it came to be. 

We are responsible for making changes in ourselves and our knowledge areas. We don&#039;t like to do this. We want to talk about design or why no one talks about design when the real issue is that we need to talk and learn about more than just design. More of this in an article I am writing for DWM. Again, Thanks as always.</description>
		<content:encoded><![CDATA[<p>Joshua, You are the man!<br />
I enjoyed this post and felt rather vindicated, to be honest. I agree with your key points. Of course, I have my own spin on the issue as well.</p>
<p>Designers, not design, are frustrated; and for good reasons. I say designers for the obvious reason that design hasn&#8217;t gone anywhere. It is just fine in it&#8217;s skin. What I believe is that designers are looking at and discussion the wrong problem.</p>
<p>Let me explain (your phase I am borrowing). My sense is that designers are craving meaning and voice. We have the difficult task of creating something that is essentially invisible. I was always taught that good design is transparent. Art on the other hand is quite different. It communicates ideas about the inner life of the artist-expression is a better word. While we can&#8217;t help but leave some traces of ourselves-a fingerprint-design is not about the designer. So we are essentially transparent and without voice. </p>
<p>However, this doesn&#8217;t have to be the case. If we could force ourselves to look to the past, just for a moment, we would see that much of the history of design involved ideologies and collective action. There where profound and meaningful ideas that were real movements, as we see in Art History. The Bauhaus is the perfect example.</p>
<p>So I am of the opinion that much of this is not our fault. Design education and the professional world have not encouraged nor educated us in other areas and outside disciplines. They have more and more promoted transparency. I also believe that it is our problem to solve, regardless of how it came to be. </p>
<p>We are responsible for making changes in ourselves and our knowledge areas. We don&#8217;t like to do this. We want to talk about design or why no one talks about design when the real issue is that we need to talk and learn about more than just design. More of this in an article I am writing for DWM. Again, Thanks as always.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hutch</title>
		<link>http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-537</link>
		<dc:creator>hutch</dc:creator>
		<pubDate>Thu, 28 Apr 2005 19:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://bokardo.com/archives/the-difficulty-with-articulating-design/#comment-537</guid>
		<description>I work for a company that provides human factors support to various customers on various contracts.  Currently, I am working on designing interfaces for novel controls.  After reading this article, I started reviewing old designs and asking questions such as those mentioned.  While I have been aware of the answers all along, asking the questions for the little details and design decisions I made forced me to face an ugly truth.  That is, I represent everything wrong with interface design.  

By trade I am an applied experimental psychologist.  By company title I am a human factors psychologist.  Being an experimental psychologist I am intimately familiar with the value of testing participants (users), validating the study, and concluding only what there is evidence to back up.  

Ideally, it seems that the answer to a question about a design decision should ultimately always be founded upon evidence resulting from a user study.  I have yet to see &#039;ideally&#039; happen.  Let me explain further.  I do have limited access to a handful of users, maybe 3 to 5.  These individuals are used repeatedly, but not for design evaluation, rather for concept development.  The design life cycle hardly completes a single iteration.  The users are called upon (traditionally via email) as SMEs to help work out the details and develop the concept behind the interface, i.e. input on common usage, control preferences, expert ways of thinking about the domain, etc..  I then take that info and develop an interface around the concept.  The interface is reviewed internally by peers and it is sent off to the developers.  At best the design process can be labeled as BOGSAT and driven by the persona created from the initial SME interviews.  However, that is simply an attempt to make is smell right by giving it some familiar terminology.

I am admittedly green, being that this is my first job out of school.  Yet these are the resources I am working with. I have become frustrated, but complacent.  I ask the design question of why, and realize that it&#039;s only because I felt like making it look that way.

The reason that I stand for everything that is wrong with interface design is because I recognize the mistakes being made, but because I don&#039;t know how to correct them I continue making them not under the guise of ignorance, but with an almost accepted intentionality.

How does one work towards being in a position to ask design questions and feel comfortable with the answers?
</description>
		<content:encoded><![CDATA[<p>I work for a company that provides human factors support to various customers on various contracts.  Currently, I am working on designing interfaces for novel controls.  After reading this article, I started reviewing old designs and asking questions such as those mentioned.  While I have been aware of the answers all along, asking the questions for the little details and design decisions I made forced me to face an ugly truth.  That is, I represent everything wrong with interface design.  </p>
<p>By trade I am an applied experimental psychologist.  By company title I am a human factors psychologist.  Being an experimental psychologist I am intimately familiar with the value of testing participants (users), validating the study, and concluding only what there is evidence to back up.  </p>
<p>Ideally, it seems that the answer to a question about a design decision should ultimately always be founded upon evidence resulting from a user study.  I have yet to see &#8216;ideally&#8217; happen.  Let me explain further.  I do have limited access to a handful of users, maybe 3 to 5.  These individuals are used repeatedly, but not for design evaluation, rather for concept development.  The design life cycle hardly completes a single iteration.  The users are called upon (traditionally via email) as SMEs to help work out the details and develop the concept behind the interface, i.e. input on common usage, control preferences, expert ways of thinking about the domain, etc..  I then take that info and develop an interface around the concept.  The interface is reviewed internally by peers and it is sent off to the developers.  At best the design process can be labeled as BOGSAT and driven by the persona created from the initial SME interviews.  However, that is simply an attempt to make is smell right by giving it some familiar terminology.</p>
<p>I am admittedly green, being that this is my first job out of school.  Yet these are the resources I am working with. I have become frustrated, but complacent.  I ask the design question of why, and realize that it&#8217;s only because I felt like making it look that way.</p>
<p>The reason that I stand for everything that is wrong with interface design is because I recognize the mistakes being made, but because I don&#8217;t know how to correct them I continue making them not under the guise of ignorance, but with an almost accepted intentionality.</p>
<p>How does one work towards being in a position to ask design questions and feel comfortable with the answers?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

