Blame: The Result of a Failed or Troubled Project
It is amazing how people on failing projects neglect to look at their own issues prior to blaming someone else. Yes, blame is easy and on red projects since no wants to be the source of the issues. The truth is, everyone is at blame, so before bringing in an auditor or recovery manager, tidy up your house first.
This book is currently under review, more details will be added when available
Teams are the center piece of any project. Without a team you will most likely fail at meeting any criteria for a successful project. Jackie, a personal friend of mine, has written a great book that will open your mind on a different approach to teams.
The quickest way to get lost, in business or in your personal life, is failing to make decisions. Not knowing where you are headed increases stress and frustration. It would seem natural, then, that teams on projects beleaguered with indecisive management would be excited to have the logjam broken by a dynamic, decisive leader. Simply put, they are not. Every decision has its opponents and they are bound to be irritated, feeling they have lost prestige or stature. However, turning the decision into action requires a unified team. One of the best tools to accomplish this is to understand what impeded decision making and tactfully educating the team members on the source of the problem. This will garner their backing and improve their willingness to support the decision.
I have always enjoyed cooking and rarely thought of it as a chore, let alone a project; however, when my wife became ill, I became the household chef and had to learn a new way to cook. Every evening was a project with varying degrees of success. Eventually making multi-course meals from scratch became easier. I used to joke that cooking Chinese food was two hours of chopping fresh vegetables and ten minutes with three blazing woks.
There is a reason we do not teach classes on fixing failing projects. Many a cynic feels that we simply do not want to teach our trade, however, our reason is far nobler—we should be teaching prevention rather trying to create white knights to save the day. It is the same philosophy as building a fence at the cliff's edge rather than an emergency room at its base. Our language is replete with idioms telling us to look past the symptom and address problems at their root cause. 'An ounce of prevention versus a pound of cure' or 'a stitch in time saves nine.' Please, feel free to supply your own in the comments. Unfortunately, most of our businesses loathe this philosophy, waiting to address an issue until it is irrefutably broken.
The west coast of the United States is where I call home. Many refer to us as "left coaster" because... well... that is how it looks on a map and many of us are politically a little further to the left than others. Around here, common thought is that everyone should be open-minded. A sentiment that I proudly subscribe to as I lack most prejudices. You can imagine my shock when I found out that my unbiased presumptions are not only undesirable, but also undeniably wrong.
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?
A couple weeks ago, I was in eating my pre-keynote dinner with a group of people that I had never met. Without being prompted by some general drift in the conversation, a person across that table said, to no one in particular, "Did you hear about the new app to do confessional?" Being unfamiliar with the group, how was I to know if I was sitting with a group of high-tech Catholics that would think this was great. Besides trying to determine how to react, I was trying to envision how confessing with an iPod would have the same effect as sitting down with a priest. Of course, who am I, a fringe protestant, to make any editorial comment about Catholicism's inner workings? However, I finally blurted out, "What happened to accountability?"
It happens hundreds of times a day around the world, the CIO calls an urgent IT Management Committee meeting. She has heard that one of the projects in the portfolio, a seemingly simple project doing a routine upgrade, is projecting a 20 percent cost overrun and will be three months late. How can a project go that far off track since the last week's executive team meeting? Managers scramble to get their stories straight, determine who to blame, form opinions and alibis, and pummel the project manager for failing to manage the project correctly, even though he has been saying the project is in trouble for months. The project has drifted from its initial intent and now the ultimate goal is to find someone to blame.
Projects can be on-time, within budget, meet the specifications and still be a failure. Case in point, the new Dallas 160x72 foot mega screen. It seems the screen displays what it should, but is positioned a bit too low. So low, that on August 21st, the punter kicked a ball into it. Did someone forget the purpose of the stadium was playing football?