Fatskills
Practice. Master. Repeat.
Study Guide: Business Analysis 101: Elicitation and Collaboration - Managing Stakeholder Engagement, RACI, Power-Interest Grid
Source: https://www.fatskills.com/business-analyst/chapter/business-analysis-elicitation-and-collaboration-managing-stakeholder-engagement-raci-powerinterest-grid

Business Analysis 101: Elicitation and Collaboration - Managing Stakeholder Engagement, RACI, Power-Interest Grid

By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.

⏱️ ~6 min read

What This Is

Managing stakeholder engagement is the BA’s systematic way of identifying, analyzing, and continuously communicating with anyone who can influence or be impacted by a solution. It ensures the right people are consulted at the right time, expectations are aligned, and decisions are made with the appropriate authority.

Real?world example: A financial services firm is rolling out a new Customer Relationship Management (CRM) platform. The BA must keep senior executives (who control budget), sales managers (who will use the tool), compliance officers (who must approve data?privacy controls), and the IT operations team (who will host the system) all informed and involved throughout the project.


Key Terms & Techniques

  • Stakeholder Register – A BABOK Business Analysis Planning and Monitoring deliverable that lists every stakeholder, their role, contact info, and level of influence.
  • Power/Interest Grid – A visual matrix (from the Strategy Analysis knowledge area) that plots stakeholders by their decision?making power vs. interest in the solution; used to decide engagement tactics.
  • RACI Matrix – A responsibility?assignment chart (also a Planning artifact) that clarifies who is Responsible, Accountable, Consulted, and Informed for each BA activity or deliverable.
  • Stakeholder Analysis – The process of gathering information about stakeholder needs, expectations, and potential conflicts; output is the Power/Interest Grid and a communication plan.
  • Communication Plan – A Plan deliverable that defines what information will be shared, how, when, and with whom (e.g., weekly status email to “Informed” group).
  • Engagement Strategy – Tailored approach (e.g., workshops, one?on?ones, steering?committee meetings) derived from the Power/Interest classification.
  • Change Impact Assessment – A Solution Evaluation technique that evaluates how a change will affect each stakeholder group; feeds back into the RACI and communication plan.
  • Stakeholder Mapping Workshop – An interactive session (often a Elicitation activity) where the BA and key participants co?create the Power/Interest Grid and agree on RACI roles.
  • Decision?Making Authority Matrix – A supplemental chart that clarifies who can approve scope, budget, or schedule changes; often merged with RACI for clarity.
  • Conflict Resolution Log – A Requirements Management output that records disagreements, resolution actions, and final decisions; helps keep the RACI accurate over time.

Step?by?Step Process Flow

  1. Identify & Register Stakeholders – Scan project charter, org charts, and interview the sponsor to populate the Stakeholder Register.
  2. Analyze Power & Interest – Use the Power/Interest Grid to plot each stakeholder; classify them as Manage Closely, Keep Satisfied, Keep Informed, or Monitor (low power/low interest).
  3. Define RACI for BA Activities – For every major BA deliverable (e.g., Business Requirements Document, Process Model, Traceability Matrix), assign R, A, C, I roles based on the grid classification.
  4. Develop Communication & Engagement Plan – Choose tactics (workshops, status reports, demos) that match each quadrant; document frequency, medium, and responsible party.
  5. Execute & Monitor – Conduct the planned engagements, update the RACI and Power/Interest Grid when new stakeholders appear or influence shifts, and log any conflicts.
  6. Validate & Baseline – After each major deliverable, obtain formal sign?off from the “Accountable” stakeholder; lock the baseline and communicate changes to the “Informed” group.

Common Mistakes

Mistake Correction
Mistake: Treating the RACI as a static document that never changes. Correction: BABOK stresses that RACI is a living artifact; revisit it after each major milestone or when a stakeholder’s power/interest shifts.
Mistake: Placing every stakeholder in the “Consulted” column to avoid conflict. Correction: Use the Power/Interest Grid first; only those with high expertise or decision?making need to be consulted, others can be simply informed.
Mistake: Assuming “Power” equals “Authority” – e.g., a senior manager who has no budget authority is marked as high?power. Correction: Distinguish decision?making authority (who can approve) from influence (who can sway opinions). Reflect the difference in the grid and RACI.
Mistake: Forgetting to capture the “I” (Informed) group, leading to surprise emails and missed updates. Correction: Explicitly list all “Informed” stakeholders in the communication plan; automate status updates where possible.
Mistake: Using the RACI only for requirements?related tasks and ignoring solution?evaluation activities. Correction: Extend RACI to all BA tasks (including solution validation, transition planning, and post?implementation review) as required by BABOK.

Certification Exam Tips

Exam Level Tip
ECBA Remember that Stakeholder Analysis belongs to the Business Analysis Planning and Monitoring knowledge area; the exam often asks “Which artifact would you create first?” – answer: Stakeholder Register.
CCBA Watch for questions that mix Power/Interest Grid with RACI. The correct pairing is: Grid-determines engagement strategy; RACI-clarifies responsibilities for each BA activity.
CBAP Expect scenario?based items that require you to update a RACI after a change?impact assessment. The key is: RACI is updated, not recreated, when new stakeholders are identified.
All Levels Trap: “The BA should decide the priority of requirements.” – The BA facilitates prioritization (e.g., MoSCoW) but does not unilaterally set priority.
All Levels Pattern: “What does the BA do next after a stakeholder workshop?” – The next step is usually Document outcomes-Validate with stakeholders-Update RACI/Communication Plan.

Quick Check Questions

  1. Scenario: After a kickoff meeting, the sales director (high interest, moderate power) wants daily status emails, while the CFO (high power, low interest) prefers quarterly reports. Which tool helps the BA decide the appropriate communication frequency?
    Answer: Power/Interest Grid – it matches communication cadence to the stakeholder’s quadrant (manage closely vs. keep satisfied).

  2. Scenario: The BA is drafting the Business Requirements Document. The project sponsor must approve it, the solution architect must review it, and the development team needs to be kept aware of changes. Which RACI assignment is correct?
    Answer: R – Development Team, A – Sponsor, C – Solution Architect, I – (none needed beyond R). The sponsor is Accountable for approval; the architect is Consulted; the team is Responsible for implementation.

  3. Scenario: Mid?project, a new compliance officer joins the team and has veto power over data?privacy requirements. What should the BA do first?
    Answer: Update the Stakeholder Register and re?plot the Power/Interest Grid, then adjust the RACI to reflect the officer’s new authority.


Last?Minute Cram Sheet (10 One?Liners)

  1. Stakeholder Register = BABOK Planning input that feeds the Power/Interest Grid.
  2. Power/Interest Grid-decides Engagement Strategy (manage, keep satisfied, keep informed, monitor).
  3. RACI = Responsibility matrix for every BA deliverable (not just requirements).
  4. R = does the work; A = signs off; C = provides input; I = receives info.
  5. Change Impact Assessment-updates RACI when authority shifts.
  6. Communication Plan = output of Planning; lists frequency, medium, and audience.
  7. Stakeholder Analysis belongs to the Strategy Analysis knowledge area.
  8. Decision?Making Authority Matrix is a supplement to RACI when multiple approvals exist.
  9. Exam trap: “RACI is a risk?management tool.” – It is a responsibility?assignment tool, not a risk register.
  10. Validate & Baseline = final step before moving from Elicitation to Requirements Management; sign?off comes from the Accountable stakeholder.