The Retrospective Funding Problem

Most people believe that to learn how to do things better, we have to look at how we do them now. That's the fundamental idea of project retrospectives. But there are three problems. First, we don't always conduct retrospectives. Second, when we do, we don't always do a good job. Finally, we don't consistently use what we discover when we do conduct retrospectives. We can reach a better understanding of the causes of these three problems by examining this question: who pays for retrospectives?

Typically, projects pay for their own retrospectives — or more specifically, the sponsors do. But the interest of sponsors in retrospectives is often lukewarm at best. Many sponsors feel that retrospectives add little to the deliverables they're paying for, and which have already been delivered. They do add to future deliverables of other projects, and sponsors might benefit from that someday — or they might not.

The organization as a whole is the real beneficiary of retrospectives, especially when the issues uncovered are systemic. But typically, organizations don't consciously fund retrospectives — the Chart of Accounts has no line item for them. Since organizations don't pay for retrospectives explicitly, they don't value them. I call this the Retrospective Funding Problem.

But the Retrospective Funding Problem has a deeper cause. The drive for conducting retrospectives usually comes from project teams. Since the organization isn't the driver of retrospectives, the organization is at best ambivalent about them: "You can hold a retrospective, if you want, but we won't pay extra for it. And no travel."

For virtual teams, the problem is even worse. When all elements of the virtual team are under the same financial ownership, there is at least some chance that we can apply to virtual teams any solution to the Retrospective Funding Problem for co-located teams. But even for virtual teams under one owner, divisions and other organizational structures insert a separation of financial accountability that creates obstacles for financial support.

For virtual The organization as a whole is the
real beneficiary of retrospectives,
especially when the issues
uncovered are systemicteams of mixed financial ownership, we have an additional problem: confidentiality. What can actually be disclosed in the retrospective? If an issue arises from the processes of one participating enterprise partner, can team members who hail from that partner talk about it? This tangle reduces the ability to learn, limiting performance in future partnerships between the participating enterprises.

Addressing these problems is difficult, because the retrospective expenditure happens now, and the benefit arrives in future years — three to five years from now. Because the benefit delay coincides with the tenure of most managers, the benefits of retrospectives don't arrive during the tenures of the decision makers who support them.

Until the enterprise pays for retrospectives and truly understands their value, we'll probably just muddle along.  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!

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.

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:

Restarting Projects

When a project gets off track, we sometimes cancel it. But since canceling projects takes a lot of courage, we look for ways to save them if we can. Often, things do turn out OK, and at other times they don't. There's a third choice, between pressing on with a project and canceling it. We can restart.

Start a Project Nursery

In a Project Nursery, professionals from across the entire organization collaborate to conceive of new projects. When all organizational elements help decide which projects to investigate, the menu they develop best suits organizational needs and capabilities.

Seeing Through the Fog

When projects founder, we're often shocked — we thought everything was moving along smoothly. Sometimes, with the benefit of hindsight, we can see that we had — or could have had — enough information to determine that trouble was ahead. Somehow it was obscured by fog. How can we get better at seeing through the fog?

Resuming Projects: Team Morale

Sometimes we cancel a project because of budgetary constraints. We reallocate its resources and scatter its people, and we tell ourselves that the project is on hold. But resuming is often riskier, more difficult and more expensive than we hoped. Here are some reasons why.

Films Not About Project Teams: II

Here's Part II of a list of films and videos about project teams that weren't necessarily meant to be about project teams. Most are available to borrow from the public library, and all are great fun.

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

Forthcoming issues of Point Lookout

Coming June 26: Appearance Antipatterns: I

Appearances can be deceiving. Just as we can misinterpret the actions and motivations of others, others can misinterpret our own actions and motivations. But we can take steps to limit these effects. Available here and by RSS on June 26.

And on July 3: Appearance Antipatterns: II

When we make decisions based on appearance we risk making errors. We create hostile work environments, disappoint our customers, and create inefficient processes. Maintaining congruence between the appearance and the substance of things can help. Available here and by RSS on July 3.

Coaching services

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

Public seminars

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.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.