Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 7;   February 17, 2010: The Politics of Lessons Learned

The Politics of Lessons Learned

by

Many organizations gather lessons learned — or at least, they believe they do. Mastering the political subtleties of lessons learned efforts enhances results.
USS Indianapolis' last Commanding Officer, Captain Charles B. McVay, III

USS Indianapolis' last Commanding Officer, Captain Charles B. McVay, III, tells war corres­pon­dents 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 safe
produce 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. Go to top Top  Next issue: The Power of Situational Momentum  Next Issue

303 Secrets of Workplace PoliticsIs 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? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

Gen. George Casey, Dep. Sec. Paul Wolfowitz, and Sec. Donald RumsfeldDismissive Gestures: I
Humans are nothing if not inventive. In the modern organization, where verbal insults are deprecated, we've developed hundreds of ways to insult each other silently (or nearly so). Here's part one of a catalog of nonverbal insults.
A bristlecone pine in the Great Basin National ParkExtrasensory Deception: II
In negotiating agreements, the partners who do the drafting have an ethical obligation not to exploit the advantages of the drafting role. Some drafters don't meet that standard.
The ruins of the Temple of Apollo at DelphiOn Advice and Responsibility
Being asked for advice can be an affirming experience, but actually giving advice can sometimes entail risk. How can this happen, and what choices do we have?
Mohandas K. Ghandi, in the 1930sJust Make It Happen
Many idolize the no-nonsense manager who says, "I don't want to hear excuses, just make it happen." We associate that stance with strong leadership. Sometimes, though, it's little more than abuse motivated by ambition or ignorance — or both.
A white shark off the California coastSurviving Incompetence: I
When your organization decides to undertake an effort that will certainly fail, you have options. Continuing to oppose the decision probably isn't one of them. How can you respond to this incompetence and emerge with your career intact?

See also Workplace Politics and Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

A white water rafting team completes its courseComing December 11: White Water Rafting as a Metaphor for Group Development
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
Tuckman's stages of group developmentAnd on December 18: Subgrouping and Conway's Law
When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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:

Reprinting this article

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

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
Please donate!The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!

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.

303 Secrets of Workplace PoliticsIs 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!
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
My free weekly email newsletter gives concrete tips and suggestions for dealing with the challenging but everyday situations we all face.
A Tip A DayA Tip a Day arrives by email, or by RSS Feed, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.