RACI, Stakeholder Management & Airline Turbulence

Would *you* be surprised if a pilot asked you whether it was safe to fly?

I travelled on an internal flight to Edinburgh recently and it was foggy and raining.  It was a little turbulent, but I’m pleased to say that we landed safely. As a passenger, I was a very important “stakeholder” of the airline, but they did not ask me if it was a good idea to fly or not. The decision was (quite rightly) made without consulting me, and I took it on trust that those responsible had made the right decision.

Stakeholder management is an important part of any project. There will usually be many interested parties who need to be represented.   An effective way of categorising these stakeholders can be to use a RACI matrix, arranging them into the following groups against each milestone or deliverable:


It can sometimes be tempting to include a large number of stakeholders in the consulted category.  By trying to cover “all the angles” the number of names in the consulted category can quickly expand.

As Business Analysts and change practitioners, we know that engagement and communication are key to the success of a project.  But it is only worth consulting with people who have the right knowledge and are able to affect outcomes. In other words, it is essential that we ensure we are working with the right people, at the right time.

For example, I would have been shocked and surprised if before flight BE773 to Edinburgh, the pilot had presented himself and said:

“Right guys, I think it’s OK to fly, but it’s a little windy.  You are important stakeholders – what do you think? Shall we fly, or delay for an hour?”

This situation seems unimaginable, however similar situations occurs in projects all the time.  Have you ever been to a decision making meeting where the conversation was circular, or where no decision was made? Perhaps it was because the wrong people were in the meeting.  Perhaps their presence was the equivalent of the airline asking for my opinion about whether flight BE773 should fly.

When completing a RACI matrix, it is worth being ruthless with the “Consulted” category, and generous with the “Informed” category.  It is better to keep a wide range of stakeholders informed, but only rely on a few for consultation. And I also believe it’s worth asking stakeholders whether they need to be consulted, and if so whether there are any specific areas of the project in which they have a particular interest.  Using these approaches will increase the chances of talking to the right people at the right time.

Stakeholder management is so very important, and when mixed with a well composed engagement plan, can contribute to the success of the project.  Just watch out for the ‘C’ in RACI!

Many thanks to Robert Myers for his creative input and thorough review of this piece

Do you have any views on Stakeholder management, or any techniques to share?  I’d love to hear them, feel free to post a reply to this post, or contact me directly.

Stakeholder Management (Video)

As Business Analysts, it’s normal for us to interact with a wide range of stakeholders on our projects. Actively engaging with and managing our stakeholders is incredibly important, as it can increase the likelihood of success in our projects.

At the recent IIBA conference, I gave a short presentation on Stakeholder Management.  It is in the style of a Pecha Kucha – so it has 20 slides, each of which appears for 20 seconds.   I have provided an online version of the presentation (complete with sound) below.

The presentation covers stakeholder identification, analysis and management.  It also discuss informal (as well as formal) engagement techniques.  I hope you find this useful!

Please let me know what you think of the presentation, both in terms of the content but also the style.

Do you have any tips relating to Stakeholder Management or Stakeholder Engagement? If so, please reply to the post below.