Project Management

Please login or join to subscribe to this thread

Is being vague a necessity or a deterrent

linkedin twitter facebook  
avatar
Deepesh Rammoorthy ICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood Service Tarneit, Vic, Australia
After having quite a few years of Project Management experience, some PMs get the title "Senior".

Now I have interacted with a few of them and they sound extremely vague. I have to read the two lines in their email about five times and I still do not get the gist of what they are trying to say. On asking them about it face to face , they say something that may either contradict their email or is something that is clearly different.

Is Being Vague a necessary quality that they develop as they get more experienced or do they lose their basic communication skills of speaking in "simple" English.

Also, is there a need for me to start learning this secret code language?
Sort By:
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
The secret code is called human motivation. If English is their first language, and assuming they have a brain or else they wouldn't be in that position (presumably), then you have to examine their motivation for communicating that way. Communication isn't always about being clear. There are elements of disinformation at play in most organizations due to factors such as politics, power struggles, saving face, keeping one's job, reputation, fear...ergo their motivation. First ask yourself "why are they communicating this way", then ask "why are they communicating that way with me, or is it everyone", then work around that. Was this reply vague? That's cos I'm senior ;-)
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
I think the senior PMs sometimes just assume that the exact meaning of their message or words is obvious. But in reality they will be surprised to learn not only that their message was unclear but their teams were forced to guess what the boss has in mind.
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
If the PMs continue to be vague after you request clarification, then they might not know anything and are trying to bluff you. I’ve seen PMs will little skill manipulate a room full of executives in this manner. Executives are often reluctant to admit when they don’t understand something (they regard it as weakness) so a PM can show a PowerPoint and throw a few buzz words at them, and the executives will nod along just to save face. The PMs you spoke with might be trying to do something similar to you, hoping you’ll care more about saving face than pressing them for detailed answers.
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Eric made some good points. And although I am definitely one to rock the system when it needs jolting having been exposed to business transformations, I am also from the old school of respecting elders. The fact is that PM skills will vary across individuals. The majority of older PM's will have more experience than younger PM's. However, there will be some younger PM's that will run rings around an older PM. But should they display this in their attitude? I venture to say no. Being a senior PM (both in experience and age) brings along with it more than just PM skills. Many of these people have a long history with the organization and wield influence and respect that while not a substitute for great PM skills, is still a major factor why they were chosen for a particular project. While the integrity of the project must remain steadfast, calling these individuals out because they do not have as many ticks in the PM guru box as some others do is tasteless in my opinion. I recall a time (around 20 years ago) when I was a PM for a large program for one of Australia's biggest companies, and the PM above me was around 70 years old, and new less about vanilla project management than the rest of us. Some people in the program use to tease this guy behind his back, which would annoy me not least because he reminded me of my grandfather. I use to even compensate for some of his reports and meetings to make him look better. I did this not only because I didn't want this long-serving employee in the organization to look bad, but because I could see that the program required all us PM's to pull together to ensure a successful program, and that he had a lot more to offer than knowing how to populate a Gantt chart. I am rambling here, but to cut a long story short, the program ended successfully, and I would say it was largely due to the non-PM skills this senior project manager displayed: soft skills, communication, influence, compassion, pleasant nature, negotiation, understanding of the company culture, history/rapport with key stakeholders etc. After a career spanning 30 years, I can honestly say that working for this person and the program he managed was the best experience I ever had in employment.
...
1 reply by Anish Abraham
Jan 24, 2018 10:09 PM
Anish Abraham
...
Sante, glad to know about your experience 20 years ago and thanks for sharing this. I agree that we need to respect elders but they also need to give respect in order to get it back. This is just my opinion. Anyway not all seniors are like that, and I still remember working with seniors who are at least 20-30 years older than me. I'm coming from a background where we respect everyone older than us not by job title but by age.
avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
Deepesh,

Some PMs might be vague to leave to the team the choice of a better solution! The obvious is that in some case they are not at the right place.

Some are just excellent at manipulation both at team member and with the executive level.

