Want a
management tip? Learn when to shut up!
There's no shortage of books purporting to teach managers how to communicate.
In fact, I just went to Fatbrain.com,
our book vendor, and found 352 books under the listing: business
communications, general. But I think there's room for at least one more book
on the subject. I've even got the title: How to succeed in business by
learning when to shut up! I'll explain why IT managers would be well
advised to be selectively silent.
Selective silence
What I'm advocating does not require becoming a cipher or a wallflower. You
can't be a successful manager if you're unwilling to express your opinions. You
can't lead if you won't tell people where you want them to go.
What I'm pushing for is selective silence, a deliberate policy of
occasionally being quiet, and allowing the other person to talk-in fact, forcing
that person to talk.
Being strategically silent gives you some great benefits, particularly when
you're faced with a difficult situation. Rather than raising your voice, or
ranting on and on in some endless monologue, use silence to force the other
person to speak.
Human beings, like the rest of nature, abhor a vacuum. Silence makes us
uncomfortable, and most of us will talk to fill up any holes in a conversation.
Knowing this, you can sometimes use silence to your advantage.
How you can make silence work for you
Situation:
Your firm outsources its help desk operations, and over the past month, the
response time has been much worse than specified in your service level
agreement.
Proposed resolution 1:
When your account rep comes in to discuss the problem, you could get your
contract out, point out where his company is in violation, and start yelling at
the guy. That might work.
Proposed resolution 2:
On the other hand, what if you just quietly said, "Your performance is
unacceptable." And then, instead of going any further, you just stop and
look at your rep. I think you might be surprised to find that the account rep
becomes more accommodating and willing to make additional concessions, just to
get you to speak again.
Situation:
Here's an internal situation. One of your developers is three days late with
a project milestone.
Proposed resolution #1:
You could go charging into their office and berate them, reminding them of
the significance of the project, and how missing their milestone puts the whole
project delivery date in jeopardy. That might work.
Proposed resolution #2:
Here's an alternative strategy. Go into your developer's office, look them in
the eye, and calmly say, "You're three days behind schedule."
And then shut up.
Rather than immediately getting defensive when being yelled at, your
developer might attempt to fill up that silence by being more open, and
confiding about project difficulties that she would otherwise have covered up
and attempted to deal with Them self.
Things to
remember
Now the goal here is not to use silence as a method of intimidating vendors
and employees without yelling at them. The goal is to strategically use silence
to elicit more information than you would get from yelling at someone.
For this strategy to be successful, you have to remember these things: