<?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: Communication is&#8230;</title>
	<atom:link href="http://www.designassembly.org.nz/communication-is/feed" rel="self" type="application/rss+xml" />
	<link>http://www.designassembly.org.nz/communication-is</link>
	<description>Conversations on Graphic Design</description>
	<lastBuildDate>Thu, 02 Feb 2012 11:36:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Hayden Raw</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-211</link>
		<dc:creator>Hayden Raw</dc:creator>
		<pubDate>Wed, 14 Oct 2009 09:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-211</guid>
		<description>Thanks Chris

Ferdinand de Saussure was one of the forefathers of thinking around the linguistic signs and semiotics; the language of signs. As you can imagine language association to signs plays a large part in communication design.

The idea of the sign, the signifier and the signified play a large part in my representation of communication.</description>
		<content:encoded><![CDATA[<p>Thanks Chris</p>
<p>Ferdinand de Saussure was one of the forefathers of thinking around the linguistic signs and semiotics; the language of signs. As you can imagine language association to signs plays a large part in communication design.</p>
<p>The idea of the sign, the signifier and the signified play a large part in my representation of communication.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Baker</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-210</link>
		<dc:creator>Chris Baker</dc:creator>
		<pubDate>Wed, 07 Oct 2009 07:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-210</guid>
		<description>That was brilliant Hayden. Who is Saussure?</description>
		<content:encoded><![CDATA[<p>That was brilliant Hayden. Who is Saussure?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Wieck</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-209</link>
		<dc:creator>Sam Wieck</dc:creator>
		<pubDate>Mon, 05 Oct 2009 23:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-209</guid>
		<description>Not at all, I think those two absolutes, success and failure, are almost mythical.

My best guess at things, is that there&#039;s a &#039;Continuum of Quality&#039; but it&#039;s very rare, if not impossible, to reach either end.

There&#039;s always going to be someone, somewhere for whom the design is a failure, and vice versa.</description>
		<content:encoded><![CDATA[<p>Not at all, I think those two absolutes, success and failure, are almost mythical.</p>
<p>My best guess at things, is that there&#8217;s a &#8216;Continuum of Quality&#8217; but it&#8217;s very rare, if not impossible, to reach either end.</p>
<p>There&#8217;s always going to be someone, somewhere for whom the design is a failure, and vice versa.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hayden Raw</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-208</link>
		<dc:creator>Hayden Raw</dc:creator>
		<pubDate>Thu, 01 Oct 2009 19:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-208</guid>
		<description>Ellatron, James, Sam, Shaun... What are your thoughts around measuring the success of design as a product or architecture? Is it as simple as success or fail?</description>
		<content:encoded><![CDATA[<p>Ellatron, James, Sam, Shaun&#8230; What are your thoughts around measuring the success of design as a product or architecture? Is it as simple as success or fail?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shaun Lee</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-207</link>
		<dc:creator>Shaun Lee</dc:creator>
		<pubDate>Thu, 01 Oct 2009 18:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-207</guid>
		<description>I guess communication can also come from other senses - eg the feel of the chair. As a web designer myself I think usability is largely about communication too. Performance is communicating fast, Stability and Accessibility is just communicating to everyone etc.

Tho I prefer &quot;experience design&quot; if I am looking for an umbrella term, it helps remind me that my work has a bigger context.</description>
		<content:encoded><![CDATA[<p>I guess communication can also come from other senses &#8211; eg the feel of the chair. As a web designer myself I think usability is largely about communication too. Performance is communicating fast, Stability and Accessibility is just communicating to everyone etc.</p>
<p>Tho I prefer &#8220;experience design&#8221; if I am looking for an umbrella term, it helps remind me that my work has a bigger context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hayden Raw</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-206</link>
		<dc:creator>Hayden Raw</dc:creator>
		<pubDate>Thu, 01 Oct 2009 17:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-206</guid>
		<description>You&#039;re right guys, product design and the idea of communication don&#039;t sit well together but I don&#039;t think they are completely absent of each other.

For the Eames chairs, and possibly any product, the communication comes at an earlier point in the design process. Design communication goes between the designer and the customer and less between the customer and their counterparts. One of the primary objectives when designing a product is to sell them. How can we sell lots of units? One way is by designing a great product that communicates its benefits clearly.

In product design the communication gets embodied within the form and function of the product... Is this chair more comfortable than any other? Will it provide health benefits for the user? Does this design suit my decor? Will it be worth the extra money? These are the questions that the customer will be asking themselves at the time of purchase; these are the questions Charles Eames has to communicate answers to through his designs.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right guys, product design and the idea of communication don&#8217;t sit well together but I don&#8217;t think they are completely absent of each other.</p>
<p>For the Eames chairs, and possibly any product, the communication comes at an earlier point in the design process. Design communication goes between the designer and the customer and less between the customer and their counterparts. One of the primary objectives when designing a product is to sell them. How can we sell lots of units? One way is by designing a great product that communicates its benefits clearly.</p>
<p>In product design the communication gets embodied within the form and function of the product&#8230; Is this chair more comfortable than any other? Will it provide health benefits for the user? Does this design suit my decor? Will it be worth the extra money? These are the questions that the customer will be asking themselves at the time of purchase; these are the questions Charles Eames has to communicate answers to through his designs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James McGoram</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-205</link>
		<dc:creator>James McGoram</dc:creator>
		<pubDate>Thu, 01 Oct 2009 08:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-205</guid>
		<description>I don&#039;t know if I agree with you about communication, but perhaps that is because I come from an architectural background myself.

I like Sam&#039;s reference to Eames. To quote that particular architect: &quot;Design is the appropriate combination of materials in order to solve a problem.&quot;

That problem is not always about communication but sometimes about security, performance, stability, access, longevity, fitness for purpose etc. - which I feel is as true for (in my case) web designers, as it is for product design.

Perhaps this is where web design parts ways with graphic design, and holds hands with product designers ;)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if I agree with you about communication, but perhaps that is because I come from an architectural background myself.</p>
<p>I like Sam&#8217;s reference to Eames. To quote that particular architect: &#8220;Design is the appropriate combination of materials in order to solve a problem.&#8221;</p>
<p>That problem is not always about communication but sometimes about security, performance, stability, access, longevity, fitness for purpose etc. &#8211; which I feel is as true for (in my case) web designers, as it is for product design.</p>
<p>Perhaps this is where web design parts ways with graphic design, and holds hands with product designers ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Wieck</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-204</link>
		<dc:creator>Sam Wieck</dc:creator>
		<pubDate>Wed, 30 Sep 2009 20:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-204</guid>
		<description>After reading &#039;What is a designer?&#039; by Norman Potter, I&#039;ve been wont to try and keep all &#039;design&#039; bundled together for as long as possible in an attempt to find those &#039;universal truths&#039; of design.

I can see how it&#039;s not exactly relevant in this discussion though.</description>
		<content:encoded><![CDATA[<p>After reading &#8216;What is a designer?&#8217; by Norman Potter, I&#8217;ve been wont to try and keep all &#8216;design&#8217; bundled together for as long as possible in an attempt to find those &#8216;universal truths&#8217; of design.</p>
<p>I can see how it&#8217;s not exactly relevant in this discussion though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ellatron</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-203</link>
		<dc:creator>Ellatron</dc:creator>
		<pubDate>Wed, 30 Sep 2009 04:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-203</guid>
		<description>That is the crossroad where graphic design and furniture / product design can part ways. I think graphic design is about communication; that essentially why it exists, isn&#039;t it?</description>
		<content:encoded><![CDATA[<p>That is the crossroad where graphic design and furniture / product design can part ways. I think graphic design is about communication; that essentially why it exists, isn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Wieck</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-202</link>
		<dc:creator>Sam Wieck</dc:creator>
		<pubDate>Wed, 30 Sep 2009 01:33:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-202</guid>
		<description>I agree with you Brendan, but not in all cases.

I think there is a lot to be said for coded designs. People like to solve puzzles, there&#039;s a satisfaction within that. I am not saying that kind of design is appropriate for all projects. In reality, it only serves a few, and requires really good execution.

I don&#039;t think design always deals with messages and communication either; I don&#039;t get many stories from an Eames chair. Sure they may be bought by someone wishing to convey a message about themselves. But the chair, as an object, is maybe 1% message and 99% comfort.</description>
		<content:encoded><![CDATA[<p>I agree with you Brendan, but not in all cases.</p>
<p>I think there is a lot to be said for coded designs. People like to solve puzzles, there&#8217;s a satisfaction within that. I am not saying that kind of design is appropriate for all projects. In reality, it only serves a few, and requires really good execution.</p>
<p>I don&#8217;t think design always deals with messages and communication either; I don&#8217;t get many stories from an Eames chair. Sure they may be bought by someone wishing to convey a message about themselves. But the chair, as an object, is maybe 1% message and 99% comfort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Jarvis</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-201</link>
		<dc:creator>Brendan Jarvis</dc:creator>
		<pubDate>Mon, 28 Sep 2009 22:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-201</guid>
		<description>Thanks for the mind-food Hayden and Shaun.

Design is a mode of communication where objective understanding should be the primary concern.

A design&#039;s success should be measured by how clearly its intended message was understood by its intended audience. If the message wasn&#039;t understood, or was unclear, then it wasn&#039;t good design.</description>
		<content:encoded><![CDATA[<p>Thanks for the mind-food Hayden and Shaun.</p>
<p>Design is a mode of communication where objective understanding should be the primary concern.</p>
<p>A design&#8217;s success should be measured by how clearly its intended message was understood by its intended audience. If the message wasn&#8217;t understood, or was unclear, then it wasn&#8217;t good design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hayden Raw</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-200</link>
		<dc:creator>Hayden Raw</dc:creator>
		<pubDate>Mon, 28 Sep 2009 21:01:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-200</guid>
		<description>I like your thinking Shaun. I&#039;ve never really tried to equate how much time is associated with communicating through design.

I will have to try it out</description>
		<content:encoded><![CDATA[<p>I like your thinking Shaun. I&#8217;ve never really tried to equate how much time is associated with communicating through design.</p>
<p>I will have to try it out</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shaun Lee</title>
		<link>http://www.designassembly.org.nz/communication-is/comment-page-1#comment-199</link>
		<dc:creator>Shaun Lee</dc:creator>
		<pubDate>Mon, 28 Sep 2009 19:09:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.designassembly.org.nz/?p=719#comment-199</guid>
		<description>We have to communicate stuff to the client, printer, developer and our computer&#039;s as well - designers are transmission hubs.

I reckon on a small budget job 20% of my time will go into unconscious communication (like colour semantics) and on a bigger job it is more like 80%.

Cheers Hayden</description>
		<content:encoded><![CDATA[<p>We have to communicate stuff to the client, printer, developer and our computer&#8217;s as well &#8211; designers are transmission hubs.</p>
<p>I reckon on a small budget job 20% of my time will go into unconscious communication (like colour semantics) and on a bigger job it is more like 80%.</p>
<p>Cheers Hayden</p>
]]></content:encoded>
	</item>
</channel>
</rss>

