Today I will cover the last post for this series of posts on the blog. As stated before, portfolio management is a wide subject and there can be endless discussions on the subject. In my previous post, I discussed how mature organizations operate within the frameworks of portfolio management and how this seperates them from their peers in strategy alignment and object realization. I wrote about the advantage they have in connecting project execution to strategy fulfillment and how it makes the program and project initiatives frutiful. I must also admit that maturity does not come easily as it demands lots of resources to be able to provide good governance and clear oversight in project implementation, reaping along fruitful results on each and every level. This should be done with an aim of not only delivering value but also ensuring that the underlying portfolios, programs and projects incorporate this practice in the organization culture.
In a parallel project where I am working on a business report on how companies align IT projects to business strategies, I have had the opportunity to meet and interact with executives of a company who shared information on how the company is managed. For privacy reasons and with all due to respect to GDPR laws, I will keep the name of the company confidential. However, one thing that struck me is the relative simplicity of the organization’s management hierarchy and the model of implementing projects.
The program managers report direcctly to the executive, and there does not exist any portfolio manager. The management believes that having portfolio managers alienates them from the rest of the company, something that they do not want. Well, I understand that the company does not see the huge need for portfolio management and it is usually at the right time that it will be implemented. What I found amazing, is that the company claimed to have a high project completion rate, and seldomly fail to meet the strategic goals of the company through the initiatives put in place. The organization purely operates in an environment of growth through increased sales volume. However, they do acknowledge that they realize the need to implement portfolio management in the coming future, to relieve the program managers of the pressure they face in implementing projects. As the CEO states, “Implementation of project management will be done when we reach a certain target in the company, which we forecast to be in the coming 2 to 3 years. This will be critical in helping the company be agile and improve the program managers effeciency.”
While many organizations have the same mentality like the one I am working with, one thing stands out; acknowledging that portfolio management implementation and maturity is a continuous journey with lots of learning process. Truly, according to PMI, strategy implementation of a business will vary from company to company and the management have to realize their own potential, needs and capability. Though PMI taunts portfolio management as a vital success component in decision making, it may also be a source of distraction and confusion. At times, the governance may cloud the realization of strategies too much making the organization structure to be too complex, unnecessary and fail to address the considerations of the business. I would conclude that though it may bring along great positive effects, there should be caution in it’s introduction. It takes time to streamline portfolio management to the needs of the business and it is important that this be done with continous review and agility to help an organization realize the planned benefits.