Project Strategy

The statistics on strategy execution are dismal:

• 59% of middle managers fail at resolving conflicts in corporate strategy.
• 45% of middle managers cannot name one of the top five corporate goals.
• 64% of cross-department/functional issues are poorly resolved.

And maybe as you could expect from this:

• 53% of companies cannot react timely to new opportunities.

You do not need to be a rocket scientist to know that this trajectory is not going to launch most companies’ latest strategic plans successfully. In fact, these data might make you feel that middle management would be better suited as test dummies for the next generation of manned space-vehicle. Granted, the data show there is a dearth of leadership in middle management, but the executive tier has a culpable hand.

Projects build capabilities to met corporate goals. If you are a CEO, you need to make sure your employees and vendors know what those goals are and how they fit in to the plan. If you are a project manager, you need to know the bounds of you project. If you are anywhere in between, you need to understand how all the pieces fit together and keep it all aligned.

Most organizations consist of multiple business and support units, each populated by highly trained, experienced executives. But often the efforts of individual units are not coordinated, resulting in conflicts, lost opportunities, and diminished performance.

Let me be perfectly clear, I hate PMOs. It matters not if you call them project management offices, program management offices, or portfolio management offices, they only spell one thing—poor leadership. Now those of you that know me, have heard this enough times that your eyes are rolling back as you mumble, "Here he goes again. Who set the bait in front of him this time?" However, I have confused people with a couple of PMO articles that might seem contrary.

The Challenge:

You are running a project that is supposed to improve the organization to leap out in front of the competition, yet you have had little formal training on what that means. Project managers need lessons in how world class business runs to drive projects to make that happen.

Built to Last, Collins' first book and defining management study of the nineties, showed how great companies triumph over time and how long-term sustained performance can be engineered into the DNA of an enterprise from the very beginning.

But what about the company that is not born with great DNA? How can good companies, mediocre companies, even bad companies achieve enduring greatness?

The Study:

Projects build capabilities to met corporate goals. If you are a CEO, you need to make sure your employees and vendors know what those goals are and how they fit in to the plan. If you are a project manager, you need to know the bounds of you project. If you are anywhere in-between, you need to understand how all the pieces fit together and keep it all aligned.

Most organizations consist of multiple business and support units, each populated by highly trained, experienced executives. But often the efforts of individual units are not coordinated, resulting in conflicts, lost opportunities, and diminished performance.

Last week I gave a presentation at the San Diego PMI Chapter's Tutorials conference. Flanking both sides of my ten o'clock presentation in the leadership track was Steve Romero. His two presentations were on IT governance. His energy, insight, enthusiasm, and passion (not to mention being the IT governance evangelist for CA Technologies) made him an excellent selection. And, what is so news worthy about that? Nothing. However, for someone that has little regard for adding one more layer of management to solve a problem, I was surprised that I sat through both of his presentations. He provided a three hours of information on governance—both PMOs and PPMs—crammed into two intense and valuable hours.

Womack is often considered the father of writing on lean manufacturing. Nearly all books on this subject use his books as reference material.

The publisher says:
"Expanded, updated, and more relevant than ever, this best selling business classic by two internationally renowned management analysts describes a business system for the twenty-first century that supersedes the mass production system of Ford, the financial control system of Sloan, and the strategic system of Welch and GE. It is based on the Toyota (lean) model, which combines operational excellence with value-based strategies to produce steady growth through a wide range of economic conditions.

Businesses exist to make money. To improve operations they create various initiatives with promises of improving the bottom line. Projects, though, cost money. They do not make a profit. The dichotomy in a strapped economy to spend savings on projects to improve future profits usually results in the conservation of cash. Many an argument has been had over whether it is better to run improvement projects, burning precious cash and heading off the competition, or taking the traditional approach and wait for times with better cash flow. Subsequent to 2008's financial folly, it is well known that most companies sat on their reserves and waited. That action may have some unintended consequences that are in the midst of surfacing.

Management comes up with great plans for sweeping change, it implements the plans, and three years later the organization has reverted to the way it was before the initiative. Changing to new breakthrough systems is hard; maintaining those processes and procedure is far more difficult. The reason progressive ideas can have a successful implementation only to have the organization regress to its prior state a few years later has its roots in societal practices and human nature.

The 33 Strategies of War is not as much about war as it is about strategies of dealing in an offensive environment and understanding strategies. Whether you are trying to hone your offense strategy or better your defensive skills to thwart other's attacks, this book provides a series of examples and interpretations to help. Mr. Greene's examples are from a wide variety of people and conditions—Napoleon, Alfred Hitchcock, Sun Tzu, Margaret Thatcher, Shaka the Zulu, Lord Nelson, Franklin Roosevelt, Hannibal, Ulysses S. Grant, and many more.