The Politics of Lessons Learned

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

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:

Extrasensory Deception: I

Negotiation skills are increasingly essential in problem-solving workplaces. When incentives are strong, or pressure is high, deception is tempting. Here are some of the deceptions popular among negotiators.

The Discontinuity Effect: What and Why

Counterproductive competition is more likely in group-group interactions than in one-to-one or one-to-group interactions. Why does counterproductive competition happen?

Exploiting Functional Fixedness: II

A cognitive bias called functional fixedness causes difficulty in recognizing new uses for familiar things. It also makes for difficulty in recognizing devious uses of everyday behaviors. Here's Part II of a catalog of deviousness based on functional fixedness.

Judging Others

Being "judgmental" is a stance most people recognize as transgressing beyond widely accepted social norms. But what's the harm in judging others? And why do so many people do it so often?

Surviving Incompetence: II

When your organization undertakes a misguided effort that will certainly fail, you have options. One is to head for the exit. To search for a new position in such circumstances requires some care. Example: an internal transfer might not really be an exit.

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

Forthcoming issues of Point Lookout

Coming April 24: Antipatterns for Time-Constrained Communication: 1

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.

And on May 1: Antipatterns for Time-Constrained Communication: 2

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

Coaching services

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