Project Failure, Why People Can’t Own Up

I saw this funny/sad Dilbert cartoon on project management by Scott Adams (BTW, he’s terrific!).

It goes like this:

Office colleague (water cooler talk): How’s your project coming along?

Dilbert: It’s a steaming pile of failure. It’s like fifteen drunken monkeys with a jigsaw puzzle.

New scene….

Boss: How’s your project coming along?

Dilbert: Fine.

END

This common work scenario is sort of like a game of truth or dare: you either have to tell the project truth or take the dare and do something embarrassing like proceed with the project that isn’t on track.

Teammates, colleagues, peers often talk frankly and honestly about the problems with their projects and often the talk may become sarcastic or even somewhat cynical, because they know that they can’t tell their bosses what is REALLY going on.

What a shame in terms of lost opportunities to communicate, solve problems, and drive project success for the organization.

People are afraid to be honest, direct, tell the truth, and work together with their management on constructive solutions.

Instead, people simply say everything is fine, period.

Sort of like when your boss asks politely at work how are you doing? And rather than say, well I woke up late, missed my train, spilled coffee on my tie, and am having trouble meeting my deadlines this week, the person almost always replies, reflexively, “I’m fine” and “How are you?”

Another manifestation of the it’s fine syndrome is with executive dashboards or project scorecard reviews where virtually all the metrics show up as “green”, even when you know they are not—does yellow or red sound too scary to have to put on paper/screen and explain to the boss.

We are conditioned NOT to talk casually or to report to our superiors about issues, problems, or anything that can be perceived as negative, least they be labeled as trouble-makers or “the problem,” rather than the solution. Ultimately, employees don’t want to be blamed for the failures, so they would rather hide the truth then own up to the project issues, and work constructively with their management on solutions or course correction—before it’s too late.

Now isn’t that a novel idea? Management and staff working together, actually identifying the issues—proactively and in forthright manner—and working together to resolve them, rather than sitting across the table, sugar-coating or pointing the accusatory finger.

People have to take responsibility and own up when there is a problem and be willing to talk about them with their management, and management needs to encourage frankness, a “no surprises” culture, and a team-collaborative environment to solving problems rather than instilling fear in their employees or implicitly or explicitly communicating that they only want to hear “good news.”

Good news is not good news when it’s fabricated, a distortion, or a complete sham.

A culture of teamwork, collaboration, honesty, and integrity is the underpinning of project success. If everything in the project “is fine”, it’s probably not.

Project Failure, Why People Can’t Own Up

Delivering Obsolete and Broken IT Projects, No More

NextGov reported on 9 Nov 2009, that the Government Accountability Office (GAO) released a report that “forecasts $3 billion in cost overruns on 16 major projects.”

What’s so of baffling is that these overruns occurred despite the agency’s use of earned value management.

According to Dave Powner, director of IT management issues at GAO, “Every one of the agencies had major problems in determining earned value management…as a result the agencies were unable to accurately identify the progress contractors had made on IT projects.”

These finding are expected to drive the 2009 Information Technology Oversight and Waste Prevention Act to increase oversight of IT investments.

This bill calls for “a Web site to publish information on the status of federal IT investments, similar to the Federal IT Dashboard,” but with more accurate data and with explanations on why projects are over budget.

Certainly, the use of measurements and dashboards to display and track these are helpful in understanding how we are doing in managing our IT investments—so they are on schedule, within budget, and to customer specification.

Clearly, we can only begin to better manage that which we measure and track. Our IT investments and their execution are no longer a black box or so it’s supposed to work.

However, to make these metrics and dashboard effective to improve IT execution, there are a number of critical success factors:

