<?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: Designing Design Teams</title>
	<atom:link href="http://jamin.org/archives/2008/designing-design-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://jamin.org/archives/2008/designing-design-teams/</link>
	<description>Jamin Hegeman on design, writing, and life</description>
	<lastBuildDate>Thu, 04 Mar 2010 18:54:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom Key</title>
		<link>http://jamin.org/archives/2008/designing-design-teams/comment-page-1/#comment-68373</link>
		<dc:creator>Tom Key</dc:creator>
		<pubDate>Tue, 06 May 2008 01:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://jamin.org/archives/2008/designing-design-teams/#comment-68373</guid>
		<description>Hi Jamin,
Can I encourage your thinking by saying that it [creating design teams within organizations as our main mission] is not just &quot;an academic exercise&quot;. This is what 2nd Road does, and there are many stories we can tell you from the front line. We combine basic design training with a &#039;do and learn&#039; approach on real organizational projects. In summary - the people love it, the management push against it. It&#039;s where the rivers of Design and Culture hit head on - the rapids are rough but exciting...</description>
		<content:encoded><![CDATA[<p>Hi Jamin,<br />
Can I encourage your thinking by saying that it [creating design teams within organizations as our main mission] is not just &#8220;an academic exercise&#8221;. This is what 2nd Road does, and there are many stories we can tell you from the front line. We combine basic design training with a &#8216;do and learn&#8217; approach on real organizational projects. In summary &#8211; the people love it, the management push against it. It&#8217;s where the rivers of Design and Culture hit head on &#8211; the rapids are rough but exciting&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jamin</title>
		<link>http://jamin.org/archives/2008/designing-design-teams/comment-page-1/#comment-66891</link>
		<dc:creator>Jamin</dc:creator>
		<pubDate>Tue, 15 Apr 2008 05:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://jamin.org/archives/2008/designing-design-teams/#comment-66891</guid>
		<description>Great point. I agree, design firms already act as mentors or management consultants. I did this myself when working with my clients before graduate school. Education was a big component of what I provided. And I know many other smaller design firms that establish this kind of relationship with their clients. Still, many others do not handle education so well, or don&#039;t even try.

But to clarify, what we were discussing was creating design teams within organizations as our main mission. We would not just educate or mentor clients as we worked with them to design a traditional product or service. Our service would be to help put together an internal design team that would sustain itself. We would then mentor that design team. However, they would be the ones providing design services to the organization. 

As a possible strategy to transition to this from design traditional products and services, we considered allowing people to work on one of our teams for a project not related or in association with their company. So it would start off, perhaps, as education by doing alongside us. Then, as that program became a success, we might be able to transition to creating design teams within organizations instead of having individuals come to us.

This is all an academic exercise. But I still thought the idea was intriguing.</description>
		<content:encoded><![CDATA[<p>Great point. I agree, design firms already act as mentors or management consultants. I did this myself when working with my clients before graduate school. Education was a big component of what I provided. And I know many other smaller design firms that establish this kind of relationship with their clients. Still, many others do not handle education so well, or don&#8217;t even try.</p>
<p>But to clarify, what we were discussing was creating design teams within organizations as our main mission. We would not just educate or mentor clients as we worked with them to design a traditional product or service. Our service would be to help put together an internal design team that would sustain itself. We would then mentor that design team. However, they would be the ones providing design services to the organization. </p>
<p>As a possible strategy to transition to this from design traditional products and services, we considered allowing people to work on one of our teams for a project not related or in association with their company. So it would start off, perhaps, as education by doing alongside us. Then, as that program became a success, we might be able to transition to creating design teams within organizations instead of having individuals come to us.</p>
<p>This is all an academic exercise. But I still thought the idea was intriguing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Jones</title>
		<link>http://jamin.org/archives/2008/designing-design-teams/comment-page-1/#comment-66882</link>
		<dc:creator>Peter Jones</dc:creator>
		<pubDate>Tue, 15 Apr 2008 01:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://jamin.org/archives/2008/designing-design-teams/#comment-66882</guid>
		<description>Many designers do this already - I consider it part of the job of consulting. Perhaps because I view design consulting more like management consulting than &quot;design delivery,&quot; I stay very close to my long term clients. I&#039;ve done this since 2001 as a small research/design consulting firm, and have noticed that smaller consulting firms have always done this. Its the larger firms like IDEO that have to formalize a process for customer intimacy - but when you&#039;re already close to your client, you nurture them in many ways outside of the contractual relationship. 

A problem with larger design agencies is they cannot afford to seat their better designers or advisors with clients in a mentoring capacity, and their rate structure won&#039;t easily allow them to give up the time. If we all did a better job of educating the client while working on projects, this would not seem a novel idea but par for the course. We also need to realize that better transition planning (the deliverables handoff from design to development) will reduce the need for mitigating turmoil in the client&#039;s implementation of our design plans.</description>
		<content:encoded><![CDATA[<p>Many designers do this already &#8211; I consider it part of the job of consulting. Perhaps because I view design consulting more like management consulting than &#8220;design delivery,&#8221; I stay very close to my long term clients. I&#8217;ve done this since 2001 as a small research/design consulting firm, and have noticed that smaller consulting firms have always done this. Its the larger firms like IDEO that have to formalize a process for customer intimacy &#8211; but when you&#8217;re already close to your client, you nurture them in many ways outside of the contractual relationship. </p>
<p>A problem with larger design agencies is they cannot afford to seat their better designers or advisors with clients in a mentoring capacity, and their rate structure won&#8217;t easily allow them to give up the time. If we all did a better job of educating the client while working on projects, this would not seem a novel idea but par for the course. We also need to realize that better transition planning (the deliverables handoff from design to development) will reduce the need for mitigating turmoil in the client&#8217;s implementation of our design plans.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
  
