Project Management

How to Deal With Stakeholders Who are Obstacles

From the People and Projects Blog
by
The source of your greatest joys as a project manager will be the same as your biggest challenges: people. This is a blog for discussing issues related to leading teams and delivering projects.

About this Blog

RSS

Recent Posts

The Increasing Influence of Women in Project Management

How To Connect With People In a World of Virtual Meetings

An Experiment That Can Significantly Improve Your Performance

A Practical Way to Build Relationships (Even When You’re Short on Time)

You Are Hurting Your Career (and Project) If You're Not Doing This

Categories

accountability, bias, career, conflict, constraints, culture, decision-making, Estimating, excellence, feedback, influence, Leadership, learning, Lessons Learned, meeting management, negotiation, networking, personal performance, priority management, project management, project planning, project sponsorship, stakeholder management, time management

Date

linkedin twitter facebook Request to reuse this  


“Watch out for Susan. She pretends to be nice then blindsides you every chance she gets. It’s always all about her. Don’t trust her.”

It was my first week at a new company. I was a newly hired IT leader being warned by a colleague about my peer on the Marketing side of the house. My initial meetings with Susan seemed cordial enough, but the warning remained ominous. When would the daggers start flying?

Identifying Your Stakeholders

Identifying project stakeholders is a critically important step in getting from idea to delivery. Assuming your project will deliver real value to people, there will likely be many stakeholders excited about your project. Some will be neutral—neither for nor against your project. And then there will be the Susans. She represents those stakeholders who can be obstacles to your project success.

Some obstacle stakeholders remain in hiding until they sense their opportunity to pounce. Others are right out in the open. Their intentions of derailing your project are clear.

Strategies for Challenging Stakeholders

When a key stakeholder does not support your project, I suggest your goals should be to either Win them or Neutralize their impact. That does not mean neutralize in the sense of employing a mafia hit man! Rather, your goal is to avoid writing them off, so to speak. When someone is an obstacle, it can be tempting to respond in ways that make it even more difficult to gain their support.

Here are some strategies to consider:

Take it as a challenge. How you think about the other person will make all the difference. Since I was warned about Susan before even meeting her, my viewpoint was already painted in a negative light. Taking your equivalent of Susan as a challenge requires us to re-frame how we look at the situation. What if you forced yourself to look at their lack of support as a challenge? What if you could turn them into an ally? This doesn’t mean they need to become a best friend. But getting them off the enemy list could be a great place to start.

At the age of 16 my son Zach had the opportunity to train with a semi-pro soccer team. When Zach showed up for the first practice donning his keeper jersey and gloves, teammates warned him about the starting goalkeeper, Rick. As it turns out, Rick had a reputation for being tough on rookies. When Zach approached the veteran keeper, Rick blurted out, “What are you doing here?” Zach flashed a big smile and replied, “I’m here to learn from you!” Zach made it clear he wasn’t there to diminish Rick’s dominance as the starting keeper. From that moment on, something clicked between the two of them, leading to a season that Zach will never forget.

It may not be possible to change the “Rick” and "Susan" in your project life. But is it possible to look at them differently? The mindset change can provide the extra motivation and positive intent that can fuel the energy to at least try to win them over.

Do your homework. Every stakeholder is unique. Research consistently finds you are more likely to influence someone if you customize your approach to the other person. By doing your homework, you are better aware of what they really need, their hot buttons, and preferences.

Susan liked to be in charge. She liked to sit at the head of the table. She avoided widely swinging emotions. She liked to think of herself as being rather technical. Learning about her preferences informed me on what to expect in meetings and how to best interact with her.

Here’s another example. I once collaborated with an airline executive who had a particular bias that it was unprofessional to show up for a meeting without pen and paper. Despite the near ubiquity of tablets and other electronics for note taking, she strongly felt that you are signaling irresponsibility if you came to a meeting unequipped with a writing instrument and paper. After this bias came out in my homework about her, you can bet I showed up with pen and paper proudly in hand when I met with her!

Some executives look at a polished slide deck as a sign of a well-prepared presentation. Others want you to roll up your sleeves and draw things out on a whiteboard. Some want to see detailed project plans. Others want it on one page.

My point is that if you do your homework, you will gain insights on how to best prepare for your interactions with the stakeholder. Since your access to the stakeholder may be limited, consider soliciting advice and insight from existing allies who might better know the stakeholder.

