I was sitting on the plane last week trying to get some writing done and as it always, one thought lead to another until I realized I was contemplating why organizations fear shades of gray. All the incredible emphasis on process is designed to eliminate human judgment and ensure consistency but if we’d ever stop kidding ourselves, the truth is all this emphasis on process isn’t actually getting us the result we claim to want. Every time I think about this topic I imagine a closed tube being squished flat. There is a 100% guarantee that the tube will spring a leak and that the contents will ooze out until the tube is flat. It’s the same thing with most business processes. Since the process is always under pressure there will always be a leak somewhere. By encouraging people to “follow a highly prescription Process” (and capital P processes are always highly prescriptive) there’s nobody who believes he or she has the authority to either relieve the pressure in the first place or at least take the cap off the tube and catch what squirts out.
Don’t get me wrong – I believe in process (with a lowercase p). So why do processes work when Processes don’t? The answer is actually rather simple. A process (small p) says begin by establishing if the thing that is happening is abnormal in any way. If so go into problem solving mode immediately. Apply judgment, knowledge and experience until it’s fixed. If it isn’t abnormal – follow the standard practice. Anthropologically this works very well because human beings are hard wired to do very rapid problem identification. If you tell them there are bad things in the proverbial bushes they will keep their eyes peeled. At this point some of you are probably saying “But that’s what I’m afraid of… When they take independent action they just make things worse” and my answer would be,” possibly true”. And here is where we come full circle. If you reserve problem resolution to management (as defined as those individuals who get paid to think about what they do”) then all the problems are going to come to your desk anyway, so tell me again what the big P Process actually accomplished?
By the way I should mention that the litmus test on what’s a big P process is always the fact that somebody somewhere feels the need to do a compliance audit to ensure adherence to the Process (not success in creating the results of the process but adherence to the Process itself.) I understand that for many people the advantages of compliance auditing for adherence to process boarders on religious faith and I am normally open minded enough to entertain that there are many paths to the same outcome BUT I absolutely draw the line on this one when it comes to PPM processes.
I should say very clearly that this is MY OPINION. It is not a Gartner Position. There are lots of folks inside the company who feel just as strongly in the other direction. My reasons for airing the issue are that I think we as a community need to discuss it. My objection is that we are wasting time, money and people, none of which we can afford to waste now or in the future. On the other hand, there’s always an open mind hidden beneath my diatribes and if there’s a middle ground I’d love to find it.
Read Complimentary Relevant Research
Predicts 2017: Artificial Intelligence
Artificial intelligence is changing the way in which organizations innovate and communicate their processes, products and services. Practical...
View Relevant Webinars
An Integrated Approach to Strengthening Your Supply Chain
Digital disruption and the weakening global economy have made profitable growth more challenging than ever. Yet, some CSCOs are able...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.