Are You Changing Tactics or Moving the Goal Posts?

When we change our minds about the goals of a project, delays often result. Changing goals can cause delays even when the changes narrow the scope of the project. Why do we make so many major changes so late in development? Two possible reasons are that some goal changes seem smaller than they really are, while other goal changes masquerade as changes in tactics.

Some goal changes seem smaller than they really are

Imagine that you're an office tower developer, and that your 188-story building in Singapore has in place about 80 stories of steel, 60 stories of concrete floors, and 40 stories of glass skin. One thing that won't be on the agenda of a status review meeting is switching to a different steel alloy for floors 1 through 50.

No one would consider changing something so basic so late in the project. Yet, in product development in other industries, this sort of thing happens maddeningly often. When schedules slip and budgets overrun, our first instinct — too often — is to change the design.

Using computers for new product development is one source of this problem. Whether the product is software, integrated circuits, or even legislation, products developed with software tools don't exist physically until development is fairly advanced. When we're building a skyscraper, the physical form of the building itself helps us see the folly of many proposed changes, but products developed using software tools often lack physical form. Because of this "software effect" we feel free to move the goal posts.

Some goal changes masquerade as changes in tactics

When the workpiece
isn't physical, but is
instead represented in
software, it often
seems more malleable
than it really is

Proximity to the troubles of the status quo lets us see the necessity of a change, but it also distorts our view of it. People who propose changes are usually very familiar with the reasons for the change, and very likely to see clearly — or be affected by — the consequences of not making the change. To the proposer, the change is necessary and merely tactical, while everyone else can see clearly that it's a change in goal.

Every project goes through changes, and we must learn to limit them. Too often, my change is a needed correction, while your change is needless feature-mongering. When a debate about a change has taken this form, it's possible that both sides are right — there is a real need to change tactics, but the change proposed to address that need is more than tactical.

So if you're about to propose a change, ask yourself: Am I actually moving the goal posts — are my perceptions affected by the "software effect?" And if the change is tactical: "Is it only tactical, or is it a change of goal too?"  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:

Team Thrills

Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. How can we make it happen more often?

Backtracking in Incremental Problem Solving

Incremental problem solving is fashionable these days. Whether called evolutionary, incremental, or iterative, the approach entails unique risks. Managing those risks sometimes requires counterintuitive action.

The Risks of Too Many Projects: I

Some organizations try to run too many development projects at once. Whether developing new offerings, or working to improve the organization itself, taking on too many projects can defocus the organization and depress performance.

Yet More Obstacles to Finding the Reasons Why

Part III of our catalog of obstacles encountered in retrospectives, when we try to uncover why we succeeded — or failed.

The Risk of Astonishing Success

When we experience success, we're more likely to develop overconfidence. And when the success is so extreme as to induce astonishment, we become even more vulnerable to overconfidence. It's a real risk of success that must be managed.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming June 14: Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due to performance management systems, or lack of authority, or lack of access to information. Available here and by RSS on June 14.

And on June 21: Asking Burning Questions

When we suddenly realize that an important question needs answering, directly asking that question in a meeting might not be an effective way to focus the attention of the group. There are risks. Fortunately, there are also ways to manage those risks. Available here and by RSS on June 21.

Coaching services

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