Stakeholder Onion Diagram: A Practical Guide
/ Stephanie FamuyideSTAKEHOLDER ONION DIAGRAM - Includes Free Template
Knowledge Area: Business Analysis Planning & Monitoring
Applicable Task: Conduct Stakeholder Analysis
Useful When: Identifying stakeholders involved in your project. Helps the BA determine which stakeholders will directly interact with a system or process and those outside the organization.
I’ll use the customer ordering system example. The Stakeholder onion diagram would look like this:
PRACTICAL APPLICATION
To develop a Stakeholder Onion Diagram, identify the following categories of stakeholders:
Layer 1: Stakeholders closely involved in the creation of the product, which could be a new system or a new process. Stakeholders may include the project manager, software developer, business analyst, etc
Layer 2: Stakeholders whose work changes when the solution is defined. For example, end users.
Layer 3: Sponsors, executives and subject matter experts who interact closely with the system
Layer 4: External Stakeholders such as customers, regulators, government, suppliers and the like.
An editable template of the stakeholder diagram can be downloaded here.
Data mining can be described as the process of improving decision-making by identifying useful patterns and insights from data.
A data dictionary holds data about the fields in a database, such as field definitions, meanings and allowable values that reflect how data is used within a domain or organization.
Are you a business analyst involved in the documentation of business rules and creation of complex decision tables?
A concept model provides a great way of documenting definitions and communicating precise meanings of terms to stakeholders.
Employing the user journey mapping technique involves adopting a user-centric approach to product design, revealing opportunities to delight customers and identifying pain points that can be addressed thereby creating a product with an improved user experience.
Within the context of agile software development, the product backlog is a platform where all the potential work (product backlog items) that need to be delivered are recorded, tracked and prioritized. Though owned by the Product Owner, anyone may suggest items to add to it.
Failure Mode and Effects Analysis (FMEA) is a proactive technique that can be applied to the early detection of failures or defects in products and services. It is a systematic risk assessment process used by analysts looking to reduce the chances of faults by detecting problems and their possible repercussions in time for remediation.
If you are in business, here is a brief overview of how cause and effect analysis helps you find viable business solutions. Guest post by Lucas Cappel.
A roles and permissions matrix, an audit requirement in some organizations, is used to ensure that business activities are covered by identifying the responsibilities and roles linked to them.
Business Process Model and Notation (BPMN) is a global standard for constructing process models, with more organizations using it and schools teaching it as a subject.
User story maps are an interesting and collaborative way of eliciting user requirements. One of the reasons why I find it so powerful is because it provides a unique approach for aligning discussions relating to the user, their goals, the process that supports the accomplishment of their predefined goals; and the requirements that need to be addressed to solve business problems.