<?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: Observations on Designers</title>
	<atom:link href="http://johnnyholland.org/2009/11/observations-on-designers/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnnyholland.org/2009/11/observations-on-designers/</link>
	<description>It&#039;s all about interaction</description>
	<lastBuildDate>Wed, 05 Jun 2013 06:03:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: It&#8217;s not about new ideas, it&#8217;s about getting new ideas made&#8230;. &#171; User Experience Design Life</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109655</link>
		<dc:creator>It&#8217;s not about new ideas, it&#8217;s about getting new ideas made&#8230;. &#171; User Experience Design Life</dc:creator>
		<pubDate>Fri, 18 Dec 2009 20:19:45 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109655</guid>
		<description>[...] (A great foray into another post: Observations on Designers) [...]</description>
		<content:encoded><![CDATA[<p>[...] (A great foray into another post: Observations on Designers) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interact Seattle &#187; Blog Archive &#187; User eXperience (UX) Digest #4</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109654</link>
		<dc:creator>Interact Seattle &#187; Blog Archive &#187; User eXperience (UX) Digest #4</dc:creator>
		<pubDate>Mon, 23 Nov 2009 22:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109654</guid>
		<description>[...] Great creativity comes from a great team, not great things. [...]</description>
		<content:encoded><![CDATA[<p>[...] Great creativity comes from a great team, not great things. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: User eXperience (UX) Digest #4 &#171; Chasing the Dream</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109653</link>
		<dc:creator>User eXperience (UX) Digest #4 &#171; Chasing the Dream</dc:creator>
		<pubDate>Mon, 23 Nov 2009 22:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109653</guid>
		<description>[...] Great creativity comes from a great team, not great things. [...]</description>
		<content:encoded><![CDATA[<p>[...] Great creativity comes from a great team, not great things. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanael Boehm</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109652</link>
		<dc:creator>Nathanael Boehm</dc:creator>
		<pubDate>Mon, 23 Nov 2009 06:38:07 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109652</guid>
		<description>Designers are no more creative than anyone else in a team — they just might spend more time creating than others. Programmers, project managers, team leaders, copywriters, system admins ... they all have to be creative to do their job so putting designers up on this &quot;creative&quot; pedestal and catering to designer divas with fancy office furniture is ridiculous!

Disclaimer: I&#039;ve only ever worked in a grey box cubicle so I *may* be slightly jealous of those who get to work somewhere cool.

While working with peers is very important you&#039;re not going to be able to develop a fully-considered design without including others and everyone, *everyone* has something to contribute. So get out and see the world - as it were.

Good article.

Nathanael
UX designer</description>
		<content:encoded><![CDATA[<p>Designers are no more creative than anyone else in a team — they just might spend more time creating than others. Programmers, project managers, team leaders, copywriters, system admins &#8230; they all have to be creative to do their job so putting designers up on this &#8220;creative&#8221; pedestal and catering to designer divas with fancy office furniture is ridiculous!</p>
<p>Disclaimer: I&#8217;ve only ever worked in a grey box cubicle so I *may* be slightly jealous of those who get to work somewhere cool.</p>
<p>While working with peers is very important you&#8217;re not going to be able to develop a fully-considered design without including others and everyone, *everyone* has something to contribute. So get out and see the world &#8211; as it were.</p>
<p>Good article.</p>
<p>Nathanael<br />
UX designer</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dbrondeau</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109651</link>
		<dc:creator>dbrondeau</dc:creator>
		<pubDate>Tue, 17 Nov 2009 15:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109651</guid>
		<description>I couldn&#039;t agree more with the need for teams to be more inclusive and not designers-only. Where I work, the majority of our projects have what we call &quot;hybrid&quot; teams. That means the design team is comprised of 2 designers from our company and 2-3 people from the client company. In my experience, you always get a much wider range of creativity when you include people with different roles and experiences.

I&#039;ve also been humbled many a time by a client team member who has no &quot;design&quot; experience, yet comes up with such a great idea that I can only say, &quot;I wish I had thought of that.&quot;

So naturally,I also disagree with the opinion that &quot;finding great ideas anywhere&quot; is the exception. I believe that if you give the people on your design team the right data to design from and a clear process for designing—that you will always find great ideas.

One last thought: you should also consider the composition of your all-inclusive team. Be careful that you don&#039;t fill it with experts only; try to also include people who are cross-functional with broader backgrounds and experiences. They make excellent cross-pollinators and will enhance innovation, in contrast to a team of all &quot;experts&quot;, each with their own narrow experience. You can read more about this idea at http://incontextdesign.com/blog/t-shaped-teams/</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more with the need for teams to be more inclusive and not designers-only. Where I work, the majority of our projects have what we call &#8220;hybrid&#8221; teams. That means the design team is comprised of 2 designers from our company and 2-3 people from the client company. In my experience, you always get a much wider range of creativity when you include people with different roles and experiences.</p>
<p>I&#8217;ve also been humbled many a time by a client team member who has no &#8220;design&#8221; experience, yet comes up with such a great idea that I can only say, &#8220;I wish I had thought of that.&#8221;</p>
<p>So naturally,I also disagree with the opinion that &#8220;finding great ideas anywhere&#8221; is the exception. I believe that if you give the people on your design team the right data to design from and a clear process for designing—that you will always find great ideas.</p>
<p>One last thought: you should also consider the composition of your all-inclusive team. Be careful that you don&#8217;t fill it with experts only; try to also include people who are cross-functional with broader backgrounds and experiences. They make excellent cross-pollinators and will enhance innovation, in contrast to a team of all &#8220;experts&#8221;, each with their own narrow experience. You can read more about this idea at <a href="http://incontextdesign.com/blog/t-shaped-teams/" rel="nofollow">http://incontextdesign.com/blog/t-shaped-teams/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#171;&#160;Observations on designers&#160;&#187;</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109650</link>
		<dc:creator>&#171;&#160;Observations on designers&#160;&#187;</dc:creator>
		<pubDate>Fri, 13 Nov 2009 01:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109650</guid>
		<description>[...] un article très intéressant concernant le designer, ses clichés et l&#8217;ouverture de la [...]</description>
		<content:encoded><![CDATA[<p>[...] un article très intéressant concernant le designer, ses clichés et l&#8217;ouverture de la [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Fletcher</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109649</link>
		<dc:creator>Joe Fletcher</dc:creator>
		<pubDate>Thu, 12 Nov 2009 07:36:17 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109649</guid>
		<description>@Stinermas - you own a Starck juicer don&#039;t you? :D
Actually one of the key points was the irony in the way designers can complain. Not about mediocre ideas. I forget who the quote was from, but I remember someone mentioning how most of the time we don’t create anything new, we just slightly change things. So of course it’s nothing new.</description>
		<content:encoded><![CDATA[<p>@Stinermas &#8211; you own a Starck juicer don&#8217;t you? <img src='http://johnnyholland.org/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /><br />
Actually one of the key points was the irony in the way designers can complain. Not about mediocre ideas. I forget who the quote was from, but I remember someone mentioning how most of the time we don’t create anything new, we just slightly change things. So of course it’s nothing new.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stinermas</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109648</link>
		<dc:creator>Stinermas</dc:creator>
		<pubDate>Thu, 12 Nov 2009 07:15:30 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109648</guid>
		<description>There&#039;s nothing new about this. The mediocre idea with great execution wins over the great idea with mediocre execution. 1% inspiration, blah blah blah.</description>
		<content:encoded><![CDATA[<p>There&#8217;s nothing new about this. The mediocre idea with great execution wins over the great idea with mediocre execution. 1% inspiration, blah blah blah.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Fletcher</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109647</link>
		<dc:creator>Joe Fletcher</dc:creator>
		<pubDate>Wed, 11 Nov 2009 19:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109647</guid>
		<description>@Auke - good point. I&#039;m torn on specs. On one hand they get out of date, but on the opposite side, when you work at Microsoft, you have a lot of testers/QA that need to know what to test. You can&#039;t loop in everyone all the time, so at points documentation is not only good, but essential.

@Leigh - I know what you&#039;re saying on the philosophy aspect. I&#039;d say great ideas are often like coal in a way. Everyone can have them, but they&#039;re probably unrefined and a mess. That&#039;s where design &amp; marketing can come in to help to a story. Being in marketing you should know there are tons of great ideas, but telling the story is what sells it. I also have a feeling that other disciplines can&#039;t communicate as well. So when they have a good idea, it&#039;s hard to explain. The other thing I&#039;ve seen is someone will have a good idea that doesn’t relate to anything you&#039;re doing.
&quot;Ok, how&#039;s the campaign on shirts coming&quot;
&quot;What if you froze orange juice into a popsicle&quot;
...wrong timing... which again, being in marketing, timing has a lot to do with success :)

@Jeffie - calm down and have an ambien :D</description>
		<content:encoded><![CDATA[<p>@Auke &#8211; good point. I&#8217;m torn on specs. On one hand they get out of date, but on the opposite side, when you work at Microsoft, you have a lot of testers/QA that need to know what to test. You can&#8217;t loop in everyone all the time, so at points documentation is not only good, but essential.</p>
<p>@Leigh &#8211; I know what you&#8217;re saying on the philosophy aspect. I&#8217;d say great ideas are often like coal in a way. Everyone can have them, but they&#8217;re probably unrefined and a mess. That&#8217;s where design &#038; marketing can come in to help to a story. Being in marketing you should know there are tons of great ideas, but telling the story is what sells it. I also have a feeling that other disciplines can&#8217;t communicate as well. So when they have a good idea, it&#8217;s hard to explain. The other thing I&#8217;ve seen is someone will have a good idea that doesn’t relate to anything you&#8217;re doing.<br />
&#8220;Ok, how&#8217;s the campaign on shirts coming&#8221;<br />
&#8220;What if you froze orange juice into a popsicle&#8221;<br />
&#8230;wrong timing&#8230; which again, being in marketing, timing has a lot to do with success <img src='http://johnnyholland.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@Jeffie &#8211; calm down and have an ambien <img src='http://johnnyholland.org/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffie</title>
		<link>http://johnnyholland.org/2009/11/observations-on-designers/#comment-109646</link>
		<dc:creator>Jeffie</dc:creator>
		<pubDate>Wed, 11 Nov 2009 18:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://johnnyholland.org/?p=4376#comment-109646</guid>
		<description>Joe, if I EVER catch you bad mouthing having a great coffee machine in the office again, there will be trouble...</description>
		<content:encoded><![CDATA[<p>Joe, if I EVER catch you bad mouthing having a great coffee machine in the office again, there will be trouble&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