Keep them in the loop. When dealing with a difficult stakeholder, it can be tempting to spend as little time with them as possible.  We might want to treat them with similar disrespect as they treat us.

But that approach will not likely serve the best interests of you and your project. It can certainly stretch a project manager’s patience to deal with stakeholders who are considered obstacles. However, it’s important to respectfully communicate with intent. Keep them informed. Take the high road, remaining respectful in your interactions regardless of how they treat you. The high road is almost always the path to a successful outcome.

Listen to them. I'm convinced that an enormous amount of conflict is caused by people who are not listening to each other. Donny Ebenstein, author of I Hear You, recommends you listen so well that you can tell their version of the story as well as they can. There's a reason behind the behavior. If you listen close enough, you can learn the story they are telling themselves about the project. You don't have to agree with their version of the story, but if you listen close enough, it might explain some of their obstacle behavior.

Explain the why. It’s possible that our project decisions make perfect sense to us, but we don’t take the time to communicate the rationale to stakeholders. The result can be confusion and conflict. In Robert Cialdini’s book Influence, he suggests that “because” is the most influential word in the English language because people are more likely to comply when they know the basis of a decision. 

Stay near. As Sun-tzu wisely said, “Keep your friends close and your enemies closer.” Though it’s generally not productive to consider stakeholders as enemies, the point is to stay sufficiently in touch that you aren’t blindsided by them.

Instead of avoiding a meeting because a challenging stakeholder will be there, Dr. Nick Morgan suggests that you show up and sit down right next to the difficult person. Why? People will say things in an e-mail that they won’t say face-to-face (it’s called the online disinhibition effect). Your presence may make them think twice about spewing derogatory statements about your project. But even if the challenging person disparages you or your project during the meeting, you are there to provide perspective.

Escalate when necessary. If the stakeholder issue is causing your project to delay, you may need to escalate. Dr. Allan Cohen, author of Influence Without Authorityrecommends you never blind-side someone by escalating an issue without a warning. For example, "We need to resolve this by Friday. Otherwise the project will slip, which means I will need to escalate it to the sponsor." Escalation need not be your first strategy, but it may be one you need to employ after unsuccessfully trying to resolve the issues yourself. 

Susan never became a great friend. And we certainly had disagreements along the way. But were able to work together once I learned how to manage her. I encourage you to try one or more of these strategies out on your “Susan”. Let me know how it goes!

What additional advice do you have for dealing with stakeholders who are obstacles?


Posted on: December 17, 2014 02:59 PM | Permalink

Comments (18)

Please login or join to subscribe to this item
avatar
Patti Gilchrist Product Manager| UnitedHealth Group Bluffton, Sc, United States
Excellent advice about sitting next to the difficult stakeholder. Most difficult people are more comfortable being difficult in an email and not face to face. This shows them that you are ready to come to the table as a partner. Thanks for sharing!

avatar
Andy Kaufman Host| People and Projects Podcast Lake Zurich, Il, United States
Thanks for the feedback, Patti. We've had Nick Morgan on the podcast twice and I've learned much from him. I'm afraid there are way too many example of online disinhibition (I can't even spell it) effect!

Nick's excellent blog is at http://publicwords.com/blog/.

avatar
Bindu Pillai Manager - IT| Lödige Systems Middle East Doha, Qatar
The highlight about this article is Dr. Nick Morgan's suggestion to sit down next to the Difficult person. This does work and I did experience this myself.

We considered escalating this issue several times but once we were forced in a situation where this "Susan" [borrowed the character name] wrote an email with all irrelevant logistic calculation and business jargon to all Top management. We called him for a meeting, sat facing him and addressed all his concerns.
Even though he still has his own justifications, we certainly believe that addressing his concerns in a neutralized manner did help.

Thanks Andy for the link to Nick's blog.

avatar
Chethal Mataraarachchi Associate Director, Project Management Office| Ansell Colombo, Sri Lanka
Thanks Andy, for some very good advice on this topic. I have also come across few "Susan's" in some of my projects. My comment / question? is, want it be more practical to tackle a stubborn stakeholder depending on the role he or she plays in the project (the influence they have on it). So going in to all that trouble in some cases might not be fruitful.
Any tips / your opinion on handling these two types of stakeholders at either end. For very influential ones to the project I am 100% with you on above methods. But for a stakeholder not that important we should just ignore them or is there a quick-fix method to get them aboard without spending much time?, thanks.

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
Andy, excellent points! I really appreciate your links to resources and use of examples. This is such an important topic, and one, with which, so many people seem to struggle.

