Study guide

3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map

TOGAF Enterprise Architecture Practitioner OGEA-103

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Mechanics & Foundation Overview

1.1 OGEA-103 Exam Structure, Gradient Scoring & Open-Book Strategy 1.2 The TOGAF Standard 10th Edition Structure & Core Concepts 1.3 Enterprise Architecture in Practice: Context, Scope, and Architecture Domains 1.4 The Context for Enterprise Architecture: Purpose, Capability, Security, and the Digital Enterprise

2 Chapter 2: Preliminary Phase & Establishing the EA Capability

2.1 Preliminary Phase Objectives, Inputs, and Activities 2.2 Scope of the Enterprise and Defining the Architecture Footprint 2.3 Establishing Architecture Governance, Frameworks, and Tools

3 Chapter 3: Architecture Vision & Stakeholder Management (Phase A)

3.1 Phase A Objectives, Request for Architecture Work, and Scope Definition 3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map 3.3 Business Scenarios Technique for Problem Definition and Requirements Elicitation 3.4 Architecture Vision, Communications Plan, and Statement of Architecture Work Approval

4 Chapter 4: Business Architecture (Phase B)

4.1 Phase B Objectives, Steps, and Business Modeling Approaches 4.2 Business Capabilities, Capability Mapping, and Assessment 4.3 Value Streams, Value Stream Mapping, and Capability Cross-Mapping 4.4 Business Architecture Artifacts, Gap Analysis, and Architecture Definition Document Updates

5 Chapter 5: Information Systems Architectures — Data Architecture (Phase C)

5.1 Phase C Data Architecture Objectives, Approach, and Data Principles 5.2 Conceptual, Logical, and Physical Data Models and Data Management 5.3 Data Entity/Business Function Matrix, Data Architecture Gap Analysis, and Interoperability Requirements

6 Chapter 6: Information Systems Architectures — Application Architecture (Phase C)

6.1 Phase C Application Architecture Objectives, Approach, and Baseline vs. Target First 6.2 Application Portfolio Rationalization, Component Modeling, and Application Integration 6.3 Application/Organization Matrix, Application Gap Analysis, and Boundary Definitions

7 Chapter 7: Technology Architecture (Phase D)

7.1 Phase D Objectives, Cloud & Modern Platforms, and Technology Principles 7.2 Technology Standards, the Standards Library, Platform Services, and Infrastructure Modeling 7.3 Technology Gap Analysis, Non-Functional Requirements, and Reference Models

8 Chapter 8: Opportunities and Solutions (Phase E)

8.1 Phase E Objectives, Consolidated Gap Analysis, and Work Package Formulation 8.2 Architecture Building Blocks (ABBs) to Solution Building Blocks (SBBs) Transition 8.3 Transition Architectures, Incremental Delivery, and Dependency Analysis 8.4 Architecture Roadmap Development and Trade-Off Analysis 8.5 Business Transformation Readiness Assessment and Risk Management

9 Chapter 9: Migration Planning (Phase F)

9.1 Phase F Objectives, Stakeholder Collaboration, and Governance Alignment 9.2 Business Value Assessment, Cost-Benefit Analysis, and Risk/Feasibility Scoring 9.3 Implementation and Migration Plan Deliverable, Resource Allocation, and Transition Roadmaps

10 Chapter 10: Implementation Governance (Phase G)

10.1 Phase G Objectives, Implementation Governance Structure, and Project Architecture Hand-off 10.2 Architecture Contracts: Purpose, Types, Timing, and Stakeholder Commitments 10.3 Architecture Compliance Reviews: Conformance Levels, Process, Timing, and Checklists

11 Chapter 11: Architecture Change Management (Phase H) & Requirements Management

11.1 Phase H Objectives, Drivers of Architecture Change, and Value Monitoring 11.2 Change Classification: Simplification, Incremental, and Re-Architecting Changes 11.3 Ongoing Governance, Retirement of Solutions, and Maintenance vs. New ADM Cycle 11.4 Requirements Management: Central Role, Traceability, Mid-Phase Discovery, and Scope Conflict

12 Chapter 12: Architecture Governance, Boards, and Dispensations

