December 13, 2006	Volume 6, Issue 50
Recommend this issue to a friend Join the Friends of Point Lookout HTML to link to this article…	Archive: By Topic    By Date Links to Related Articles Sign Up for A Tip A Day!
Create a perpetual bookmark to the current issue
| Follow @RickBrenner	Random Article

---

Managing Pressure:
Communications and Expectations

by Rick Brenner

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.

Just as Les was about to answer Anna, his desk phone rang. He glanced at the caller ID, looked up at Anna, and said, "It's him again. Should I answer?" He knew what she would say.

"Yeah," she said. "He probably knows we're here."

Les picked up the handset. "Yeah," he said. Nobody used Hello for internal calls anymore.

Anna couldn't hear much, but she didn't need to. The caller was their boss, and he was probably asking for yet another briefing before the review the next afternoon. The conversation went on for a while, until Les looked up at Anna.

"Three PM OK with you?"

Anna nodded. Les said "OK" into the phone and put the handset back in its cradle. Hello was already gone, and Good-Bye was well on its way.

He turned to Anna. "That's lucky," he said sarcastically. "We're just so bored here sitting around doing nothing."

They both laughed, but it wasn't funny.

When projects falter,
demands for status
and explanations
escalateWhen projects falter, demands for status and explanations escalate. Sometimes satisfying these requests interferes with the work, but at least we can understand why people worry. What's more puzzling is how this happens to projects that aren't in trouble.

Perceptions of an absence of progress usually drive such concerns. Here's Part I of a catalog of strategies for managing pressure by enhancing perceptions of progress. See "Managing Pressure: The Unexpected," Point Lookout for December 20, 2006, and "Managing Pressure: Milestones and Deliveries," Point Lookout for December 27, 2006, for more.

Choose names carefully

If a particular task encountered serious trouble in a previous project, re-using its name in a current project invites people to use their past experiences in assessing current risks.

Ironically, we often do better the second time around. Choose names that are relatively free of negative baggage.

When in trouble, don't talk — deliver

When there's little new to demonstrate, project leaders sometimes resort to words to convey a sense of progress. But during extended intervals between demonstrations of new capability, words interfere with perceptions of progress.

Because demonstrating new capability frequently does help, reschedule to provide something useful as soon as possible.

Short schedules help perceptions

Long schedules undermine perceptions of progress. This phenomenon appears to be psychological in origin, and it applies wherever customers have to wait for what they really want.

Schedule projects to complete as fast as possible. If necessary, decompose a large project into a sequence (or a partially parallel set) of smaller projects. The effectiveness of this approach might be one reason why agile methods are so popular, because they call for frequent deliveries of useful functionality.

Managing perceptions isn't just politics. Since pressure is usually counterproductive, these strategies can truly benefit your projects. I'll say more next time, but I'll pause here because I want to send this part to you as soon as possible.  Top    Next Issue

Micromanagement is a common source of pressure. For insights on micromanagers and micromanaging, see "When Your Boss Is a Micromanager," Point Lookout for December 5, 2001; "There Are No Micromanagers," Point Lookout for January 7, 2004; "Are You Micromanaging Yourself?," Point Lookout for November 24, 2004; and "How to Tell If You Work for a Nanomanager," Point Lookout for March 7, 2007.

---

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. Order Now!

Would you like to see your comments posted here? Send me your comments by email, or by Web form. 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.

More articles on Workplace Politics:

The "What-a-Great-Idea!" Trap

You just made a great suggestion at a meeting, and ended up with responsibility for implementing it. Not at all what you had in mind, but it's a trap you've fallen into before. How can you share your ideas without risk of getting even more work to do?

Currying Favor

The behavior of the office kiss-up drives many people bats. It's more than annoying, though — it does real harm to the organization. What is the behavior?

Lateral Micromanagement

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.

A Critique of Criticism: Part II

To make things better, we criticize, but we often miss the mark. We inflict pain without meaning to, and some of that pain comes back to us. How can we get better outcomes, while reducing the risks of inflicting pain?

Mitigating Risk Resistance Risk

Project managers are responsible for managing risks, but they're often stymied by insufficient resources. Here's a proposal for making risk management more effective at an organizational scale.

See also Workplace Politics, Conflict Management and Managing Your Boss for more related articles.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact me for details at rbrenner@ChacoCanyon.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 Their Tails (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 19.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

Public seminars

The Race to the South Pole: Ten Lessons for Project Managers

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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

• Northern Quest Casino, 100 N Hayford Rd, Airway Heights, WA 99001: June 11, Professional Development Day, Inland Northwest Chapter of the Project Management Institute.
   

The Race to the South Pole: The Power of Agile Development

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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

• Download to
  your calendarThe Yard, 1211 South Mammoth Road, Manchester, NH 03109: June 15, Seminar, New Hampshire Chapter of the Project Management Institute.