> For the complete documentation index, see [llms.txt](https://www.lawfirm-operations.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/2.-people-2.1.-culture/2.2.-roles-and-accountabilities/2.4-stakeholders.md).

# 2.4 Stakeholders

When talking about the people involved in a legal project, those outside the project team should also be considered. Stakeholders are all people or even institutions (e.g. legislature) who have an interest or may affect the project. They consist, for example, of all team members in the law firm and on the client side who are part of the project, suppliers, and the counterparty, if any.

The core message of this chapter is that it is important to deal with stakeholders and assess them, and we want to show how to visualize this process. In practice, you will not map your stakeholders for every tiny case, but the more complex, the more critical and the bigger a case gets, the more important it gets to keep track of all the stakeholders involved and to know how to deal with them.

Even though it is the Product Owner who mainly deals with the stakeholders, it helps to visualize them so that they are transparent for everyone involved. Stakeholders can be shown on a grid which shows their infl uence on one axis and their interest in the project on another. For a more detailed assessment, a table can be fi lled out that deals with each individual stakeholder. On each one, it is noted how big their infl uence on and interest in the project are. From low “-“, through neutral “0”, to positive “+”. The last column consists of a note how to deal with a stakeholder of a particular rating or comments on an individual person.

<figure><img src="/files/2tTBP1siuXStlmj0vNfp" alt="" width="563"><figcaption></figcaption></figure>

## Story

### Of witnesses and other stakeholders

The team’s client, Bob, reacted well to their Agile project and our team is thinking about being even more open. First, they have a meeting with the client’s project manager, Caleb, to introduce more details about the project and the people involved. They already know about the counterparty, Eric, and his company but they neither know much about Horizontal Building’s customer, nor about potential interfaces with other third parties. While they have ample experience in explaining to clients about the challenges of working with witnesses, Gabriel read about stakeholder management when he delved into Agile literature. They decide to implement the stakeholder tools often used in Agile to get a joint understanding with Caleb and Bob about who is directly or indirectly involved in the case and how much infl uence each stakeholder has. The stakeholder map might have an impact on the fl ow of information, based on the actions regarding the different stakeholders. With this you should not forget to inform any important stakeholders.

## Example

The team sets up a stakeholder map for the current case:

| Name                     | Influence | Interest | Action                                                    |
| ------------------------ | --------- | -------- | --------------------------------------------------------- |
| **Internal Stakeholder** |           |          |                                                           |
| Partner A                | +         | +        | Inform and use as champion.                               |
| Partner B                | +         | -        | Inform and sway.                                          |
| Marketing                | -         | +        | Inform if there are interesting aspects that can be used. |
| Secretary                | 0         | 0        | Keep in the loop.                                         |
| IT Professional          | +         | 0        | Inform and bring on board.                                |
| E**xternal Stakeholder** |           |          |                                                           |
| Bob                      | +         | +        | Focus!                                                    |
| Caleb                    | -         | +        | Get information.                                          |
| Eric                     | +         | +        | Focus! Sway                                               |
| Sara                     | -         | 0        | Use as expert.                                            |
| Court                    | +         | 0        | Inform                                                    |
| Legislator               | +         | -        | Keep up to date with legislative changes                  |

## Template

<table><thead><tr><th>Name</th><th width="191">Influence</th><th width="187">Interest</th><th>Action</th></tr></thead><tbody><tr><td><strong>Internal Stakeholder</strong></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td>E<strong>xternal Stakeholder</strong></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td></tr></tbody></table>

<figure><img src="/files/PvpnXuLo2IT2Yb2t2PQ7" alt="" width="120"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.lawfirm-operations.org/publications-and-articles/agile-law-firm-workbook/2.-people-2.1.-culture/2.2.-roles-and-accountabilities/2.4-stakeholders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.