Stakeholder Management in Change Programs

From apppm
Revision as of 19:23, 16 September 2016 by Z4p2od (Talk | contribs)

Jump to: navigation, search

Abstract

Contents

Overview

TBD


Stakeholder Analysis

Stakeholder analysis typically involves the following four steps (BSR):

  1. Identifying: Listing the individuals or groups that can be affected by and/or affect the change program.
  2. Analyzing: Formulating an understanding of the stakeholders, regarding their point of view, ambitions, power etc.
  3. Mapping: Visualizing the results of the previous step.
  4. Prioritizing: Ranking the relevance/importance of stakeholders in order to decide with which to engage.

Identifying

The objective of the first step is to produce a list of the stakeholders relevant to the organizational change program. Various tools and methods can be used on this stage such as:

  • Brain Storming: Where people are ask to write down any individuals/groups that come to mind as relevant and then the results are gathered and sorted.
  • Mind Mapping: A visualization technique used to organize information. A mind map is hierarchical and illustrates the relationships between pieces of the whole. Broad categories can be used as a starting point such as the OGC stakeholder categories (ref) (users/beneficiaries, governance, influencers & provider) and be expanded until a list of stakeholders is composed
  • Experience from previous projects/program: Utilize a stakeholder analysis that have been conducted during a previous project/ program. However, this should be performed with caution since the dynamics of stakeholders can change over time and also because stakeholders that are relevant considering one project/program are not necessarily relevant regarding another.
  • Organization charts: These can be especially helpful for identifying the internal stakeholders i.e. those entities within the organization

Typical examples of stakeholders regarding organizational change programs include:


Analyzing

Once the list of stakeholders has been conducted, the next step involves further analysis of each stakeholder in order to determine their relation to the change program, the links between each other as well as their importance, based on a chosen set of criteria. Multiple criteria have been proposed and being used in practice and their selection depends on the specific case and the background of the people conducting the analysis. Some of the most common criteria are: (ref)

  • Support towards the change program
  • Ability to influence the outcome of the change program (power)
  • Awareness regarding the change program
  • Interest towards the change program
  • Willingness to engage
  • Necessity of involvement
  • Position in the information flow network. (LINK TO ARTICLE)

Mapping

The mapping stage aims to provide a better understanding of the relative importance of stakeholders by visualizing the relative position of the stakeholders based on some or all of the criteria used previously on the analysis phase. Usually mapping is two dimensional with each axis representing a criterion. However three dimensional mapping is also possible with the size/color/shape of the depiction of the stakeholders representing the third dimension. Frequently use stakeholder mapping tools are:

  • Power/Influence- Interest grid
  • Power/Influence – Impact grid
  • Three-dimensional grouping of power, interest and attitude (ref)

Prioritizing

As it is not practical and usually unnecessary to engage with all stakeholder groups with the same level of intensity it is important to prioritize them in order allocate the most time and effort to the most important ones. The analysis and mapping steps, if performed correctly, would lead to a shorted list of stakeholders based on a set of criteria. Furthermore groups of stakeholders can be formed at this stage that require the same form of engagement. Finally the importance of the selection of the right set of criteria at a given time should also be stressed.

Stakeholder engagement

Once the stakeholders have been identified, analyzed and prioritized the next step is the formulation strategies and action plans in order to engage with the necessary stakeholders. This is of course case specific but high level “grouping” of stakeholders and engagement tactics can be useful. Perhaps, the most widely used such “grouping” deploys the power/influence – interest grid and forms the following four groups.

  • High Power High Interest: Those stakeholders are the “key players” thus they should be a top priority and managed closely. If an organization falls into this category possible beneficial engagement tactics could include some sort of partnership or collaboration.
  • High Power Low Interest: The stakeholders that fall on this category should be kept satisfied and their need should be attended because, even though they have low interest on the change program, they have the power to influence its outcome.
  • Low Power High Interest: Those stakeholders have low power to influence the change program individually. However it is best to be kept informed about the developments and their attitude towards the program should be monitored since they could form coalitions with enough power to influence the program.
  • Low Power Low Interest: The organization should spent minimum effort and time regarding the engagement with the stakeholders of this category. Nevertheless those stakeholders should be monitored in case their level of influence or interest changes or in case a powerful coalition arises from them.


Actions for influencing stakeholders to support the change program

John Heyes (ref) based on a stakeholder analysis process developed by Grundy (ref) proposed a list of actions that could help the change program obtain the maximum level of support. Grundy mapped the stakeholders on two dimensions based on their power to influence the change program (high, low) and their attitude towards the change (positive, negative). Once the stakeholder analysis based on these criteria is performed, the following actions could take place.

  1. Gaining the support of stakeholders that have negative attitude towards the change but have high power to influence the program. This could be managed by involving them more in the change process, bargaining with them or provide them with information that could persuade them about the necessity of the program. It is important for the program manager to try and understand the point of view of those who oppose the change and even giving the sceptics an opportunity to express and discuss their thoughts could lessen their negative attitude and prevent firm opposition due to stubbornness. (ref)
  2. Increasing the influence of the supporters. In order to achieve this a program manager could try to allocate supporters on positions with high power, or in decision making groups.
  3. Reducing the influence of powerful stakeholders who oppose the change. This can be achieved by preventing individuals to be part of decision making groups regarding the change program or if possible transfer them to another part of an organization. Moreover they can challenge their arguments or openly counter-argue their criticism
  4. Forming coalitions of stakeholders who support the change. Even though a stakeholder can have small influence as one entity a group of stakeholders working together could have a strong impact. A program manager can influence the formation of such coalitions by successfully communicating the vison of the change program and highlight the mutual benefits that individual stakeholders would achieve by working together towards the implementation of the change.
  5. Breaking apart existing coalitions opposing to the change or preventing their formation. This might be achieved by turning key players of the coalition into supporters as discussed on the first action.
  6. Introducing new powerful supporters. The program manager can try to persuade powerful stakeholders that have a neutral or indifferent attitude towards the change to embrace and support it. This can be achieved by publicizing the change process so it would reach stakeholders outside the organization.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox