Answer.

Identifying all stakeholders is one of the top priorities for a business analyst. If the interests of all significant participants are not considered, the project may face "surprises" at later stages. For correct identification and classification, the following methods are used:

1. Interviews with key individuals: discussions with known project leaders who can point to other influencing groups.
2. Analysis of the organizational structure: studying the organization chart to identify formal and informal leaders.
3. Brainstorming with the team: helps gather data about hidden and secondary stakeholders.
4. Stakeholder mapping: visual representation of the influence and interest of each group or person on a stakeholder map.

Classification is done based on the degree of influence and interest, for example, using Mendelow’s matrix or the Power/Interest Grid.

Key features:

• Analysis of both formal and informal stakeholders.
• Use of special tools for categorization.
• Classification allows for establishing communication priorities.

Trick Questions.

Is it enough to identify just the budget owner as the key stakeholder?

No, besides them, there may be users, technical specialists, external suppliers, etc., all of whom can influence the success of the project.

Do all stakeholders need to receive the same level of attention?

No, it is important to determine their degree of influence and interest. Some may only need to be informed, while others require close collaboration.

Can an outdated organizational chart be used to identify stakeholders?

No, the structure may have changed, and real influence may now be held by different individuals or departments.

Common Mistakes and Anti-Patterns

• Ignoring "invisible" stakeholders (for example, regular users).
• Insufficient detail in the influence/interest matrix.
• Overloading communications with low-significance groups.

Real-Life Example

Negative Case: The analyst took a list of stakeholders from an old project without clarifying within the organization. Pros: Quick initial documentation. Cons: Unexpected influencing groups surfaced during the process, a hidden opposer emerged, project got stalled.

Positive Case: Conducted a workshop with the team, created a stakeholder map, identified a new active user representative. Pros: Accounting for everyone who can influence success. Cons: Time spent on detailing and initial communications.