When Projects Fail
We had a project fail.
- Let it sting. Soothing pain is for babies, not big boys and girls. Team members who don’t care about losing are losers. Don’t sooth discomfort by minimizing failure, but don’t overreact, either.
- Expect responsibility. Blamers are covering for something they should have done. Finger-pointing is the loser’s way of getting out of the spotlight.
- Remember what worked and why.
- Celebrate wins. One failure isn’t reason to stop celebrating all successes. Don’t give failure so much power that it turns out the lights.
- Make it personal. Ask, “How did we let each other down?”
- Step up to excellence not down to mediocrity. Excuses are the path to ease, insignificance, and irrelevance. “How can we be better?”
- Pick the scab. Dig into issues optimistically and respectfully. The goal is improving next time, not blaming and putting down.
- Don’t assume you know the reasons for failure.
- Evaluate the project. Was the project worth doing in the first place? Improve individual performance, but, don’t improve what isn’t worth repeating.
- Separate planning from execution during evaluation.
- Seek feedback from constituents outside the team.
- Explore lessons learned. What can be improved and how?
- Avoid globalizing. One failure doesn’t mean everything is going to hell.
- Don’t identify failure with who you are.
- Believe improvement is possible.
- Don’t assume working harder will make things better. What will you do differently, next time?
- Was the duration of the project too long? Short timelines are best.
- Explain how you’ll do better next time. Be specific. Clarity is the mother of success.
- Put it to bed.
- Re-vitalize momentum. Examine what happened with what’s next in mind. Create a win and celebrate.
Bonus: Let time pass between failure and review to allow emotions to stabilize.
What do you do when projects fail?