When Less Is More
I see the project portfolios of a lot of different organizations. I can honestly say I have never felt that an organization had too few projects. In most cases, organizations approve way more initiatives than they are capable of delivering, and then get frustrated when those projects fail to achieve the expected results. Why is there such a reluctance to reduce the number of projects underway? And more importantly, how do we change that mindset?
The problem starts with the way the organization sets priorities. At the enterprise level there may be somewhere between three and five key objectives established for the year, but then there are additional goals set for each division, for each of the departments that make up those divisions, etc. As a result, there are three, four, perhaps even five layers of the organization approving projects. And the level of coordination between anything but the top level is almost nonexistent. So resources end up being allocated to multiple projects at the same time, and the need for work from other business areas is missed. And that doesn’t even consider the fact that projects are approved based on high-level estimates of time and financial cost that are likely to be way too conservative.
At some level organizations already know this. They are used to delaying, combining, cancelling or stripping down projects at various points throughout
Please log in or sign up below to read the rest of the article.