That is not different than other field!
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Jan 24, 2018 7:59 PM
Replying to Sante Delle-Vergini, PhD
...
Eric made some good points. And although I am definitely one to rock the system when it needs jolting having been exposed to business transformations, I am also from the old school of respecting elders. The fact is that PM skills will vary across individuals. The majority of older PM's will have more experience than younger PM's. However, there will be some younger PM's that will run rings around an older PM. But should they display this in their attitude? I venture to say no. Being a senior PM (both in experience and age) brings along with it more than just PM skills. Many of these people have a long history with the organization and wield influence and respect that while not a substitute for great PM skills, is still a major factor why they were chosen for a particular project. While the integrity of the project must remain steadfast, calling these individuals out because they do not have as many ticks in the PM guru box as some others do is tasteless in my opinion. I recall a time (around 20 years ago) when I was a PM for a large program for one of Australia's biggest companies, and the PM above me was around 70 years old, and new less about vanilla project management than the rest of us. Some people in the program use to tease this guy behind his back, which would annoy me not least because he reminded me of my grandfather. I use to even compensate for some of his reports and meetings to make him look better. I did this not only because I didn't want this long-serving employee in the organization to look bad, but because I could see that the program required all us PM's to pull together to ensure a successful program, and that he had a lot more to offer than knowing how to populate a Gantt chart. I am rambling here, but to cut a long story short, the program ended successfully, and I would say it was largely due to the non-PM skills this senior project manager displayed: soft skills, communication, influence, compassion, pleasant nature, negotiation, understanding of the company culture, history/rapport with key stakeholders etc. After a career spanning 30 years, I can honestly say that working for this person and the program he managed was the best experience I ever had in employment.
Sante, glad to know about your experience 20 years ago and thanks for sharing this. I agree that we need to respect elders but they also need to give respect in order to get it back. This is just my opinion. Anyway not all seniors are like that, and I still remember working with seniors who are at least 20-30 years older than me. I'm coming from a background where we respect everyone older than us not by job title but by age.
avatar
Drake Settsu Project Manager / Blogger Hi, United States
As alway great feedback from the group.

My motto is transparency and clarity. Project Management has no room for the word "vague".
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Deepesh -

When I've encountered this before, it has been usually one of four reasons:

1. They are hedging their bets and don't want to commit

2. They are bluffing and know less than they are pretending to

3. No one has ever called them on this before

4. The situation IS genuinely foggy and hence they can't provide greater clarity

If it is a chronic behavior, then I'd suggest asking them if they are open to receiving some constructive feedback as it might help them later in their careers.

This is by no means a normal practice for seasoned PMs - while "it depends" is our favorite saying, transparency and ownership require that we take a stand.

Kiron
...
1 reply by Eric Simms
Jan 25, 2018 8:08 AM
Eric Simms
...
I'm just responding to point 4. If a situation is genuinely foggy the PM should say as much, then explain what prevents them from providing a clearer answer. That would be a non-vague explanation. For example:
"I don't know the project's end date because senior management hasn't returned answers to these two questions I sent them last week."
avatar
Eric Simms Senior Program Manager Baltimore, Maryland, United States
Jan 25, 2018 7:54 AM
Replying to Kiron Bondale
...
Deepesh -

When I've encountered this before, it has been usually one of four reasons:

1. They are hedging their bets and don't want to commit

2. They are bluffing and know less than they are pretending to

3. No one has ever called them on this before

4. The situation IS genuinely foggy and hence they can't provide greater clarity

If it is a chronic behavior, then I'd suggest asking them if they are open to receiving some constructive feedback as it might help them later in their careers.

This is by no means a normal practice for seasoned PMs - while "it depends" is our favorite saying, transparency and ownership require that we take a stand.

Kiron
I'm just responding to point 4. If a situation is genuinely foggy the PM should say as much, then explain what prevents them from providing a clearer answer. That would be a non-vague explanation. For example:
"I don't know the project's end date because senior management hasn't returned answers to these two questions I sent them last week."
avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Until projects, people and processes become truly transparent, there will always be mind games, political struggles, vagueness...I see thee things as constraints in a project but they are not documented as such. That is the reason for having a little black book to write private notes in to keep abreast of things that are "foggy".

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Two roads diverged in a wood, and I... took the one less traveled by, and that has made all the difference."

- Robert Frost

ADVERTISEMENT

Sponsors