This repository has been archived by the owner on May 31, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 67
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #645 from 18F/New-method-stakeholder-influence-map
New method stakeholder influence map
- Loading branch information
Showing
2 changed files
with
37 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
layout: card | ||
title: Stakeholder influence mapping | ||
permalink: /discover/stakeholder-influence-mapping/ | ||
redirect_from: | ||
- /stakeholder-influence-mapping/ | ||
description: A visual representation of stakeholders — the people who are involved — and their potential influence and impact on a project or service system, in comparison to one another. | ||
category: Discover | ||
what: A visual representation of stakeholders — the people who are involved — and their potential influence and impact on a project or service system, in comparison to one another. | ||
why: To uncover and describe power dynamics — the often-unspoken balances of influence and control — that could impact project outcomes; prioritize which stakeholders to engage with and how, and inform a communication and engagement approach. | ||
timeRequired: ~1 hour | ||
governmentConsiderations: | ||
|
||
--- | ||
|
||
## How to do it | ||
|
||
1. Gather the team and, ideally, at least one crucial stakeholder familiar with their organization and how it works from both a technical and an interpersonal point of view. | ||
1. If meeting in person, you’ll need sticky notes and a whiteboard; if meeting remotely, use a virtual whiteboard or tools that support online document collaboration, ideally simultaneously. | ||
1. Divide the whiteboard into four areas, as a grid. Label the x axis influence and the y axis interest. | ||
1. List out stakeholders together. Write down names of people, groups, communities, or organizations that your work may impact, and organize them into the four quadrants based on your understanding of their relative influence and interest. | ||
1. Look at each quadrant to sort who to engage with and how: | ||
- interested and influential - collaborate with them | ||
- either influential or interested - keep them informed | ||
- neither influential nor interested - allow them to drive their own involvement | ||
1. If your map reveals power dynamics that route around policy, consider whether the information poses personal or professional risk to any stakeholders. Avoid possible harm by sharing this map with only the people who need to understand it, and consider the consequences of those you do share with — or share an edited version. | ||
1. Review and update the map as you understand the situation better. | ||
|
||
<section class="method--section method--section--18f-example" markdown="1" > | ||
|
||
|
||
## Considerations for use in government | ||
|
||
No PRA implications. No information is collected from members of the public. | ||
|
||
</section> |