How to Find Lessons to Learn

Lessons learned sessions are now part of the standard way of doing things, even though we know them by any number of names: Lessons Learned, After Action Review, Navy Lessons Learned, Post Mortem, Post Partum, Retrospective, Team Reflection, Project Review, and more. By whatever name, the goal is to determine what would have improved performance in the effort underway or just completed, and what might help in future efforts.

A systematic method for uncovering potential nuggets is valuable, because it reduces the chance of overlooking something important. General Morphological Analysis (GMA), invented by Fritz Zwicky, can help. [Ritchey 1998] That's a fancy name for slicing the problem space into cells and examining those cells one by one.

Slicing the problem space along two dimensions is the easiest to imagine. For Lessons Learned, I like to use the dimensions Innovation by Audience.

Innovation

Along the Innovation axis, use five categories. "Keep" includes what worked well, and what we want to keep doing. "Start" includes things we want to start doing. "Stop" includes the things that didn't work, and which we want to stop doing. "Alter" includes adjustments that we believe would be helpful for future efforts. "Try" includes ideas for experiments for the future.

Audience

The Audience axis is a list of roles, commonly called stakeholders. As we investigate each role, we imagine a conversation with people in those roles. We don't necessarily conduct actual conversations — many of these people are unavailable, and a few of them might not want to talk to us. The imaginary conversations are just tools we use to generate ideas. Audience roles can include the Project Management Office, the Team, Functional Managers, Senior Managers, Customers, Purchasing, Marketing, and so on. For this discussion, let's go with these seven roles.

In this way, we create a 5x7 matrix with one cell for each Innovation by Role combination. For each cell, we consider what we might ask or tell someone in that role about some particular Innovation.

For example, A systematic method for uncovering
potential nuggets is valuable,
because it reduces the chance of
overlooking something importantwe might consider telling a Functional Manager to stop substituting one team member for another, and then explain why. We wouldn't necessarily say this to a Functional Manager, but imagining saying it gives us a way to uncover an issue that we might then examine to determine what we can do to improve performance. This example leads to a suggestion that we plan more thoroughly for handling the risk of team member substitution.

By repeating this investigation for all 5x7=35 cells of the problem space, we might discover lessons to be learned that we might otherwise overlook.

Overlooking a lesson is one thing; being reluctant to talk about it is another. People can be reluctant to say aloud what they can easily imagine saying to senior management. To provide some safety, consider collecting suggestions for all cells anonymously.

GMA and safety, together, can provide a useful framework for your next Lessons Learned session.  Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Footnotes

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 Personal, Team, and Organizational Effectiveness:

Heavy Burdens: Should, Always, Must, and Never

As a leader you carry a heavy burden. You're accountable for everything from employee development to meeting organizational objectives, and many of these responsibilities conflict. Life is tough enough, but most of us pile on a load of over-generalized rules of work life — a load too heavy for anyone to bear.

Achieving Goals: Inspiring Passion and Action

Achieving your goals requires both passion and action. Knowing when to emphasize passion and when to emphasize action are the keys to managing yourself, or others, toward achievement.

Clueless on the Concept

When a team member seems not to understand something basic and important, setting him or her straight risks embarrassment and humiliation. It's even worse when the person attempting the "straightening" is wrong, too. How can we deal with people we believe are clueless on the concept?

I've Been Right All Along

As people, we're very good at forming and holding beliefs and opinions despite nagging doubts. These doubts lead us to search for confirmation of our beliefs, and to reject information that might conflict with our beliefs. Often, this process causes us to persist in believing nonsense. How can we tell when this is happening?

A Review of Performance Reviews: The Checkoff

As practiced in most organizations, performance reviews, especially annual performance reviews, are toxic both to the organization and its people. A commonly used tool, the checkoff, is especially deceptive.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming April 30: On Planning in Plan-Hostile Environments: II

When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.

And on May 7: Subject Matter Bullying

Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and rumor-mongering are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.

Coaching services

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