Stakeholder map

As explained in Effective Platform Engineering

A stakeholder map is a structured representation of stakeholders and their influence, alignment, constraints, or relationship to a product.

A stakeholder map represents stakeholders by their influence over the engineering-platform backlog and their alignment with platform objectives. Maintaining one reveals where stakeholder solutions, processes, or decisions may conflict with platform needs. section 2.1.2

Build the map by assessing:

• Influence: how much authority the stakeholder has or wants over the engineering platform. section 2.1.2
• Alignment: whether the stakeholder provides API access or outcome requirements, or requires tickets and existing operating models. section 2.1.2
• Risk: highly influential stakeholders need strong alignment for the platform to succeed. section 2.1.2

Identity platform scenario

An identity team can provide a single source of user identity and self-service API access, while other teams implement compatible solutions using OAuth2 when requirements differ. Mapping the CTO, CEO, and vice-president of human resources clarifies their influence and alignment. section 2.1.2

Figure 2.2 Internal stakeholders have legitimate concerns. But these outcomes can be achieved without the stakeholders controlling the implementation.

Use the stakeholder-map diagram to compare influence over the backlog with alignment to platform objectives. section 2.1.2

How Effective Platform Engineering covers it

How deep it goes

Maps influence and alignment and maintains the result to expose conflicts, but does not specify a formal scoring method.

Examples

Uses an identity service, self-service APIs, OAuth2, and stakeholder comparisons involving the CTO, CEO, and vice-president of human resources.

What you can do after

Diagnose stakeholder conflicts and identify where alignment, API access, or operating-model changes could prevent platform blockage.

How it connects

Connects platform engineering with backlog management, developer self-service, API access, operating models, and OAuth2.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• arraykind of · An array is an indexed, ordered collection of elements arranged in one or more dimensions, with elements accessed by position.
• stakeholderuses · A stakeholder is a person or group with an interest in, influence over, responsibility for, or potential impact from a system, project, decision, or outcome.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.