<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Reflexivity in Design Practice</title>
	<link>http://eismann-sf.com/news/?p=755</link>
	<description>Adobe Thermo, AIR, Flash, Flex, and design writ large.</description>
	<pubDate>Mon, 06 Sep 2010 06:33:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Al Gammate</title>
		<link>http://eismann-sf.com/news/?p=755#comment-3720</link>
		<dc:creator>Al Gammate</dc:creator>
		<pubDate>Wed, 01 Apr 2009 02:35:32 +0000</pubDate>
		<guid>http://eismann-sf.com/news/?p=755#comment-3720</guid>
		<description>Hello Ethan: 

I enjoyed reading your article entitled "Reflexivity in Design Practice." 

I agree that the practice of reflexivity occurs naturally in design practice. 

Though there may be many people involved in creating an object design, everyone involved affects the object design and the object design, in turn, affects everyone involved. 

One may be wondering "Okay, it's obvious that everyone involved affects an object design; but how does the object design affect everyone involved?" 

The answer is simple. 

Any defects or negative attributes of an object design will cause everyone involved to try to eliminate these defects or negative attributes. And any advantages or positive attributes of an object design will cause everyone involved to try to enhance these advantages or positive attributes. 

Reflexivity isn't turned on or off at will. Instead, it's a natural part of the human condition!</description>
		<content:encoded><![CDATA[<p>Hello Ethan: </p>
<p>I enjoyed reading your article entitled &#8220;Reflexivity in Design Practice.&#8221; </p>
<p>I agree that the practice of reflexivity occurs naturally in design practice. </p>
<p>Though there may be many people involved in creating an object design, everyone involved affects the object design and the object design, in turn, affects everyone involved. </p>
<p>One may be wondering &#8220;Okay, it&#8217;s obvious that everyone involved affects an object design; but how does the object design affect everyone involved?&#8221; </p>
<p>The answer is simple. </p>
<p>Any defects or negative attributes of an object design will cause everyone involved to try to eliminate these defects or negative attributes. And any advantages or positive attributes of an object design will cause everyone involved to try to enhance these advantages or positive attributes. </p>
<p>Reflexivity isn&#8217;t turned on or off at will. Instead, it&#8217;s a natural part of the human condition!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan Eismann</title>
		<link>http://eismann-sf.com/news/?p=755#comment-3685</link>
		<dc:creator>Ethan Eismann</dc:creator>
		<pubDate>Thu, 05 Feb 2009 20:43:52 +0000</pubDate>
		<guid>http://eismann-sf.com/news/?p=755#comment-3685</guid>
		<description>It's true, my post analyzes an individual designer's process and practice. Furthermore, it's doesn't comment on the greater team processes related to design (that wasn't the point of the post). 

In my experience, I have worked with designers who create no less than 4 alternatives per each design problem, and iterate on each to develop their recommendation. I have also worked with designers who create only one solution and don't iterate at all. The former is obviously the preferred practice. 

One final note, the reflexive process should be a part of every stage in the design practice, the sketching, the modeling, the concept-mapping, etc. In a sense, it's being reflexive that defines - to a certain extent - one as a designer.</description>
		<content:encoded><![CDATA[<p>It&#8217;s true, my post analyzes an individual designer&#8217;s process and practice. Furthermore, it&#8217;s doesn&#8217;t comment on the greater team processes related to design (that wasn&#8217;t the point of the post). </p>
<p>In my experience, I have worked with designers who create no less than 4 alternatives per each design problem, and iterate on each to develop their recommendation. I have also worked with designers who create only one solution and don&#8217;t iterate at all. The former is obviously the preferred practice. </p>
<p>One final note, the reflexive process should be a part of every stage in the design practice, the sketching, the modeling, the concept-mapping, etc. In a sense, it&#8217;s being reflexive that defines - to a certain extent - one as a designer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Hobson</title>
		<link>http://eismann-sf.com/news/?p=755#comment-3684</link>
		<dc:creator>Andrew Hobson</dc:creator>
		<pubDate>Thu, 05 Feb 2009 19:07:23 +0000</pubDate>
		<guid>http://eismann-sf.com/news/?p=755#comment-3684</guid>
		<description>I think you're putting far too much emphasis on the design as the result of one persons process. That one person does something, presents it as a solution, the world reacts and 'the' designer alone makes changes to what he hears and sees. This seems incredibly simplistic and overlooks that designers work in teams, they rarely 'commission' the design, almost never own the business case, and overlooks the likelihood that someone else probably realizes the 'object' — an engineer, a printer, a manufacturing plant. You seem to be suggesting that design is an indeterminate process that is an endeavor making and presenting solution after solution after solution — one which may be right sooner rather than later, or later rather soon. Isn't this an art process not design? Given that fact that designs are more often than not way bigger than one person, aren't you over looking a fundamental need to break design problems down by sketching out pieces, build models and try things out. 

Thinking about the later, I find it ironic that you state that iteration is often overlooked. By who? The designer, the greater team, or the world at large? I think no designer overlooks iteration (if they do I would contest they are not a designer.) The problem arises when the greater team and the world at large doesn't allow for iteration and ignores design process of sketching, modeling and trying things out. Something you seem to be overlooking by suggesting designers solely create final designs, present them as such and then observe they're not.</description>
		<content:encoded><![CDATA[<p>I think you&#8217;re putting far too much emphasis on the design as the result of one persons process. That one person does something, presents it as a solution, the world reacts and &#8216;the&#8217; designer alone makes changes to what he hears and sees. This seems incredibly simplistic and overlooks that designers work in teams, they rarely &#8216;commission&#8217; the design, almost never own the business case, and overlooks the likelihood that someone else probably realizes the &#8216;object&#8217; — an engineer, a printer, a manufacturing plant. You seem to be suggesting that design is an indeterminate process that is an endeavor making and presenting solution after solution after solution — one which may be right sooner rather than later, or later rather soon. Isn&#8217;t this an art process not design? Given that fact that designs are more often than not way bigger than one person, aren&#8217;t you over looking a fundamental need to break design problems down by sketching out pieces, build models and try things out. </p>
<p>Thinking about the later, I find it ironic that you state that iteration is often overlooked. By who? The designer, the greater team, or the world at large? I think no designer overlooks iteration (if they do I would contest they are not a designer.) The problem arises when the greater team and the world at large doesn&#8217;t allow for iteration and ignores design process of sketching, modeling and trying things out. Something you seem to be overlooking by suggesting designers solely create final designs, present them as such and then observe they&#8217;re not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ethan Eismann</title>
		<link>http://eismann-sf.com/news/?p=755#comment-3683</link>
		<dc:creator>Ethan Eismann</dc:creator>
		<pubDate>Mon, 02 Feb 2009 18:30:57 +0000</pubDate>
		<guid>http://eismann-sf.com/news/?p=755#comment-3683</guid>
		<description>Both reflexive and iterative design practices should occur. In my experience, reflexive design practice helps the designer mold the design solution into something better, faster. By being reflexive, the designer is able to take a step back from the design, and respond to it with improvements or variations, even before presenting it to peers or users. 

So in a sense, reflexive is a design process within iterative.</description>
		<content:encoded><![CDATA[<p>Both reflexive and iterative design practices should occur. In my experience, reflexive design practice helps the designer mold the design solution into something better, faster. By being reflexive, the designer is able to take a step back from the design, and respond to it with improvements or variations, even before presenting it to peers or users. </p>
<p>So in a sense, reflexive is a design process within iterative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pedro</title>
		<link>http://eismann-sf.com/news/?p=755#comment-3682</link>
		<dc:creator>pedro</dc:creator>
		<pubDate>Mon, 02 Feb 2009 09:51:42 +0000</pubDate>
		<guid>http://eismann-sf.com/news/?p=755#comment-3682</guid>
		<description>You are mostly talking about iterative design, not reflexive.
"Of course feedback and questioning should come from other sources - peers and users especially." - that's how it should be, not reflexive</description>
		<content:encoded><![CDATA[<p>You are mostly talking about iterative design, not reflexive.<br />
&#8220;Of course feedback and questioning should come from other sources - peers and users especially.&#8221; - that&#8217;s how it should be, not reflexive</p>
]]></content:encoded>
	</item>
</channel>
</rss>
