Yet More Obstacles to Finding the Reasons Why

We conduct retrospectives so that we might learn. We want to improve our process by identifying what worked and what did not and why or why not. But some people are not so motivated. Some fear that if the truth comes out about something that didn't work, they might suffer in some way, and they could be right. Others believe that if the truth comes out about something that did work, a rival of theirs might benefit. They might not want that to happen.

For whatever reason, there might be among the attendees those who don't want the retrospective to uncover certain facts. Here's a short catalog of techniques available to these, um, individuals.

Scheduling obstinacy

Even when we don't meet face-to-face for the retrospective, we do usually try to have all parties present at once, if only electronically. We do this because discussion and collaborative exploration of everyone's recollections of what happened can rapidly generate insight and understanding.

Anyone intent on limiting the group's ability to find those insights can do so by failing to attend, by preventing others from attending, or by attending only when certain other people can't.

Delay

Delaying the retrospective delays any discoveries it might produce.

But Delaying the retrospective
delays any discoveries
it might produceit does more. Some people might be unavailable after a certain date, either because of termination, or transfer, or commitment to high-priority activities, or something else. By delaying the retrospective, our retro-saboteur might be hoping for scheduling conflicts to develop.

Failure to keep records

Early on in the effort, motivated by concerns that some actions they've taken (or haven't taken) might lead to problems later, especially at the retrospective, some people intentionally fail to keep records that they know are required. Or if they do keep records, they omit information or record misleading or falsely exculpatory information in those records.

Ensure that people are recording required information faithfully. If you anticipate that someone might engage in these practices, review those required records frequently, long before they're actually needed.

Evidence corruption

Differences in perspectives, recollections, and interpretations of past events often arise in retrospectives. Exchanging views, and resolving these differences, can lead to insights that advance everyone's understanding. Concrete evidence — logs, email messages, documents of all kinds — can help clarify what actually happened, which can differ from everyone's previous recollections.

Be certain of the validity of documentary evidence of actual events. By announcing at the outset of the effort — or at least, well before the retrospective — that measures are in place to protect such evidence, you can deter at least some of those who might be contemplating corrupting it.

All retrospectives are vulnerable to distraction. Digressions, irrelevancies, and spending inordinate amounts of time on minor issues can all happen innocently. Or they can be the work of individuals determined to waste time so as to prevent examination of incidents they regard as threatening. Be alert.   First issue in this series   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 Project Management:

The Politics of the Critical Path: I

The Critical Path of a project or activity is the sequence of dependent tasks that determine the earliest completion date of the effort. If you're responsible for one of these tasks, you live in a unique political environment.

Unnecessary Boring Work: II

Workplace boredom can result from poor choices by the person who's bored. More often boredom comes from the design of the job itself. Here's Part II of our little catalog of causes of workplace boredom.

How to Get Out of Firefighting Mode: II

We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

Cost Concerns: Scale

When we consider the costs of problem solutions too early in the problem-solving process, the results of comparing alternatives might be unreliable. Deferring cost concerns until we fully understand the problem can yield more options and better decisions.

Allocating Action Items

From time to time in meetings we discover tasks that need doing. We call them "action items." And we use our list of open action items as a guide for tracking the work of the group. How we decide who gets what action item can sometimes affect our success.

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

Forthcoming issues of Point Lookout

Coming May 14: Working with the Overconfident

A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.

And on May 21: Mismanaging Project Managers

Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.

Coaching services

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