<?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: Management Poka-Yoke</title>
	<atom:link href="http://timebackmanagement.com/blog/management-poka-yoke/feed/" rel="self" type="application/rss+xml" />
	<link>http://timebackmanagement.com/blog/management-poka-yoke/</link>
	<description>Working At The Intersection of Personal Productivity and Lean Manufacturing</description>
	<lastBuildDate>Wed, 09 May 2012 15:37:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: John Hunter</title>
		<link>http://timebackmanagement.com/blog/management-poka-yoke/comment-page-1/#comment-120</link>
		<dc:creator>John Hunter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-120</guid>
		<description>I agree CEO&#039;s need to work to keep real feedback available to them.  Getting trapped in the center of a bunch of yes-men (especially if the organization &quot;doesn&#039;t want to hear problems just solutions...).  But is it poka-yoke?  It doesn&#039;t really mistake proof I don&#039;t think.  It provides some additional information that can be used wisely to avoid mistakes.

That would seem closer to explaining to workers that a USB cable must be plugged in with the side that says top on the top. Which is not the same as designing the USB cable to only plug in if you have the top in the right orientation.

Granted this distinction might not be that great.  I have just thought about the idea of applying mistake proofing thinking to problems (but not actually implementing counter-measures, other than awareness) that prevent mistakes.  To me this seems like something less than actual poka-yoke.</description>
		<content:encoded><![CDATA[<p>I agree CEO&#8217;s need to work to keep real feedback available to them.  Getting trapped in the center of a bunch of yes-men (especially if the organization &#8220;doesn&#8217;t want to hear problems just solutions&#8230;).  But is it poka-yoke?  It doesn&#8217;t really mistake proof I don&#8217;t think.  It provides some additional information that can be used wisely to avoid mistakes.</p>
<p>That would seem closer to explaining to workers that a USB cable must be plugged in with the side that says top on the top. Which is not the same as designing the USB cable to only plug in if you have the top in the right orientation.</p>
<p>Granted this distinction might not be that great.  I have just thought about the idea of applying mistake proofing thinking to problems (but not actually implementing counter-measures, other than awareness) that prevent mistakes.  To me this seems like something less than actual poka-yoke.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: testking 70-291</title>
		<link>http://timebackmanagement.com/blog/management-poka-yoke/comment-page-1/#comment-127</link>
		<dc:creator>testking 70-291</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-127</guid>
		<description>I agree CEO&#039;s need to work to keep real feedback available to them. For management poka-yoke, you could design a system that didn&#039;t allow a meeting to be scheduled until an agenda was posted</description>
		<content:encoded><![CDATA[<p>I agree CEO&#8217;s need to work to keep real feedback available to them. For management poka-yoke, you could design a system that didn&#8217;t allow a meeting to be scheduled until an agenda was posted</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan</title>
		<link>http://timebackmanagement.com/blog/management-poka-yoke/comment-page-1/#comment-139</link>
		<dc:creator>dan</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-139</guid>
		<description>John,

You raise a good point. I suppose whether or not it&#039;s &quot;true&quot; poka-yoke depends on whether the internal surveys and review are a routine and necessary part of the CEO&#039;s annual review. If, for example, he had to submit the feedback to the board of directors each year and list his action steps based on that feedback, that would get a whole lot closer to true poka-yoke.

But no, it doesn&#039;t actually prevent him from sucking, or treating his employees like dirt, or running the company into the ground. Given that humans have free will, my guess is that true human poka-yoke is impossible.

What do you think?</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>You raise a good point. I suppose whether or not it&#8217;s &#8220;true&#8221; poka-yoke depends on whether the internal surveys and review are a routine and necessary part of the CEO&#8217;s annual review. If, for example, he had to submit the feedback to the board of directors each year and list his action steps based on that feedback, that would get a whole lot closer to true poka-yoke.</p>
<p>But no, it doesn&#8217;t actually prevent him from sucking, or treating his employees like dirt, or running the company into the ground. Given that humans have free will, my guess is that true human poka-yoke is impossible.</p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Hunter</title>
		<link>http://timebackmanagement.com/blog/management-poka-yoke/comment-page-1/#comment-141</link>
		<dc:creator>John Hunter</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-141</guid>
		<description>Well unless there are constraints then poka-yoke probably is impossible.  With a USB cord you can design it to essentially be impossible to put in wrong (though really not totally impossible, I mean I think I could get it to fit wrong if I really tried).  But a much easier way to not plug it in correctly would be just not to plug it in at all.

For management poka-yoke, you could design a system that didn&#039;t allow a meeting to be scheduled until an agenda was posted (I can see doing that with software - of course people could just put in fake agenda stuff - but I can push in the USB cable the wrong way too).  Of course that can create problems, I sometimes want to schedule a meeting and having set the details yet.  But I am just trying to think how you could enforce less obvious (less physical often) poka-yoke solutions.

You could require things like an A3 report before x is done.  Of course the A3 report could be done in a sloppy lame manner.  I think the non-physical poka-yoke attempts do have challenges, sometimes I can imagine creating physical like (software...) bottlenecks...  Which then could act as preventing certain types of mistakes...</description>
		<content:encoded><![CDATA[<p>Well unless there are constraints then poka-yoke probably is impossible.  With a USB cord you can design it to essentially be impossible to put in wrong (though really not totally impossible, I mean I think I could get it to fit wrong if I really tried).  But a much easier way to not plug it in correctly would be just not to plug it in at all.</p>
<p>For management poka-yoke, you could design a system that didn&#8217;t allow a meeting to be scheduled until an agenda was posted (I can see doing that with software &#8211; of course people could just put in fake agenda stuff &#8211; but I can push in the USB cable the wrong way too).  Of course that can create problems, I sometimes want to schedule a meeting and having set the details yet.  But I am just trying to think how you could enforce less obvious (less physical often) poka-yoke solutions.</p>
<p>You could require things like an A3 report before x is done.  Of course the A3 report could be done in a sloppy lame manner.  I think the non-physical poka-yoke attempts do have challenges, sometimes I can imagine creating physical like (software&#8230;) bottlenecks&#8230;  Which then could act as preventing certain types of mistakes&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

