Most failed BA projects do not fail because the requirements were wrong. They fail because someone with influence was never consulted, or someone responsible was never made accountable, or someone who needed to know was never told. Stakeholder identification is the work that prevents all three.
This is the first deliverable on most BA projects, before any requirements are even discussed. Get it right and the rest of the work flows. Miss a stakeholder and you find out at sign-off, when the cost of going back is highest.
The discipline in one sentenceStakeholder identification is the systematic process of finding every person and group who has a stake in the outcome, classifying their relationship to the work and capturing it in a form the project team can act on.
RACI: who does what with each decision
RACI is the most widely-used stakeholder classification tool in SA enterprises. Four letters, four roles per decision or deliverable.
1
Responsible (R)The person who actually does the work. There can be multiple Rs per task. They get hands dirty in producing the deliverable.
2
Accountable (A)The person who answers for the result. Only one A per task. If the deliverable is late or wrong, the A is the one who owns the outcome. Often a manager or sponsor.
3
Consulted (C)People whose input is needed before the work happens. Two-way communication. Experts, subject matter authorities, neighbouring teams whose work depends on this one.
4
Informed (I)People who need to know the outcome after the fact. One-way communication. Affected teams, downstream consumers, governance bodies who track progress.
A worked RACI example
A small SA insurer is changing how new motor policies get quoted. Here is a slice of the RACI matrix for one decision: changing the underwriting rules.
| Stakeholder | Decision: Change underwriting rules |
|---|
| Head of Underwriting | Accountable (A) |
| Underwriting BA | Responsible (R) |
| Actuarial team | Consulted (C) |
| Legal and Compliance | Consulted (C) |
| IT delivery team | Consulted (C) |
| Claims team | Informed (I) |
| Reinsurance partners | Informed (I) |
Read it horizontally: for this one decision, the Head of Underwriting is the single accountable owner, the BA does the work, three teams are consulted before the change is made and two teams are notified after.
A common mistake is having more than one A. If two people are accountable, neither truly is. Force the conversation to pick one.
The onion diagram: who lives at what distance from the work
RACI tells you who does what. The onion diagram tells you who lives at what distance from the project. It is a complementary view, useful when you are trying to make sure you have not missed anyone.
1
The solution itselfThe product, the system, the change being delivered. The bullseye.
2
Direct users and operatorsThe people who will interact with the solution every day. The underwriters using the new rules engine. The call-centre agents using the new claims system. Their hands are on it.
3
Direct beneficiariesPeople who get value from the solution without operating it. Policyholders who get faster quotes. Brokers who get better commission data. Customers downstream of the operators.
4
The organisationOther teams, departments and functions inside the company whose work touches the solution. Finance, reporting, audit, internal IT, security, HR. The wider business.
5
External partiesRegulators, partners, suppliers, customers' customers. People outside the organisation who are affected. The Prudential Authority. SARS. The Information Regulator if POPIA matters. Reinsurance partners.
When you do the exercise, walk the onion outward and ask "who lives here?". You will find stakeholders the project sponsor forgot about.
Stakeholders SA BAs most often miss
A few SA-specific categories that are easy to leave off the first draft of the stakeholder list.
Legal and ComplianceAlmost every SA enterprise system change has a compliance implication. POPIA, FAIS, the Banks Act, FICA, JSE listings rules, the Cybercrimes Act. Adding Legal and Compliance early avoids late surprises.
Information SecurityMany SA enterprises now require InfoSec sign-off on any system change involving customer data. Looping them in late costs weeks.
Internal AuditAudit cares about traceability, segregation of duties and controls. If the change affects financial reporting, the audit team needs visibility.
B-BBEE and TransformationProcurement choices (especially around new vendors) have B-BBEE scorecard implications. The transformation officer is sometimes the one who can approve or block a contract.
Trade UnionsIn unionised sectors (mining, manufacturing, public sector, banking back-office) any change to how work gets done can trigger consultation obligations. NUMSA, NEHAWU, SASBO and others. Engage early.
Operational RiskCommon in financial services. Op Risk owns the risk register and may need to assess new operational risks introduced by the change.
How to actually run the identification
Practical sequence for a new BA project.
1
Sponsor interviewSit with the project sponsor and ask "who else is affected by this". Capture names. Then ask "who would be upset if we did not include them".
2
Org chart walkOpen the company's org chart and walk it. For each team within two reporting levels of the work, ask whether they have a stake. Sounds slow. Takes 30 minutes. Catches the people the sponsor forgot.
3
Onion sweepApply the onion model. Walk outward from the bullseye. Capture any new names that surface.
4
RACI per major decisionFor each major decision the project will need to make, draft a RACI line. The act of writing the matrix often reveals missing stakeholders.
5
Validation passSend the draft list to two or three stakeholders you already have buy-in from. Ask "who is missing". They almost always find one.
Key Takeaways- Failed projects rarely fail on requirements alone. They fail because someone with influence was missed during identification.
- RACI is the workhorse. Responsible, Accountable, Consulted, Informed. Only one A per decision.
- The onion is the safety net. Walk outward from the solution to confirm no stakeholder group is missing.
- SA has predictable missing roles. Legal/Compliance, InfoSec, Audit, B-BBEE, Unions and Op Risk are the usual blind spots.
- Validate with people you trust. Send the draft to a few stakeholders and ask who is missing. They will tell you.