Blog: Fixing Problem and High-Risk Projects
"We can fix this project ourselves." I hear that line all the time. And, of course, you can. It will just be a lot slower and more expensive because consultants cheat. Consultants simply have much more flexibility than employees do. At least consultants that put the client first. For instance, they can... Wait, I am getting a little ahead of myself. We need a little context before making that case. Obviously, consultants cannot do everything. It takes a delicate balance of consultants, employees, and contractors to get the optimal performance out of an organization.
The other day, someone said, once again, that an issue we were discussing was like pushing string. She said it with the sigh of resignation in her voice. I understand the metaphor, but the people saying it are stuck looking at the problem wrong. Immediately, two solutions to their dilemma come to mind. First, add a little water, freeze the string. Voilà! Push that string wherever your little heart desires. If that is too hard, then roll it into a ball or put it on a spindle. Now, we can push, roll, carry, and even throw it. The problem is the predisposition to the inevitability of the issue—there is no reason to look for a solution because it is out of our control. Worse than that, we are so defeated that we rarely ask the question "Why are we trying to push that string?"
I sent a note to professional organization's program director the other day asking if their group would be interested in hearing about methods to increase project success. The organization was for a technical group that worked with data transformation—a skill set used in every IT project I have ever been on. The reply came in a prompt, succinct, and sarcastic reply:
"We [sic] you please tell me just how this would ever relate to the members of our group. You obviously do not understand that we are not responsible for running the project."
A project manager's job is to deliver value. Achieving the original schedule, budget, and features is meaningless if the customer does not receive value. As with all simple statements, this much easier said than accomplished. Projects managers must assemble adaptable teams that use flexible, lean methodologies. Arrogantly selling the latest technology or tool is narcissistic. Focus on the customer. Be vigilant at ensuring the information is always available for the customer to reassess the project's value and for the project team to reevaluate their proposal.
"People say I am indecisive, but I am not so sure about that." I have seen this quote attributed to a former US President, but I doubt he actually siad this. First, it is too intelligent a comment for him and, second, he is far from indecisive. The liberal pundits trying to attribute that quote to him confuse indecision with defective decision making. You can figure out who the President is on your own; however, it is irrelevant. This article is about leadership not politics. Organizations confronted with a decision-challenged individual in a leadership role, is adrift in the sea of serendipity. They bobble around having no direction.
Walking onto any troubled project, guess what I hear? We are spending too much money, we cannot miss the due date, we need everything we are asking for, and it is "their" fault. My job is telling them the bad news—we need more money, we are cutting scope, and the project is still going to be late. Those are the unavoidable facts and the stakeholders need to accept them. Worse than that, I am not going to blame anyone. Blame is counterproductive. So, how does this compare to the situation with the United States Congress? In short, they do not get it. They need an apolitical, outside entity to build the recovery plan—just like we do anytime we are recovering any project.
Back in the eighties, I was working for a large aerospace company cutting my teeth as a systems analyst. My bosses were a little older than I am now, and they loved talking about the days before cubicles, pontificating on how personal computers were inferior to mainframes, and reminiscing about the days of the BOMARC missile. It was their way of telling us thirty-something kids that they were in control and we needed to respect their position. Then, as now, information was king and these pterodactyls were not letting it go. To earn the stripes, one had to partake in the tribal rituals, smoke cigars during three-martini lunches, and attend your boss's parties. They saw no value in email let alone the boondoggle shop floor automation project I was part of. In two words, communication sucked.
A friend of mine alerted me to an article in a PMI Community post titled Is Manipulation Ethical? From the title, I thought this would be neat read. However, the article was pretty swallow. How foolish to think that a 650-word article would address an issue that has plagued philosophers for a few millennia. The initial reaction was to the manipulative title, which was deceptive. It led me to believe the article would supply some profound knowledge. The short treatise failed. To its credit, though, it made me think. On the second pass, I decided that I disliked the article. In fact, its thesis—manipulation is ethical—is morally wrong.
Decisions, deshmisions, what is the big deal? Anyone can make a decision! Hardly. After years of working with ineffective initiatives and consternated companies, I have a healthy respect for the D-word. It is all about the seven 'tudes—ineptitude, attitude, fortitude, altitude, aptitude, incertitude, and vicissitude. Some organizations obtrude the 'tude in which they are imbued, while others are denude of a common 'tude.
I have written about, spoke on, and lobbied against blame. Regardless, it just seems like a bottomless pit of contention, conversation, and criticism. People fail to see how to correct a crisis without hastily pointing fingers at failure's first sight. Yet, in the next breath they claim accusations serve no purpose as they attempt to sidestep the fate of blame's gauntlet. We can talk about how we should solve the issues rather than going on the proverbial witch-hunt to find the individual, group, or organization who we think should be burned at the stake and wear the corporate tattoo of failure. Why do we need this and what does it achieve?
Filling Execution Gaps
Rescue The Problem Project
- New PM Articles for the Week of November 9 – 15, The Practicing IT Project Manager, November 9, 2015
- The Argument for Disbanding Your PMO, Accellerated IT Success, Nov 13, 2015
- New PM Articles for the Week of September 28 – October 4, The Practicing IT Project Manager, October 4, 2015
- Episode 332: Project Sponsor Challenges and Solutions, PM Podcast, Cornelius Fichtner, September, 2015
- New PM Articles for the Week of December 1 – 7, The Practicing IT Project Manager, December 7, 2014
- How to buy Project Management Consulting Services: Service as a Product (SaaP), Guerrilla Project Management, Samad Aidane, December 2, 2014
- Episode 275: Your Project Statement of Work is Missing a Comma!, PM Podcast, Cornelius Fichtner, June 14, 2014
- State Invites 10 Firms To Shift Cover Oregon To The Federal Health Insurance Exchange, Oregonian, Portland, Nick Budnick, May 28, 2014
- Decision To Scrap Or Salvage Cover Oregon Health Insurance Exchange Poses Risks Either Way, Oregonian, Nick Budnick, Portland, April 9, 2014
- Cover Oregon Consultant: Fix For Health Insurance Exchange Could Take $40 Million, 21 Months, Oregonian, Nick Budnick, Portland, April 4, 2014
- Episode 205: Rescue The Problem Project, PM Podcast, Cornelius Fichtner, June, 2013
- Episode 206: How to Keep your Project out of Trouble, PM Podcast, Cornelius Fichtner, May, 2013
- How to identify, prevent, and recover from project failure, Accellerated IT Success,April 2, 2013
- Episode 260: The Seven Steps to Rescuing the Problem Project, PM Podcast, Cornelius Fichtner, January. 2014
- New PM Articles for the Week of August 6 – 12, The Practicing IT Project Manager, August 12, 2012
- New PM Articles for the Week of June 11 – 17, The Practicing IT Project Manager, June 17, 2012