I think your suggestion about viewing an obstacle as a potential ally is spot on. It doesn't always work and creating an collaborative environment, but it does tend to keep things respectful. I particularly appreciate your suggestion about learning their point of view sufficiently to tell their side of the story. This does two things, first it lets them know that you really did listen. This is a sign of respect, and one that is often in short supply. It makes a difference for people to know that they were heard. Second, it provides you as a PM with a perspective, which can often give insights into how to improve the project, or performance.

I believe that a team perspective is always more circumspect and thorough than the best thought out perspective from even the most thorough and intelligent individual. I find that if someone takes the time to voice their concerns about a project, that if I then take the time to understand their concerns and engage with them about their concerns, to address those concerns, they often do become an ally.

Chethal, give that a try. Below is a link to an article I wrote about project success, and the importance of including your team. In terms of including "difficult" stakeholders, everything still generally applies. My suggestion, try to figure out what the stakeholder is committed to, what is their primary concern, and address that.

http://www.projectmanagement.com/blog/PM-Interface/11208/

avatar
Andy Kaufman Host| People and Projects Podcast Lake Zurich, Il, United States
Michael and Chethal, thank you for your recent comments!

Chethal, if I understand your scenario correctly, you have a relatively unimportant stakeholder who you would like to gain their support with as little effort as possible. Is that approximately correct? I'd love any clarifications prior to answering. Thanks!

Michael, thank you for your kind comments and for the link to the article! I look forward to reading it!

But for a stakeholder not that important we should just ignore them or is there a quick-fix method to get them aboard without spending much time?, thanks.

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
I am always a little nervous about the idea of an "unimportant" stakeholder. Particularly if they are an end-user. I've seen unimportant stakeholders become important in short order, and in terms of longevity, they may not be important on this project, but what about the next one, or in a few months?

I like to steer clear of alienating people, even if they don't seem too influential right now. They might be influential in a short period, and I would prefer to have a good working relationship with them at that point.

I don't think it requires much time, a few minutes, to find out their concern, ensure that I understand it, and that they know I heard them. Then I ask if they have an idea of how to address it, I explore the topic with them.

Most importantly, however, particularly when I used to work construction, I saw some really ingenious solutions come out of guys who normally dug ditches, and would have been classified as unimportant stakeholders. Often I was the only guy on the site to take the time to understand their concerns and thoughts.

It did two things, first, I found some really cool solutions to problems we were facing, second they were all on my team from that moment forward. They all had my back, and they worked hard at what ever their role was, to ensure project success.

All that being said, Chethal, what kind of unimportant stakeholder do you mean? Andy's question is right on there. Is it a team member, or more of a community disturber...someone who shows up at local government meetings with a tape recorder, who argues with every point, who is contentious as a way of finding importance in the world?

avatar
Chethal Mataraarachchi Associate Director, Project Management Office| Ansell Colombo, Sri Lanka
Andy and Michael thanks for you input on my inquiry.
Michael you have actually spelled out my scenario in your last para. Let me give the picture in few sentences. On my previous job I was a PM for a hotel chain in the south Asia region, was involved in putting up 100 to 150 room 4, 5 start hotel properties (in Sri Lanka). The unimportant stakeholder which I referred to is not a core members of the team, they are the representatives of government authorities / agencies that attend meetings for observation and to check that we are within our limits during construction, etc. etc. They don't have any other right to intervene in the project unless we break rules, BUT we will never do. They have all sorts of additional queries, request for reports, etc. most of the time we don't attend since it is not required as part of the project and will not effect the project outcome.
As Michael said, we want to be on their good side since some day in the future I might have to go again to them to get approval, etc. for a new construction project. But doing all they request during meetings in the present project is not compulsory and also add a lot of unnecessary work which we don't have the time for, hope it is clear