1. Transparency—This is a concept that is in common use these days, and we need to continue to put it in action. All IT investments need to be measured, not just the “major” ones, and their success and failures need to be visible. The purpose must not to scrutinize or shame project managers, but to be able to genuinely guide projects to successful conclusions. This is what the control phase of capital planning and investment control is all about. We need to course correct projects early and often, if necessary, before they are billions of dollars out of control.
2. Honesty in Reporting—Projects need to be reported accurately—no gaming the system. If the facts are sugarcoated or whitewashed, then no dashboard in the world is going to catch the problems that are misreported to begin with. Unfortunately with project management, the elements of scope, schedule, and cost can be manipulated to make it seem as if a project is okay, when it isn’t. One example is de-scoping the project to enable a delivery on schedule and on cost, even though what’s being delivered is not what was asked for or agreed upon.
3. Skills Enhancement—With better measurement of IT investments, we need to provide more training to our project managers. We can’t just expect perfection day 1. We need to work with people and grow them to be better project managers. We can do this with training, mentoring, coaching, and so on. Remember, it’s generally the people that make the IT project a success or failure, not the technology—so let’s invest in our people to make them better project managers.
4. Accountability—We shouldn’t be looking to exact a pound of flesh for genuine human foibles—mistakes do happen. But at the same time, people must be held accountable for fraud, waste, and abuse. Sometimes, people get complacent and they need a reminder that there are real implications to an IT project’s success or failure—mission and people are depending on you to do your job, so you had better do it responsibly and to the best of your ability.
5. Continuous Improvement—Ever since business school, I’ve always loved the Japanese management practice of Kaizen—continuous improvement. This concept is right on the mark with our IT investment and project execution. We are not going to magically put up a dashboard and whoola—better IT projects. It’s going to be a process, a transformation over time. We need to incrementally improve our IT project success rate through learning measurement, and best practices implementation. Of course, time is money, and we need to move quickly, but we do not want to artificially create the appearance of short-term performance improvement at the expense of genuine long-term success.

All the power to IT performance measurement and dashboarding, but with the absolute commitment to not only track and measure, but also grow and improve our customer results. It’s not a gotcha that we need, but a how can we help you succeed.

Delivering Obsolete and Broken IT Projects, No More

What We Lose When We Lie

If you watch House MD on TV, House always says something sort of striking: “everyone lies.”

Today, an article in the Wall Street Journal, 20 October 2009, says something similar, that we all lie even (some, not me, would say “especially”) in our closest relationships, marriage.

“We fib to avoid conflict. To gain approval. To save face. Or just to be kind.”

Some claim lying is a survival mechanism because “they [lies] allow us to avoid conflict.”

Others feel that it’s okay to lie in order to be tactful with others. For example, a retired financial executive explained that “when his wife ask how she looks, he always tells her she is beautiful. ‘A bad hair day isn’t going to change your life. What’s to be gained by saying something negative to someone that is of such fleeting importance.'”

Even those who supposedly don’t lie, have all these little twists:

One man when asked about lying said: “I don’t lie, I tell the truth…slowly.”

George Costanza on Seinfeld used to say: “It’s not a lie if you believe it.”

In society, we’ve even come up with a terms for lies that are small or harmless and we call those “white lies.”

Even in court rooms, we don’t trust that people will tell the truth, but rather we have to literally ask them “Do you swear to tell the truth, the whole truth, and nothing but the truth, so help you G-d?”

Many people have pointed out that even in the Ten Commandments, we are not commanded directly not to lie, but rather “you shall not bear false witness against your neighbor.”—Hey, just for the record, that’s close enough for me!

Not surprisingly, the mixed thinking about whether it is okay to lie in certain “charged” situations carries over into our organizations.

On one hand, many of our organizations, especially in the public sector, have wonderful core values such as truth, justice, integrity, and so on. Moreover, for certain national security positions, we even give people lie detector (polygraph) tests to ensure their personal truthfulness.

Yet, on the other hand, we all have heard of project managers who lie in order to cover up failing or failed projects—and many implicitly accept this behavior.

I read that the Standish Group recently reported that 82% of our organizational projects are failing or seriously challenged i.e. they are over budget, behind schedule, or not meeting customer requirements. Moreover, we have for years, seen numerous projects end up on watch list for failing projects and even have websites that track these.

