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? rbrenCnIqWFgoNsEUBAzKner@ChacZyVftnwGzhsCFiiAoCanyon.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:
- Ground Level Sources of Scope Creep
- We usually think of scope creep as having been induced by managerial decisions. And most often, it probably
is. But most project team members — and others as well — can contribute to the problem.
- Some Hazards of Skip-Level Interviews: III
- Skip-level interviews — dialogs between a subordinate and the subordinate's supervisor's supervisor
— can be hazardous. Here's Part III of a little catalog of the hazards, emphasizing subordinate-initiated
- Suppressing Dissent: I
- In some groups, disagreeing with the majority, or disagreeing with the Leader, can be a personally expensive
act. Here is Part I of a set of tactics used by Leaders who choose not to tolerate dissent.
- Unethical Coordination
- When an internal department or an external vendor is charged with managing information about a large
project, a conflict of interest can develop. That conflict presents opportunities for unethical behavior.
What's the nature of that conflict, and what ethical breaches can occur?
- Dealing with Credit Appropriation
- Very little is more frustrating than having someone else claim credit for the work you do. Worse, sometimes
they blame you if they get into trouble after misusing your results. Here are three tips for dealing
with credit appropriation.
Forthcoming issues of Point Lookout
- Coming February 20: Brainstorming and Speedstorming: I
- Recent research suggests that brainstorming might not be as effective as we would like to believe it is. An alternative, speedstorming, might have some advantages for some teams solving some problems. Available here and by RSS on February 20.
- And on February 27: Brainstorming and Speedstorming: II
- Recent research into the effectiveness of brainstorming has raised some questions. Motivated to examine alternatives, I ran into speedstorming. Here's Part II of an exploration of the properties of speedstorming. Available here and by RSS on February 27.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfigpjBzNJFvvDljiner@ChacefpNPHYWDXBikrpFoCanyon.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.