avatar
Andy Kaufman Host| People and Projects Podcast Lake Zurich, Il, United States
Michael, I love your coaching that "unimportant" is a weak--even risky--classification. I can think of multiple examples of where I thought someone was--let's say--not as influential on the project, only to find out to the contrary later on.

(BTW, reviewing my previous post, I notice now that the last paragraph should be ignored--it was pasted from Chethal's comments).

Rather than "unimportant", let's try on some of the categorizations mentioned in the PMBOK Guide (under Stakeholder Analysis):
* Their level of authority ("power")
* Their level of concern ("interest")
* Their active involvement ("influence")
* Their ability to effect changes to the project's planning or execution ("impact")
* Their power (ability to impose their will)
* Their level of urgency (their need for immediate attention)
* The legitimacy of the involvement (their involvement is appropriate)

Those are so much richer than important vs. unimportant. Every stakeholder deserves respect. As Michael aptly reminds, we should not be alienating anyone.

Yet not all stakeholders are impacted in the same way. Or have the same need to be involved. Or the same sense of urgency, etc.

Where I have erred far more often is by not casting my stakeholder net wide enough. I only considered the actively involved stakeholders instead of the people further downstream, so to speak, that would nonetheless be impacted. Once we identify the wider group, then we do the analysis to figure out the best way to collaborate with them.

Chethal, I'd be interested in how you would describe the stakeholder(s) you have in mind using some of the above categorizations.

avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
Well said Andy!

Chethal, I'd be curious to see your analysis of the stakeholder/s in question based on those points too.

Beyond that, have you talked with them personally long enough to know what their concern is...meaning the concern which is motivating their behavior?

- Do they need to feel important?
- Do they have a concern about the project or impact of the project?
- Are they invested in project success or failure?

If you can figure out the driving concern, it may give you some clarity on how to proceed, and keep them on your side.

avatar
Aamer Inam Project Manager| NetSol Technologies Inc Lahore, Punjab, Pakistan
Great analysis when it comes to stakeholder analysis and it does not come in all in one ego starting from the start of project life cycle. This is superb approach to think in Stakeholders in that way to know what matters to them and then address it to constructively use their stake in any kind endeavor.

And in current era of ROI there is a fine notion of ROR (Return on Relationship) which can lead to a pretty good situation to deal with such Stakeholders.

avatar
Chethal Mataraarachchi Associate Director, Project Management Office| Ansell Colombo, Sri Lanka
As per the questions, below will the most relevant answers as per my interpretation their involvement in the project;
Do they need to feel important? Yes, very much
Do they have a concern about the project or impact of the project? Not really, unless it goes beyond the control limits / rules set by them
Are they invested in project success or failure? No


avatar
Michael Adams Solutions Architect| LANL Los Alamos, Nm, United States
Thank Chethal, I wonder if there is a way to have them feel important, that won't interfere too much with the project, or your time? That would be my suggestion, that way, you keep the door open for future dealings.

Great Advice, Nice Post

avatar
anil kukreti Senior engineer | Mobiquity softech pvt ltd Ghaziabad, Uttar Pradesh, India
Thanks great post. Managing susan in a project in an effective way.

avatar
DEBASIS CHAKRABARTI General Manager & Country Operations Head - Burundi Africa| Kalpataru Power Transmission Limited Kolkata, West Bengal, India
Sitting next to the difficult person is an excellent idea. I am going to try that in my next meeting.

Also, homework always helps. I know of someone who, besides getting direct feedback about someone, tries to go through linkedin, facebook, and all kinds of available online profiles of both 'friends' and 'enemies' as part of his homework. I am not sure whether its ethical or not, but according to him, this 'homework' allows him to understand the person better and if possible empathize with him/her.

avatar
Andy Kaufman Host| People and Projects Podcast Lake Zurich, Il, United States
Let me know how your next meeting goes, Debasis!

Your question about ethics is a good one. My take: as long as the goal remains to improve the relationship for mutual benefit, I don't see a problem with your colleague's "homework". His comment about this allowing him to better understand the person and empathize sounds very reasonable.

I'm a bit concerned about calling people "enemies", but other than that, have no concerns about researching stakeholders to better manage the relationships.

Thank you for your comments Debasis!

interesting!

Please Login/Register to leave a comment.

ADVERTISEMENTS

"A noble spirit enbiggens the smallest man"

- Jebediah Springfield

ADVERTISEMENT

Sponsors