Usually we regard the critical path as future-oriented, including only incomplete tasks. But if CP is a critical-path task, depending on a completed task C, C can suddenly find itself in the critical path. Here are some insights that help us understand the politics of the most common situations.
- Sudden discoveries
- CP, one of the consumers of C's deliverables, might suddenly discover a problem with C's deliverables. Since CP is in the critical path, it's probably experiencing pressure. By asserting that the problem lies in C, rather than CP, some of that pressure is relieved, at least temporarily.
- Notice the sources of claims that C's deliverables are deficient. If the source lies in the critical path, investigate the evidence for those claims especially carefully.
- Shipping the problem upstream
- Sometimes, troubles in a dependent task CP lead to decisions to solve the problem by reaching back to the completed task C and demanding changes. Shipping the trouble upstream in this way requires political clout, but it does happen.
- The pressure of the critical path is a common motivation for shipping trouble upstream. CP might have multiple issues. By exporting some of them, CP gains time and resources to address other issues. The intention isn't necessarily malevolent (though it can be), but as time passes, the temptation to use the excuse that "C hasn't yet fixed its deliverable" can be irresistible. C can often defend itself from such actions by making the cost of rework explicit.
- Requirements volatility
- When requirements change, they sometimes affect work already completed. If C's deliverables no longer meet requirements, C can suddenly find itself in the critical path, even if it was considered complete under the old requirements.
- Maintain vigilance over requirements that pertain to completed tasks. Changing them is usually expensive. Constituencies with interests in critical-path tasks, seeking to avoid rework in their own tasks, sometimes exert pressure to change requirements that affect already-completed tasks.
- Defective completion criteria
- Sometimes defects in the completion criteria for the completed task C aren't recognized until a dependent The pressure of the critical
path is a common motivation
for shipping trouble upstreamcritical-path task CP starts using C's deliverables. In some political environments, CP might insist that C "fix" its deliverable, even though it met the original completion criteria.
- Careful review of all completion criteria can reduce the probability of this happening, and close cooperation between C and CP can sometimes uncover completion criteria defects before C's work is complete. This is especially important when C and CP are executed at different locations or by different organizations.
Among the nastiest problems to resolve is contention for resources between a critical path task and a task that was considered complete, but which has been re-opened by the political actions of that critical-path task. Take care: sparks can fly. 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? rbrenCFBeqPDbYuBOEQihner@ChacgYrTZOHDLjldFFXVoCanyon.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 Workplace Politics:
- Is It Blame or Is It Accountability?
- When we seek those accountable for a particular failure, we risk blaming them instead, because many
of us confuse accountability with blame. What's the difference between them? How can we keep blame at bay?
- Using Indirectness at Work
- Although many of us value directness, indirectness does have its place. At times, conveying information
indirectly can be a safe way — sometimes the only safe way — to preserve or restore
well-being and comity within the organization.
- How to Avoid Responsibility
- Taking responsibility and a willingness to be held accountable are the hallmarks of either a rising
star in a high-performance organization, or a naïve fool in a low-performance organization. Either
way, you must know the more popular techniques for avoiding responsibility.
- Projects as Proxy Targets: I
- Some projects have detractors so determined to prevent project success that there's very little they
won't do to create conditions for failure. Here's Part I of a catalog of tactics they use.
- That Was a Yes-or-No Question: II
- When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances
are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no
Forthcoming issues of Point Lookout
- Coming December 13: Reframing Revision Resentment: II
- When we're required to revise something previously produced — prose, designs, software, whatever, we sometimes experience frustration with those requiring the revisions. Here are some alternative perspectives that can be helpful. Available here and by RSS on December 13.
- And on December 20: Conceptual Mondegreens
- When we disagree about abstractions, such as a problem solution, or a competitor's strategy, the cause can often be misunderstanding the abstraction. That misunderstanding can be a conceptual mondegreen. Available here and by RSS on December 20.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenuUfAhmhgjcXuMDKHner@ChacSzqmszWrsYlLnSDtoCanyon.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
- Person-to-Person Communications: Models and Applications
- When we talk, listen, send or read emails,
read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person.
And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling
hurt, and being confused. There are so many ways for things to go wrong that we could never learn how
to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes
their occurrence. In this very interactive program we'll explain — and show you how to use —
a model of inter-personal communications that can help you stay out of the ditch. We'll place particular
emphasis on a very tricky situation — expressing your personal power. In those moments of intense
involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive.
Read more about this program. Here's a date for this
- Embassy Suites by Hilton Jacksonville Baymeadows, 9300 Baymeadows
Road, Jacksonville, Florida, 32256, USA: January 15, 2018,
Monthly Meeting, Northeast Florida Chapter of the Project Management Institute. Register now.
- Embassy Suites by Hilton Jacksonville Baymeadows, 9300 Baymeadows Road, Jacksonville, Florida, 32256, USA: January 15, 2018, Monthly Meeting, Northeast Florida Chapter of the Project Management Institute. Register now.
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- 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.