
USS Indianapolis' last Commanding Officer, Captain Charles B. McVay, III, tells war correspondents about the sinking of his ship. Photographed on Guam in August 1945, following the rescue of her survivors. On July 26, 1945, the Indianapolis delivered to a base on Tinian, parts of the bomb known as Little Boy, which would be used against Hiroshima. She then left for Guam, and after departing Guam, she was attacked and sunk by a Japanese submarine. Over 300 of her crew of 1196 died in the attack, and of the 880 who went into the water, all but 317 were lost to sharks. In November, in a Naval Court Martial, Capt. McVay was convicted of Negligence in "Suffering a Vessel of the Navy to be Hazarded." His sentence was remitted and he was returned to active duty, retiring in 1949. Still, disgraced, he committed suicide in 1968. In October of 2000, Congress passed and the President signed legislation declaring that Captain McVay's military record should reflect exoneration for the loss of his command and the lives of the men who died in that disaster.
Courts martial share much in common with retrospectives. One common feature is the goal of uncovering of truth. In its handling of Capt. McVay's court martial the U.S. Navy exhibited several of the effects described here, including the consequences of compromised safety of witnesses, a lack of emphasis on what was done correctly, and very limited explorations of the contributions to the disaster by those with organizational power.
For more about the loss of the Indianapolis, visit Indianapolis.org. Official U.S. Navy Photograph, courtesy Wikimedia.
A list of "lessons learned" is usually among the deliverables of retrospectives and after-action reviews. Since listing lessons is different from learning them, there's room to question the import of the lessons learned exercise. The lists themselves are also worth examining. Here are some suggestions for anyone hoping to gather truly valuable lessons learned.
- Gathering lessons learned is necessary but not sufficient
- Many organizations do gather lessons learned, and that's useful. The next step, also necessary, is using the data collected to determine how to incorporate those lessons into organizational processes and culture. To gain from the exercise we must spend real money and allocate real effort to incorporating what we learn into future projects and ongoing processes.
- Reviewing lessons learned is essential to planning
- Lessons learned are valuable only when our successors learn from them. When we add lessons to the knowledge base, how do future planners learn about these new lessons? Reviewing past lessons learned during the planning process is one good way to propagate the benefits.
- Safety is essential
- Candid self-assessment is more likely when the assessors feel safe. If self-assessors feel that acknowledgement of responsibility for errors leads to retribution, they will (justifiably) withhold truth. Worse, they might suggest that responsibility lies elsewhere when it doesn't, or they might emphasize contributions from elsewhere to a far greater extent than they merit. A sense of safety in retrospectives is essential for eliciting Truth.
- The term "Lessons Learned" is misleading
- Many "lessons learned" aren't actually lessons we've learned. Often they're lessons we still need to learn. When we apply the label "lesson learned" to something we haven't yet learned, we enhance the risk that we'll move on without actually learning it. "Lessons To Be Learned" is usually a more accurate term.
- Beware lessons that others should learn
- When teams Candid self-assessment is
more likely when the
assessors feel safeproduce lessons learned, they sometimes include prescriptions for educating others, especially when pointing out these deficits relieves the team of responsibility for some errors. For a Lessons Learned exercise, lessons for others to learn are out of scope. Within scope are lessons about coping with others' needs for learning. But even discussing the coping can be difficult if safety is compromised, and if the others in need of learning are powerful enough. - We also learn from what went right
- Lists of lessons learned that include insights based on things that went well, in addition to those insights based on more troubled parts of the effort, probably present a more complete view. Understanding the reasons for success is at least as valuable as understanding the reasons for failure.
It's curious how so many organizations gather lessons learned about project efforts, but fail to gather lessons learned about the lessons learned effort. They probably don't know whether or not the lessons learned effort is worthwhile. I wonder what they would learn if they took a look at it…and I wonder why they aren't looking at it now. Top
Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Your comments are welcome
Would you like to see your comments posted here? rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Workplace Politics:
Management Debt: II
- As with technical debt, we incur management debt when we make choices that carry with them recurring
costs. How can we quantify management debt?
The Perils of Limited Agreement
- When a group member agrees to a proposal, even with conditions, the group can move forward. Such agreement
is constructive, but there are risks. What are those risks and what can we do about them?
Influence and Belief Perseverance
- Belief perseverance is the pattern that causes us to cling more tightly to our beliefs when contradictory
information arrives. Those who understand belief perseverance can use it to manipulate others.
Grace Under Fire: III
- When someone at work seems intent on making your work life a painful agony, you might experience fear,
anxiety, or stress that can lead to a loss of emotional control. Retaining composure is in that case
the key to survival.
Virtual Interviews: II
- The pandemic has made face-to-face job interviews less important. And so we must now also master virtual
interviews, and that requires understanding the effects of the attendance list, video presence, and
the technologies of staging, lighting, and makeup.
See also Workplace Politics and Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming December 13: Contrary Indicators of Psychological Safety: I
- To take the risks that learning and practicing new ways require, we all need a sense that trial-and-error approaches are safe. Organizations seeking to improve processes would do well to begin by assessing their level of psychological safety. Available here and by RSS on December 13.
And on December 20: Contrary Indicators of Psychological Safety: II
- When we begin using new tools or processes, we make mistakes. Practice is the cure, but practice can be scary if the grace period for early mistakes is too short. For teams adopting new methods, psychological safety is a fundamental component of success. Available here and by RSS on December 20.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick





Recommend this issue to a friend
Send an email message to a friend
rbrenogMhuqCxAnbfLvzbner@ChacigAthhhYwzZDgxshoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed


Beware any resource that speaks of "winning" at workplace politics or "defeating" it. You can benefit or not, but there is no score-keeping, and it isn't a game.
- Wikipedia has a nice article with a list of additional resources
- Some public libraries offer collections. Here's an example from Saskatoon.
- Check my own links collection
- LinkedIn's Office Politics discussion group