SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

Requirements

Stakeholder analysis and RACI matrix: a step-by-step guide with an example

Requirements · Published · Updated · 8 min read · By BA Mentorship Editorial

Part of our guide to business analyst roles and responsibilities.

Why stakeholder analysis comes first

Most projects that go wrong do so because of people, not technology. A rule is missed because the person who knew it was never asked. A release is blocked by a manager who first heard about it a week before go-live. Two departments assumed the other would own a decision, so nobody did.

Stakeholder analysis is the practice of preventing those surprises. A stakeholder is anyone who is affected by the project or can influence it. That includes obvious people, such as the sponsor and users, and easily forgotten ones, such as the support team who will answer calls about the new system, the compliance officer who must approve the change and the supplier whose system you will connect to.

This is usually the second thing a business analyst does after understanding the problem; see what a business analyst does. It shapes who you interview in your elicitation, who approves what and how you communicate. It takes less time than the problems it prevents.

Stakeholder analysis in five steps

Step 1: Identify

List every person or group who might care. Prompts that help: Who will use it? Who will be affected by it? Who pays for it? Who approves or regulates it? Who will build and support it? Who supplies data or systems we depend on? Who might be against it? Check org charts, process maps and ask each person you meet, "Who else should I talk to?"

Step 2: Understand

For each stakeholder, record their role, what they need from the project, what they fear, and what they know that you need. Be factual. "The head of operations wants fewer customer complaints and fears extra work for her team" is more useful than "likes the project".

Step 3: Assess influence and interest

Rate each person's power (ability to affect the outcome) and interest (how much it matters to them). Use simple ratings such as high and low. The rating is a judgement, so check it with colleagues and revise it as you learn.

Step 4: Plan engagement

Decide what each person needs from you and how often: a weekly review, a monthly summary, an early consultation on a particular rule. The grid below guides this.

Step 5: Review regularly

Stakeholders change as the project moves. New people join, interests shift and an unconvinced person may become a champion. Revisit the register at each project phase.

  1. IdentifyWho uses, pays, approves, builds, supplies or opposes it?
  2. UnderstandRole, needs, fears and what they know.
  3. AssessPower and interest, as a judgement you revise.
  4. Plan engagementWhat each person needs from you, and how often.
  5. Review regularlyRevisit the register at each phase.
Five steps, then repeat. Step 5 sends you back to step 1 at every project phase, because people and interests change.

The power/interest grid

The power/interest grid is a simple two-by-two chart used in Step 3 and Step 4.

Low interestHigh interest
High powerKeep satisfied. Brief, regular updates; consult before decisions affecting them; do not overload.Manage closely. Involve in key decisions; frequent contact; address concerns early.
Low powerMonitor. Minimal effort; watch for change.Keep informed. Regular updates and chances to give feedback; often your users and your best source of detail.

Two cautions. First, "low power" does not mean "unimportant". Front-line users may not control the budget but they can make or break adoption, and they know how the work really happens. Second, the grid is a discussion tool, not a scoreboard. Treat the positions as hypotheses, and move people as you learn more.

The stakeholder register

The register is the working record. A simple table is enough.

Name or groupRoleNeeds and concernsPowerInterestApproachOwner
Head of ClaimsSponsorFaster settlement; budget limitsHighHighWeekly review; escalation pointAnalyst
Claims handlersDaily usersLess re-keying; fear of more checksLowHighWorkshops; early demosAnalyst

Keep it factual and respectful. A register may be seen by others, and honest professional wording protects relationships. Store it where the team can find it, as described in documentation for business analysts.

The RACI matrix

While the register says who matters, a RACI matrix says who does what. It is a table in which rows are tasks or deliverables, columns are people or roles, and each cell holds one of four letters.

  • R: Responsible does the work. There can be several.
  • A: Accountable owns the outcome and approves it. There must be exactly one per row.
  • C: Consulted gives input before the work is finished (two-way).
  • I: Informed is told the result (one-way).

Rules that keep a RACI honest

  1. Exactly one A per row. Zero means nobody owns it; two means a fight.
  2. At least one R per row, and sometimes the R and A are the same person.
  3. Keep the C list short. Everyone in C slows the work; everyone missed from C may block it later.
  4. Use roles, not only names, so the matrix survives people changing jobs.
  5. Agree the matrix with the people in it. A RACI no one has seen is a wish, not an agreement.

Check every RACI row

  • Exactly one A (Accountable). None means nobody owns it; two means a fight.
  • At least one R (Responsible). R and A may be the same person.
  • A short C (Consulted) list: two-way input before the work is finished.
  • I (Informed) for people told the result, one way.
  • Roles as well as names, so the matrix survives job changes.
  • Agreed with the people in it.
Run this check on each row before you share the matrix. The conversation it starts is the real value.

A worked example: a claims portal at Tidewater Insurance

Tidewater Insurance is a fictional insurer. It plans a customer portal where policyholders can check claim status. The analyst, Fatima, starts with a list of stakeholders.

Register and grid placement

