<?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: &#8216;Made to Stick&#8217; Cover Design</title>
	<atom:link href="http://zug.flathatter.com/made-to-stick-cover-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://zug.flathatter.com/made-to-stick-cover-design/</link>
	<description>Bryan Zug's blog on interactive development and the art of thriving in a world of change.</description>
	<pubDate>Sun, 05 Jul 2009 02:49:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John</title>
		<link>http://zug.flathatter.com/made-to-stick-cover-design/comment-page-1/#comment-16982</link>
		<dc:creator>John</dc:creator>
		<pubDate>Wed, 11 Apr 2007 15:54:31 +0000</pubDate>
		<guid isPermaLink="false">http://elearningskinny.com/made-to-stick-cover-design/#comment-16982</guid>
		<description>I'm a university prof myself and couldn't agree more.  As faculty, are we interested in how much we teach or how much students LEARN.  For me, it's about learning, and so making sure that there's a "sticky" side to knowledge is vital--a core competency--to being an educator.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a university prof myself and couldn&#8217;t agree more.  As faculty, are we interested in how much we teach or how much students LEARN.  For me, it&#8217;s about learning, and so making sure that there&#8217;s a &#8220;sticky&#8221; side to knowledge is vital&#8211;a core competency&#8211;to being an educator.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Zug</title>
		<link>http://zug.flathatter.com/made-to-stick-cover-design/comment-page-1/#comment-7112</link>
		<dc:creator>Bryan Zug</dc:creator>
		<pubDate>Wed, 21 Feb 2007 15:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://elearningskinny.com/made-to-stick-cover-design/#comment-7112</guid>
		<description>&gt;&gt;
I’M HELPING MY CLIENT UNDERSTAND.
&gt;&gt;

exactly.</description>
		<content:encoded><![CDATA[<blockquote>
<p>><br />
  I’M HELPING MY CLIENT UNDERSTAND.<br />
  ></p>
</blockquote>
<p>exactly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://zug.flathatter.com/made-to-stick-cover-design/comment-page-1/#comment-6777</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Sun, 18 Feb 2007 23:57:48 +0000</pubDate>
		<guid isPermaLink="false">http://elearningskinny.com/made-to-stick-cover-design/#comment-6777</guid>
		<description>Hmmm...
as a technology consultant I consider myself to be an educator of sorts.  Again and again I discuss with my mentors and peers this concept of stickiness (we use the term "getting the client to the spot").  Every phone call, meeting, email, status report, etc. with a client (the list inlcudes Microsoft and other enterprise level companies) is considered a prescious moment in time, which can never be recaptured, and every situation is an opportunity to get to the spot.  The spot may be: understanding the ramifications (schedule/cost) of changing some functional requirement, or helping to understand the reasons for the selected technology to implement a business solution.

My clients are typically double/triple booked, with large simultaneous intiatives.  I'm convinced I only have 3/4 sentences to get them there, and I use a variety of tools depending on my need.  They include: pictures with Visio, tables in Word, a spoken metaphor, a working prototype.  Hell, if the needs change in the middle of a meeting, I'll scratch a workflow diagram on a napkin with the best of them.  Regardless, I'm not entertaining with pretty pictures - I'M HELPING MY CLIENT UNDERSTAND.  

Should they be punished by pithy explanations because I can't communicate the point concisely?</description>
		<content:encoded><![CDATA[<p>Hmmm&#8230;<br />
as a technology consultant I consider myself to be an educator of sorts.  Again and again I discuss with my mentors and peers this concept of stickiness (we use the term &#8220;getting the client to the spot&#8221;).  Every phone call, meeting, email, status report, etc. with a client (the list inlcudes Microsoft and other enterprise level companies) is considered a prescious moment in time, which can never be recaptured, and every situation is an opportunity to get to the spot.  The spot may be: understanding the ramifications (schedule/cost) of changing some functional requirement, or helping to understand the reasons for the selected technology to implement a business solution.</p>
<p>My clients are typically double/triple booked, with large simultaneous intiatives.  I&#8217;m convinced I only have 3/4 sentences to get them there, and I use a variety of tools depending on my need.  They include: pictures with Visio, tables in Word, a spoken metaphor, a working prototype.  Hell, if the needs change in the middle of a meeting, I&#8217;ll scratch a workflow diagram on a napkin with the best of them.  Regardless, I&#8217;m not entertaining with pretty pictures - I&#8217;M HELPING MY CLIENT UNDERSTAND.  </p>
<p>Should they be punished by pithy explanations because I can&#8217;t communicate the point concisely?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
