Accountability: The Key to Resolving Project Issues
|Author:||Roger Fisher, William L. Ury|
One of the primary tasks of a project manager is to negotiate—negotiate scope, negotiate for resources, negotiate for money, negotiate end dates, etc.—there is almost nothing that a project manager has as a give. Even in your personal life, negotiation skills are essential for dealing with everything from your kids' bedtime, to the price of your next car. Understanding the art and science of negotiation is critical. This book, especially in conjunction with one of our classes, is a great way to get you down the road to improving you negotiation skills. Don't be fooled though, negotiation takes practice.
|Publisher:||Union Square Press|
This book is currently under review, more details will be added when available
In my opinion, as a project manager, you cannot read too many books on handling change. Each gives you a different perspective on how to effectively deliver a project whose product is valuable. This is a lesser known book, but has a great perspective.
Many businesses try to change, but few succeed. At best, a few buzzwords and new reports become part of the company's structure. At worst, programs crash and burn, and the members of the organization become irreparably disillusioned with the revolving door of new-mission statements. According to David Shaner-a business consultant with a 100% success rate of change at companies including Duracell, Frito-Lay, Caesars Palace and Gillette-the problem is that those changes don't address either individuals or the corporate culture. They're only on the surface.
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 executive tier has a culpable hand.
eCameron took a serious look at project sponsorship by conducting a series on non-scientific interviews. Initially the focus was the healthcare industry. As patterns started to emerge, however, others outside of that industry expressed serious interest. To address that interest and better understand the larger issue we expanded the interviews to outside healthcare. Candid and confidential interviews were conducted with project related personnel including executives, sponsors, project managers, and Project Management Office (PMO) managers. In summary:
- Sponsorship is an issue in all business domains.
- Good sponsorship is an essential component in creating successful projects.
- Many issues are pervasive across industries.
- Sponsors need to work with project managers to design a successful project outcome.
- Sponsor roles are neither properly defined nor supported.
This white paper presents the results of the research and highlights areas where organizations need to improve to change their project success rates.
From her corner office, the new executive decried, "Decentralize the PMO. Let each department be responsible for their own projects." Maybe she had made a pact with another executive for some other bit of power, or it could be she lost a power struggle and the PMO had to go, or possibly she has little regards for project management thinking it is a mechanical, blue collar discipline that methodically follows a recipe to execute each project. Bottom line, she is missing the point of the Project Management Office (PMO)—it is all about business goals. Unfortunately, for the company, decentralized PMOs provide little if any value. They are similar to distributed teamwork—an oxymoron. The concept is illogical.
Risk is a risk in itself. It is risk for you if you dare bring it up. Have you ever identified the risk, in writing, that your boss' inherent inability to make decisions is going to sink the project? How about the company loss of market share will require laying off half the project team? Or, that the project manager has never had a successful project? These are CLMs (career limiting moves). Even mentioning such common risks as a company's inexperience in the project's domain is too risky to put in the risk register. It is as if management enjoys blissful ignorance and relishes the firefight that ensues. Cowboy mentality. Identifying risk, modeling mitigation plans, and compiling contingency are too boring compared to the thrill of disaster recovery.
Customer Relationship Management (CRM) implementations fail at an alarming rate. For the last fourteen years, numerous independent parties have come up with the same dismal statistics. In fact, your implementation probably will not meet your goals either. The graphic above does not bode well for anyone heading out on that journey. To be sure, configuring the software is significantly more difficult that it appears at first glance. As much as one wants to blame Salesforce, Microsoft, or some other software vendor, though, the trouble lies much closer to home.
For the astute onlookers it is easy to tell when the implementation is going the awry. It is the argument over who is going to drive the project—IT or Sales and Marketing. Unfortunately, these are the wrong people to have in the discussion.
After nearly 30 years of project work, I struggle to understand the role of a project management office (PMO). Even though, I have written of the pros and cons, and read a plethora of articles, opinions, and how-to guides little has been done to convince me that the PMO is reducing project failure. It seems to be nothing more than a tool to fill a void in leadership? Even the acronym, which is so widely thrown around, has little meaning as the "P" has no less than four meanings. It is an executive's crutch for their lack of understanding in how projects work. These, like other, unattended holes in the corporate accountability create opportunities for new and greater bureaucracies and empires that further obfuscate accountability.
Few would question that executives are responsible for ensuring projects are aligned with the corporate strategy. They also need to ensure these initiatives remain in line with these goals as business conditions change. To achieve this, they have to be engaged with the project when it starts and maintain that context throughout its life cycle. This requires more than ensuring the project maintains its scope, schedule, and budget; projects must deliver value. Too many projects start with the inspirational support of upper management, but as the project (or company) drifts, the executives have long since disengaged from the project and are unable to straighten out the misalignment. This wastes company resources and hinders the company's ability to deliver.
"Kotter, ADKAR, or CAP which methodology should we be using to build our approach to improving project adoption?" I hear this question repeatedly from people trying to implement an organizational change management (OCM) program. The problem is that is the wrong question. Take a perfunctory peek at any of the models and you will see that in the quest for an answer people have mistakenly jumped over the first few steps and they head down the road of failure. It is a Catch-22; unless you already have an OCM process in place, you will most likely fail at implementing it. Putting one in place, however, is a change—one of the most difficult cultural transformations your company will undertake. As a result, people jump to the solution stage, which is well down the change management process path (which, they did not know, ironically, since there was no procedure in place).