StakeholderPowerInterestApproach
Head of Claims (sponsor)HighHighManage closely: weekly review
Fraud team leadHighLow (so far)Keep satisfied: consult on what may be shown to customers; early meeting booked
Claims handlersLowHighKeep informed and involve in workshops
Customer contact centreLowHighKeep informed; they will field the questions
Compliance officerHighMediumKeep satisfied; review of data shown
IT development teamMediumHighManage closely during design and build
MarketingLowLowMonitor

The grid reveals something: the fraud team lead has high power but has not been engaged. Fatima books a meeting immediately. In it, she learns that showing "assessor visit date" to customers could allow someone to prepare for an inspection in suspected fraud cases. That rule is added to the requirements before design starts. Without the analysis, it might have surfaced after build.

RACI for the requirements document

TaskAnalystHead of ClaimsFraud leadComplianceDev leadContact centre
Write status requirementsRACCCI
Define data shown to customersRCCACI
Approve requirementsRAICII
Estimate and buildCIIIA/RI
Run user acceptance testingRACICR

Looking at the table, Fatima checks each row: exactly one A each, and A/R for the dev lead where one person is both. She notices that the fraud lead is only Consulted and Informed, which matches their role. She shares it with the sponsor, who moves one A to compliance for the data row. That conversation, rather than the table itself, is the real value.

Tidewater Insurance stakeholders on a power and interest gridA grid with power rising upwards and interest rising to the right. Quadrants: top left Keep satisfied, top right Manage closely, bottom left Monitor, bottom right Keep informed. Head of Claims (sponsor): high power, high interest; Fraud team lead: high power, low interest; Compliance officer: high power, low interest; IT development team: high power, high interest; Claims handlers: low power, high interest; Contact centre: low power, high interest; Marketing: low power, low interest.Keep satisfiedManage closelyMonitorKeep informedHead of Claims(sponsor)Fraud teamleadComplianceofficerIT developmentteamClaimshandlersContact centreMarketingInterest →Power →
The grid reveals a gap. The fraud team lead has high power but had not been engaged. The meeting Fatima booked found a rule about the assessor visit date before design started.
Diagram in words
  • Head of Claims (sponsor): high power, high interest, so Manage closely.
  • Fraud team lead: high power, low interest, so Keep satisfied.
  • Compliance officer: high power, low interest, so Keep satisfied.
  • IT development team: high power, high interest, so Manage closely.
  • Claims handlers: low power, high interest, so Keep informed.
  • Contact centre: low power, high interest, so Keep informed.
  • Marketing: low power, low interest, so Monitor.

From register to communication plan

An analysis that stays in a spreadsheet changes nothing. The last step is to turn the register into a simple communication plan: who hears what, from whom, how often and in what form. Keep it light enough that you will actually follow it.

AudienceWhat they needFormat and frequencyOwner
SponsorProgress, decisions needed, risksShort weekly summary and a standing 20-minute callAnalyst and project manager
Daily usersWhat is changing and when, a chance to reactFortnightly demo or workshop; notes by emailAnalyst
ComplianceAnything touching regulated data or customer wordingReview at each requirements milestoneAnalyst
Wider departmentAwareness, how to get helpMonthly note on the team pageProject manager

Check the plan after the first two weeks. If someone says they are drowning in updates, reduce the frequency; if someone says they heard about a decision too late, increase it. Communication is a service to the stakeholder, not a report about the project.

Mistakes to avoid

  • Listing only the obvious. Ask "who else?" in every interview.
  • Confusing influence with seniority. A junior system administrator can block a release.
  • Making the register a secret. Share the approach, not private opinions.
  • Too many A's or none. Check every row of the RACI.
  • Treating it as one-off. Update as the project and the people change.
  • Over-consulting. Everyone in C slows the work. Consult those who truly have input.
  • Forgetting communication. The register should lead to a plan: what, to whom, how often.

The skill is part of a bigger set; see business analyst skills. To practise, build a register and RACI for a change at your own workplace, then check them with one person in the list. The BA Lab has a stakeholder stage with a fictional company, a register and RACI task, and feedback on gaps. For the next step after stakeholders, read about how to write user stories from what they tell you.

Frequently asked questions

What is the difference between a stakeholder register and a RACI matrix?

The register lists stakeholders with their needs, influence and engagement approach. The RACI matrix assigns roles for each task or deliverable. They answer different questions: who matters and who does what.

Can a RACI have more than one Accountable person?

No. Each task should have exactly one Accountable person. Two accountable owners usually means unclear ownership and delays in decisions.

What does RACI stand for?

Responsible, Accountable, Consulted and Informed.

How often should I update stakeholder analysis?

At each project phase and whenever people, scope or priorities change. A short review during planning meetings is usually enough.

What do I do with a stakeholder who opposes the project?

Find out why. Their concern may reveal a real risk. Involve them early, address the concern with evidence, and escalate to the sponsor if the disagreement cannot be resolved.

This article is educational. All companies, people and numbers in the examples are fictional. BA Mentorship does not issue professional certifications and cannot guarantee any job or interview outcome.

Key terms in this article

Browse the full glossary

CHECK BEFORE CONTINUING

Keep your work safe