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? rbrenteYUFXnRWhqpETASner@ChacYcAIYukguLTTagKGoCanyon.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:
- Some Causes of Scope Creep
- When we suddenly realize that our project's scope has expanded far beyond its initial boundaries —
when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope
creep. Preventing scope creep starts with understanding how it happens.
- 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.
- Status Risk and Risk Status
- One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising,
because we often fail to report the status of the project's risks, as well. What can we do to better
manage status risk and risk status?
- Project Improvisation as Group Process
- When project plans contact reality, things tend to get, um, a bit confused. We can sometimes see the
trouble coming in time to replan thoughtfully — if we're nearly clairvoyant. Usually, we have
to improvise. How a group improvises tells us much about the group.
- How to Get Out of Firefighting Mode: I
- When new problems pop up one after the other, we describe our response as "firefighting."
We move from fire to fire, putting out flames. How can we end the madness?
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming December 19: Embarrassment, Shame, and Guilt at Work: Creation
- Three feelings are often confused with each other: embarrassment, shame, and guilt. To understand how to cope with these feelings, begin by understanding what different kinds of situations we use when we create these feelings. Available here and by RSS on December 19.
- And on December 26: Embarrassment, Shame, and Guilt at Work: Coping
- Coping effectively with feelings of embarrassment, shame, or guilt is the path to recovering a sense of balance that's the foundation of clear thinking. And thinking clearly at work is important if you want to avoid feeling embarrassment, shame, or guilt. Available here and by RSS on December 26.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenIRvtlkDNIWpjanIuner@ChacHLXvFKArDxcpccxdoCanyon.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
- 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.
- 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.