Project Management

Worth Hiding: Valuable Stakeholder Analysis

From the Eye on the Workforce Blog
by
Workforce management is a key part of project success, but project managers often find it difficult to get trustworthy information on what really works. From interpersonal interactions to big workforce issues we'll look the latest research and proven techniques to find the most effective solutions for your projects.

About this Blog

RSS

Recent Posts

Help Your Team Succeed as AI Reshapes Delivery

Show an Explorer's Courage in Today's Work Environment

Facilitating Team When Given New Tight Budget Part 2

Facilitating Team When Given New Tight Budget

Your RTO Employer Missed It But You Can Fix It

Categories

Artificial Intelligence, Benefits Realization, Career Development, Change Management, Communications Management, Complexity, Decision Making, Employee Engagement, HR Mgmt, Innovation, Leadership, Learning, Manage People, Organizational Culture, Performance Improvement, Recruiting, Risk Management, Robotic Process Automation, Schedule Management, Stakeholder Management, Teams, Worker Selection

Date

linkedin twitter facebook Request to reuse this  


The best information on stakeholders is safest hidden away.

That's the gist of a point I made in an article recently.  The point was that good stakeholder information can be so controversial that you cannot place it in a standard stakeholder analysis document.

Stakeholders are a key part of your project workforce. And good stakeholder information is a very valuable project treasure. If you know your stakeholders well, you have already reduced surprises. 

The wise project manager keeps two kinds of stakeholder information. The first kind can be documented in standard forms and posted on sites for document sharing. The second kind should be kept away from public view.

So there is a public analysis and there is a private analysis. Your public analysis, includes information like

  • Preferred methods of communication/interaction
  • Requirements for project
  • Ability to participate
  • Preferred meeting cadence, time of day

Your private analysis can include all the public information, but have extra columns. These extra columns should show

  • Whether the stakeholder is a supporter of the project objective, an active resistor, a passive resistor, or a "bedfellow". A bedfellow is  passive supporter.
  • How it is to work with
  • Conflicts with other stakeholders
  • Level of power or prestige in the organization
  • Conditions of satisfaction (What it takes to be satisfied with project)
  • Needs for interaction / how close to keep
  • Level of interest / impact from project on activities

Consider creating a diagram with level of Power/prestige on the X axis and on the Y axis, a spectrum from  Fully opposes (project), Somewhat opposes, Neutral, Somewhat supports, Fully supports. Place stakeholders within this diagram.

How do you get this information? If you have been in an organization for a long time, you pick it up from experience. If you are new to an organization, then start talking to people informally about the stakeholders. Do your best from it appearing as an interview. You want the feel of a friendly (safe) conversation. Ask questions about the stakeholders.

  • "She says that she is a supporter, but is she really fully supportive of this effort?"
  • "How powerful is this person in the organization?"

And so on. You get the idea.

And, because this private information can be controversial if made public, you'll need to keep this for yourself in your own notebook or somewhere else where it will not get into other's hands. Like any valuable treasure.


Posted on: April 21, 2017 12:07 AM | Permalink

Comments (14)

Please login or join to subscribe to this item
avatar
Deepesh Rammoorthy ICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood Service Tarneit, Vic, Australia
This is the portion of PMBOK that you have to know but you better not produce a formal document with the "controversial bits"
The best piece of advice and the unsaid Moses' Commandment is "know thy stakeholder" ! and maintain that deathly silence about them

avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Right Joe, this is where transparency needs to be tuned back a bit.

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks, Stakeholder Analysis is a good topic

avatar
Karthik T Senior Engineering Manager| Nike Bangalore, Karnataka, India
Interesting.

avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
Very good
Thanks

avatar
Jennifer Colucci Project Manager| 3M HIS San Marcos, Ca, United States
Yes I have learned that silent Stakeholders can make or break your project. It is very true that you should assess all stakeholders involved with your project and be aware of their influence.

avatar
Thomas Kennedy Project Engineer| BP Aberdeen, Aberdeenshire, United Kingdom
Interesting article, thanks.

avatar
Jess De Ocampo Lean Six Sigma Professional/Project Manager/Consultant/| . Manila, Ncr, Philippines
Classifying your stakeholders whether they are influencers, opposers, etc. help you determine the ways to manage their expectations. Thank you for sharing your article.

avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Thanks for the article Joe.

avatar
Mansoor Mustafa Senior PM| Government Department Rawalpindi Punjab, Pakistan
Thanks for sharing article Joe.

avatar
Dawson Preethi Design Manager BSc(Eng) MSc (Str Eng) MASCE PMP| AECOM ARABIA Riyadh, Saudi Arabia
In fact, this article is a valuable treasure to me. Thanks for sharing.

avatar
Alexandra Cote Content Marketing| Paymo Romania
Great article once again!

avatar
Karan Shah Bangalore, Karnataka, India
Fantastic article, Joe. Thanks for setting things so crisply.

I would request for a follow-up on your experience on what you would do once you have this map/chart prepared.

What would your strategies be to handle high-power x opposes stakeholders? Or for toxic team members (that may fall under low-power x opposes)? Or, indeed, how best could one leverage on all the stakeholders in supportive category?

Thanks.

avatar
Luis Branco CEO| Business Insight, Consultores de Gestão, Ldª Carcavelos, Lisboa, Portugal
Dear Joe
Interesting your perspective on the topic: "Worth Hiding: Valuable Stakeholder Analysis"
Thanks for sharing


Excellent recommendation:
"Because this private information can be controversial if it becomes public, you will need to keep it in your own notebook or elsewhere where it will not fall into the hands of others. Like any valuable treasure."

Please Login/Register to leave a comment.

ADVERTISEMENTS

"A good composer does not imitate; he steals."

- Igor Stravinsky

ADVERTISEMENT

Sponsors