Sponsors, customers, and management all expect projects to deliver what they promised, for the price promised, by the date promised. When they perceive that progress isn't in line with expectations, they can apply pressure to the project team, and that pressure can itself become a hindrance.

Freeway damage in the 1989 Loma Prieta, California, earthquake. Unexpected events often have unexpected consequences.
Photo by U.S. Geological Survey courtesy Wikipedia.
Here are some insights about the unexpected that can help with managing and preventing pressure. See "Managing Pressure: Communications and Expectations," Point Lookout for December 13, 2006, and "Managing Pressure: Milestones and Deliveries," Point Lookout for December 27, 2006, for more.
- Educate everyone about the inevitability of setbacks
- When a setback happens, perceptions of progress can change permanently, even if the setback is eventually overcome, and even if time lost is recovered. If customers or sponsors have to report the setback to people who have great organizational power, they are sometimes subject to personal consequences.
- Outside the context of any specific project, educate sponsors and managers about setbacks. Explain that because project work has either never been done before, or has never been done by this organization, setbacks are inevitable. When setbacks happen, be open about them. Hiding them or spinning them puts your own credibility at risk.
- Be wary of near-delivery setbacks
- Setbacks just prior to delivery are especially problematic. Customers might have made preparations for the delivery and those arrangements constitute both financial and psychological commitment. A setback just prior to delivery creates embarrassment, frustration, and irritation, which can lead to distrust and perceived lack of progress that are otherwise unwarranted.
- Monitor internal status carefully just prior to any delivery. As soon as you know of problems that put delivery at risk, pass the information along. Help people mitigate the consequences of slips, and commit to all this in the project plan.
- Keep loads uniform
- Setbacks just
prior to delivery
are especially
problematic - Uniform loads create a sense of steady progress. Load variations, especially spikes, degrade assessments of progress. For instance, if a project undergoes a crisis requiring an out-of-plan management decision, management endures a load spike. Afterwards, the incident isn't forgotten - it usually lingers in the form of degraded perceptions of progress. Similar effects occur within the project team.
- When trouble looms, inform management early, to give them time to prepare for decision making. Balance the loads on project team members carefully, making schedule changes as necessary — if you can — to keep loads uniform.
- Don't expect breakthroughs to erase anxiety
- Breakthroughs usually seem less significant than setbacks of similar magnitude. Hyping breakthroughs to enhance morale, or to correct perceptions about progress, probably won't work — people tend to discount such announcements because they tend to serve the project's leaders' interests.
- Use breakthroughs instead to enhance the status of the people who achieve them. Honor them and recognize them. You'll do more for morale that way than you can accomplish by trying to send the all-is-now-well message to skeptical audiences.
Next time we'll look at managing pressure by means of defining milestones, deliveries, and their spacing. 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!
More about micromanagement
When Your Boss Is a Micromanager [December 5, 2001]
- If your boss is a micromanager, your life can be a seemingly endless misery of humiliation and frustration. Changing your boss is one possible solution, but it's unlikely to succeed. What you can do is change the way you experience the micromanagement.
There Are No Micromanagers [January 7, 2004]
- If you're a manager who micromanages, you're probably trying as best you can to help your organization meet its responsibilities. Still, you might feel that people are unhappy — that whatever you're doing isn't working. There is another way.
Are You Micromanaging Yourself? [November 24, 2004]
- Feeling distrusted and undervalued, we often attribute the problem to the behavior of others — to the micromanager who might be mistreating us. We tend not to examine our own contributions to the difficulty. Are you micromanaging yourself?
Managing Pressure: Communications and Expectations [December 13, 2006]
- Pressed repeatedly for "status" reports, you might guess that they don't want status — they want progress. Things can get so nutty that responding to the status requests gets in the way of doing the job. How does this happen and what can you do about it? Here's Part I of a little catalog of tactics and strategies for dealing with pressure.
Managing Pressure: Milestones and Deliveries [December 27, 2006]
- Pressed repeatedly for "status" reports, you might guess that they don't want status — they want progress. Things can get so nutty that responding to the status requests gets in the way of doing the job. How does this happen and what can you do about it? Here's Part III of a set of tactics and strategies for dealing with pressure.
How to Tell If You Work for a Nanomanager [March 7, 2007]
- By now, we've all heard of micromanagers, and some have experienced micromanagement firsthand. Some of us have even micromanaged others. But there's a breed of micromanagers whose behavior is so outlandish that they need a category of their own.
Reverse Micromanagement [July 18, 2007]
- Micromanagement is too familiar to too many of us. Less familiar is inappropriate interference in the reverse direction — in the work of our supervisors or even higher in the chain. Disciplinary action isn't always helpful, especially when some of the causes of reverse micromanagement are organizational.
Lateral Micromanagement [September 10, 2008]
- Lateral micromanagement is the unwelcome intrusion by one co-worker into the responsibilities of another. Far more than run-of-the-mill bossiness, it's often a concerted attempt to gain organizational power and rank, and it is toxic to teams.
Bottlenecks: I [February 4, 2015]
- Some people take on so much work that they become "bottlenecks." The people around them repeatedly find themselves stuck, awaiting responses or decisions. Why does this happen and what are the costs?
Bottlenecks: II [February 11, 2015]
- When some people take on so much work that they become "bottlenecks," they expose the organization to risks. Managing those risks is a first step to ending the bottlenecking pattern.
What Micromanaging Is and Isn't [April 14, 2021]
- Micromanaging is a dysfunctional pattern of management behavior, involving interference in the work others are supposedly doing. Confusion about what it is and what it isn't makes effective response difficult.
On Schedule Conflicts [May 10, 2023]
- Schedule conflicts happen from time to time, even when the organization is healthy and all is well. But when schedule conflicts are common, they might indicate that the organization is trying to do too much with too few people.
Your comments are welcome
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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:
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?
How to Stop Being Overworked: II
- Although many of us are overloaded as a result of our own choices, some are overloaded by abusive supervisors.
If you find yourself in that situation, what can you do?
Holding Back: I
- When members of teams or groups hold back their efforts toward achieving group goals, schedule and budget
problems can arise, along with frustration and destructive intra-group conflict. What causes this behavior?
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?
Surviving Incompetence: I
- When your organization decides to undertake an effort that will certainly fail, you have options. Continuing
to oppose the decision probably isn't one of them. How can you respond to this incompetence and emerge
with your career intact?
See also Workplace Politics for more related articles.
Forthcoming issues of Point Lookout
Coming July 16: Responding to Unwelcome Events
- Unwelcome events have two kinds of effects on decision-makers. One set of effects appears as we respond to events that have actually occurred. Another set manifests itself as we prepare for unwelcome events that haven't yet occurred, but which might occur. Making a wrong decision in either case can be costly. Available here and by RSS on July 16.
And on July 23: Microdelegation
- Microdelegation is a style of delegation in which the delegator unintentionally communicates the task to the subordinate in such detail and so repetitively that the subordinate is offended. As a result of this delegation style, many subordinates feel distrusted or suspected of fraud or goldbricking. Available here and by RSS on July 23.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed


Beware any resource that speaks of "winning" at workplace politics or "defeating" it. You can benefit or not, but there is no score-keeping, and it isn't a game.
- Wikipedia has a nice article with a list of additional resources
- Some public libraries offer collections. Here's an example from Saskatoon.
- Check my own links collection
- LinkedIn's Office Politics discussion group