12.1 Architecture Governance Framework, Organizational Roles, and RACI Matrix 12.2 Architecture Board Structure, Federation, Responsibilities, and Meeting Operations 12.3 Compliance Assessment, Dispensation Process, Expiration, and Remediation Tracking 12.4 Architecture Principles, the Decision Log, and Resolving Principle Conflicts

13 Chapter 13: Architecture Content Framework & Architecture Repository

13.1 The TOGAF Content Framework and Enterprise Metamodel 13.2 Deliverables, Artifacts (Catalogs, Matrices, Diagrams), and Building Blocks (ABBs vs SBBs) 13.3 Architectural Views, Viewpoints, Stakeholder Concerns, and ISO/IEC/IEEE 42010 13.4 The Enterprise Continuum and the TOGAF 10 Architecture Repository

14 Chapter 14: EA Capability, Tailoring, and Iteration

14.1 Tailoring the ADM: Enterprise Context, Process Weight, and Agile Integration 14.2 ADM Iteration Cycles, Levels, and Classes of Architecture Engagement 14.3 Architecture Maturity Models, Capability Assessment, and EA Performance Measures 14.4 Supporting the ADM Work: The TOGAF Library, Series Guides, Patterns, and Security

3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map

Key Takeaways Explain This Topic AI

TOGAF's stakeholder management steps are: identify stakeholders, classify stakeholder positions, determine the stakeholder management approach, and tailor engagement deliverables.

The power/interest grid classes are Key Players, Keep Satisfied, Keep Informed, and Minimal Effort.

TOGAF's sample analysis groups 22 stakeholder types into five categories: Corporate Functions, End-user Organization, Project Organization, System Operations, and Outside Services.

The Stakeholder Map records each stakeholder's key concerns, class, and the catalogs, matrices, and diagrams that address them.

Stakeholder analysis starts in Phase A and is updated in every later phase, because new stakeholders emerge as the engagement progresses.

Last updated: October 2026

3.2 Stakeholder Management: Identification, Classification, the Power/Interest Grid, and the Stakeholder Map

Stakeholder Management is the second Level 2 topic area for Part 2, and it is one of the ADM Techniques in the TOGAF Standard, 10th Edition. The Level 2 learning outcome expects you to apply it: identify stakeholders, their concerns, the views they need, and the communication involved; use architecture views; manage stakeholder engagement and requirements; and use trade-offs to support architecture development.

Why TOGAF Treats Stakeholder Management as a Technique

The TOGAF Standard lists the benefits of successful stakeholder management:

The most powerful stakeholders are identified early, so their input shapes the architecture and their support is secured.

Support from powerful stakeholders helps the engagement win resources .

Early and frequent communication means stakeholders understand the architecture process and can support the team when needed.

The team can anticipate reactions to models and reports and plan for them.

Conflicting or competing objectives among stakeholders are found early, so a strategy for resolving them can be developed.

TOGAF recommends using stakeholder analysis in Phase A to identify the key players, then updating it throughout every phase . New stakeholders often surface in Opportunities & Solutions, Migration Planning, and Architecture Change Management.

A stakeholder is an individual, team, organization, or class of these with an interest in, or concerns relative to, the outcome of the architecture. A concern is an interest in the architecture that is important to one or more stakeholders. The technique connects directly to the content concepts of Architecture View , Architecture Viewpoint , Concern , and Stakeholder (Section 13.3).

  • The Four Steps of the Stakeholder Management Process
  • Step 1: Identify Stakeholders

Work out who is affected by the architecture, who has influence or power over it, and who has an interest in its success or failure. TOGAF's sample analysis distinguishes 22 types of stakeholder in five broad categories :

Category Examples of stakeholders

Corporate Functions CxOs, Program Management Office, Procurement, Human Resources, Enterprise Security, QA/Standards group

End-user Organization Business unit executives, line management, business domain experts

Project Organization Sponsor and program manager, project manager, business process or functional experts, product and technical specialists

System Operations IT service management, IT operations for applications, infrastructure, and data/voice communications

Outside Services Regulatory bodies, suppliers and alliance partners

