<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for I&#039;m Not Actually a Geek</title>
	<atom:link href="http://bhc3.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://bhc3.com</link>
	<description>Observations on technology and business from someone who should know better</description>
	<lastBuildDate>Wed, 23 May 2012 00:14:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Jobs-to-be-done&#8217;s place in a customer-centric organization by James Hendricks</title>
		<link>http://bhc3.com/2012/05/16/jobs-to-be-dones-place-in-a-customer-centric-organization/#comment-19300</link>
		<dc:creator><![CDATA[James Hendricks]]></dc:creator>
		<pubDate>Wed, 23 May 2012 00:14:17 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7148#comment-19300</guid>
		<description><![CDATA[Great thread....let&#039;s build on it. Thinkdisruptive touches on the deeper understanding of &quot;why&quot;. Knowing the JTBD may help decide what to build but knowing the motivation(s) behind it can greatly influence design and is essential for marketing, sales, and service.]]></description>
		<content:encoded><![CDATA[<p>Great thread&#8230;.let&#8217;s build on it. Thinkdisruptive touches on the deeper understanding of &#8220;why&#8221;. Knowing the JTBD may help decide what to build but knowing the motivation(s) behind it can greatly influence design and is essential for marketing, sales, and service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Jobs-to-be-done&#8217;s place in a customer-centric organization by thinkdisruptive</title>
		<link>http://bhc3.com/2012/05/16/jobs-to-be-dones-place-in-a-customer-centric-organization/#comment-19212</link>
		<dc:creator><![CDATA[thinkdisruptive]]></dc:creator>
		<pubDate>Thu, 17 May 2012 13:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7148#comment-19212</guid>
		<description><![CDATA[Great post.

I&#039;d add one thing to asking customers about their jobs, which in truth, they can only half express, especially if they haven&#039;t imagined or don&#039;t believe there is solution for what they really want to do. That is, go out and visit the customers, watch them work for a few hours, ask why they do things the way they do and observe broken processes and workarounds. The truest expression of behavior and of needs is what people do, not what they say.

Still, this is a minor quibble/addition to some good insight.

What I find troubling is when execs believe they know better and don&#039;t want to be confused with the facts. This is not the same thing as Steve Jobs stating &quot;customers don&#039;t know what they want&quot;. Actually, Steve was correct in that customers often sublimate what&#039;s wrong with the way they do things now, and aren&#039;t aware of their workarounds. But, he and his team were very keen observers of behavior, which is why they got the needs and designs right. But many senior execs are convinced, even when they don&#039;t talk to or visit customers, that their ideas about what needs to be done and how it should be done are better.

You&#039;d think what you document here would be intuitively obvious. How could you possibly design a solution to a problem if you don&#039;t really know what the problem is? But, we still have a long way to go.]]></description>
		<content:encoded><![CDATA[<p>Great post.</p>
<p>I&#8217;d add one thing to asking customers about their jobs, which in truth, they can only half express, especially if they haven&#8217;t imagined or don&#8217;t believe there is solution for what they really want to do. That is, go out and visit the customers, watch them work for a few hours, ask why they do things the way they do and observe broken processes and workarounds. The truest expression of behavior and of needs is what people do, not what they say.</p>
<p>Still, this is a minor quibble/addition to some good insight.</p>
<p>What I find troubling is when execs believe they know better and don&#8217;t want to be confused with the facts. This is not the same thing as Steve Jobs stating &#8220;customers don&#8217;t know what they want&#8221;. Actually, Steve was correct in that customers often sublimate what&#8217;s wrong with the way they do things now, and aren&#8217;t aware of their workarounds. But, he and his team were very keen observers of behavior, which is why they got the needs and designs right. But many senior execs are convinced, even when they don&#8217;t talk to or visit customers, that their ideas about what needs to be done and how it should be done are better.</p>
<p>You&#8217;d think what you document here would be intuitively obvious. How could you possibly design a solution to a problem if you don&#8217;t really know what the problem is? But, we still have a long way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Do big companies need a &#8216;slow development&#8217; movement? by Hutch Carpenter</title>
		<link>http://bhc3.com/2012/05/04/do-big-companies-need-a-slow-development-movement/#comment-19207</link>
		<dc:creator><![CDATA[Hutch Carpenter]]></dc:creator>
		<pubDate>Thu, 17 May 2012 04:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/2012/05/04/do-big-companies-need-a-slow-development-movement/#comment-19207</guid>
		<description><![CDATA[Thanks Chris. I did come across an interesting quote by Steve Jobs in 1989: 

&quot;It takes a long time to pull out of customers what they really want, and it takes a long time to pull out of technology what it can really give.&quot;

http://www.inc.com/magazine/19890401/5602.html]]></description>
		<content:encoded><![CDATA[<p>Thanks Chris. I did come across an interesting quote by Steve Jobs in 1989: </p>
<p>&#8220;It takes a long time to pull out of customers what they really want, and it takes a long time to pull out of technology what it can really give.&#8221;</p>
<p><a href="http://www.inc.com/magazine/19890401/5602.html" rel="nofollow">http://www.inc.com/magazine/19890401/5602.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Jobs-to-be-done&#8217;s place in a customer-centric organization by George Castellion</title>
		<link>http://bhc3.com/2012/05/16/jobs-to-be-dones-place-in-a-customer-centric-organization/#comment-19202</link>
		<dc:creator><![CDATA[George Castellion]]></dc:creator>
		<pubDate>Wed, 16 May 2012 19:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7148#comment-19202</guid>
		<description><![CDATA[Hutch,

Thank you for a thoughtful post.

I agree with your comment “You know what? Customers love talking about their jobs-to-be-done”

Hutch, you are correct. Your approach is sort of radical. However, when all is said and done about the need for firms to be customer-centric ... generally more is said than done and radical approaches are useful. 

My experience is that elicitation … a conversation with a customer about the job-to-be-done … is the most productive tool for market analysis in the front end of new product development. It also helps tone down ineffective decisions made by executive fiat and usage vectors. http://goo.gl/AmNNE

Elicitation fits into the following range of primary marketing research tools.

Surveying — surveyor asks closed-ended questions that can be answered in a few words.
Interviewing —interviewer clearly keeps control of the interview.
Elicitation — elicitor controls the conversation without revealing the agenda to the respondent.
Conversation — two people talk and exchange information freely and unplanned.

This is especially true when considering elicitation as a primary research tool for the job-to-be-done. Below are three reasons corporate employees do not use elicitation more often.

1. Elicitation sounds exciting (and it is) but it is also just hard work. A seasoned elicitor gathers and analyzes data and information from many conversations with customers, end users, and competitors. 

2. Customers are seldom happy when you discount their knowledge and probe for job-to-be-done knowledge in conversations with their end users. (I am sometimes surprised about how little some of my clients’ customers understand about their customers’ job-to-be-done.) 

3. Corporate employees cannot pick up the phone and elicit sensitive data and information from an employee of a competitor.

George]]></description>
		<content:encoded><![CDATA[<p>Hutch,</p>
<p>Thank you for a thoughtful post.</p>
<p>I agree with your comment “You know what? Customers love talking about their jobs-to-be-done”</p>
<p>Hutch, you are correct. Your approach is sort of radical. However, when all is said and done about the need for firms to be customer-centric &#8230; generally more is said than done and radical approaches are useful. </p>
<p>My experience is that elicitation … a conversation with a customer about the job-to-be-done … is the most productive tool for market analysis in the front end of new product development. It also helps tone down ineffective decisions made by executive fiat and usage vectors. <a href="http://goo.gl/AmNNE" rel="nofollow">http://goo.gl/AmNNE</a></p>
<p>Elicitation fits into the following range of primary marketing research tools.</p>
<p>Surveying — surveyor asks closed-ended questions that can be answered in a few words.<br />
Interviewing —interviewer clearly keeps control of the interview.<br />
Elicitation — elicitor controls the conversation without revealing the agenda to the respondent.<br />
Conversation — two people talk and exchange information freely and unplanned.</p>
<p>This is especially true when considering elicitation as a primary research tool for the job-to-be-done. Below are three reasons corporate employees do not use elicitation more often.</p>
<p>1. Elicitation sounds exciting (and it is) but it is also just hard work. A seasoned elicitor gathers and analyzes data and information from many conversations with customers, end users, and competitors. </p>
<p>2. Customers are seldom happy when you discount their knowledge and probe for job-to-be-done knowledge in conversations with their end users. (I am sometimes surprised about how little some of my clients’ customers understand about their customers’ job-to-be-done.) </p>
<p>3. Corporate employees cannot pick up the phone and elicit sensitive data and information from an employee of a competitor.</p>
<p>George</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Jobs-to-be-done&#8217;s place in a customer-centric organization by Jobs-to-be-done’s place in a customer-centric organization &#171; Serve4Impact</title>
		<link>http://bhc3.com/2012/05/16/jobs-to-be-dones-place-in-a-customer-centric-organization/#comment-19201</link>
		<dc:creator><![CDATA[Jobs-to-be-done’s place in a customer-centric organization &#171; Serve4Impact]]></dc:creator>
		<pubDate>Wed, 16 May 2012 18:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7148#comment-19201</guid>
		<description><![CDATA[[...] on bhc3.com Share this:LinkedInTwitterFacebookStumbleUponEmailTumblrMoreDiggRedditPrintLike this:LikeBe the [...]]]></description>
		<content:encoded><![CDATA[<p>[...] on bhc3.com Share this:LinkedInTwitterFacebookStumbleUponEmailTumblrMoreDiggRedditPrintLike this:LikeBe the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on It&#8217;s the Jobs-to-Be-Done, Stupid! by Jobs-to-be-done&#8217;s place in a customer-centric organization &#171; I&#039;m Not Actually a Geek</title>
		<link>http://bhc3.com/2012/02/16/its-the-jobs-to-be-done-stupid/#comment-19197</link>
		<dc:creator><![CDATA[Jobs-to-be-done&#8217;s place in a customer-centric organization &#171; I&#039;m Not Actually a Geek]]></dc:creator>
		<pubDate>Wed, 16 May 2012 13:08:17 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7018#comment-19197</guid>
		<description><![CDATA[[...] written recently about jobs-to-be-done. As in, what customers hire your product to do. Those jobs have a tendency to (i) be hidden from [...]]]></description>
		<content:encoded><![CDATA[<p>[...] written recently about jobs-to-be-done. As in, what customers hire your product to do. Those jobs have a tendency to (i) be hidden from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Carving Up the Retail Industry by Customer Jobs to Be Done by Anonymous</title>
		<link>http://bhc3.com/2012/01/11/carving-up-the-retail-industry-by-customer-jobs-to-be-done/#comment-19058</link>
		<dc:creator><![CDATA[Anonymous]]></dc:creator>
		<pubDate>Mon, 07 May 2012 03:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=6925#comment-19058</guid>
		<description><![CDATA[I couldn’t resist commenting. Perfectly written!]]></description>
		<content:encoded><![CDATA[<p>I couldn’t resist commenting. Perfectly written!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Do big companies need a &#8216;slow development&#8217; movement? by Chris Spiek</title>
		<link>http://bhc3.com/2012/05/04/do-big-companies-need-a-slow-development-movement/#comment-19024</link>
		<dc:creator><![CDATA[Chris Spiek]]></dc:creator>
		<pubDate>Fri, 04 May 2012 20:32:12 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/2012/05/04/do-big-companies-need-a-slow-development-movement/#comment-19024</guid>
		<description><![CDATA[I love the line of thinking, Hutch. I&#039;ve seen the pressure of timelines lead to product failures in large companies countless times. 

I&#039;m not sure that things need to go slower in order to get them right though. 

I think you&#039;re two points are spot on, but once you establish a routine of responding to consumer JTBD and experimenting/rapid prototyping, I think it can be done very quickly. 

In fact I&#039;ve seen many instances when JTBD insights uncover opportunities at the low-end that make product launches faster and easier than what was initially planned (take features out and launch!!). 

If speed is indeed to blame, from my experience it would be due to teams rushing to pass insights from one function to another (e.g. Ideation or early product research groups to the dev / supply chain / scale-up groups). If this info-transfer is rushed, and the key insights are watered down along the way, great products can launch as less-than-great.]]></description>
		<content:encoded><![CDATA[<p>I love the line of thinking, Hutch. I&#8217;ve seen the pressure of timelines lead to product failures in large companies countless times. </p>
<p>I&#8217;m not sure that things need to go slower in order to get them right though. </p>
<p>I think you&#8217;re two points are spot on, but once you establish a routine of responding to consumer JTBD and experimenting/rapid prototyping, I think it can be done very quickly. </p>
<p>In fact I&#8217;ve seen many instances when JTBD insights uncover opportunities at the low-end that make product launches faster and easier than what was initially planned (take features out and launch!!). </p>
<p>If speed is indeed to blame, from my experience it would be due to teams rushing to pass insights from one function to another (e.g. Ideation or early product research groups to the dev / supply chain / scale-up groups). If this info-transfer is rushed, and the key insights are watered down along the way, great products can launch as less-than-great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bell Labs Created Our Digital World. What They Teach Us about Innovation. by trish</title>
		<link>http://bhc3.com/2012/04/16/bell-labs-created-our-digital-world-what-they-teach-us-about-innovation/#comment-18813</link>
		<dc:creator><![CDATA[trish]]></dc:creator>
		<pubDate>Wed, 18 Apr 2012 18:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7086#comment-18813</guid>
		<description><![CDATA[I completely agree about Google+ not solving any actual problem. However, what would you say Apple&#039;s done? I mean, they didn&#039;t invent the phone or the MP3 player, but they took those devices and made them so much better. I&#039;m fascinated by innovation, though I&#039;ll admit I wouldn&#039;t have thought to pick up this particular book. Your review has convinced me I need to, though!

Thanks for being on the tour and sharing your thoughts on the book.]]></description>
		<content:encoded><![CDATA[<p>I completely agree about Google+ not solving any actual problem. However, what would you say Apple&#8217;s done? I mean, they didn&#8217;t invent the phone or the MP3 player, but they took those devices and made them so much better. I&#8217;m fascinated by innovation, though I&#8217;ll admit I wouldn&#8217;t have thought to pick up this particular book. Your review has convinced me I need to, though!</p>
<p>Thanks for being on the tour and sharing your thoughts on the book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Bell Labs Created Our Digital World. What They Teach Us about Innovation. by salman_paracha (@salman_paracha)</title>
		<link>http://bhc3.com/2012/04/16/bell-labs-created-our-digital-world-what-they-teach-us-about-innovation/#comment-18792</link>
		<dc:creator><![CDATA[salman_paracha (@salman_paracha)]]></dc:creator>
		<pubDate>Tue, 17 Apr 2012 15:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7086#comment-18792</guid>
		<description><![CDATA[It will be interesting to see if the companies that fail to realize the shift in &quot;jobs-to-be-done&quot; (or are stuck by #5) are largely publicly traded companies? One could argue that Google had the right idea by incubating tons of ideas and exploring avenues, much like Bell Labs. given their CPC cash cow. But, at the end it come to hurt them, IMO. 

You alluded to focus, which I believe is critical, but with focus who aids the development and research of break through technologies? Certainly, quarterly earning calls curtail innovation to some extent, as companies become highly focused and partially myopic in favor of maintaining a business lead.

I suppose there could be a utopia, where you can bake your cake and eat it too...but in order to sustain cognitive diversity, I would imagine that &quot;talent&quot; would need more freedom, which could conflict with the direction of business goals?

With all the forces at play, can we reasonably expect another Bell labs for our generation?]]></description>
		<content:encoded><![CDATA[<p>It will be interesting to see if the companies that fail to realize the shift in &#8220;jobs-to-be-done&#8221; (or are stuck by #5) are largely publicly traded companies? One could argue that Google had the right idea by incubating tons of ideas and exploring avenues, much like Bell Labs. given their CPC cash cow. But, at the end it come to hurt them, IMO. </p>
<p>You alluded to focus, which I believe is critical, but with focus who aids the development and research of break through technologies? Certainly, quarterly earning calls curtail innovation to some extent, as companies become highly focused and partially myopic in favor of maintaining a business lead.</p>
<p>I suppose there could be a utopia, where you can bake your cake and eat it too&#8230;but in order to sustain cognitive diversity, I would imagine that &#8220;talent&#8221; would need more freedom, which could conflict with the direction of business goals?</p>
<p>With all the forces at play, can we reasonably expect another Bell labs for our generation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on It&#8217;s the Jobs-to-Be-Done, Stupid! by Bell Labs Created Our Digital World. What They Teach Us about Innovation. &#171; I&#039;m Not Actually a Geek</title>
		<link>http://bhc3.com/2012/02/16/its-the-jobs-to-be-done-stupid/#comment-18778</link>
		<dc:creator><![CDATA[Bell Labs Created Our Digital World. What They Teach Us about Innovation. &#171; I&#039;m Not Actually a Geek]]></dc:creator>
		<pubDate>Mon, 16 Apr 2012 13:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.com/?p=7018#comment-18778</guid>
		<description><![CDATA[[...] Uncategorized          &#8592; It&#8217;s the Jobs-to-Be-Done,&#160;Stupid! [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Uncategorized          &larr; It&#8217;s the Jobs-to-Be-Done,&nbsp;Stupid! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enterprise 2.0: Culture Is as Culture Does by &#8220;Do. Or do not. There is no try&#8221; &#171; sueduran</title>
		<link>http://bhc3.com/2009/07/10/enterprise-2-0-culture-is-as-culture-does/#comment-18120</link>
		<dc:creator><![CDATA[&#8220;Do. Or do not. There is no try&#8221; &#171; sueduran]]></dc:creator>
		<pubDate>Mon, 26 Mar 2012 01:29:58 +0000</pubDate>
		<guid isPermaLink="false">http://bhc3.wordpress.com/?p=4663#comment-18120</guid>
		<description><![CDATA[[...] H. (2009). Enterprise 2.0: Culture Is as Culture Does. Retrieved from http://bhc3.com/2009/07/10/enterprise-2-0-culture-is-as-culture-does/ Share this:TwitterFacebookLike this:LikeBe the first to like this [...]]]></description>
		<content:encoded><![CDATA[<p>[...] H. (2009). Enterprise 2.0: Culture Is as Culture Does. Retrieved from <a href="http://bhc3.com/2009/07/10/enterprise-2-0-culture-is-as-culture-does/" rel="nofollow">http://bhc3.com/2009/07/10/enterprise-2-0-culture-is-as-culture-does/</a> Share this:TwitterFacebookLike this:LikeBe the first to like this [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

