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? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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:
- Hostile Collaborations
- Sometimes collaboration with people we hold in low regard can be valuable. If we enter a hostile collaboration
without first accepting both the hostility and the value, we might sabotage it outside our awareness,
and that can render the effort worthless — or worse. What are the dynamics of hostile collaborations,
and how can we do them well?
- Durable Agreements
- People at work often make agreements in which they commit to cooperate — to share resources, to
assist each other, or not to harm each other. Some agreements work. Some don't. What makes agreements durable?
- OODA at Work
- OODA is a model of decision-making that's especially useful in rapidly evolving environments, such as
combat, marketing, politics, and emergency management. Here's a brief overview.
- Allocating Airtime: II
- Much has been said about people who don't get a fair chance to speak at meetings. We've even devised
processes intended to more fairly allocate speaking time. What's happening here?
- Stone-Throwers at Meetings: II
- A stone-thrower in a meeting is someone who is determined to halt forward progress. Motives vary, from
embarrassing the chair to holding the meeting hostage in exchange for advancing an agenda. What can
chairs do about stone-throwers?
Forthcoming issues of Point Lookout
- Coming August 21: Perfectionism and Avoidance
- Avoiding tasks we regard as unpleasant, boring, or intimidating is a pattern known as procrastination. Perfectionism is another pattern. The interplay between the two makes intervention a bit tricky. Available here and by RSS on August 21.
- And on August 28: Playing at Work
- Eight hours a day — usually more — of meetings, phone calls, reading and writing email and text messages, briefing others or being briefed, is enough to drive anyone around the bend. To re-energize, to clarify one's perspective, and to restore creative capacity, play is essential. Play at work, I mean. Available here and by RSS on August 28.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Lessons in Leadership
- 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. We'll use the history of this event to explore
lessons in leadership and its application to organizational efforts. A fascinating and refreshing look
at leadership from the vantage point of history. Read
more about this program. Here's a date for this program:
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio
44017: November 7,
Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute.
- Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
- 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.