I Made a Mistake
So, what do I do now?
We all make mistakes. Sometimes they are small and personal like forgetting to put the trash at the curb to be picked up. Or, larger and embarrassing, like writing the amount differently in numbers and words on a check. Or, sending a critical email to the wrong addressee. Or, being the only one to show up for a meeting because you failed to send a notice of the meeting around to the expected attendees. Or, you crash an application server because you didn’t stop and check the command before you entered it. Or, you enter a network configuration change incorrectly and take down a major national system affecting large numbers of customers.
Mistakes happen. Sometimes small, sometimes very large; sometimes private, sometimes very public. In each instance, we must ask the question “What do I do now?” And, as much as we might prefer to run and hide, we know that’s neither wise nor even possible in most cases, even when the mistake is small and personal. So, we have to set aside any feelings of being ashamed, feeling guilty, and being angry at ourselves and address the issue.
So, what do you do? Fundamentally, you need to acknowledge the mistake, apologize for it, and fix it. It is perhaps helpful to think about this in terms of six processes that often will need to run concurrently:
1. Acknowledge and own – Whether it’s small or large, a missed appointment because it didn’t make it’s way to your calendar, a meeting when the guest you had agreed to invite doesn’t show up because you forgot to invite her, or a major system becomes unavailable because you entered the wrong command, you need to first acknowledge and own what you did. No excuses. No need to say, I was busy and forgot or I didn’t check the command. You inform those who are or need to be involved, apologize, and set out to remediate the problem as rapidly as possible.
But first, in order to take these next steps effectively, you have to do something that is difficult for many of us. You have to forgive yourself for making the mistake and put aside all the self-talk that may be screaming in your brain about how dumb and stupid you are because of what you did. You won’t really be able to perform at the level you need to without doing this.
As Dorie Clark reminds us in her Harvard Business Review essay, “Unfortunately, making bad decisions are a part of life: No one has a 100% success rate. Even so, it’s challenging to admit our mistakes, in a culture that still often hides them. But when you do, and you work to remedy them quickly and honestly, it can mitigate the initial problem and earn the lasting respect of your peers.”
2. Apologize – Apologies need to be made quickly and must be specific and real, not something lame and self-protective. “I’m sorry, but I didn’t invite the guest speaker I committed to invite. It is my bad. Can we reschedule when I find she is available?” In 2011 Amazon had a major system failure affecting many clients across the country. It wrote this apology in its incident note to its customers:
“We want to apologize. We know how critical our services are to our customer’s business and we will do everything we can to learn from this event and use it to drive improvement across our services. As with any significant operational issue, we will spend many hours over the coming days and weeks improving our understanding of the details of the various parts of this event and determining how to make changes to improve our services and processes.”
3. Fix – From the client’s perspective, the most immediate thing to be done is to resolve the issue. Get the meeting on the calendar or restore their system so that work can resume. Make fixing your mistake a very high priority and allocate the necessary resources.
4. Understand – Don’t just fix what was broken. Take the time and work to understand what contributed to the situation. Look for root causes. What steps might you take to keep the mistake from happening again? What can you do differently? Take the time to really understand what went wrong. Were you careless in thinking that you’d remember the details at a later date? Were you over-confident in setting an optimistic delivery schedule? Did more redundancy need to be build-in to the system? Etc. These are all learnings that should come from a carefully performed, rigorous After Action Review.
5. Improve – And, go beyond just understanding what happened to ask, how might I change the system so as to better serve my clients in the future? It is not enough to restore a process or system to its previous state when that system was marginal. Do what needs to be done to make the restored system robust.
6. Communicate – In many instances, we’d like to sweep our mistakes under the rug and pretend that they never happened. However, there is value and power in taking responsibility; the mistakes we make often have unexpected consequences. In an HBS article, “Lessons on Toyota’s Long Drive,” a former Toyota chairman, Katsuaki Watanabe, is quoted as saying: “Hidden problems are the ones that become serious threats eventually. If problems are revealed for everyone to see, I will feel reassured. Because once problems have been visualized, even if our people didn’t notice them earlier, they will rack their brains to find solutions to them.”
In some environments, sharing information about your mistakes can be a lifesaver. In her research on learning in hospitals, Amy Edmondson, Harvard Business School faculty member, discovered that the highest-performing nursing units reported the largest number of mistakes. This wasn’t because they made more mistakes, but because they felt safe to report and share the ones they did make. In fact, it became the norm.
Bad decisions and mistakes are part of life. No one has a 100% success rate in this area. And, even though we all make them it is exceedingly difficult to acknowledge them. And, this is particularly difficult in our risk-adverse culture, which too often hides its mistakes. We don’t want to be embarrassed or, in the corporate world, we don’t want to be sued. Yet when you do step forward and admit your mistakes, and work quickly and honestly to remedy them, it can earn you lasting respect from clients and peers.
So, when you make your next mistake, and you will, take care in how you respond!
Make this week a great week for you and your team. . . . jim
Jim Bruce is a Senior Fellow and Executive Coach at MOR Associates, and Professor of Electrical Engineering, Emeritus, and CIO and Vice President for Information Systems, Emeritus, at the Massachusetts Institute of Technology, Cambridge, MA.
References:
John Caddell, How To Bounce Back From A Big Mistake, 99U
Dorie Clark, What to Do When You’ve Made a Bad Decision, Harvard Business Review, August 2016.
Summary of Amazon EC2 and Amazon RDS Service Disruption in the US East Region, April 2011.
- November 2024 (2)
- October 2024 (5)
- September 2024 (4)
- August 2024 (4)
- July 2024 (5)
- June 2024 (4)
- May 2024 (4)
- April 2024 (5)
- March 2024 (4)
- February 2024 (4)
- January 2024 (5)
- December 2023 (3)
- November 2023 (4)
- October 2023 (5)
- September 2023 (4)
- August 2023 (4)
- July 2023 (4)
- June 2023 (4)
- May 2023 (5)
- April 2023 (4)
- March 2023 (1)
- January 2023 (4)
- December 2022 (3)
- November 2022 (5)
- October 2022 (4)
- September 2022 (4)
- August 2022 (5)
- July 2022 (4)
- June 2022 (4)
- May 2022 (5)
- April 2022 (4)
- March 2022 (5)
- February 2022 (4)
- January 2022 (4)
- December 2021 (3)
- November 2021 (4)
- October 2021 (3)
- September 2021 (4)
- August 2021 (4)
- July 2021 (4)
- June 2021 (5)
- May 2021 (4)
- April 2021 (4)
- March 2021 (5)
- February 2021 (4)
- January 2021 (4)
- December 2020 (4)
- November 2020 (4)
- October 2020 (6)
- September 2020 (5)
- August 2020 (4)
- July 2020 (7)
- June 2020 (7)
- May 2020 (5)
- April 2020 (4)
- March 2020 (5)
- February 2020 (4)
- January 2020 (4)
- December 2019 (2)
- November 2019 (4)
- October 2019 (4)
- September 2019 (3)
- August 2019 (3)
- July 2019 (2)
- June 2019 (4)
- May 2019 (3)
- April 2019 (5)
- March 2019 (4)
- February 2019 (3)
- January 2019 (5)
- December 2018 (2)
- November 2018 (4)
- October 2018 (5)
- September 2018 (3)
- August 2018 (3)
- July 2018 (4)
- June 2018 (4)
- May 2018 (5)
- April 2018 (4)
- March 2018 (5)
- February 2018 (5)
- January 2018 (3)
- December 2017 (3)
- November 2017 (4)
- October 2017 (5)
- September 2017 (3)
- August 2017 (5)
- July 2017 (3)
- June 2017 (8)
- May 2017 (5)
- April 2017 (4)
- March 2017 (4)
- February 2017 (4)
- January 2017 (4)
- December 2016 (2)
- November 2016 (7)
- October 2016 (5)
- September 2016 (8)
- August 2016 (5)
- July 2016 (4)
- June 2016 (12)
- May 2016 (5)
- April 2016 (4)
- March 2016 (7)
- February 2016 (4)
- January 2016 (10)
- December 2015 (4)
- November 2015 (6)
- October 2015 (4)
- September 2015 (7)
- August 2015 (5)
- July 2015 (6)
- June 2015 (12)
- May 2015 (4)
- April 2015 (6)
- March 2015 (10)
- February 2015 (4)
- January 2015 (4)
- December 2014 (3)
- November 2014 (5)
- October 2014 (4)
- September 2014 (6)
- August 2014 (4)
- July 2014 (4)
- June 2014 (4)
- May 2014 (5)
- April 2014 (5)
- March 2014 (5)
- February 2014 (4)
- January 2014 (5)
- December 2013 (5)
- November 2013 (5)
- October 2013 (10)
- September 2013 (4)
- August 2013 (5)
- July 2013 (8)
- June 2013 (6)
- May 2013 (4)
- April 2013 (5)
- March 2013 (4)
- February 2013 (4)
- January 2013 (5)
- December 2012 (3)
- November 2012 (4)
- October 2012 (5)
- September 2012 (4)
- August 2012 (4)
- July 2012 (5)
- June 2012 (4)
- May 2012 (5)
- April 2012 (4)
- March 2012 (4)
- February 2012 (4)
- January 2012 (4)
- December 2011 (3)
- November 2011 (5)
- October 2011 (4)
- September 2011 (4)
- August 2011 (4)
- July 2011 (4)
- June 2011 (5)
- May 2011 (5)
- April 2011 (3)
- March 2011 (4)
- February 2011 (4)
- January 2011 (4)
- December 2010 (3)
- November 2010 (4)
- October 2010 (4)
- September 2010 (3)
- August 2010 (5)
- July 2010 (4)
- June 2010 (5)
- May 2010 (4)
- April 2010 (3)
- March 2010 (2)
- February 2010 (4)
- January 2010 (4)
- December 2009 (4)
- November 2009 (4)
- October 2009 (4)
- September 2009 (4)
- August 2009 (3)
- July 2009 (3)
- June 2009 (3)
- May 2009 (4)
- April 2009 (4)
- March 2009 (2)
- February 2009 (3)
- January 2009 (3)
- December 2008 (3)
- November 2008 (3)
- October 2008 (3)
- August 2008 (3)
- July 2008 (4)
- May 2008 (2)
- April 2008 (2)
- March 2008 (2)
- February 2008 (1)
- January 2008 (1)
- December 2007 (3)
- November 2007 (3)
- October 2007 (3)
- September 2007 (1)
- August 2007 (2)
- July 2007 (4)
- June 2007 (2)
- May 2007 (3)
- April 2007 (1)
- March 2007 (2)
- February 2007 (2)
- January 2007 (3)
- December 2006 (1)
- November 2006 (1)
- October 2006 (1)
- September 2006 (3)
- August 2006 (1)
- June 2006 (2)
- April 2006 (1)
- March 2006 (1)
- February 2006 (1)
- January 2006 (1)
- December 2005 (1)
- November 2005 (2)
- October 2005 (1)
- August 2005 (1)
- July 2005 (1)
- April 2005 (2)
- March 2005 (4)
- February 2005 (2)
- December 2004 (1)