Project Management is certainly rife with processes, regardless of the particular methodology to which you, or your organization, adhere. Something like 44 processes in nine knowledge areas in the PMI Body of Knowledge, and 40 separate activities in seven processes in Prince2.
As organizations look for ways to be more efficient in delivery of products or services to market, every business process can (and should) come under scrutiny, and this includes the project management processes. Process improvement is the accepted approach to extracting new efficiency from existing process.
I submit what is needed is process destruction. While one could argue that is part of the improvement process, I believe a destructive approach sets a higher bar. The improvement process allows retention, or tweaking, of “pet” processes – ones that keep control in place, provide perceived job security for a group or individual, or institutionalize risk and change aversion.
Taking a destructive approach should ask the tougher, more difficult questions regarding the efficacy of a process. It should require business, financial, or regulatory proof to pass muster. And when it comes to project management it should also answer the question “how does this increase speed to market?” While it is understood there are quality considerations with any product or service, and being the first to market with a seriously flawed product is rarely successful, the rigor of the destructive process is no less valid or valuable.
As a function of business improvement, this process should be continual, not something taken of the shelf every fiscal year and given a cursory glance. With the pace of innovation in today’s global markets, using the same processes from 2 or 5 or 10 years ago, and not putting them through the destructive process, is moving backwards, regardless of the industry or product.
So if you’re using the same project management process and haven’t asked the tough questions, there is only one question your leadership should be asking…
WHY?