<?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: CONFESSIONS OF A CKO: WHAT I SHOULD HAVE DONE</title>
	<atom:link href="http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/</link>
	<description>In search of a better way to live and make a living, and a better understanding of how the world really works.</description>
	<lastBuildDate>Wed, 16 May 2012 01:47:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Dave Pollard</title>
		<link>http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/comment-page-1/#comment-10954</link>
		<dc:creator>Dave Pollard</dc:creator>
		<pubDate>Tue, 01 Jun 2004 21:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/#comment-10954</guid>
		<description>&lt;a&gt;&lt;/a&gt;Thanks, Matt. Love the expression &#039;the poetics of their jobs&#039; -- really makes the olverused and inappropriate expression &#039;management science&#039; look righteously silly.Jon: It&#039;s interesting how everyone except top management is largely above the culture, structure and politics -- they just appreciate someone realizing that their job is much more difficult than it should be, and offering to help. The problem, ultimately, is entirely a management one: Management prides itself on &lt;i&gt;not&lt;/i&gt; using knowledge (&quot;they pay me a million a year to draw on my experience and gut, not to ask other people what to do&quot;, as one put it), refuses to pay for &#039;work effectiveness improvement&#039; programs or services (&quot;if they&#039;re not effective at doing their jobs, they should be fired, not coached&quot;), and generally look at employees as a necessary evil until the opportunity to outsource or offshore presents itself.</description>
		<content:encoded><![CDATA[<p><a></a>Thanks, Matt. Love the expression &#8216;the poetics of their jobs&#8217; &#8212; really makes the olverused and inappropriate expression &#8216;management science&#8217; look righteously silly.Jon: It&#8217;s interesting how everyone except top management is largely above the culture, structure and politics &#8212; they just appreciate someone realizing that their job is much more difficult than it should be, and offering to help. The problem, ultimately, is entirely a management one: Management prides itself on <i>not</i> using knowledge (&#8220;they pay me a million a year to draw on my experience and gut, not to ask other people what to do&#8221;, as one put it), refuses to pay for &#8216;work effectiveness improvement&#8217; programs or services (&#8220;if they&#8217;re not effective at doing their jobs, they should be fired, not coached&#8221;), and generally look at employees as a necessary evil until the opportunity to outsource or offshore presents itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Husband</title>
		<link>http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/comment-page-1/#comment-10953</link>
		<dc:creator>Jon Husband</dc:creator>
		<pubDate>Tue, 01 Jun 2004 14:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/#comment-10953</guid>
		<description>&lt;a&gt;&lt;/a&gt;My sense is that you would have found the &quot;work effectiveness&quot; part more gnarly when it came to culture and structural bottlenecks (and the politics therein) than with respect to the range of quasi-reengineering elements you mention above.Just a guess.  I know that you are very aware of the issues of culture and org structure.</description>
		<content:encoded><![CDATA[<p><a></a>My sense is that you would have found the &#8220;work effectiveness&#8221; part more gnarly when it came to culture and structural bottlenecks (and the politics therein) than with respect to the range of quasi-reengineering elements you mention above.Just a guess.  I know that you are very aware of the issues of culture and org structure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Loader</title>
		<link>http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/comment-page-1/#comment-10952</link>
		<dc:creator>Matt Loader</dc:creator>
		<pubDate>Tue, 01 Jun 2004 12:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://howtosavetheworld.ca/2004/05/31/confessions-of-a-cko-what-i-should-have-done/#comment-10952</guid>
		<description>&lt;a&gt;&lt;/a&gt;Fine article Dave, I found your comment &#039;We have actually made workers&#039; intellectual activities harder rather than easier, by presuming, top-down or back-office-to-front-lines, to understand what information they need, and how, when and why they need it&#039; to be a key point. Being of an ethnographic bent, I can see the areas where anthropology can be dragged in, in a spirit of true interdisciplinarity, to assist in the work you mention later: &#039;Work one-on-one to understand the problems each worker is having acquiring and processing information, and finding, contacting and working with experts; provide them with personalized training, tools, suggested processes and &#039;cheat sheets&#039; to address these problems; and, if these problems are endemic to the organization or can&#039;t be solved at the individual level, bring them back to management with recommendations for more systematic changes. [this is the only element of this job description that would require any staff -- all the rest is a one-person job]&#039;. I love the idea of &#039;cheat sheets&#039;, and have strongly suggested we adopt these: faced by learning a new software app. who sits down and reads the manual straight off? We need these &#039;quick starts&#039;, and they are at the task / activity level. Major respect Dave, for dragging KM back to the immediacy of The Task- if we take the time to look at how people are working; if we understand the poetics of their jobs, we can see that here is where the difference can be made...</description>
		<content:encoded><![CDATA[<p><a></a>Fine article Dave, I found your comment &#8216;We have actually made workers&#8217; intellectual activities harder rather than easier, by presuming, top-down or back-office-to-front-lines, to understand what information they need, and how, when and why they need it&#8217; to be a key point. Being of an ethnographic bent, I can see the areas where anthropology can be dragged in, in a spirit of true interdisciplinarity, to assist in the work you mention later: &#8216;Work one-on-one to understand the problems each worker is having acquiring and processing information, and finding, contacting and working with experts; provide them with personalized training, tools, suggested processes and &#8216;cheat sheets&#8217; to address these problems; and, if these problems are endemic to the organization or can&#8217;t be solved at the individual level, bring them back to management with recommendations for more systematic changes. [this is the only element of this job description that would require any staff -- all the rest is a one-person job]&#8216;. I love the idea of &#8216;cheat sheets&#8217;, and have strongly suggested we adopt these: faced by learning a new software app. who sits down and reads the manual straight off? We need these &#8216;quick starts&#8217;, and they are at the task / activity level. Major respect Dave, for dragging KM back to the immediacy of The Task- if we take the time to look at how people are working; if we understand the poetics of their jobs, we can see that here is where the difference can be made&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

