Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Tue, Sep 29, 2009 22:26 EDT

|
Posted by: Jim Vaughan in Best Practices Topic: IT Organization ManagementBlog: The IT Project Management Blog
Current Rating: |
Interesting. I prepared my blog and logged into the site to submit. That’s when I saw the blog by Phil Ayres entitled “Dreaming about Process Perfection.” So I checked my calendar to see if it was process improvement month. When you are done reading this blog (and I do hope that you do get to the end) go check out Phil’s blog which is well worth the read. Here follows my original blog unedited even after reading what Phil had to say.
I remember Tom Peters once wrote that the worst decision is the decision that does not get made. The premise was that if you wait to have a failsafe decision you may never get to a decision. There is a point where a decision must be made. If the decision is incorrect you can discover this early enough and correct your course. I find a similar pattern with process development.
Often we want to create failsafe processes. We want to make sure that we cover every scenario, walk through the process 100 times, have thirty people review, comment and agree on the process. These processes become bloated with information. Us type A personalities gloss over as we read through the details and the error legs that we will never use. Frustration sets in and the process is submitted to the plastic lined file for safe keeping. This often becomes the fate of many processes. A lot of effort is put into the creation and very little value is achieved.
Applying the KISS principle you can create a fairly simple process in a short period of time on one sheet of paper. (font = 10 pt or larger) Put the process in place and start using it. Yes there will be flaws and there will be questions. Using a continual process improvement philosophy you can start improving this process. The process will continue to improve and be used more widely. Rather than being clumsy and awkward to use the process becomes lean and mean. The process works within the organization culture and has been “road tested” by those experts that need to use the process.
If you take a look at any product you will see that is improves over time. This is the evolution of product development. A process is a product that will make your organization tick. Get your product to market and allow it to evolve.
Jim, you are spot on with your thoughts. Us Type A personalities that desire perfection are essential in some processes. Fortunately most of us do not need to manage air traffic control with what we do.
Any improvement shows pursuit of a best practice, more than sitting back worrying the result is imperfect. Even an industry regulator will understand this, and your customers and bottom line definitely prefer progress over perceived and expensive inaction.
I've written about this on my blog as well, in another post, Pave the cowpath - good and bad. Its probably worth a read wanting to see the hidden reality of process improvement - imperfection is everywhere and us Type As need to embrace it.
I couldn't agree more and discussed a similar point in a recent blog - Best Practice - the Enemy of Good Practice!.
Indeed, humble approach, permanent planning, deferring commitments by delaying the decision until the "last responsible moment” (when you are armed with information and experience) - this is one of two core philosophical ideas behind agile movement. (Another core idea is - trust and cooperation). Everything else, including agile flavours and techniques, derive from these two.
Eugene Nizker
Evident Point Software