Recently I interviewed the authors of *. They shared their insights into why managing stakeholders on projects doesn’t always work out as the books would have you believe. Today it’s the turn of Jake Holloway.
Hello, Jake. What’s the difference between the textbook approach to managing stakeholders and your approach?
Standard project management textbooks assume that stakeholders are universally compliant, rational and available.
You mean they’re not??
The reality is that some of them will not even read emails or attend meetings, and are completely irrational! They might even be completely opposed to the project for any number of personal and professional reasons.
The reality is that stakeholders are people, which means that they are potentially Irrational, selfish, tribal, and proud. They like authority, influence, money, status. And sometimes they don’t like other people, and they don’t like change.
Think of our approach as bringing a political and social dimension to project management. Like Machiavelli did with The Prince.
Well, there’s a gap in my literary knowledge exposed. I’ve never read The Prince. Tell me about the most unhelpful stakeholder you’ve ever worked with.
We have all had very demanding sponsors/steering cos – so I don’t think that counts as difficult. I had a project sponsor who said in our first meeting, “I want you to know that this project shouldn’t exist and I will oppose the final recommendations, whatever they are.” Strangely enough that wasn’t the most difficult because at least he was being honest!
I think the most difficult was a CEO who took away an 100% essential technical specialist from a project, and then fired me for not being able to hit the schedule without him!
We need to be able to turn those people around. Do you see people doing that?
Good project managers do this all the time. It is what separates good project managers from bad ones. It works because they persuade, motivate, sell, enthuse and even manipulate! They don’t hide behind Gantt charts and reports and RAG statuses.
They also take the time to truly understand their stakeholders and what motivates them. They listen and empathise and put themselves in the stakeholders’ shoes, rather than think about the project only from their own perspective.
Tick box technocratic project managers are useless in projects with powerful and difficult stakeholders.
External suppliers, including individual contractors, have their own commercial objectives. It is in their interest to have projects go through change controls that increase profits. It suits them if the projects take longer to increase revenue.
This conflict of interest is not always balanced out by the external suppliers making the right decisions for the client. Even if the team delivering the project want to do the right thing, the sales person might be directly financially motivated to prevent it.
If you as a project manager pretend otherwise, the suppliers can get the upper hand. For evidence, see almost every single Central Government IT contract ever!
The team has a huge part to play in all this and they can be equally difficult. What’s your top tip for project managers struggling with their project team?
The book has a chapter full of very specific advice for dealing with a demotivated team. Whether they are being difficult or in full-on mutiny, the key is understanding the team and looking for what is behind the behaviour.
Are they bored, stressed, not learning? Is it a personality clash? Different cultures? Only once you have a handle on this can you start to come up with solutions.
Three simple things always work for me:
- Be completely honest with them.
- Talk to them much more than you think you need to.
- Have some fun together.
Look out for my review of later this year.
Read my interview with one of the other authors, Roger Joby here: The Reality of Difficult Stakeholders.
About my interviewee: Jake Holloway is an experienced project manager, consultant and Business Development Director in the areas of IT, Digital and Marketing. He has managed and sponsored hundreds of projects and portfolios, and has been involved in building and designing project management systems.
*This article contains affiliate links at no cost to you.