In this article, I want to talk about the need for “Reengineering Project Management”; but before we get into that, let’s review what “reengineering” is and what it has meant.
What is “Reengineering”?
“Reengineering” became very popular in the early 1990’s. The essence of the reengineering movement was that sometimes an incremental approach to process improvement isn’t sufficient; sometimes you need to almost completely disregard the way the existing process works and use out-of-the-box thinking to explore completely different ways of doing things. As an example:
- In those days, many retail stores relied on large networks of distribution warehouses to supply product to all of their retail store locations.
- Many manufacturers used a similar system to stock inventory in warehouses to support their production operations.
That was a well-established way of doing logistics at that time, but it wasn’t very efficient and effective. It consumed huge amounts of inventory sitting in warehouses unnecessarily and a lot of unnecessary warehouse space. The concept of overall supply chain management and “Just-in-Time” production changed all that:
- Instead of stockpiling lots of inventory in distribution warehouses to support their retail stores, many retailers learned to eliminate the distribution warehouses altogether by having manufacturers deliver products direct to their stores on a just-in-time basis to meet customer demand.
- In a similar way, manufacturers eliminated huge amounts of inventory that they were carrying by having suppliers deliver parts and components that were needed for man
It required some fairly radical, out-of-the-box thinking, to reengineer these processes in a completely different way rather than simply continuing to tweak and improve the current processes. Michael Hammer who was one of the leaders of the reengineering movement in those days came up with an expression of “paving the cow paths”. Here’s what he meant by that:
Paving Cow Paths
What Happened to the Reengineering Movement?
Like many things, the reengineering movement took on a life of its own where:
- The emphasis shifted to a brute-force approach for slashing and burning existing organizations, laying off people, and radical downsizing.
- In some cases, it went too far and resulted in “throwing out the baby with the bath water”. In other words, “if it ain’t broke, don’t fix it”.
As a result, the reengineering movement fell out of favor with many people who began to associate it with just a brute-force way to reorganize and downsize existing companies. That’s unfortunate because the fundamental concept behind reengineering of using out-of-the-box thinking to come up with new and innovative approaches to perform many existing processes was very sound.
How Does This Apply to Project Management?
Many people in the project management community think that there is only one way of doing project management and that is based on a well-established, traditional plan-driven approach that emphasizes planning and control to achieve predictability over project costs and schedules. That’s the fundamental way that project management has been done for many years and it has become so well-established that it defines the essence of what “project management” is and is difficult to change. Much of the current emphasis in the project management community has been on using automation and tools such as AI to improve the efficiency of the way that process works. There’s an insufficient level of emphasis on changing the very nature of how project management is done. That’s what Michael Hammer referred to as ‘paving the cow paths”.
Don’t Throw the Baby Out with the Bath Water
I’m not advocating completely throwing away the traditional plan-driven approach that has been so fundamental to project management for a long time, but it clearly is not the only way to do project management. In situations where there is a relatively low level of uncertainty, requirements are well-defined, and predictability of costs and schedules is important; a traditional plan-driven approach clearly has value and should continue to be the primary project management approach. A good example of that is the construction industry. However, that approach should not be the only way to do project management and force-fitting all projects to that approach is certainly not optimal.
Why is a Different Approach Needed?
A different approach is needed where any of the following conditions exist:
- There is a high level of uncertainty in the project that makes it difficult or impossible to define detailed requirements prior to the start of the project.
- It requires creativity and innovation to optimize the business value of the solution, and the business value of the solution is more important than meeting arbitrary cost and schedule goals.
- It is important to the organization to have a sufficient level of adaptivity and flexibility in their project management approach to dynamically adjust to a competitive business environment.
As I’ve emphasized many times, this is not a black-and-white, all-or-nothing choice between a traditional plan-driven approach to project management and an Agile approach. It is a matter of focusing on the value that the project needs to produce and using an approach that is well-suited to delivering that value. In many cases, that may require blending the two approaches in the right proportions to fit the situation.
What Does This Mean for Project Managers?
Project Managers need to focus on delivering value rather than simply managing and executing a well-defined project management process; however, the idea of “value” may not be well-defined and there’s no standardized, “cookbook” approach that works in all situations for delivering value. As a result, Project Managers need to be well-aligned with the business environment that they operate in and must be capable of making decisions of what the best approach is to optimize the business value of a solution in that environment. That means that:
- The Project Manager role might begin to look more like a Program Manager role where a Program Manager is responsible for broad-based business initiatives that may not be well-defined.
- It also may begin to look like an Agile Product Owner role who makes business decisions to define and prioritize the work being done, provides business direction to the team, and reviews the results of the work against the business value it is meant to achieve.
- The role of a Project Manager may be more heavily associated with larger and more complex enterprise-level projects rather than small, simple single-team projects.
This raises the bar for project managers to a new level that goes beyond simply managing and executing a well-defined project management process to achieve predictability over the project costs and schedules. In this environment, the Project Manager needs to take a much more active decision-making role in shaping the direction of the project to optimize the business value that it produces. This approach is what I call “Value-driven Project Management“.
Overall Summary
We need to use the same concepts that were used for reengineering business processes to rethink what “project management” is and develop a new and broader approach that is designed to focus on producing business value. I call this approach, “Value-driven Project Management” as opposed to “Plan-driven Project Management”. This requires some out-of-the-box thinking to view Project Management in a whole new perspective that will change the very nature of what we have known as “project management”. However, we need to be careful not to “throw the baby out with the bath water”. The traditional plan-driven approach to project management does have value and it is not a matter of completely throwing out that approach. It’s a matter of recognizing the limitations in that approach and blending that approach in the right proportions with a focus on delivering business value.