Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 10, Issue 41;   October 13, 2010: The Politics of the Critical Path: II

The Politics of the Critical Path: II

by

Last updated: August 8, 2018

The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.
The Dalles of the St. Croix River

The Dalles of the St. Croix River, which separates Minnesota and Wisconsin. The upper photo shows just a small part of a monumental two-mile-long logjam, which occurred in 1886. The lower photo is a modern view. Between 1837 and 1912, local loggers used the river as a transportation channel for timber cut during the winter. When the river cleared of ice, the logs were dumped into the river for transport to sawmills in Stillwater, Minnesota. Just below the Dalles, the river takes a sharp turn, which repeatedly caused logjams.

By exporting trouble upstream, critical-path tasks can create logjams in projects. Those jams help to relieve the political pressure on tasks downstream in the critical path.

Lower photo courtesy Wikipedia. Upper photo courtesy Minnesota Historical Society and the U.S. National Park Service.

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 upstream
critical-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  Go to top Top  Next issue: Forward Backtracking  Next Issue

303 Secrets of Workplace PoliticsIs 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 welcome

Would 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.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

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.

Related articles

More articles on Workplace Politics:

Stalin, Roosevelt and Churchill on the portico of the Soviet Embassy at the Teheran ConferenceHostile 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?
The Japanese battleship Yamato during machinery trials 20 October 1941Durable 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?
Col. John Boyd, U.S. Air Force, in a photo taken during his time as a fighter pilotOODA 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.
A collaborative discussionAllocating 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?
The U.S. Senate Chamber in 2011Stone-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?

See also Workplace Politics and Project Management for more related articles.

Forthcoming issues of Point Lookout

An abandoned railwayComing 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.
A dog playing catch with a discAnd 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.

Coaching services

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:

Reprinting this article

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

Public seminars

The Race to the South Pole: Lessons in Leadership
On 14The Race to the South Pole: Lessons in Leadership 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:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.