<?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: Build your very own seat at the strategy table</title>
	<atom:link href="http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/</link>
	<description>Adaptive Path Blog</description>
	<lastBuildDate>Sat, 20 Mar 2010 07:58:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Livia Labate</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179582</link>
		<dc:creator>Livia Labate</dc:creator>
		<pubDate>Thu, 11 Sep 2008 06:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179582</guid>
		<description>I&#039;m totally with Austin on this. It&#039;s not really &quot;just semantics&quot;. When designers acknowledge that their core contribution is modeling, I find it that it actually helps at &#039;being at the strategy table&#039; because if you are focused on modeling, you are primarily concerned with the outcome that the &#039;final product&#039; will produce -- which is very aligned with what &#039;strategy&#039; means in essence. It doesn&#039;t mean you aren&#039;t making things any less, it&#039;s more of a frame of mind that helps frame the conversation in a way that doesn&#039;t engage designers in self-defeating conversations like &quot;I&#039;m only doing tactical stuff, I never get to do any strategy work&quot;.</description>
		<content:encoded><![CDATA[<p>I&#8217;m totally with Austin on this. It&#8217;s not really &#8220;just semantics&#8221;. When designers acknowledge that their core contribution is modeling, I find it that it actually helps at &#8216;being at the strategy table&#8217; because if you are focused on modeling, you are primarily concerned with the outcome that the &#8216;final product&#8217; will produce &#8212; which is very aligned with what &#8217;strategy&#8217; means in essence. It doesn&#8217;t mean you aren&#8217;t making things any less, it&#8217;s more of a frame of mind that helps frame the conversation in a way that doesn&#8217;t engage designers in self-defeating conversations like &#8220;I&#8217;m only doing tactical stuff, I never get to do any strategy work&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Austin Govella</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179580</link>
		<dc:creator>Austin Govella</dc:creator>
		<pubDate>Thu, 11 Sep 2008 04:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179580</guid>
		<description>A while back Victor Lombardi framed design as a discipline that makes models that others use to make things, and I think that&#039;s very true.

We don&#039;t make things. We make models of things.

(I know I&#039;m poking at semantics, here, but I think this is a really, really, really important distinction to remember. It really affects and changes how we approach everything.)</description>
		<content:encoded><![CDATA[<p>A while back Victor Lombardi framed design as a discipline that makes models that others use to make things, and I think that&#8217;s very true.</p>
<p>We don&#8217;t make things. We make models of things.</p>
<p>(I know I&#8217;m poking at semantics, here, but I think this is a really, really, really important distinction to remember. It really affects and changes how we approach everything.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Hinton</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179578</link>
		<dc:creator>Andrew Hinton</dc:creator>
		<pubDate>Wed, 10 Sep 2008 18:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179578</guid>
		<description>Kate: This is great! (I went somewhat into this headspace a while back with a post on Strategy vs Innovation, I&#039;d love to know what you think of it: http://tinyurl.com/5ptvq4).  Your post sharpens something I hadn&#039;t really focused on yet, though: that practitioners&#039; best work is at the level of practice. They make things, and they make things better, based on the concrete experience of the things themselves. The strategy table, however, has traditionally been populated by those who are pretty far removed from the street-level effects of their decisions, working from the level of ideology. (Not that it&#039;s a bad thing -- most ideology is the result of learned wisdom over time, it just gets too calcified and/or used in the wrong context at times.) This is one reason why so many strategists love data rather than first-hand experience: they can (too often) see the data however they need to, based on whatever ideological glasses they&#039;re wearing. 
When designers leave the context of hands-on, concrete problem solving and try to mix it up with the abstraction/ideology crowd, they&#039;re no longer in their element. So they have to *bring* their element along with them. Take that concrete, messy, human design problem, and drop it on the table with a *thud* -- just be ready to have some &quot;data&quot; and business speak ready to translate for the audience. 
It&#039;s too bad that so many folks are getting tied up in semantic dogfights about  &quot;design&quot; -- but it&#039;s unavoidable, I guess, given how deeply people&#039;s identities are wrapped up in the word.</description>
		<content:encoded><![CDATA[<p>Kate: This is great! (I went somewhat into this headspace a while back with a post on Strategy vs Innovation, I&#8217;d love to know what you think of it: <a href="http://tinyurl.com/5ptvq4)" rel="nofollow">http://tinyurl.com/5ptvq4)</a>.  Your post sharpens something I hadn&#8217;t really focused on yet, though: that practitioners&#8217; best work is at the level of practice. They make things, and they make things better, based on the concrete experience of the things themselves. The strategy table, however, has traditionally been populated by those who are pretty far removed from the street-level effects of their decisions, working from the level of ideology. (Not that it&#8217;s a bad thing &#8212; most ideology is the result of learned wisdom over time, it just gets too calcified and/or used in the wrong context at times.) This is one reason why so many strategists love data rather than first-hand experience: they can (too often) see the data however they need to, based on whatever ideological glasses they&#8217;re wearing.<br />
When designers leave the context of hands-on, concrete problem solving and try to mix it up with the abstraction/ideology crowd, they&#8217;re no longer in their element. So they have to *bring* their element along with them. Take that concrete, messy, human design problem, and drop it on the table with a *thud* &#8212; just be ready to have some &#8220;data&#8221; and business speak ready to translate for the audience.<br />
It&#8217;s too bad that so many folks are getting tied up in semantic dogfights about  &#8220;design&#8221; &#8212; but it&#8217;s unavoidable, I guess, given how deeply people&#8217;s identities are wrapped up in the word.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kate Rutter</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179561</link>
		<dc:creator>Kate Rutter</dc:creator>
		<pubDate>Mon, 08 Sep 2008 08:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179561</guid>
		<description>Thank you all for the interesting and insightful comments. 

Jeffrey, I think we can agree to disagree on some points. But to clarify, I do think there is a difference between 1) designers who talk about strategic design, 2) designers who make things, and 3) the people who are responsible for producing things other people have designed. Perhaps it&#039;s a clarification of language. I do believe that designers who both talk about design and who also actually make things have the greatest power to impact business. I&#039;ve seen too many grand plans fail because they weren&#039;t implemented well, and too many high-minded designs be amazing...but not realistic for real-world implementation. Being engaged in the implementation of a design is crucial to its success. When you&#039;re next in SF, stop by and we can have a beer and wrangle semantics further. ;)

Candice-Leigh: I couldn&#039;t agree more. Being open to changing our thinking and engaging in healthy dialog is key. 

Alex: thanks! 

Joshua: I think you&#039;ve hit something really important: creating an environment for critique and critical assessment and evaluation of design results is an important factor in making designs work. Listening to feedback from customers and responding to market changes are both strategic issues. We&#039;ve been talking about the culture of critique internally, and Peter recently sent out a link to the article in Harvard Business Review about the creative culture at Pixar. Note that this is internal critique approach only, not customer feedback. But it&#039;s a great story about building a culture where delivering the strongest designs/products is the top priority, and where criticism is accepted, expected and welcomed. You can read it here: http://icanhaz.com/pixarcreativity</description>
		<content:encoded><![CDATA[<p>Thank you all for the interesting and insightful comments. </p>
<p>Jeffrey, I think we can agree to disagree on some points. But to clarify, I do think there is a difference between 1) designers who talk about strategic design, 2) designers who make things, and 3) the people who are responsible for producing things other people have designed. Perhaps it&#8217;s a clarification of language. I do believe that designers who both talk about design and who also actually make things have the greatest power to impact business. I&#8217;ve seen too many grand plans fail because they weren&#8217;t implemented well, and too many high-minded designs be amazing&#8230;but not realistic for real-world implementation. Being engaged in the implementation of a design is crucial to its success. When you&#8217;re next in SF, stop by and we can have a beer and wrangle semantics further. <img src='http://www.adaptivepath.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Candice-Leigh: I couldn&#8217;t agree more. Being open to changing our thinking and engaging in healthy dialog is key. </p>
<p>Alex: thanks! </p>
<p>Joshua: I think you&#8217;ve hit something really important: creating an environment for critique and critical assessment and evaluation of design results is an important factor in making designs work. Listening to feedback from customers and responding to market changes are both strategic issues. We&#8217;ve been talking about the culture of critique internally, and Peter recently sent out a link to the article in Harvard Business Review about the creative culture at Pixar. Note that this is internal critique approach only, not customer feedback. But it&#8217;s a great story about building a culture where delivering the strongest designs/products is the top priority, and where criticism is accepted, expected and welcomed. You can read it here: <a href="http://icanhaz.com/pixarcreativity" rel="nofollow">http://icanhaz.com/pixarcreativity</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Porter</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179528</link>
		<dc:creator>Joshua Porter</dc:creator>
		<pubDate>Fri, 29 Aug 2008 13:18:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179528</guid>
		<description>This is an issue of responsibility. When design teams are responsible, they provide constant feedback to the strategy folks...saying &quot;this is working&quot; or &quot;this isn&#039;t working&quot;. And because they&#039;re close to the ground, they might even have a recommendation for improvement...

If all designers do is build and forget to evaluate what they&#039;ve done, then the company flounders for a while until someone catches the usability bug and invites some usability consultant to come in and tell them again why it&#039;s important to focus on people and what they&#039;re actually doing. I worked for a company like this for five years (UIE), and honestly we helped many clients but the problems we saw were so much deeper than one usability study could fix...there was no design team kicking its own ass. There were exceptions, like Netflix, who were self-critical, and thus felt responsible for what they did, and thus didn&#039;t really need usability help. They knew that evaluation was a critical part of design...

Designers who are critical of their own design, who constantly ask how it can be better are the ones who will get a seat at the strategy table. As we all know (at least I hope we do) design is an ongoing process that happens over time. The design once and forget it publishing model just doesn&#039;t work on the web. If you&#039;re creating a template well then that&#039;s fine. But if you&#039;re creating a real application that is of value to people, designers really need to be their own critics. And when designers are their own critics, when they give a damn about how its actually being used, and when they feed that information back into the organization and make visible changes to improve it, people will listen.</description>
		<content:encoded><![CDATA[<p>This is an issue of responsibility. When design teams are responsible, they provide constant feedback to the strategy folks&#8230;saying &#8220;this is working&#8221; or &#8220;this isn&#8217;t working&#8221;. And because they&#8217;re close to the ground, they might even have a recommendation for improvement&#8230;</p>
<p>If all designers do is build and forget to evaluate what they&#8217;ve done, then the company flounders for a while until someone catches the usability bug and invites some usability consultant to come in and tell them again why it&#8217;s important to focus on people and what they&#8217;re actually doing. I worked for a company like this for five years (UIE), and honestly we helped many clients but the problems we saw were so much deeper than one usability study could fix&#8230;there was no design team kicking its own ass. There were exceptions, like Netflix, who were self-critical, and thus felt responsible for what they did, and thus didn&#8217;t really need usability help. They knew that evaluation was a critical part of design&#8230;</p>
<p>Designers who are critical of their own design, who constantly ask how it can be better are the ones who will get a seat at the strategy table. As we all know (at least I hope we do) design is an ongoing process that happens over time. The design once and forget it publishing model just doesn&#8217;t work on the web. If you&#8217;re creating a template well then that&#8217;s fine. But if you&#8217;re creating a real application that is of value to people, designers really need to be their own critics. And when designers are their own critics, when they give a damn about how its actually being used, and when they feed that information back into the organization and make visible changes to improve it, people will listen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Wipf</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179527</link>
		<dc:creator>Alex Wipf</dc:creator>
		<pubDate>Fri, 29 Aug 2008 13:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179527</guid>
		<description>Great idea to offer the blow-out-proportion chair at the table as a DIY prop.

It insprired me to add &lt;a&gt;my two cents&lt;/a&gt;.

Thanks!</description>
		<content:encoded><![CDATA[<p>Great idea to offer the blow-out-proportion chair at the table as a DIY prop.</p>
<p>It insprired me to add <a>my two cents</a>.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pouring oil on an already hot debate of design &#171; Leo Burnett - Cultural Fuel Blog</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179526</link>
		<dc:creator>Pouring oil on an already hot debate of design &#171; Leo Burnett - Cultural Fuel Blog</dc:creator>
		<pubDate>Fri, 29 Aug 2008 13:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179526</guid>
		<description>[...] Says Kate Rutter (Adaptive Path): I hear folks say that design thinking is different from other kind of thinking, and that by infusing design thinking into the strategy of an organization, the business will be more innovative. The perception here is that designers are the hero best suited to use design thinking to pull the innovation sword from the strategy stone. In fact, the more I read about it, the more there is to read about it. Conversation in the blogdom is aswirl with the trifecta of seat at the table + design thinking + innovation. [...]</description>
		<content:encoded><![CDATA[<p>[...] Says Kate Rutter (Adaptive Path): I hear folks say that design thinking is different from other kind of thinking, and that by infusing design thinking into the strategy of an organization, the business will be more innovative. The perception here is that designers are the hero best suited to use design thinking to pull the innovation sword from the strategy stone. In fact, the more I read about it, the more there is to read about it. Conversation in the blogdom is aswirl with the trifecta of seat at the table + design thinking + innovation. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candice-Leigh Baumgardner</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179523</link>
		<dc:creator>Candice-Leigh Baumgardner</dc:creator>
		<pubDate>Thu, 28 Aug 2008 22:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179523</guid>
		<description>Designers want a seat at the table because (in the world of product development) Marketing has traditionally leaned on what has worked in the past as a means to address the needs of the future.  Ask any designer (heck, any design student!) and he or she will tell you this is just plain wrong.  Especially if the goal is innovation.  I think designers are right to want to participate in, guide, and change the nature of the Business dialogue.  Of course, sitting at the table is only the first step.  Now Design and Marketing have to learn how to talk to one another, and to be open to hearing new perspectives.  A fruitful discussion will result when both sides agree on the objective and open their minds to fresh thinking and true collaboration.</description>
		<content:encoded><![CDATA[<p>Designers want a seat at the table because (in the world of product development) Marketing has traditionally leaned on what has worked in the past as a means to address the needs of the future.  Ask any designer (heck, any design student!) and he or she will tell you this is just plain wrong.  Especially if the goal is innovation.  I think designers are right to want to participate in, guide, and change the nature of the Business dialogue.  Of course, sitting at the table is only the first step.  Now Design and Marketing have to learn how to talk to one another, and to be open to hearing new perspectives.  A fruitful discussion will result when both sides agree on the objective and open their minds to fresh thinking and true collaboration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeffrey Dachis</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179521</link>
		<dc:creator>Jeffrey Dachis</dc:creator>
		<pubDate>Thu, 28 Aug 2008 17:03:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179521</guid>
		<description>Interesting post.  Thanks.

Although, as you reference it, I think you are undervaluing Design with a capital D or overvaluing design/implementation.

Design isnt about implementation. Designers who just &quot;make things&quot; dont really deserve a seat at the big table.  

My sense is that Designers who are strategic thinkers wanting to apply that thinking to a specific business outcome are required to achieve that outcome and need to be at the table, and businesses need them to be there.  

Unfortunately, Design is too often thought of in tactical terms, commoditized, and then relegated to the kids table.

I dont think that is what youre advocating, yet your advice seems to indicate an assumption that somehow implementation skills are equal to Design skills and they just aren&#039;t.

Designers need a seat at the table, designers do not.</description>
		<content:encoded><![CDATA[<p>Interesting post.  Thanks.</p>
<p>Although, as you reference it, I think you are undervaluing Design with a capital D or overvaluing design/implementation.</p>
<p>Design isnt about implementation. Designers who just &#8220;make things&#8221; dont really deserve a seat at the big table.  </p>
<p>My sense is that Designers who are strategic thinkers wanting to apply that thinking to a specific business outcome are required to achieve that outcome and need to be at the table, and businesses need them to be there.  </p>
<p>Unfortunately, Design is too often thought of in tactical terms, commoditized, and then relegated to the kids table.</p>
<p>I dont think that is what youre advocating, yet your advice seems to indicate an assumption that somehow implementation skills are equal to Design skills and they just aren&#8217;t.</p>
<p>Designers need a seat at the table, designers do not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kate Rutter</title>
		<link>http://www.adaptivepath.com/blog/2008/08/27/build-your-very-own-seat-at-the-strategy-table/comment-page-1/#comment-179520</link>
		<dc:creator>Kate Rutter</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:53:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.adaptivepath.com/blog/?p=1178#comment-179520</guid>
		<description>Michael: I totally agree that the current rules of business are different. I do wonder tho, if they are really so very different from the ways of making great things (the key here is *great*.) I hope that somewhere among the pathways for making great things and making great businesses, we can find the shared ground on how the two intertwine, so that we don&#039;t end up in an &quot;either-or&quot; situation.

Either-or choices smell like ultimatums. I think they are often the best indicator that thinking is trapped and we need to find another way.</description>
		<content:encoded><![CDATA[<p>Michael: I totally agree that the current rules of business are different. I do wonder tho, if they are really so very different from the ways of making great things (the key here is *great*.) I hope that somewhere among the pathways for making great things and making great businesses, we can find the shared ground on how the two intertwine, so that we don&#8217;t end up in an &#8220;either-or&#8221; situation.</p>
<p>Either-or choices smell like ultimatums. I think they are often the best indicator that thinking is trapped and we need to find another way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
