Q: How should I lead my team when our project isn't successful?
A: I have never met a successful person who doesn't have at least one story of a project that went spectacularly awry. Whether it is an underwater robot that dove into an ocean and never returned, or a much hyped new product that ended up selling poorly, examples are easy to find.
The longer a person's career, the more catastrophe stories they are likely to have amassed. Some of these incidents were likely instrumental in future successes.
So what should you do when it's your venture that didn't succeed in the way you had hoped?
The first thing I advise is to acknowledge that all companies and leaders face setbacks. As a leader, your team is going to be looking to you for guidance as you figure out what to do next. It is important that you recognize the hard work that inevitably went into the project. Your team spent time and energy on it, and should be given a chance to discuss what worked and what didn't. There are surely some lessons that can be learned from the experience.
I've also never encountered a project where there weren't at least a few things that went well. Start with those. A roundtable discussion where everyone on the team is asked for a positive insight from the work is often enlightening. (No win is too small. Perhaps the late nights led to finding a new favorite local restaurant, or a team member learning to use a new type of software.)
The "what went wrong" discussion is one that needs some careful planning. The purpose of reviewing the project is not to point blame, but rather to note the lessons you can pull forward for future work. That's why I often phrase this query as "What have we learned?"
Finally, and most important, clean up your messes. Make sure to apologize to the partners or shareholders where you need to.
And then? Onward to the next endeavor.
AnnMarie Thomas is a professor of entrepreneurship and engineering at the University of St. Thomas, where she directs the Playful Learning Lab.