LEARN. PRACTICE. GROW.Concept and mechanism
A stakeholder map should include people using, operating, approving, funding, or depending on the solution, as well as those indirectly affected. An initial invitation list does not establish coverage. In a middleware project, the team receiving a file after processing may have essential requirements even without application access. Identify interests, influence, responsibilities, and concerns. Do not assume two people with the same role have the same perspective. Communication should enable action: a committee needs decisions, risks, and commitments; APS may need symptoms, procedures, and contacts; business needs to understand effects on its activities.
Guided application
When business and operations disagree on a change window, clarify their reasons. One group may want speed while another wants to avoid a peak period without support capacity. Record constraints, alternatives, and consequences, and facilitate a decision with the appropriate owner. Avoid settling matters through the highest-ranking attendee or promising dates without consulting dependencies. In international teams, confirm time zones, terms, and owners in writing. Silence after an email does not necessarily mean approval. Plan feedback throughout the initiative because interests and risks can change. Early operations involvement helps uncover diagnosis, recovery, and knowledge requirements that are difficult to add in the final week.
A downstream team can be affected without attending the first workshop.
Common pitfalls
Static map; silence treated as agreement; identical detail for everyone; APS absent until handover.
Related topics: Need, value, and BACCM · Mindset, examples, and collaboration · Approach, change, and traceability
Adapt communication to the decision and keep the stakeholder map current.
Reference: Designing reports around consumption needs · 2025-07-21 / blueprint V1.1