What is a Stakeholder Analysis, what is the ideal approach and which techniques will work best?
Stakeholder Analysis Definition
Stakeholder analysis identifies the most important stakeholders for a project or development, their goals, motives and attitudes. In the course of stakeholder management, stakeholder analysis follows identification. It can be used to find opponents, obstacles and resistances that can emanate from certain people, as well as supporters and promoters who want to advance a project. It also helps to identify early conflicts between stakeholders and/or between their goals.
Challenges of Analysis
Within the scope of stakeholder analysis, organisations try to collect information about stakeholders in a structured and methodical way. However, since all conceivable information will never be available, findings must be interpreted. There is a danger of subjectivation here. To reduce this danger, teams often carry out the analyses. Companies must ensure that the findings of stakeholder analysis are not made public outside the team, as this can have negative consequences for the project or product development. Stakeholders could try to exert more influence or obstruct the project just because it is being promoted by someone else.
Stakeholder Analysis as a Snapshot
Requirements often change in the course of a project. Not only do requirements change, stakeholders’ goals and motives can also change. Stakeholder analysis, like stakeholder management as a whole, is therefore always a snapshot. It is therefore important not only to carry it out once at the start of a project – often referred to as a project environment analysis – but also repeatedly. In the course of the project, you may also identify additional persons and organisations that did not exist at the start of the project or that were overlooked. In development projects, for example, this could be the IT of the client in whose environment you later want to operate your solution.
Tips for Conducting a Stakeholder Analysis
The Best Techniques
How do you find out what a stakeholder wants? The choice of the best technique depends on the project conditions, the skills of the investigating team and the type of knowledge to be sought:
- Survey techniques help to identify explicit knowledge. Examples of survey techniques are questionnaires and interviews.
- Creativity techniques are used to identify visions of products. Examples of creativity techniques are brainstorming, brainwriting and braindumping.
- Observation techniques are useful in situations that are difficult to describe. Examples of observation techniques are field observation and apprenticing.
- Document centred techniques are used in combination with other techniques. They try to use known solutions in the context of analysis. Examples of document-centered techniques are perspective-based reading and systems archaeology.
The Ideal Procedure
The following procedure is recommended in the course of stakeholder analysis:
- List all persons and organisations by name. In addition to the contact data, record the appropriate communication options and times. Also document the locations.
- Record the influence, attitude and motivation of each stakeholder on the project and its goals. The possibilities of influencing (how easily he can be influenced, how he influences others) should also be described.
- Document the areas of knowledge and contextual experiences. Existing methodological knowledge and expertise should also be written down.
- Evaluate and prioritise each stakeholder.
- Version your findings, because this will allow you to trace changes in projects back to changes in stakeholders at a later stage.
The Evaluation of Stakeholders
An important result of stakeholder analysis is the distinction between important and less important stakeholders. You can assess your stakeholders in different categories:
- What influence does the stakeholder have on your project?
- How great is the interest? In order to answer the question, it is a good idea to shed light on the change for the stakeholder: What changes are there in the way he works? What influence will the change have on his future position in the company? What opportunities and risks arise for him?
- What will be the reactions of individuals or organisations? Do you have to reckon with hidden or open resistance due to your project and the changes that accompany it? Or are the consequences for the stakeholder so positive that it promotes and promotes your project?
- How powerful is the stakeholder? When assessing power, it is irrelevant whether he has direct influence like a superior or indirect influence as an external organisation. It is important to recognise that negative effects often lead to demonstrations of power and are difficult to combat.
In most cases, it is sufficient to work with simple gradations such as “low, medium, high”, since these are subjective assessments, so that more detailed gradations would provide little additional insight.
Visualisation with Stakeholder Map
You should record the results of your stakeholder analysis in tabular form, as this enables you to easily document a great deal of detailed information. For a better understanding, it is a good idea to visualize important elements. With a stakeholder map or stakeholder matrix, you can see at a glance which stakeholders have a great deal of influence and interest, but must fear negative effects. Such insights form the basis for your stakeholder communication.
Challenges for Companies
Stakeholder Analysis as the Basis for Stakeholder Communication
The stakeholder identification and analysis are complete – and what now? How do you communicate with relevant stakeholders? In the course of stakeholder communication, it is advisable to draw up a plan and record how and with what frequency you communicate with whom. In terms of the stakeholder map, this means an increase in communication the greater the stakeholder’s interest and power is. In this way they receive structured feedback and opinions at an early stage. This information is important if you want to shape your project successfully and avoid conflicts. Note that stakeholders are also people with preferences: some prefer meetings, others a one-on-one conversation or a short SMS. In addition, communication should be mutual, i.e. people and organisations should also be able to communicate with you. You should define the ideal framework for this.
We are happy to provide you with knowledge, experience and 100% passion for your software development and requirements analysis. We help you with the collection, structuring and administration of requirements and pay attention to consistency, completeness and traceability. We support you in identifying technical correlations and consider stakeholders, goals and boundary conditions. And we plan and control your projects with these requirements on the basis of defined processes.