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 welcomeWould you like to see your comments posted here? rbrenwepdagFNgXyUEsLiner@ChacZMulyVZvJGGMEQwdoCanyon.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:
- Toxic Projects
- A toxic project is one that harms its organization, its people or its customers. We often think of toxic
projects as projects that fail, but even a "successful" project can hurt people or damage
the organization — sometimes irreparably.
- Remote Facilitation in Synchronous Contexts: I
- Whoever facilitates your distributed meetings — whether a dedicated facilitator or the meeting
chair — will discover quickly that remote facilitation presents special problems. Here's a little
catalog of those problems, and some suggestions for addressing them.
- Symbolic Self-Completion and Projects
- The theory of symbolic self-completion holds that to define themselves, humans sometimes assert indicators
of achievement that either they do not have, or that do not mean what they seem to mean. This behavior
has consequences for managing project-oriented organizations.
- Ten Approaches to Managing Project Risks: II
- Managing risk entails coping with unwanted events that might or might not happen, and which can be costly
if they do happen. Here's Part II of our exploration of coping strategies for unwanted events.
- Wishful Thinking and Perception: II
- Continuing our exploration of causes of wishful thinking and what we can do about it, here's Part II
of a little catalog of ways our preferences and wishes affect our perceptions.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming June 28: Tackling Hard Problems: I
- Hard problems need not be big problems. Even when they're small, they can halt progress on any project. Here's Part I of an approach to working on hard problems by breaking them down into smaller steps. Available here and by RSS on June 28.
- And on July 5: Tackling Hard Problems: II
- In this Part II of our look at solving hard problems, we continue developing properties of the solution, and look at how we get from the beginning to the end. Available here and by RSS on July 5.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenBIwCZXKOQmxfWFOiner@ChachVCUXFzSCQwwlKHeoCanyon.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 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. Here are some upcoming dates for this program:
- 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 an upcoming date
for this program:
- 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 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's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England 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.
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.