Useful questions include: who gains and who loses from the change, who controls resources, who will make the decisions, who procures IT systems, and who has influence. TOGAF warns against relying only on the formal organization chart: informal stakeholder groups and influencers can be as powerful as formal ones. Consider both the visible team obviously associated with the change and the invisible team whose contribution is still essential, such as providers of support services.

Step 2: Classify Stakeholder Positions

Record an analysis of the most important stakeholders. TOGAF's example analysis rates each stakeholder's ability to disrupt the change , their current and required understanding , their current and required commitment , and the support required (high, medium, or low). It also asks how ready each person is to move toward the target, whether they could act as an advocate, how involved they need to be, and whether they have made a commitment to the architecture.

  • Step 3: Determine the Stakeholder Management Approach
  • Map stakeholders by power and interest on a power/interest grid to choose an engagement strategy: HIGH POWER
  • |
  • KEEP | KEY
  • SATISFIED | PLAYERS
  • (high power, | (high power,
  • low interest) | high interest)
  • -----------------------+------------------------
  • |
  • MINIMAL | KEEP
  • EFFORT | INFORMED
  • (low power, | (low power,
  • low interest) | high interest)
  • |
  • LOW POWER
  • LOW INTEREST ------------------------ HIGH INTEREST

Key Players (high power, high interest): involve them fully and engage closely; their views shape the architecture.

Keep Satisfied (high power, lower interest): give them what they need to stay supportive without overloading them with detail. In TOGAF's template map, CxOs, the PMO, business unit executives, regulators, and suppliers are typically classed here.

Keep Informed (lower power, high interest): keep them regularly informed; examples in the template include HR, IT service management, and project managers.

Minimal Effort (low power, low interest): monitor them in case their position changes.

TOGAF's template places many specialist and operational roles (procurement, enterprise security, line management, domain experts, and infrastructure and application operations) among the Key Players . These are examples, not fixed rules, so classify the actual people in each scenario.

Step 4: Tailor Engagement Deliverables

Identify the catalogs, matrices, and diagrams each stakeholder group needs, so the architecture is communicated in terms they understand and they can confirm their concerns are addressed. This is how stakeholder management feeds view and viewpoint selection in Phases B to D.

The Stakeholder Map

The result is recorded in a Stakeholder Map , which Phase A produces as a matrix and which is updated throughout the ADM. TOGAF's template lists, for each stakeholder:

  • Column Example (CxO, Corporate Functions)
  • Stakeholder CEO, CFO, CIO, COO

Key Concerns High-level drivers, goals, and objectives, and how they translate into an effective process and IT architecture

Class Keep Satisfied

Catalogs, Matrices, and Diagrams Business Footprint diagram, Goal/Objective/Business Service diagram, Business Capability Map, Value Stream Map

The Stakeholder Map is where concerns are captured and traced to the views that address them. The Communications Plan in Phase A then sets out how, when, and where the architects will communicate with each group.

Using Stakeholder Management to Resolve Conflicts

Stakeholders often want incompatible things. Picture a Head of Sales who wants frictionless onboarding alongside a CISO who wants strong authentication. TOGAF's guidance points to a disciplined approach:

Make the conflict visible early in the stakeholder analysis rather than letting it surface at implementation.

Refer to the agreed Architecture Principles , which exist to guide exactly these decisions.

Use the Architecture Alternatives and Trade-offs technique (Section 8.4): present alternatives, with views that let stakeholders explore their consequences, so hidden agendas and requirements come out.

Escalate through governance when stakeholders cannot agree. The Architecture Board is the visible escalation route for out-of-bounds decisions.

Practitioner Traps in Part 2 Scenarios

Treating stakeholder analysis as a one-off. Re-check the Stakeholder Map in later phases; new or newly powerful stakeholders appear.

Ignoring informal influence. A respected manager with no formal title can block adoption.

Overloading powerful but less-interested stakeholders. Keep Satisfied stakeholders need concise, relevant views, not detailed models.

Neglecting operational stakeholders. Key players such as IT operations and security can derail implementation if their concerns are missed.

Producing generic deliverables. Step 4 exists so each group gets the catalogs, matrices, and diagrams that address its concerns.

Loading diagram... TOGAF Stakeholder Management Process