<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Design Thought Leader &#187; Problem Solving</title>
	<atom:link href="http://www.designthoughtleader.com/labels/problem-solving/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designthoughtleader.com</link>
	<description>A world of ideas from across the web</description>
	<lastBuildDate>Tue, 27 Jul 2010 12:57:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Kit Hinrichs on Problem Solving</title>
		<link>http://www.designthoughtleader.com/2009/06/hinrichs-problem-solving/</link>
		<comments>http://www.designthoughtleader.com/2009/06/hinrichs-problem-solving/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 15:25:05 +0000</pubDate>
		<dc:creator>Nate Burgos</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[Problem Solving]]></category>

		<guid isPermaLink="false">http://www.designthoughtleader.com/?p=469</guid>
		<description><![CDATA[<p>When we’re all put on this earth. We start out as visual people; language comes later, as a coding learned along the way. As you go through the education process, early on you’re more likely to look at pictures in books and learn visually—you take it all in, you see everything. Then as you begin to code things in words, it makes everything more linear and specific. At some point, within our education system, it seems like we shift from a balance of right and left hand brain, to being very left brain. The consequence of this is, if you&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>When we’re all put on this earth. We start out as visual people; language comes later, as a coding learned along the way. As you go through the education process, early on you’re more likely to look at pictures in books and learn visually—you take it all in, you see everything. Then as you begin to code things in words, it makes everything more linear and specific. At some point, within our education system, it seems like we shift from a balance of right and left hand brain, to being very left brain. The consequence of this is, if you go through all the important books they are really image free, they’re all words. But designers keep looking at the whole picture. I think this is the reason why designers are so welcome in the boardrooms of corporations. Businesspeople have been kind of brainwashed out of solving problems in anything other than a linear approach. But sometimes, we need both sides of the brain to solve problems. Which is why I find that there are times I can go into a boardroom with guys who have degrees from 12 universities I could never get into, and help them look at a problem in a new way. Once the problem is described, the designer is more likely to say, ‘Well, did you look at this? How about doing it this way?’ It&#8217;s about not adhering to a set of restrictions that have defined how you think in business. Designers don’t follow that same book of rules.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.designthoughtleader.com/2009/06/hinrichs-problem-solving/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cameron Moll on Problem Solving</title>
		<link>http://www.designthoughtleader.com/2009/03/moll-problem-solving/</link>
		<comments>http://www.designthoughtleader.com/2009/03/moll-problem-solving/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 13:30:35 +0000</pubDate>
		<dc:creator>Nate Burgos</dc:creator>
				<category><![CDATA[Short Post]]></category>
		<category><![CDATA[Problem Solving]]></category>

		<guid isPermaLink="false">http://www.designthoughtleader.com/?p=268</guid>
		<description><![CDATA[<p><a href="http://twitter.com/cameronmoll/status/1149502127"><img class="alignnone size-full wp-image-267" title="add-quote_problemsolving_030509" src="http://www.designthoughtleader.com/wp-content/uploads/2009/03/add-quote_problemsolving_030509.gif" alt="add-quote_problemsolving_030509" width="519" height="88" /></a></p>
<p>Tweet by <a href="http://www.cameronmoll.com" target="_blank">Cameron Moll</a>, Designer, Author, Speaker</p>
]]></description>
			<content:encoded><![CDATA[<p><a href="http://twitter.com/cameronmoll/status/1149502127"><img class="alignnone size-full wp-image-267" title="add-quote_problemsolving_030509" src="http://www.designthoughtleader.com/wp-content/uploads/2009/03/add-quote_problemsolving_030509.gif" alt="add-quote_problemsolving_030509" width="519" height="88" /></a></p>
<p>Tweet by <a href="http://www.cameronmoll.com" target="_blank">Cameron Moll</a>, Designer, Author, Speaker</p>
]]></content:encoded>
			<wfw:commentRss>http://www.designthoughtleader.com/2009/03/moll-problem-solving/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Saul Bass on Problem Solving</title>
		<link>http://www.designthoughtleader.com/2009/03/bass-problem-solving/</link>
		<comments>http://www.designthoughtleader.com/2009/03/bass-problem-solving/#comments</comments>
		<pubDate>Sat, 07 Mar 2009 14:30:07 +0000</pubDate>
		<dc:creator>Nate Burgos</dc:creator>
				<category><![CDATA[Quote]]></category>
		<category><![CDATA[Problem Solving]]></category>

		<guid isPermaLink="false">http://www.designthoughtleader.com/?p=214</guid>
		<description><![CDATA[<p>A client comes to you with a definition of the problem, or ideas about what they want to accomplish. Sometimes they have a sophisticated view of it, sometimes they don’t. I find myself frequently spending time with the client redefining the problem, backing up, going back to the beginning. Not infrequently the ‘problem’ turns out to be the ‘symptom.’ You have to sometimes move back, in order to move forward to really understand what the nature of the solution should be.</p>
]]></description>
			<content:encoded><![CDATA[<p>A client comes to you with a definition of the problem, or ideas about what they want to accomplish. Sometimes they have a sophisticated view of it, sometimes they don’t. I find myself frequently spending time with the client redefining the problem, backing up, going back to the beginning. Not infrequently the ‘problem’ turns out to be the ‘symptom.’ You have to sometimes move back, in order to move forward to really understand what the nature of the solution should be.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.designthoughtleader.com/2009/03/bass-problem-solving/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
