This guide provides a step-by-step approach to embedding the TOGAF Stakeholder Map table into your documentation or presentation. The goal is to ensure that the table is not only included but also presented in a way that is clear, comprehensive, and useful for stakeholders involved in the architecture project.
Step 1: Define the Purpose of the Stakeholder Map
Before embedding the table, clarify its purpose:
- Identify Stakeholders: Understand who the stakeholders are and their roles in the architecture project.
- Highlight Key Concerns: Recognize the primary concerns of each stakeholder to address them effectively.
- Classify Stakeholders: Categorize stakeholders based on their influence and interest in the project (e.g., Keep Satisfied, Key Players, Keep Informed).
Step 2: Prepare the Table Structure
Use the following structure for the table:
| Stakeholder | Key Concerns | Class | Catalogs, Matrices, and Diagrams |
|---|---|---|---|
| [Stakeholder Name] | [Key Concerns] | [Class] | [Catalogs, Matrices, and Diagrams] |
Step 3: Populate the Table
Fill in the table with the relevant information for each stakeholder. Use the provided template as a reference. Here’s how to do it:
- Stakeholder: List the name and role of the stakeholder (e.g., CxO, Program Management Office).
- Key Concerns: Describe the main concerns or interests of the stakeholder in relation to the architecture project.
- Class: Classify the stakeholder based on their level of influence and interest (e.g., Keep Satisfied, Key Players, Keep Informed).
- Catalogs, Matrices, and Diagrams: List the relevant artifacts that will be useful for the stakeholder, such as diagrams, catalogs, and matrices.
Step 4: Format the Table for Clarity
Ensure that the table is visually appealing and easy to read:
- Use Clear Headings: Make sure the headings are bold and distinguishable.
- Adjust Column Widths: Ensure that each column is wide enough to accommodate the content without excessive wrapping.
- Use Bullet Points: For the “Catalogs, Matrices, and Diagrams” column, use bullet points for better readability.
- Consistent Font and Size: Use a consistent font style and size throughout the table.
Step 5: Provide Context and Explanation
Before or after the table, include a brief explanation of the stakeholder map:
- Purpose of the Map: Explain why the stakeholder map is important for the architecture project.
- How to Use the Map: Provide guidance on how stakeholders can use the map to understand their roles and responsibilities.
- Importance of Engagement: Emphasize the need for ongoing communication and engagement with stakeholders.
Step 6: Embed the Table in Your Document or Presentation
Depending on the medium you are using (Word document, PowerPoint presentation, etc.), follow these steps:
- In a Word Document:
- Insert a table with the specified number of rows and columns.
- Copy and paste the content into the respective cells.
- Format the table as needed.
- In a PowerPoint Presentation:
- Create a new slide.
- Insert a table and adjust the size to fit the slide.
- Copy and paste the content into the table.
- Use design elements (e.g., colors, borders) to enhance visual appeal.
Step 7: Review and Revise
After embedding the table:
- Proofread: Check for any spelling or grammatical errors.
- Seek Feedback: Share the table with a colleague or stakeholder for feedback on clarity and completeness.
- Revise as Necessary: Make any necessary adjustments based on feedback received.
Step 8: Update Regularly
As the project progresses, ensure that the stakeholder map is updated to reflect any changes in stakeholder roles, concerns, or classifications. Regular updates will keep the map relevant and useful.
Here’s a template for a TOGAF Stakeholder Map based on the information provided. You can fill in the details for each stakeholder as needed.
TOGAF Stakeholder Map Template
| Stakeholder | Key Concerns | Class | Catalogs, Matrices, and Diagrams |
|---|---|---|---|
| CxO (Corporate Functions)e.g., CEO, CFO, CIO, COO | The high-level drivers, goals, and objectives of the organization, and how these are translated into an effective process and IT architecture to advance the business. | KEEP SATISFIED | – Business Footprint diagram- Goal/Objective/Business Service diagram- Organization Decomposition diagram- Business Capabilities catalog- Capability/Organization matrix- Business Capability Map- Strategy/Capability matrix- Business Model diagram- Value Stream catalog- Value Stream Stages catalog- Value Stream/Capability matrix- Value Stream Map |
| Program Management Office (Corporate Functions)e.g., Project Portfolio Managers | Prioritizing, funding, and aligning change activity. An understanding of project content and technical dependencies between projects supports portfolio management decision-making. | KEEP SATISFIED | – Requirements catalog- Project Context diagram- Benefits diagram- Business Footprint diagram- Application Communication diagram- Organization map- Business Capabilities catalog- Capability/Organization matrix- Business Capability Map- Strategy/Capability matrix- Business Model diagram- Value Stream catalog- Value Stream Stages catalog- Value Stream/Capability matrix- Value Stream Map |
| Procurement (Corporate Functions)e.g., Acquirers | Understanding what building blocks of the architecture can be bought, and what constraints (or rules) are relevant to the purchase. | KEY PLAYERS | – Technology Portfolio catalog- Technology Standards catalog |
| Human Resources (HR) (Corporate Functions)e.g., HR Managers, Training & Development Managers | The roles and actors required to support the architecture and changes to it. The key concern is managing people transitions. | KEEP INFORMED | – Organization Decomposition diagram- Organization/Actor catalog- Location catalog- Application and User Location diagram- Business Capabilities catalog- Capability/Organization matrix- Business Capability Map- Strategy/Capability matrix- Business Model diagram |
| Enterprise Security (Corporate Functions)e.g., Corporate Risk Management, Security Officers, IT Security Managers | Ensuring that the information, data, and systems of the organization are available to only those that have permission, and protecting the information, data, and systems from unauthorized tampering. | KEY PLAYERS | – Product Lifecycle diagram- Data Dissemination diagram- Data Security diagram- Actor/Role matrix- Networked Computing Hardware diagram- Network and Communications diagram |
| QA/Standards Group (Corporate Functions)e.g., Data Owners, Process Owners, Technical Standards Bodies | Ensuring the consistent governance of the organization’s business, data, application, and technology assets. | KEY PLAYERS | – Process/Event/Control/Product catalog- Contract/Measure catalog- Application Portfolio catalog- Interface catalog- Technology Standards catalog- Technology Portfolio catalog- Value Stream catalog- Value Stream Stages catalog- Value Stream/Capability matrix- Value Stream Map |
| Executive (End-user Organization)e.g., Business Unit Directors, Business Unit CxOs, Business Unit Head of IT/Architecture | The high-level drivers, goals, and objectives of the organization, and how these are translated into an effective process and architecture to advance the business. | KEEP SATISFIED | – Business Footprint diagram- Goal/Objective/Business Service diagram- Organization Decomposition diagram- Process Flow diagram- Application Communication diagram- Business Capabilities catalog- Capability/Organization matrix- Business Capability Map- Strategy/Capability matrix- Business Model diagram |
| Line Management (End-user Organization)e.g., Senior Business Managers, Operations Regional Managers, IT Managers | Top-level functions and processes of the organization, and how the key applications support these processes. | KEY PLAYERS | – Business Footprint diagram- Organization Decomposition diagram- Organization map- Process Flow diagram- Application Communication diagram- Application and User Location diagram- Business Capabilities catalog- Capability/Organization matrix- Business Capability Map- Strategy/Capability matrix- Business Model diagram |
| Business Domain Experts (End-user Organization)e.g., Business Process Experts, Business/Process Analyst, Process Architect, Process Designer, Functional Managers, Business Analyst | Functional aspects of processes and supporting systems. | KEY PLAYERS | – Business Interaction matrix- Actor/Role matrix- Business Service/Information di |
Conclusion
Embedding the TOGAF Stakeholder Map table into your documentation or presentation is a crucial step in ensuring effective stakeholder engagement in architecture projects. By following this comprehensive guide, you can create a clear, informative, and visually appealing stakeholder map that serves as a valuable resource for all project participants.