Yet, ask many project managers how their projects are doing and you get the spectrum of whitewash answers like “everything is great,” “we’re right on track,” “no problem,” “everyone’s working hard,” or sometimes simply “nothing to report.”

Perhaps, project managers are afraid to tell the truth for fear of retribution, punishment, or other negative impacts to their career, those that work for them, or others who are “implicated.”

As one psychologist says about little white lies: “If you don’t fib, you don’t live.”

How unfortunate this thinking is—rather than encouraging honesty, we develop cultures of fear, where cover-ups are routine and truth in reporting is a practically a misnomer.

By creating a culture where lying is endemic to reporting, we are harming our people and our organizations. Organizationally, we can only manage if we can measure, and we can only measure if people are honest as to what is working and what isn’t. Personally, we hurt our own integrity as human beings by lying (or being dishonest, deceiving, whitewashing or whatever you want to call it) and then justifying it in so many little and big ways.

Sure, there is such a thing as tact, but you can be tactful and truthful at the same time!

Some of this may come down to improving communication and people skills and this needs to be emphasized in our training plans. Of course, we need to work with each other in socially appropriate ways.

But at the same time, at the end of the day, people need to maintain what is really important—their integrity, and at the same time move the organization to make the right decisions, and this can only be done by being frank and honest with ourselves and with each other.

My suggestion is for leaders to surround themselves with those who are not only “the best and the brightest,” but also those with the most honesty and integrity around.

What We Lose When We Lie

Constructive Truth Hurts, But Helps

It is pretty hard to give and to get honest feedback.

It is often acknowledged that performance reviews are one of the most difficult task for managers to perform. Managers don’t like to “get into it” with the employees, and employees often can’t deal with a straightforward evaluation from their supervisors. Plenty of sugarcoating seems to go on to make the process more digestible for all.

Similarly, people tend not to say what they “really think” in many situations at work. Either, they feel that saying what they mean would be “politically incorrect” or would be frowned upon, ignored, or may even get them in trouble. So people generally “toe the line” and “try not to rock the boat,” because the “nail that stands up, gets hammered down hard.”

An article in the Wall Street Journal, 5 October 2009, reports a similar pattern of behavior with ratings on the Internet. “One of the Web’s little secrets is that when consumers write online reviews, they tend to be positive ratings: The average grade for things online is about 4.3 stars out of five.” On Youtube, the average review for videos is even higher at 4.6.

Ed Keller, the chief executive of Bazaarvoice, says that on average he finds that 65% of the word-of-mouth reviews are positive and only 8% are negative. Likewise, Andy Chen, the chief executive of Power Reviews, says “It’s like gambling. Most people remember the times they win and don’t realize that in aggregate they’ve lost money.”

Some people say that ratings are inflated because negative reviews are deleted, negative reviewers are given flak for their “brutal honesty,” or the reviews are tainted with overly positive self-aggrandizing reviews done on themselves.

With product reviews or performance reviews, “it’s kind of meaningless if every one is great.”

I remember when I was in the private sector, as managers we had to do a “forced rankings” of our employees regardless of their performance rating, in an effort to “get to truth” across the organization.

Generally speaking, performance systems have been lambasted for years for not recognizing and rewarding high performers or for dealing with performance problems.

Whether it products, people, or workplace issues, if we are not honest in measuring and reporting on what’s working and what's not—fairly and constructively—then we will continue to delude ourselves and each other and hurt future performance. We cannot improve the status quo, if we don’t face up to real problems. We cannot take concrete, constructive action to learn and grow and apply innovate solutions, if we don’t know or can’t acknowledge our fundamental weaknesses.

“Being nice” with reviews may avert a confrontation in the short-term, but it causes more problems in the long-term.

Being honest, empathetic, and offering constructive suggestions for improvement with a genuine desire to see the person succeed or product/service improve—and not because the manager is "going after" someone—can be a thousand times more helpful than giving the nod, wink, and look-away to another opportunity for learning, growth, and personal and professional success.

Constructive Truth Hurts, But Helps