Managing Pressure: Communications and Expectations

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

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

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.

Your comments are welcome

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:

Embarrassment, Shame, and Guilt at Work: Coping

Coping effectively with feelings of embarrassment, shame, or guilt is the path to recovering a sense of balance that's the foundation of clear thinking. And thinking clearly at work is important if you want to avoid feeling embarrassment, shame, or guilt.

Conway's Law and Technical Debt

Conway's Law is an observation that the structures of systems we design tend to replicate our communication patterns. This tendency might also contribute to their tendency to accumulate what we now call technical debt.

Appearance Anti-patterns: II

When we make decisions based on appearance we risk making errors. We create hostile work environments, disappoint our customers, and create inefficient processes. Maintaining congruence between the appearance and the substance of things can help.

The Fallacy of Division

Errors of reasoning are pervasive in everyday thought in most organizations. One of the more common errors is called the Fallacy of Division, in which we assume that attributes of a class apply to all members of that class. It leads to ridiculous results.

Commenting on the Work of Others

Commenting on the work of others risks damaging relationships. It can make future collaboration more difficult. To be safe when commenting about others' work, know the basic principles that distinguish appropriate and inappropriate comments.

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

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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