Stakeholder Management
(→Stakeholder compatibility) |
|||
| (20 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | ''Developed by Anna Maria Greve'' | ||
| + | |||
| + | |||
'''Summary''' | '''Summary''' | ||
| − | The ISO 21500 standard defines a stakeholder as ''"a person, group or organisation that has interests in, or can affect, be affected by, or perceive itself to be affected by, any aspect of the project"'' <ref name="Iso"/>. Consequently, in any project it is important to analyse and identify all the key stakeholders and define which interest they have in the project and how important they are for the completion of the project. When the stakeholder analysis has been performed a plan for handling and communicating with the different stakeholders can then be created. When managing stakeholders, both internal and external, it is important to | + | The ISO 21500 standard defines a stakeholder as ''"a person, group or organisation that has interests in, or can affect, be affected by, or perceive itself to be affected by, any aspect of the project"'' <ref name="Iso"/>. Consequently, in any project it is important to analyse and identify all the key stakeholders and define which interest they have in the project and how important they are for the completion of the project. When the stakeholder analysis has been performed a plan for handling and communicating with the different stakeholders can then be created. When managing stakeholders, both internal and external, it is important to strive towards finding solutions that are mutually beneficial. The growing focus on stakeholder analysis is a clear reflection of the general tendency to recognise how stakeholders can influence decision-making processes. This article contains an overview of the importance of managing different types of stakeholders in order to ensure a suitable stakeholder involvement. |
== What are stakeholders and why are they important? == | == What are stakeholders and why are they important? == | ||
| − | Stakeholders are organisations and persons | + | Stakeholders are organisations and persons who are actively involved in a project or affected by a project at some stage during its execution or completion. The purpose of identifying and classifying stakeholders is to simplify the process of identifying stakeholder concerns and thereby obtaining an easier tool for solving issues. The prioritisation of the stakeholders is a key outcome of a stakeholder analysis, allowing the project manager to gain the necessary knowledge in order to be able to integrate all of the stakeholders’ contribution to the project in the best possible way. |
| + | Stakeholder management was first observed in Scandinavian management <ref name="Scandi">''Scandinavian Cooperative Advantage: The Theory and Practice of Stakeholder Engagement in Scandinavia, Robert Strand and R. Edward Freeman, 2013, Springer'' </ref> where they started differentiating between shareholder theory and stakeholder theory. The major differences between these two terminologies is that a shareholder owns a share in the organisation typically through stocks, thereby giving shareholder theory a more egoistic perspective since each shareholder seeks to maximise their own profit. On the other hand, a stakeholder has interests in the organisation's overall performance for other reasons than the stock value. | ||
| − | Freeman, who is particularly well-known for his work on stakeholder theory originally published in his book <ref name="REF 84">''Strategic Management: A stakeholder approach, R. Edward Freeman, 1984, Pitman, Boston, isbn=0-273-01913-9''</ref>, has defined that stakeholders with similar interests or rights will move towards forming a group<ref name="Ref1"> ''A model for stakeholder classification and stakeholder relationships, E. Mainardes, H. Alves, M.Raposo, 2012'' </ref>. The model that followed this definition is a stakeholder map, placing the company at the centre interacting with its surrounding stakeholders. Freeman also defines a stakeholder with the following sentence ‘‘a stakeholder in an organisation is any group or individual who can affect or is affected by the achievement of the organisation’s objectives’’. | + | Freeman, who is particularly well-known for his work on stakeholder theory originally published in his book <ref name="REF 84">''Strategic Management: A stakeholder approach, R. Edward Freeman, 1984, Pitman, Boston, isbn=0-273-01913-9''</ref>, has defined that stakeholders with similar interests or rights will move towards forming a group<ref name="Ref1"> ''A model for stakeholder classification and stakeholder relationships, E. Mainardes, H. Alves, M.Raposo, 2012'' </ref>. The model that followed this definition is a stakeholder map, placing the company at the centre interacting with its surrounding stakeholders. Freeman also defines a stakeholder with the following sentence ''‘‘a stakeholder in an organisation is any group or individual who can affect or is affected by the achievement of the organisation’s objectives’’''. |
Over the years more focus has been given to developing corporate social responsibility, in which understanding stakeholders plays an important role. This contributes to the growing focus on stakeholder management <ref name="CSR">''The pyramid of corporate social responsibility: Toward the moral management of organizational stakeholders, Carroll, A. B. (1991), Business Horizons, 34(4), 39–48'' </ref>. | Over the years more focus has been given to developing corporate social responsibility, in which understanding stakeholders plays an important role. This contributes to the growing focus on stakeholder management <ref name="CSR">''The pyramid of corporate social responsibility: Toward the moral management of organizational stakeholders, Carroll, A. B. (1991), Business Horizons, 34(4), 39–48'' </ref>. | ||
<span class="plainlinks">[http://en.wikipedia.org/wiki/PRINCE2 PRINCE2]</span><ref name="Prince">''Managing successful projects with PRINCE2, TSO, 2009'' </ref>, a well respected generic project management method, mentions that in order to run a successful project, the project management team should have an effective strategy to manage communication flows to and from stakeholders. It also puts an emphasis on the importance of analysing the involved stakeholders with the purpose of being able to engage properly with them. Furthermore, it underlines the importance of stakeholder involvement, especially in projects that are not a part of a programme. | <span class="plainlinks">[http://en.wikipedia.org/wiki/PRINCE2 PRINCE2]</span><ref name="Prince">''Managing successful projects with PRINCE2, TSO, 2009'' </ref>, a well respected generic project management method, mentions that in order to run a successful project, the project management team should have an effective strategy to manage communication flows to and from stakeholders. It also puts an emphasis on the importance of analysing the involved stakeholders with the purpose of being able to engage properly with them. Furthermore, it underlines the importance of stakeholder involvement, especially in projects that are not a part of a programme. | ||
| − | The <span class="plainlinks">[http://en.wikipedia.org/wiki/A_Guide_to_the_Project_Management_Body_of_Knowledge PMBOK]</span> Guide's 4th edition had stakeholder identification and management of stakeholder expectations in the communication management knowledge area. However with the 5th edition the <span class="plainlinks">[http://en.wikipedia.org/wiki/Project_Management_Institute Project Management | + | The <span class="plainlinks">[http://en.wikipedia.org/wiki/A_Guide_to_the_Project_Management_Body_of_Knowledge PMBOK]</span> Guide's 4th edition had stakeholder identification and management of stakeholder expectations in the communication management knowledge area. However with the 5th edition the <span class="plainlinks">[http://en.wikipedia.org/wiki/Project_Management_Institute Project Management Institute]</span> (PMI) has recognised the importance of stakeholder management and given it its own knowledge area - Project Stakeholder Management. <ref name="PMI"/> |
| + | |||
| + | This really underlines the importance of creating awareness of the importance of integrating stakeholders in all types of projects. | ||
==Identifying and classifying stakeholders== | ==Identifying and classifying stakeholders== | ||
| Line 41: | Line 47: | ||
Furthermore, the client/end-user of the project outcome is also an important stakeholder, because the outcome of the project can become an utter failure if the accept of the client/end-user is taken for granted. This is why it is crucial to maintain a continuous dialogue with the client to constantly manage expectations. | Furthermore, the client/end-user of the project outcome is also an important stakeholder, because the outcome of the project can become an utter failure if the accept of the client/end-user is taken for granted. This is why it is crucial to maintain a continuous dialogue with the client to constantly manage expectations. | ||
|} | |} | ||
| + | |||
| + | |||
===Power, legitimacy, and urgency classification=== | ===Power, legitimacy, and urgency classification=== | ||
| Line 65: | Line 73: | ||
:* It is dynamic because it considers changes in interests over social space and time | :* It is dynamic because it considers changes in interests over social space and time | ||
| − | Furthermore, the stakeholder salience model proposed by Mitchell ''et al.'' <ref name="Mitch">''“Toward a theory of stakeholder identification and salience: defining the principle of who and what really counts”, R. Mitchell, B. Agle, and D. Wood, 1997, Academy of Management Review, Vol. 22 No. 4, pp. 853-8.''</ref> suggests that strategic behaviour is subject to various groups located in the surrounding environment with organisational strategies needing to meet the needs of these groups in accordance with their respective importance. This is defined by the three aforementioned factors varying in accordance with the situation. The proposed model is therefore dynamic for the following three reasons: | + | Furthermore, the stakeholder salience model proposed by Mitchell ''et al.'' <ref name="Mitch">''“Toward a theory of stakeholder identification and salience: defining the principle of who and what really counts”, R. Mitchell, B. Agle, and D. Wood, 1997, Academy of Management Review, Vol. 22 No. 4, pp. 853-8.''</ref> <ref name="Ref2"/> suggests that strategic behaviour is subject to various groups located in the surrounding environment with organisational strategies needing to meet the needs of these groups in accordance with their respective importance. This is defined by the three aforementioned factors varying in accordance with the situation. The proposed model is therefore dynamic for the following three reasons: |
:* The three attributes are variables - neither static nor stationary | :* The three attributes are variables - neither static nor stationary | ||
:* The attributes are socially constructed - not objective | :* The attributes are socially constructed - not objective | ||
:* Stakeholders do not always know that they are in possession of one or more attributes | :* Stakeholders do not always know that they are in possession of one or more attributes | ||
| − | + | There are some suggested limitations to this model following empirical work<ref name="Ref2"/>. Mitchell ''et al.'' <ref name="Mitch"/> suggests that the attributes are binary, however when looking further in to the characteristics of each attribute, questions start to arise as to whether it these maybe could be more that binary attributes <ref name="Ref1"/>. These limitations are somewhat related to following classification method, where specific categories have been made for each of the combinations. | |
===Detailed stakeholder classification=== | ===Detailed stakeholder classification=== | ||
| Line 110: | Line 118: | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | |+Four stakeholder configurations | + | |+Four stakeholder configurations <ref name="Ref2"/> |
|- | |- | ||
|'''Configuration''' | |'''Configuration''' | ||
| − | |''' | + | |'''Description''' |
|- | |- | ||
|Necessary compatible | |Necessary compatible | ||
| Line 129: | Line 137: | ||
=== The classic stakeholder matrix=== | === The classic stakeholder matrix=== | ||
| − | [[File:StakeholderMatrix.jpg|thumb|left|350px|A stakeholders matrix showing what overall strategy should | + | [[File:StakeholderMatrix.jpg|thumb|left|350px|A stakeholders matrix showing what overall strategy should choose for each of the four categories <ref name="PI"/>]] |
Stakeholders need to be involved along the whole process of a project no matter the type. This is where the identification and categorisation shows its crucial importance. Based on the analysis of the stakeholders these can be mapped into overall categories, which allows the managers in an organisation to take action. The most commonly used stakeholder map is the power/interest matrix, seen in the figure to the left, which gives an easy and simple overview of what the different categories require with regards to what their needs are and how much they are able to influence the project. | Stakeholders need to be involved along the whole process of a project no matter the type. This is where the identification and categorisation shows its crucial importance. Based on the analysis of the stakeholders these can be mapped into overall categories, which allows the managers in an organisation to take action. The most commonly used stakeholder map is the power/interest matrix, seen in the figure to the left, which gives an easy and simple overview of what the different categories require with regards to what their needs are and how much they are able to influence the project. | ||
| Line 136: | Line 144: | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | |+ How to use the Power/Interest Matrix <ref name="PI">''http://www.mindtools.com/pages/article/newPPM_07.htm, accessed | + | |+ How to use the Power/Interest Matrix <ref name="PI">''http://www.mindtools.com/pages/article/newPPM_07.htm, accessed December 1st'' </ref> |
|- | |- | ||
|'''Position''' | |'''Position''' | ||
| Line 163: | Line 171: | ||
{| class="wikitable" | {| class="wikitable" | ||
| − | |+Stakeholder Engagement approaches<ref name="Tri">''http://www.stakeholdermap.com/stakeholder-engagement.html, accessed | + | |+Stakeholder Engagement approaches<ref name="Tri">''http://www.stakeholdermap.com/stakeholder-engagement.html, accessed November 30th'' </ref> |
|- | |- | ||
|'''Engagement approach''' | |'''Engagement approach''' | ||
| Line 181: | Line 189: | ||
|- | |- | ||
|Pull communications | |Pull communications | ||
| − | |One-way engagement. Information is made available | + | |One-way engagement. Information is made available and stakeholders choose whether to engage with it. |
|} | |} | ||
| Line 189: | Line 197: | ||
The matrix prompts planners to think about responding to or engaging different stakeholders in different ways over the course of a policy or strategy change effort. As a result, the benefits of taking stakeholders seriously may be gained while avoiding the perils of inappropriately responding to or engaging stakeholders <ref name="PartMatrix"/> | The matrix prompts planners to think about responding to or engaging different stakeholders in different ways over the course of a policy or strategy change effort. As a result, the benefits of taking stakeholders seriously may be gained while avoiding the perils of inappropriately responding to or engaging stakeholders <ref name="PartMatrix"/> | ||
| − | In the following some more detailed ways of integrating stakeholders to the project will be | + | In the following some more detailed ways of integrating stakeholders to the project will be described. |
===Stakeholder integration methods=== | ===Stakeholder integration methods=== | ||
| Line 197: | Line 205: | ||
[[File:Typology.jpg|thumb|left|450px|The typology of Stakeholder Integration Mechanisms <ref name="Int"/>]] | [[File:Typology.jpg|thumb|left|450px|The typology of Stakeholder Integration Mechanisms <ref name="Int"/>]] | ||
| − | :*Buffering: Buffering strategies are adopted by many organisations in order to cope with the need for certainty. The aim is to seal of the core transformation processes from external influences in the environment. Buffering can also be used as a tool for stakeholder integration, and attempts to create close relations with representative organisations. The main purpose is to avoid the many problems associated with having many indirect stakeholder, who are thereby less controllable. Having many indirect stakeholders puts organisations in a vulnerable position with regards to influencing the information exchange processes in the stakeholder network. <ref name="Int"/> | + | :* '''Buffering''': Buffering strategies are adopted by many organisations in order to cope with the need for certainty. The aim is to seal of the core transformation processes from external influences in the environment. Buffering can also be used as a tool for stakeholder integration, and attempts to create close relations with representative organisations. The main purpose is to avoid the many problems associated with having many indirect stakeholder, who are thereby less controllable. Having many indirect stakeholders puts organisations in a vulnerable position with regards to influencing the information exchange processes in the stakeholder network. <ref name="Int"/> |
| − | :*Co-optation: Organisations will always have to deal with direct stakeholders, who differ in their degree of perceived salience. Buffering is not always an option due to the fact that some of the most important stakeholders provide direct contributions to the organisation's technical core through investments in co-specialised assets. As a tool for handling the challenges and uncertainties linked with these types of stakeholder bonds, the organisation may choose to create co-optation. Co-optation has been defined by Selznick as “the process of absorbing new elements into the leadership or policy-determining structure of an organisation as a means of averting threats to its stability or existence” <ref name="Selz"> ''TVA and the grass roots, P. Selznick, 1949, Berkeley: University of California Press.''</ref>. Co-optation is thereby a partial absorption technique used in cases where total absorption is not possible. In regards to stakeholder integration, co-optation is a <span class="plainlinks">[http://en.wikipedia.org/wiki/Dyad_(sociology) dyadic]</span> technique. By using this technique the organisation adapts to a firm's leadership structure with the purpose of obtaining external stakeholders' consent or to communicate mutually beneficial information <ref name="Int"/>. | + | :* '''Co-optation''': Organisations will always have to deal with direct stakeholders, who differ in their degree of perceived salience. Buffering is not always an option due to the fact that some of the most important stakeholders provide direct contributions to the organisation's technical core through investments in co-specialised assets. As a tool for handling the challenges and uncertainties linked with these types of stakeholder bonds, the organisation may choose to create co-optation. Co-optation has been defined by Selznick as “the process of absorbing new elements into the leadership or policy-determining structure of an organisation as a means of averting threats to its stability or existence” <ref name="Selz"> ''TVA and the grass roots, P. Selznick, 1949, Berkeley: University of California Press.''</ref>. Co-optation is thereby a partial absorption technique used in cases where total absorption is not possible. In regards to stakeholder integration, co-optation is a <span class="plainlinks">[http://en.wikipedia.org/wiki/Dyad_(sociology) dyadic]</span> technique. By using this technique the organisation adapts to a firm's leadership structure with the purpose of obtaining external stakeholders' consent or to communicate mutually beneficial information <ref name="Int"/>. |
| − | :*Mutual learning: The purpose is to redefine the interdependencies between organisations and stakeholders <ref name="Gray">''Collaborating: Finding common ground for multiparty problems, B. Gray, 1989, San Francisco: Jossey-Bass'' </ref>. Individual organisations will most likely bring their own feasibility preoccupations to the table, which consequently puts a restriction on the range of cooperative options. However, by using dyadic collaboration processes, interdependent organisations and stakeholders will be able to discover each other’s feasibility preoccupations and find a solution that satisfies some, if not all, of the interests of each of the stakeholders involved <ref name="Wood">''Toward a comprehensive theory of collaboration, D.J. Wood & B. Gray, 1991, Journal of Applied Behavioral Science, 27, 139-162.''</ref>. | + | :* '''Mutual learning''': The purpose is to redefine the interdependencies between organisations and stakeholders <ref name="Gray">''Collaborating: Finding common ground for multiparty problems, B. Gray, 1989, San Francisco: Jossey-Bass'' </ref>. Individual organisations will most likely bring their own feasibility preoccupations to the table, which consequently puts a restriction on the range of cooperative options. However, by using dyadic collaboration processes, interdependent organisations and stakeholders will be able to discover each other’s feasibility preoccupations and find a solution that satisfies some, if not all, of the interests of each of the stakeholders involved <ref name="Wood">''Toward a comprehensive theory of collaboration, D.J. Wood & B. Gray, 1991, Journal of Applied Behavioral Science, 27, 139-162.''</ref>. |
| − | :*Meta-problem solving: "Symbiotic interdependencies are not necessarily restricted to the dyadic level but may extend to the network level" <ref name="Wes">''Interorganizational collaboration and the preservation of global biodiversity, F. Westley & H. Vredenburg, 1997, Organization Science, 8, 381-403.''</ref>. An example of these interdependencies is when many organisations are facing the same ill-defined problem domain. This could be a domain in which the key stakeholders are not yet defined <ref name="Gray"/>. Meta-problems exceed the boundaries of the majority of individual organisations; therefore, they must be addressed by combining multiple perspectives and resources in order to find a resolution.Consequently, effective meta-problem solving consists of collaborative processes operated at the network level in order to help with the integration of organisations “that may be widely disparate in wealth, power, culture, language, values, interests, and structural characteristics” <ref name="Int"/>. | + | :* '''Meta-problem solving''': "Symbiotic interdependencies are not necessarily restricted to the dyadic level but may extend to the network level" <ref name="Wes">''Interorganizational collaboration and the preservation of global biodiversity, F. Westley & H. Vredenburg, 1997, Organization Science, 8, 381-403.''</ref>. An example of these interdependencies is when many organisations are facing the same ill-defined problem domain. This could be a domain in which the key stakeholders are not yet defined <ref name="Gray"/>. Meta-problems exceed the boundaries of the majority of individual organisations; therefore, they must be addressed by combining multiple perspectives and resources in order to find a resolution. Consequently, effective meta-problem solving consists of collaborative processes operated at the network level in order to help with the integration of organisations “that may be widely disparate in wealth, power, culture, language, values, interests, and structural characteristics” <ref name="Int"/>. |
| − | These four integrations mechanisms can be seen in the figure above to the left, where their relation to | + | These four integrations mechanisms can be seen in the figure above to the left, where their relation to each other can be visualised. |
== Discussion == | == Discussion == | ||
| − | An interesting note to add | + | An interesting note to add is that the newest addition to the PMBOK 5 is a tenth Knowledge Area, Project Stakeholder Management. However, stakeholder management is of course not new to this standard, it has merely been given its own area instead of being a part of the Communications Knowledge Area. PMI has done this in order to emphasise the importance of this area. This helps raise the level of importance of stakeholder management to an equal level with the other Knowledge Areas. |
| − | Stakeholder management is in fact one of the hardest things a project manager has to deal with and a major aspect of this is equal parts stakeholder involvement and communication. In compliance with the main message of this article, PMBOK 5 is putting a strong emphasis on the fact that the project manager must keep the stakeholders engaged throughout the project, not just informed. <ref name="PMI">''http://www.allpm.com/index.php/our-community/94-article/newsletter-article/496-changes-in-pmbok-5th-edition, accessed | + | Stakeholder management is in fact one of the hardest things a project manager has to deal with and a major aspect of this is equal parts stakeholder involvement and communication. In compliance with the main message of this article, PMBOK 5 is putting a strong emphasis on the fact that the project manager must keep the stakeholders engaged throughout the project, not just informed. <ref name="PMI">''http://www.allpm.com/index.php/our-community/94-article/newsletter-article/496-changes-in-pmbok-5th-edition, accessed November 30th 2014''</ref> |
In the spirit of looking at standards it should be mentioned that stakeholder management and involvement is only very briefly described in the ISO standard 21500 <ref name="Iso">''Guidance on project management, DS/ISO 21500, Danish Standards, 2013'' </ref> and has yet to be described in a way which underlines its importance. | In the spirit of looking at standards it should be mentioned that stakeholder management and involvement is only very briefly described in the ISO standard 21500 <ref name="Iso">''Guidance on project management, DS/ISO 21500, Danish Standards, 2013'' </ref> and has yet to be described in a way which underlines its importance. | ||
| Line 216: | Line 224: | ||
Managing the relationships with each stakeholder should furthermore pay attention to how these are guided by organisational actions and initiatives established with the purpose of creating, building and strengthening the organisation’s bonds with each respective stakeholder <ref name="Ref1"/><ref name="PartMatrix"/>. | Managing the relationships with each stakeholder should furthermore pay attention to how these are guided by organisational actions and initiatives established with the purpose of creating, building and strengthening the organisation’s bonds with each respective stakeholder <ref name="Ref1"/><ref name="PartMatrix"/>. | ||
| − | Conclusively, it can be seen that there are a variety of stakeholder management tools. The importance of stakeholder management is | + | Conclusively, it can be seen that there are a variety of stakeholder management tools. The importance of stakeholder management is gradually being recognised by the major project management standards, instead of only including stakeholder management as a part of the communication paragraphs. |
It is important for project managers to realise the importance of creating the right involvement from each stakeholder, this is where the different classification tools will be helpful. The need for more or less detailed stakeholder classification is dependent on the size and type of a given project. However, stakeholder management will always be of the utmost importance for the success of project. | It is important for project managers to realise the importance of creating the right involvement from each stakeholder, this is where the different classification tools will be helpful. The need for more or less detailed stakeholder classification is dependent on the size and type of a given project. However, stakeholder management will always be of the utmost importance for the success of project. | ||
| Line 223: | Line 231: | ||
| − | + | [[Category:Project Management]] [[Category:Stakeholder Analysis]][[Category:Conflict Management]] | |
Latest revision as of 13:34, 20 December 2018
Developed by Anna Maria Greve
Summary
The ISO 21500 standard defines a stakeholder as "a person, group or organisation that has interests in, or can affect, be affected by, or perceive itself to be affected by, any aspect of the project" [1]. Consequently, in any project it is important to analyse and identify all the key stakeholders and define which interest they have in the project and how important they are for the completion of the project. When the stakeholder analysis has been performed a plan for handling and communicating with the different stakeholders can then be created. When managing stakeholders, both internal and external, it is important to strive towards finding solutions that are mutually beneficial. The growing focus on stakeholder analysis is a clear reflection of the general tendency to recognise how stakeholders can influence decision-making processes. This article contains an overview of the importance of managing different types of stakeholders in order to ensure a suitable stakeholder involvement.
Contents |
[edit] What are stakeholders and why are they important?
Stakeholders are organisations and persons who are actively involved in a project or affected by a project at some stage during its execution or completion. The purpose of identifying and classifying stakeholders is to simplify the process of identifying stakeholder concerns and thereby obtaining an easier tool for solving issues. The prioritisation of the stakeholders is a key outcome of a stakeholder analysis, allowing the project manager to gain the necessary knowledge in order to be able to integrate all of the stakeholders’ contribution to the project in the best possible way. Stakeholder management was first observed in Scandinavian management [2] where they started differentiating between shareholder theory and stakeholder theory. The major differences between these two terminologies is that a shareholder owns a share in the organisation typically through stocks, thereby giving shareholder theory a more egoistic perspective since each shareholder seeks to maximise their own profit. On the other hand, a stakeholder has interests in the organisation's overall performance for other reasons than the stock value.
Freeman, who is particularly well-known for his work on stakeholder theory originally published in his book [3], has defined that stakeholders with similar interests or rights will move towards forming a group[4]. The model that followed this definition is a stakeholder map, placing the company at the centre interacting with its surrounding stakeholders. Freeman also defines a stakeholder with the following sentence ‘‘a stakeholder in an organisation is any group or individual who can affect or is affected by the achievement of the organisation’s objectives’’. Over the years more focus has been given to developing corporate social responsibility, in which understanding stakeholders plays an important role. This contributes to the growing focus on stakeholder management [5].
PRINCE2[6], a well respected generic project management method, mentions that in order to run a successful project, the project management team should have an effective strategy to manage communication flows to and from stakeholders. It also puts an emphasis on the importance of analysing the involved stakeholders with the purpose of being able to engage properly with them. Furthermore, it underlines the importance of stakeholder involvement, especially in projects that are not a part of a programme.
The PMBOK Guide's 4th edition had stakeholder identification and management of stakeholder expectations in the communication management knowledge area. However with the 5th edition the Project Management Institute (PMI) has recognised the importance of stakeholder management and given it its own knowledge area - Project Stakeholder Management. [7]
This really underlines the importance of creating awareness of the importance of integrating stakeholders in all types of projects.
[edit] Identifying and classifying stakeholders
The process of identifying and classifying stakeholders is the preliminary part of managing stakeholders in an organisation. This can be made by the use of different classifications methods. These will be briefly introduced in the following segment.
[edit] Classification according to "direction"
Firstly stakeholders can be categorised into the following three overall categories also depicted in the figure to the left:[8]
| Direction | Description |
| Downward stakeholders | Here you find the project group itself – they hold a critical role in the completion of the project and their effort is crucial. In order to manage the project group it is important to clarify what the members wish to obtain or accomplish by participating in the project. Moreover it is important for each member to state what his/her contribution will be depending on the set of skills each member possesses. |
| Upward stakeholders | Here you find the stakeholders financing the project, amongst them you will also find the project owner. In order to manage the expectations of the project owner, it is important that these are discussed at the beginning of the project in order for the expectations to be achievable and in compliance with the reality.
The role of the project owner is to give visible support to the project and to use his formal power to help the project move along. |
| Outward stakeholders | These stakeholders can both be internal and external to the organisation where the project is taking place.
The external outward stakeholders could be the clients, suppliers, authorities and competitors amongst others. The internal outward stakeholders could be the other project managers for projects run in parallel, other employees not directly involved in the project at hand, line managers, etc.… Furthermore, the client/end-user of the project outcome is also an important stakeholder, because the outcome of the project can become an utter failure if the accept of the client/end-user is taken for granted. This is why it is crucial to maintain a continuous dialogue with the client to constantly manage expectations. |
[edit] Power, legitimacy, and urgency classification
A common method is to classify the stakeholders according to the following three categories: [4]
| Stakeholder classification 2 [4] |
| Power |
| Legitimacy |
| Urgency |
With the use of this classification method, the stakeholders can either hold a combination of the categories or only one of them.
Stakeholder salience [4] is, according to Friedman and Miles [9], a model which includes stakeholder powers of negotiation, their relational legitimacy and the urgency in attending to stakeholder requirements. Mitchell et al. [10] view this model as being a dynamic model, displaying three main advantages:
- It is political because it considers the organisation as the result of conflicting and unequal interests
- It is operationally practical because it qualifies the stakeholders
- It is dynamic because it considers changes in interests over social space and time
Furthermore, the stakeholder salience model proposed by Mitchell et al. [10] [11] suggests that strategic behaviour is subject to various groups located in the surrounding environment with organisational strategies needing to meet the needs of these groups in accordance with their respective importance. This is defined by the three aforementioned factors varying in accordance with the situation. The proposed model is therefore dynamic for the following three reasons:
- The three attributes are variables - neither static nor stationary
- The attributes are socially constructed - not objective
- Stakeholders do not always know that they are in possession of one or more attributes
There are some suggested limitations to this model following empirical work[11]. Mitchell et al. [10] suggests that the attributes are binary, however when looking further in to the characteristics of each attribute, questions start to arise as to whether it these maybe could be more that binary attributes [4]. These limitations are somewhat related to following classification method, where specific categories have been made for each of the combinations.
[edit] Detailed stakeholder classification
Stakeholders can also be classified into further specific types, as presented by the article "A model for stakeholder classification and stakeholder relationships": [4]
| Classification | Description |
| Dormant | Groups and individuals with the power to impose their wills on the organisation but lack either legitimacy or urgency. Consequently, their power is of no use when there is little or no ongoing interaction with the company. However, this should not be misinterpreted by the organisation, because they still need to monitor this stakeholder type. |
| Discretionary | Groups and individuals with legitimacy but a lack of both the power and urgency. With these stakeholders, attention should be paid to them under the framework of corporate social responsibility as they tend to be more receptive. |
| Demanding | When the most important attribute is urgency. Without power or legitimacy, they will not have great demands to the company, however, they do require monitoring as regards their potential to gain a second attribute. |
| Dominant | Groups and individuals that hold influence over the company guaranteed by power and legitimacy. These types of stakeholder will expect and receive a lot of attention from the company, as they should. |
| Dangerous | Groups and individuals that hold attributes of power as well as urgency but who are lacking legitimacy. The coercive stakeholder may represent a threat to the organisation and should therefore be managed closely. |
| Dependent | Groups and individuals that hold attributes of urgency and legitimacy but who are also dependent on another stakeholder in order to draw attention to their claims. |
[edit] Differences in stakeholder influence
[edit] Stakeholder compatibility
Why do some stakeholders have more influence over organizations than others? Some literature [11] suggests that this is influenced by:
- The structural nature of the organisation / stakeholder relation
- The contractual forms existing
- The institutional support that is available.
These influences are strongly linked to the stakeholder configurations and the associated stakeholder types. The same article [11] suggests that there are the following four stakeholder configurations:
| Configuration | Description |
| Necessary compatible | This category represents the relation between shareholders and corporations and would typically be bound by a contract. These contracts would of course differ based on the type of stakeholders. |
| Contingent incompatible | This category represents non-contractual relations. These can be both implicit or explicit and recognised or unrecognised. |
| Necessary incompatible | This category typically involves recognised explicit or implicit contracts, however, there are differences in interests among the parties involved. |
| Contingent compatible | This represents relations with no formal contract and no direct relationship between the parties. |
[edit] The classic stakeholder matrix
Stakeholders need to be involved along the whole process of a project no matter the type. This is where the identification and categorisation shows its crucial importance. Based on the analysis of the stakeholders these can be mapped into overall categories, which allows the managers in an organisation to take action. The most commonly used stakeholder map is the power/interest matrix, seen in the figure to the left, which gives an easy and simple overview of what the different categories require with regards to what their needs are and how much they are able to influence the project.
A stakeholder's position on the grid shows which actions should be taken with them:
| Position | Description |
| High power / High interest | These stakeholders need to be fully engaged and great efforts must be made to keep them satisfied. |
| High power / Low interest | These stakeholders need to be kept satisfied in order to keep their power in a place that will benefit your project |
| Low power / High interest | These stakeholders should be kept informed in order to make sure that important issues do not arise. They can often be rather helpful due to their level of interest |
| Low power / Low interest | These stakeholders should be monitored in case changes in their position occur |
[edit] Creating stakeholder engagement
After having defined and classified the stakeholders it is important to generate engagement and keep the stakeholders interested in the project at hand. Donaldson & Preston explained the need for stakeholder engagement very well with this simple quote "The view that stakeholder management and beneficial corporate performance go hand in hand has now become commonplace in the management literature." [13]. Freeman brings a nice addition to underline the importance of stakeholder engagement by the following quote “If organisations want to be effective, they will pay attention to all and only those relationships that can affect or be affected by the achievement of the organisation’s purposes”.[14]
[edit] Stakeholder engagement methods
After having mapped out the key stakeholder in accordance to the most basic factors, influence and interest, an initial stakeholder engagement approach could be to follow the following table. For each on the combinations of influence and interest there is a suggestion to how the engagement as well as communications should be handled. The importance of targeting each stakeholder group individually cannot be stressed enough.
| Engagement approach | Description |
| Partnership | Shared accountability and responsibility. Two-way engagement joint learning, decision making and actions. |
| Participation | Part of the team, engaged in delivering tasks or with responsibility for a particular area/activity. Two-way engagement within limits of responsibility. |
| Consultation | Involved, but not responsible and not necessarily able to influence outside of consultation boundaries. Limited two-way engagement: organisation asks questions, stakeholders answer. |
| Push communications | One-way engagement. Organisation may broadcast information to all stakeholders or target particular stakeholder groups using various channels e.g. email, letter, webcasts, podcasts, videos, leaflets. |
| Pull communications | One-way engagement. Information is made available and stakeholders choose whether to engage with it. |
The mentioned approaches from the table are very overall stakeholder engagement methods.
Another matrix has been developed called the participation matrix [16]. It has been designed with the specific purpose of planning for stakeholder participation. It has been adapted from the original made by the Association for Public Participation focusing especially on the spectrum of levels of public participation as well as the strategic management functions [17] The matrix prompts planners to think about responding to or engaging different stakeholders in different ways over the course of a policy or strategy change effort. As a result, the benefits of taking stakeholders seriously may be gained while avoiding the perils of inappropriately responding to or engaging stakeholders [16]
In the following some more detailed ways of integrating stakeholders to the project will be described.
[edit] Stakeholder integration methods
There are four different overall types of stakeholder integration as described by the article "Stakeholder Integration - Building Mutually Enforcing Relationships" [18]:
- Buffering: Buffering strategies are adopted by many organisations in order to cope with the need for certainty. The aim is to seal of the core transformation processes from external influences in the environment. Buffering can also be used as a tool for stakeholder integration, and attempts to create close relations with representative organisations. The main purpose is to avoid the many problems associated with having many indirect stakeholder, who are thereby less controllable. Having many indirect stakeholders puts organisations in a vulnerable position with regards to influencing the information exchange processes in the stakeholder network. [18]
- Co-optation: Organisations will always have to deal with direct stakeholders, who differ in their degree of perceived salience. Buffering is not always an option due to the fact that some of the most important stakeholders provide direct contributions to the organisation's technical core through investments in co-specialised assets. As a tool for handling the challenges and uncertainties linked with these types of stakeholder bonds, the organisation may choose to create co-optation. Co-optation has been defined by Selznick as “the process of absorbing new elements into the leadership or policy-determining structure of an organisation as a means of averting threats to its stability or existence” [19]. Co-optation is thereby a partial absorption technique used in cases where total absorption is not possible. In regards to stakeholder integration, co-optation is a dyadic technique. By using this technique the organisation adapts to a firm's leadership structure with the purpose of obtaining external stakeholders' consent or to communicate mutually beneficial information [18].
- Mutual learning: The purpose is to redefine the interdependencies between organisations and stakeholders [20]. Individual organisations will most likely bring their own feasibility preoccupations to the table, which consequently puts a restriction on the range of cooperative options. However, by using dyadic collaboration processes, interdependent organisations and stakeholders will be able to discover each other’s feasibility preoccupations and find a solution that satisfies some, if not all, of the interests of each of the stakeholders involved [21].
- Meta-problem solving: "Symbiotic interdependencies are not necessarily restricted to the dyadic level but may extend to the network level" [22]. An example of these interdependencies is when many organisations are facing the same ill-defined problem domain. This could be a domain in which the key stakeholders are not yet defined [20]. Meta-problems exceed the boundaries of the majority of individual organisations; therefore, they must be addressed by combining multiple perspectives and resources in order to find a resolution. Consequently, effective meta-problem solving consists of collaborative processes operated at the network level in order to help with the integration of organisations “that may be widely disparate in wealth, power, culture, language, values, interests, and structural characteristics” [18].
These four integrations mechanisms can be seen in the figure above to the left, where their relation to each other can be visualised.
[edit] Discussion
An interesting note to add is that the newest addition to the PMBOK 5 is a tenth Knowledge Area, Project Stakeholder Management. However, stakeholder management is of course not new to this standard, it has merely been given its own area instead of being a part of the Communications Knowledge Area. PMI has done this in order to emphasise the importance of this area. This helps raise the level of importance of stakeholder management to an equal level with the other Knowledge Areas. Stakeholder management is in fact one of the hardest things a project manager has to deal with and a major aspect of this is equal parts stakeholder involvement and communication. In compliance with the main message of this article, PMBOK 5 is putting a strong emphasis on the fact that the project manager must keep the stakeholders engaged throughout the project, not just informed. [7]
In the spirit of looking at standards it should be mentioned that stakeholder management and involvement is only very briefly described in the ISO standard 21500 [1] and has yet to be described in a way which underlines its importance.
The aforementioned classification of stakeholder importance is not in itself enough no matter the chosen classification. As mentioned by much of the literature, there is a need for understanding the relationships between the organisation and the different stakeholders. Furthermore, there is a need to have a broader look at stakeholder management in order to incorporate the relations between the key stakeholders themselves since this may very well end up having an impact on the organisation at hand. In addition to analysing stakeholders it is crucial to make the connection between stakeholder management and communication strategies because each category of stakeholders will have different needs that should be addressed accordingly. Most of these needs will be satisfies by communicating the right information at the right time. The need for a good communication plan is consequently of the utmost importance when looking at stakeholder involvement, which is, as discussed, a critical factor in the success of any project. Managing the relationships with each stakeholder should furthermore pay attention to how these are guided by organisational actions and initiatives established with the purpose of creating, building and strengthening the organisation’s bonds with each respective stakeholder [4][16].
Conclusively, it can be seen that there are a variety of stakeholder management tools. The importance of stakeholder management is gradually being recognised by the major project management standards, instead of only including stakeholder management as a part of the communication paragraphs. It is important for project managers to realise the importance of creating the right involvement from each stakeholder, this is where the different classification tools will be helpful. The need for more or less detailed stakeholder classification is dependent on the size and type of a given project. However, stakeholder management will always be of the utmost importance for the success of project.
[edit] References
- ↑ 1.0 1.1 Guidance on project management, DS/ISO 21500, Danish Standards, 2013
- ↑ Scandinavian Cooperative Advantage: The Theory and Practice of Stakeholder Engagement in Scandinavia, Robert Strand and R. Edward Freeman, 2013, Springer
- ↑ Strategic Management: A stakeholder approach, R. Edward Freeman, 1984, Pitman, Boston, isbn=0-273-01913-9
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 A model for stakeholder classification and stakeholder relationships, E. Mainardes, H. Alves, M.Raposo, 2012
- ↑ The pyramid of corporate social responsibility: Toward the moral management of organizational stakeholders, Carroll, A. B. (1991), Business Horizons, 34(4), 39–48
- ↑ Managing successful projects with PRINCE2, TSO, 2009
- ↑ 7.0 7.1 http://www.allpm.com/index.php/our-community/94-article/newsletter-article/496-changes-in-pmbok-5th-edition, accessed November 30th 2014
- ↑ 8.0 8.1 8.2 Power i projekter & portefølje, Attrup L., M. and Olsson R., M., Jurist-og Økonomforbundets forlag 2008
- ↑ Stakeholders: Theory and Practice, A. Friedman and S. Miles, 2006, Oxford University Press, Oxford.
- ↑ 10.0 10.1 10.2 “Toward a theory of stakeholder identification and salience: defining the principle of who and what really counts”, R. Mitchell, B. Agle, and D. Wood, 1997, Academy of Management Review, Vol. 22 No. 4, pp. 853-8.
- ↑ 11.0 11.1 11.2 11.3 11.4 Developing Stakeholder Theory, Andrew L. Friedman and Samantha Miles, Journal of Management Studies 39, January 2002
- ↑ 12.0 12.1 http://www.mindtools.com/pages/article/newPPM_07.htm, accessed December 1st
- ↑ The stakeholder theory of the corporation: Concepts, evidence, and implications. Donaldson, T., & Preston, L. E., 1995, Academy of Management Review, 20, 65-91.
- ↑ Divergent stakeholder theory, Freeman, R. E., 1999, Academy of Management Review, 24, page 234.
- ↑ http://www.stakeholdermap.com/stakeholder-engagement.html, accessed November 30th
- ↑ 16.0 16.1 16.2 What to do when stakeholders matter, John M. Bryson, Public Management Review, Vol. 6 Issue 1 2004 21-53
- ↑ [1], IAP2 Spectrum of Public Participation, 2007, International Association for Public Participation
- ↑ 18.0 18.1 18.2 18.3 18.4 Stakeholder Integration - Building Mutually Enforcing Relationships, Pursey P.M.A.R. Hugeness, Frans A.J. Van den Bosch and Cees B. M. Van Riel, Business Society 202, 41:36
- ↑ TVA and the grass roots, P. Selznick, 1949, Berkeley: University of California Press.
- ↑ 20.0 20.1 Collaborating: Finding common ground for multiparty problems, B. Gray, 1989, San Francisco: Jossey-Bass
- ↑ Toward a comprehensive theory of collaboration, D.J. Wood & B. Gray, 1991, Journal of Applied Behavioral Science, 27, 139-162.
- ↑ Interorganizational collaboration and the preservation of global biodiversity, F. Westley & H. Vredenburg, 1997, Organization Science, 8, 381-403.
