<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Top Curious Cat blog posts</title>
    <description>A feed of the all time top blog post by John Hunter. 1 new item is added to the feed every day from the previously published blog posts.</description>
    <link>http://johnhunter.com</link>
    <item>
      <title>Root Cause, Interactions, Robustness and Design of Experiments</title>
      <link>http://management.curiouscatblog.net/2014/06/18/root-cause-interactions-robustness-and-design-of-experiments/</link>
      <description>&lt;p&gt;A &lt;a href="http://curiouscat.com/management/dictionary/rootcause"&gt;single root cause&lt;/a&gt; is rare. Normally you can look at the question a bit differently see the scope a bit differently and get a different &amp;ldquo;root cause.&amp;rdquo; In my opinion &amp;ldquo;root cause&amp;rdquo; is more a decision about what is an effective way to improve the system right now rather than finding a scientifically valid &amp;ldquo;root cause.&amp;rdquo;&lt;/p&gt;</description>
      <pubDate>Sat, 3 Oct 2026</pubDate>
      <guid>http://management.curiouscatblog.net/2014/06/18/root-cause-interactions-robustness-and-design-of-experiments/</guid>
    </item>
    <item>
      <title>George Box Webcast on Statistical Design in Quality Improvement</title>
      <link>http://management.curiouscatblog.net/2014/06/11/george-box-webcast-on-statistical-design-in-quality-improvement/</link>
      <description>&lt;p&gt;There is great value in creating iterative processes with fast feedback to those attempting to design and improve. Box and Deming (with rapid turns of the PDSA cycle) and others promoted this 20, 30 and 40 years ago and now we get the same ideas tweaked for startups. The lean startup stuff is as closely related to Box&amp;rsquo;s ideas of experimentation as an iterative process as it is to anything else.&lt;/p&gt;</description>
      <pubDate>Fri, 2 Oct 2026</pubDate>
      <guid>http://management.curiouscatblog.net/2014/06/11/george-box-webcast-on-statistical-design-in-quality-improvement/</guid>
    </item>
    <item>
      <title>Practicing Mistake-Promoting Instead of Mistake-Proofing at Apple</title>
      <link>http://management.curiouscatblog.net/2014/06/05/practicing-mistake-promoting-instead-of-mistake-proofing-at-apple/</link>
      <description>&lt;p&gt;&lt;a href="http://curiouscat.com/management/dictionary/pokayoke"&gt;Mistake proofing&lt;/a&gt; is a wonderful management concept. Design systems not just to be effective when everything goes right but designing them so mistakes are prevented.&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;But guess what, the unnecessary steps Apple decided to force me through are broken so I can&amp;rsquo;t just waste my time to make them happy. No. They have created a failure point where they never should have forced the customer in the first place.&lt;/p&gt;</description>
      <pubDate>Thu, 1 Oct 2026</pubDate>
      <guid>http://management.curiouscatblog.net/2014/06/05/practicing-mistake-promoting-instead-of-mistake-proofing-at-apple/</guid>
    </item>
    <item>
      <title>How to Build a Great Software Development Team</title>
      <link>http://management.curiouscatblog.net/2014/05/29/building-a-great-software-development-team/</link>
      <description>&lt;p&gt;"Without confidence, honest debate about ideas is suppressed as people are constantly taking things personally instead of trying to find the best ideas (and if doing so means my idea is criticized that is ok).&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;This is also one of many areas where the culture within the team was self reinforcing. As new people came on they understood this practice. They saw it in practice. They could see it was about finding good ideas and if their idea was attacked they didn&amp;rsquo;t take it nearly as personally as most people do in most places."&lt;/p&gt;</description>
      <pubDate>Wed, 30 Sep 2026</pubDate>
      <guid>http://management.curiouscatblog.net/2014/05/29/building-a-great-software-development-team/</guid>
    </item>
    <item>
      <title>Give People Enough Rope (and the Right Rope) to Succeed</title>
      <link>http://evop.blogspot.com/2013/06/give-people-enough-rope-and-right-rope.html</link>
      <description>&lt;p&gt;You want systems that let people take on challenges without too many restrictions but with enough support and training that you don't leave them hanging.&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;the ropes should suit their situation. A tightrope over a chasm is fine for a trained acrobat with a balancing pole. It is foolish for someone without the right training or tools. They would be better served with something else - a rope bridge with railings.&lt;/p&gt;</description>
      <pubDate>Tue, 29 Sep 2026</pubDate>
      <guid>http://evop.blogspot.com/2013/06/give-people-enough-rope-and-right-rope.html</guid>
    </item>
  </channel>
</rss>
