When things are going wrong how hard is it to stop, reflect and, if necessary, redo?

For example, if you are in the middle of a project and discover that the solution is not going to work for the customer what do you do?  Do you push ahead and try to get the customer to rethink what they “really” need so that it matches what you are producing? Do you push your team to redesign, retest and deliver a new solution in a crashed timeframe; thereby causing undue stress and pressure on the team? Or, do you redo with full disclosure?

[Sidebar] I know what all you project managers out there are thinking “if you did proper project planning you wouldn’t be in this pickle. ”  I’m a PMP and know where you are coming from. Let’s assume that this happened for sake of argument.

My point is how willing are you to stand up and say, “We need to redo this!”  Admit that mistakes were made, take responsibility for the team and go to the customer with an apology and a new plan of attack.  It ain’t easy, it takes some guts, and it’s plenty risky.

With all the risk involved, I’m suggesting that it’s more important to do the right thing than to cover it up.  I’ve seen plenty of projects that try to do just that and more often than not the cover is eventually removed and the ugly truth is revealed.  That is not a good place to be.  I have been there and have learned this lesson the hard way.

By doing the right thing there’s a good chance you might feel some temporary pain, but in the long run you won’t have regrets.

So, if it’s the right thing to do, than (re)do.

Advertisements