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.
- 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 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 welcomeWould you like to see your comments posted here? rbrendjdydsoKIzzYJUotner@ChacBnaiOHZfWxjDwBvXoCanyon.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.
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.
More articles on Project Management:
- Beyond Our Control
- When bad things happen, despite our plans and our best efforts, we sometimes feel responsible. We failed.
We could have done more. But is that really true? Aren't some things beyond our control?
- Scope Creep, Hot Hands, and the Illusion of Control
- Despite our awareness of scope creep's dangerous effects on projects and other efforts, we seem unable
to prevent it. Two cognitive biases — the "hot hand fallacy" and "the illusion
of control" — might provide explanations.
- False Summits: I
- Mountaineers often experience "false summits," when just as they thought they were nearing
the summit, it turns out that there is much more climbing to do. So it is in project work.
- Ten Approaches to Managing Project Risks: I
- Risk management usually entails coping with losses if they do occur. Here's Part I of a concise summary
of the options for managing risk.
- 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.
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfDhomJqHFhTaKdaJner@ChactSchaeoGTmejoYlkoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.