<?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: Fear of Design</title>
	<atom:link href="http://boxesandarrows.com/fear-of-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://boxesandarrows.com/fear-of-design/</link>
	<description>Boxes and Arrows is devoted to the practice, innovation, and discussion of design; including graphic design, interaction design, information architecture and the design of business.</description>
	<lastBuildDate>Mon, 20 May 2013 13:09:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Adam Greenfield</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8538</link>
		<dc:creator>Adam Greenfield</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8538</guid>
		<description><![CDATA[(eesh...you&#039;ve just summarized my book. Do I still have to write it?)

Yes, IA IS DESIGN.
And guess what? Increasingly, design is IA. Last year, this was the &quot;5,000 foot view,&quot; but it gets closer to earth every day.

What do I mean? I mean that the methodologies we kludged together to account for a situation of explicit informational flow - a user interacting with the Web - also happens to be very useful for situations of implicit informational flow. Such as the interaction of a user with, say, a citrus juicer.

You think I&#039;m kidding? I drew up a persona, developed a (admittedly barebones) scenario bringing that persona into contact with a citrus juicer, elaborated a use case specifying each point of informational flow between object and user...the results were illuminating. 

If designers don&#039;t learn to think this way, I&#039;m betting they&#039;ll be swept aside by those who do.]]></description>
		<content:encoded><![CDATA[<p>(eesh&#8230;you&#8217;ve just summarized my book. Do I still have to write it?)</p>
<p>Yes, IA IS DESIGN.<br />
And guess what? Increasingly, design is IA. Last year, this was the &#8220;5,000 foot view,&#8221; but it gets closer to earth every day.</p>
<p>What do I mean? I mean that the methodologies we kludged together to account for a situation of explicit informational flow &#8211; a user interacting with the Web &#8211; also happens to be very useful for situations of implicit informational flow. Such as the interaction of a user with, say, a citrus juicer.</p>
<p>You think I&#8217;m kidding? I drew up a persona, developed a (admittedly barebones) scenario bringing that persona into contact with a citrus juicer, elaborated a use case specifying each point of informational flow between object and user&#8230;the results were illuminating. </p>
<p>If designers don&#8217;t learn to think this way, I&#8217;m betting they&#8217;ll be swept aside by those who do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Olsen</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8539</link>
		<dc:creator>George Olsen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8539</guid>
		<description><![CDATA[Back when I was in journalism there was an apropos phrase for the stage when you had to shear away all that beautiful prose that wasn&#039;t necessary to the story. It was called &quot;killing your babies&quot; -- and it _is_ hard to do.

But it&#039;s a skill the best writers, and designers, have to learn how to do. It&#039;s the flip side of having the courage to make the creative leap. 

The biggest difficulty I&#039;ve had with younger designers (both print and web) is getting them to understand it that&#039;s its not personal, since as John says, they&#039;ve got their egos invested in it. 

However the same might be said of usablity folks as well. Sometimes usability concerns need to be balanced against other concerns, for example as Dan Shaffer talks about in &quot;Building Brand into Structure.&quot; But too often, I hear usability results presented as an all-or-nothing proposition.]]></description>
		<content:encoded><![CDATA[<p>Back when I was in journalism there was an apropos phrase for the stage when you had to shear away all that beautiful prose that wasn&#8217;t necessary to the story. It was called &#8220;killing your babies&#8221; &#8212; and it _is_ hard to do.</p>
<p>But it&#8217;s a skill the best writers, and designers, have to learn how to do. It&#8217;s the flip side of having the courage to make the creative leap. </p>
<p>The biggest difficulty I&#8217;ve had with younger designers (both print and web) is getting them to understand it that&#8217;s its not personal, since as John says, they&#8217;ve got their egos invested in it. </p>
<p>However the same might be said of usablity folks as well. Sometimes usability concerns need to be balanced against other concerns, for example as Dan Shaffer talks about in &#8220;Building Brand into Structure.&#8221; But too often, I hear usability results presented as an all-or-nothing proposition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keith bishop</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8540</link>
		<dc:creator>keith bishop</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8540</guid>
		<description><![CDATA[I think IA  can either be &quot;design&quot; or &quot;not design&quot;. 

As Edward de Bono once stated,

&quot;You can analyse the past, but you have to design the future&quot;

This relates to IA very clearly, on one hand we can come up with the deliverables for IA in a project by applying rules learn&#039;t from past experiences (be it our own or other people&#039;s). This approach would give us a technically correct solution based on tried and tested principles.

But, that solution will not likely be very ground breaking or serve to push the development of IA (as a whole) forward.

To do that we need to design, to use our intuition, to take risks, to discover new ways of doing things and perhaps be a bit crazy.

So my boring conclusion is that there will always be room for both the &quot;non designer&quot; IA person and the &quot;designer&quot; IA person, just as some projects need a &quot;standard&quot; level of usability where as other projects may need a more &quot;innovative&quot; approach.

The sad thing is, for me, is that the majority of people I have worked with in software development or web design, fail to recogonise the importance of IA or indeed how far it can (and must) develop.]]></description>
		<content:encoded><![CDATA[<p>I think IA  can either be &#8220;design&#8221; or &#8220;not design&#8221;. </p>
<p>As Edward de Bono once stated,</p>
<p>&#8220;You can analyse the past, but you have to design the future&#8221;</p>
<p>This relates to IA very clearly, on one hand we can come up with the deliverables for IA in a project by applying rules learn&#8217;t from past experiences (be it our own or other people&#8217;s). This approach would give us a technically correct solution based on tried and tested principles.</p>
<p>But, that solution will not likely be very ground breaking or serve to push the development of IA (as a whole) forward.</p>
<p>To do that we need to design, to use our intuition, to take risks, to discover new ways of doing things and perhaps be a bit crazy.</p>
<p>So my boring conclusion is that there will always be room for both the &#8220;non designer&#8221; IA person and the &#8220;designer&#8221; IA person, just as some projects need a &#8220;standard&#8221; level of usability where as other projects may need a more &#8220;innovative&#8221; approach.</p>
<p>The sad thing is, for me, is that the majority of people I have worked with in software development or web design, fail to recogonise the importance of IA or indeed how far it can (and must) develop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave parker</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8541</link>
		<dc:creator>dave parker</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8541</guid>
		<description><![CDATA[Of course IA is design, in the same way that many things we do throughout the day are design.

Design is seeing a problem to be solved or a task to be accomplished and figuring out (or borrowing from established practice) the best way to solve that problem or accomplish that task. 

When you cook dinner--whether you make the dishes up yourself or follow someone else&#039;s directions--you are designing. When you decide whether you will mow your lawn in rows or in a circular pattern, you are designing. When you drive to work, choosing the best route based on traffic and other factors, you are designing. When you take a shower and decide to put the shampoo on your hair before scrubbing your face, you are designing. And when you organize a Web site&#039;s information and provide for a computer user the optimum path to get to that information, you are definitely designing.]]></description>
		<content:encoded><![CDATA[<p>Of course IA is design, in the same way that many things we do throughout the day are design.</p>
<p>Design is seeing a problem to be solved or a task to be accomplished and figuring out (or borrowing from established practice) the best way to solve that problem or accomplish that task. </p>
<p>When you cook dinner&#8211;whether you make the dishes up yourself or follow someone else&#8217;s directions&#8211;you are designing. When you decide whether you will mow your lawn in rows or in a circular pattern, you are designing. When you drive to work, choosing the best route based on traffic and other factors, you are designing. When you take a shower and decide to put the shampoo on your hair before scrubbing your face, you are designing. And when you organize a Web site&#8217;s information and provide for a computer user the optimum path to get to that information, you are definitely designing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ralph Brandi</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8542</link>
		<dc:creator>Ralph Brandi</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8542</guid>
		<description><![CDATA[I spent years feeling that the word &quot;design&quot; was so loaded that I didn&#039;t want to have anything to do with it. I took any number of circumlocutions to avoid the word; adopting the title &quot;Web Architect&quot; in 1996 was one of my early attempts to get across the idea that I create web sites without being associated with the baggage that the term &quot;design&quot; carries. I spent a lot of time considering fields that provided an analogous experience to what I was doing.

I had a conversation with Nick Ragouzis at CHI in 1998 about design. I denied that what I did was design, for exactly this reason. Call me a web architect, web cinematographer, webmaster, even a web engineer, anything but a web designer.

I still have a hard time explaining what I do. There&#039;s no doubt in my mind that it&#039;s a creative endeavor. I make web sites (gee, that wasn&#039;t hard). When I&#039;m done, there&#039;s something there that wasn&#039;t there before, or there&#039;s something there that&#039;s better than what was there before. Is it design? I don&#039;t know. I suppose so, especially if you define &quot;design&quot; the way Dave Parker does above. But I still have a queasy feeling in the pit of my stomach knowing that the term is most often used to describe an approach to web site creation that, in my experience, has most often resulted in unusable sites that I&#039;m then asked to tinker with to make them more able to meet the objectives laid out by my clients.]]></description>
		<content:encoded><![CDATA[<p>I spent years feeling that the word &#8220;design&#8221; was so loaded that I didn&#8217;t want to have anything to do with it. I took any number of circumlocutions to avoid the word; adopting the title &#8220;Web Architect&#8221; in 1996 was one of my early attempts to get across the idea that I create web sites without being associated with the baggage that the term &#8220;design&#8221; carries. I spent a lot of time considering fields that provided an analogous experience to what I was doing.</p>
<p>I had a conversation with Nick Ragouzis at CHI in 1998 about design. I denied that what I did was design, for exactly this reason. Call me a web architect, web cinematographer, webmaster, even a web engineer, anything but a web designer.</p>
<p>I still have a hard time explaining what I do. There&#8217;s no doubt in my mind that it&#8217;s a creative endeavor. I make web sites (gee, that wasn&#8217;t hard). When I&#8217;m done, there&#8217;s something there that wasn&#8217;t there before, or there&#8217;s something there that&#8217;s better than what was there before. Is it design? I don&#8217;t know. I suppose so, especially if you define &#8220;design&#8221; the way Dave Parker does above. But I still have a queasy feeling in the pit of my stomach knowing that the term is most often used to describe an approach to web site creation that, in my experience, has most often resulted in unusable sites that I&#8217;m then asked to tinker with to make them more able to meet the objectives laid out by my clients.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Heller</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8543</link>
		<dc:creator>David Heller</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8543</guid>
		<description><![CDATA[Congrats Christina for kicking us in the butt a bit. I think one of the reasons we are afraid of the design, is b/c our work isn&#039;t considered design.

I was just in one of those meetings with my boss telling him what I really want to do, and I said &quot;I want to design. I&#039;m sick of intuiting my wireframes. I want to use the design process to create informed designs.&quot; Something that there is currently no time in the design process to do. Even when I was at an agency where I controlled the consulting gigs the best design process I was able to conjour was just doing wireframes.

How many of us out there are in positions where doing interfaces is just about doing it? How often do we supply a client 3 versions of wireframes? I would sit in awe at how the visual designers get 3 weeks to not even come up with a final product and I would work my ass off to finish wireframes at 50 wireframes in 2 days.

This mentality that interface design is a chore, and visual design is an artform is what we are fighting against.]]></description>
		<content:encoded><![CDATA[<p>Congrats Christina for kicking us in the butt a bit. I think one of the reasons we are afraid of the design, is b/c our work isn&#8217;t considered design.</p>
<p>I was just in one of those meetings with my boss telling him what I really want to do, and I said &#8220;I want to design. I&#8217;m sick of intuiting my wireframes. I want to use the design process to create informed designs.&#8221; Something that there is currently no time in the design process to do. Even when I was at an agency where I controlled the consulting gigs the best design process I was able to conjour was just doing wireframes.</p>
<p>How many of us out there are in positions where doing interfaces is just about doing it? How often do we supply a client 3 versions of wireframes? I would sit in awe at how the visual designers get 3 weeks to not even come up with a final product and I would work my ass off to finish wireframes at 50 wireframes in 2 days.</p>
<p>This mentality that interface design is a chore, and visual design is an artform is what we are fighting against.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Heller</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8544</link>
		<dc:creator>David Heller</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8544</guid>
		<description><![CDATA[The Usability Issue:
Christina is right. I&#039;m sorry I don&#039;t know how you cut it, the heart and soul of Usability Engineering is to guide design, but not to design. They work with designers and they help them out, but in the end they are not designing. Their methods don&#039;t employ a design process, but are much more analytically and data driven. This is a necessary piece of product development, it is invaluable, but it is NOT design.

Christina (and myself) might be alienating a group of people in the BIG ia world, but lets please focus people about what IA is and isn&#039;t instead of trying to fit everywhere, especially in places that have long been filled by good people doing amazing work.]]></description>
		<content:encoded><![CDATA[<p>The Usability Issue:<br />
Christina is right. I&#8217;m sorry I don&#8217;t know how you cut it, the heart and soul of Usability Engineering is to guide design, but not to design. They work with designers and they help them out, but in the end they are not designing. Their methods don&#8217;t employ a design process, but are much more analytically and data driven. This is a necessary piece of product development, it is invaluable, but it is NOT design.</p>
<p>Christina (and myself) might be alienating a group of people in the BIG ia world, but lets please focus people about what IA is and isn&#8217;t instead of trying to fit everywhere, especially in places that have long been filled by good people doing amazing work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elmi van der Dussen</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8545</link>
		<dc:creator>Elmi van der Dussen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8545</guid>
		<description><![CDATA[The usability issue:

I found that often usability engineering is equited to a compliance audit. It might be the way it is sold and practiced. This might be a result of the emerging nature of this discipline, and opportunists climbing on the bandwagon after they&#039;ve read three sets of guidelines. 

To design (structure) an information space, or web space, and the nvaigation within this space, as well as the look-and-feel of ti, is multi-dimensional, and requires a combined skill-set. The most visible result is the look-and-feel - so graphic designers can sell themselves more easily as being required in the design process.]]></description>
		<content:encoded><![CDATA[<p>The usability issue:</p>
<p>I found that often usability engineering is equited to a compliance audit. It might be the way it is sold and practiced. This might be a result of the emerging nature of this discipline, and opportunists climbing on the bandwagon after they&#8217;ve read three sets of guidelines. </p>
<p>To design (structure) an information space, or web space, and the nvaigation within this space, as well as the look-and-feel of ti, is multi-dimensional, and requires a combined skill-set. The most visible result is the look-and-feel &#8211; so graphic designers can sell themselves more easily as being required in the design process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: christina</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8546</link>
		<dc:creator>christina</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8546</guid>
		<description><![CDATA[Thanks, Steve, for the distinction between *roles* and *people.*  Information architecture is design, Usability (testing evaluating, etc) is evaluation. Usability people may design (though it may also lessen their famed objectivity) and Information Architects may evaluate (also potentially biased). Design is always &quot;dangerous&quot; and takes courage no matter who does it.

Also, please understand that when I say IA, I also wish to include all the structural design professions that may wish to hide behind a scientific objectivity, including Interaction design, interface design and information design. It&#039;s all design.]]></description>
		<content:encoded><![CDATA[<p>Thanks, Steve, for the distinction between *roles* and *people.*  Information architecture is design, Usability (testing evaluating, etc) is evaluation. Usability people may design (though it may also lessen their famed objectivity) and Information Architects may evaluate (also potentially biased). Design is always &#8220;dangerous&#8221; and takes courage no matter who does it.</p>
<p>Also, please understand that when I say IA, I also wish to include all the structural design professions that may wish to hide behind a scientific objectivity, including Interaction design, interface design and information design. It&#8217;s all design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Olsen</title>
		<link>http://boxesandarrows.com/fear-of-design/#comment-8547</link>
		<dc:creator>George Olsen</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://boxesandarrows.com/fear-of-design/#comment-8547</guid>
		<description><![CDATA[Creation/evaluation -- This parallels Scott Berkum&#039;s argument about the need to both prove/disprove your design.

Whether it&#039;s done by different people depends on the temperment of the people involved and the context.

In &quot;traditional&quot; graphic design, one of the things that elevates you to senior designer or art director is developing the ability to look dispassionately at your own designs, which is something that generally only comes through experience.]]></description>
		<content:encoded><![CDATA[<p>Creation/evaluation &#8212; This parallels Scott Berkum&#8217;s argument about the need to both prove/disprove your design.</p>
<p>Whether it&#8217;s done by different people depends on the temperment of the people involved and the context.</p>
<p>In &#8220;traditional&#8221; graphic design, one of the things that elevates you to senior designer or art director is developing the ability to look dispassionately at your own designs, which is something that generally only comes through experience.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
