<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
         xmlns:thr="http://purl.org/syndication/thread/1.0" 
         xmlns:wfw="http://wellformedweb.org/CommentAPI/">
  <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html" /> 
  <link rel="self" type="application/atom+xml" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.xml" />
  <id>tag:blog.jackvinson.com,2007://1/tag:blog.jackvinson.com,2005://1.7376-</id> 
  <updated>2007-12-03T11:56:32Z</updated>
  <title>Comments for The Worst Thing About Best Practices</title> 
  <subtitle>Jack Vinson writes about knowledge management, personal effectiveness, theory of constraints and more.  As of December 2007 Jack will likely start writing about product management too.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.01</generator>

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7376" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7376.1094</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html#comment-1094" /> 
    <title>Comment from Denham Grey on 2005-07-03</title>
    <author>
        <name>Denham Grey</name> 
        <uri>http://denham.typepad.com/km</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://denham.typepad.com/km">     
      <![CDATA[ <p>It is that old addage about context again. If you understand the 'context' you can start to play with best practices - getting your staff to adopt them can still be an uphill battle.</p>

<p>This is one of the reasons I've found patterns to be an improvement - the community decides what to deploy after refinement, testing and validation.</p> ]]>
    </content>
    <published>2005-07-04T04:59:34Z</published>
    <updated>2005-07-04T04:59:34Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7376" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html"/>


    <id>tag:blog.jackvinson.com,2005://1.7376.1102</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html#comment-1102" /> 
    <title>Comment from Dan Keldsen on 2005-07-05</title>
    <author>
        <name>Dan Keldsen</name> 
        <uri>http://www.delphigroup.com/about/people/dan_keldsen/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.delphigroup.com/about/people/dan_keldsen/">     
      <![CDATA[ <p>Jack and Denham - Absolutely agree on the context component. As we propose in our Proving Ground on Information Architecture and Taxonomy (<a href="http://www.delphigroup.com/pg)"><a href="http://www.delphigroup.com/pg)">http://www.delphigroup.com/pg)</a></a> one should examine the "3 Cs" of Context, Content and Community to understand fully what your needs and desires are BEFORE building/buying/tweaking whatever you have now, to make the future solution worth the effort, and most important, applicable to your organization and customers (whether internal or external).</p>

<p>Best Practices are business and mind-killing viruses - The very label almost stops any critical thinking of the practice before rushing to an end state through a questionable process (who really writes up their Best Practice as it actually happened? it is almost inevitably sanitized so that the end result seemed manifest destiny). Use a "best practice" as a case study, and make sure the case is analyzed for all it's pros AND cons, not pure gospel for "this is how all future such processes will run in the future without question." Even the best run companies cannot afford to sit in an isolated looping bubble, and expect to continue on their continued upward growth.</p>

<p>From the world of statistics, a single dot/piece of data does not make a trend, and from the world of risk management, basing future predictions on the optimistic trend lines, while ignoring the pessimistic and/or realistic, is a disaster waiting to happen.</p>

<p>Einstein stated "Keep things as simple as possible, and no simpler" - and my working theory (always being tested) is that Best Practices go several steps beyond trying to be as simple as possible, to make decision making for a new practice essentially a "no-brainer" activity.</p>

<p>Thinking - The New Best Practice</p> ]]>
    </content>
    <published>2005-07-05T19:29:02Z</published>
    <updated>2005-07-05T19:29:02Z</updated>

  </entry> 

  <entry>
    <thr:in-reply-to ref="tag:blog.jackvinson.com,2005://1.7376" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html"/>

    <id>tag:blog.jackvinson.com,2005://1.7376.p234</id> 
    <link rel="alternate" type="text/html" href="http://blog.jackvinson.com/archives/2005/07/03/the_worst_thing_about_best_practices.html#p234" /> 
    <title>Trackback in article Are Best Practices really the best you can do? from AlwaysWoW!  For a Great Great WoW in Life</title>
    <author>
        <name>AlwaysWoW!  For a Great Great WoW in Life</name> 
        <uri>http://www.alwayswow.com/archives/2005/07/index.html#000326</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.alwayswow.com/archives/2005/07/index.html#000326"> 
        <p>
              Best Practices or Benchmarking is a habit that is all over the place. I am coming across them constantly during my daily work day. Best Practices basically means that you as a company look across your own industry and other... <a href="http://www.alwayswow.com/archives/2005/07/index.html#000326">[Read More]</a>
        </p>
    </content>
    <published>2005-07-20T04:11:30Z</published>
    <updated>2005-07-20T04:11:30Z</updated>


  </entry> 

</feed>
