Why accountability breaks down in IT
Decisions wait because nobody knows who decides. Benefits are never tracked because nobody owns them. Auditors find developers approving their own changes. Partners are blamed for outcomes the contract never gave them. These are not people problems. They are symptoms of accountability that was never written down, or written once and never kept up.
A technology RACI fixes this when it is short enough to use, follows a few clear rules, and is built from how work really happens rather than from the organisation chart.
The four letters, precisely
| Letter | Meaning | Common confusion |
|---|---|---|
| R: Responsible | Does the work. Several roles can be R. | Listing everyone who touches the work |
| A: Accountable | The one role that owns the outcome, approves the result and answers for it if it goes wrong. Exactly one per activity. | Giving the A to the most senior person in the room |
| C: Consulted | Gives input before the work is done or the decision taken, and that input could change the result. | Consulting everyone, which slows everything |
| I: Informed | Told after the decision or the work is done. | Treating I as a courtesy with no follow-through |
Accountable is not the most senior person involved. Seniority belongs in the escalation path, not in the A.
Six rules every row must pass
| Rule | What it means |
|---|---|
| 1. One A per activity | Two As means nobody is accountable; no A means the activity is optional. |
| 2. At least one R | Somebody is named to do the work, or the A does it (A/R). |
| 3. A at the lowest level that can decide | Give the A to the role closest to the work that has the authority and the information. Escalate exceptions, not routine decisions. |
| 4. The business owns business outcomes | Requirements, acceptance, benefits, data and access rights belong to the business owner. IT is R or C. |
| 5. A partner is never A | A managed service partner can be R, C or I. The company stays accountable, even for outsourced services. |
| 6. Keep duties apart | The role that does the work does not approve it: build and change approval, build or test and user acceptance, granting and certifying access. |
An example: ten rows
An extract for a mid-size company with a managed service partner. Every row passes the six rules: one A, at least one R, the partner is never A, the business owns business outcomes, and no role approves its own work. Note that the CIO holds no A here: routine decisions sit with the role closest to the work, and the CIO stays accountable for IT policy proposals and escalated exceptions, within the steering committee's decision rights.
| Activity | Business owner | CIO | Enterprise architect | Head of applications | Head of infrastructure | CISO | Partner |
|---|---|---|---|---|---|---|---|
| Define business requirements | A/R | – | C | C | – | – | – |
| Approve the solution design | C | – | A/R | C | C | C | – |
| Build and configure the change | I | – | C | A | – | – | R |
| System and integration testing | I | – | – | A | C | – | R |
| Accept the solution for users | A/R | – | – | C | – | – | I |
| Approve the change for production | I | – | – | C | A/R | I | C |
| Deploy the change to production | – | – | – | A | C | – | R |
| Approve and certify access to business data | A/R | – | – | – | I | C | – |
| Grant approved access | I | – | – | – | A | C | R |
| Track benefits after go-live | A/R | I | – | C | – | – | – |
A complete technology RACI usually covers forty to sixty activities across strategy, portfolio, delivery, operations, security, data and vendors, and twelve to fifteen roles. More rows than that, and nobody reads it; fewer, and the disputed activities are left out.
Segregation of duties: the rules auditors check
Some combinations should never sit with the same role. Check each role against rules like these:
- Whoever builds a change does not approve it for production.
- Whoever deploys a change does not approve it.
- Whoever builds or tests a change does not accept it for users.
- Whoever grants access does not certify it in the access review.
- Whoever builds a solution does not approve its design review.
Small teams cannot always separate duties. Where they cannot, write down the compensating control (an independent review, a log checked by someone else, an automated control in the tool) and who performs it.
Build it in six steps
| Step | What you do |
|---|---|
| 1. Frame | Agree the purpose, scope and roles (roles, not names) with a sponsor; write the activity list as verbs with an object. |
| 2. Map today | Interview people about real recent cases: who did the work, who decided, who was surprised. Record the RACI as it really works. |
| 3. Draft the target | Apply the six rules to every row; note where the target differs from today and why. |
| 4. Settle disputes in workshops | Work through only the disputed rows, with the people involved, using the four questions below. |
| 5. Roll it out | Change what makes it real: role descriptions, approval steps in the tools, contracts with partners, committee terms of reference. |
| 6. Keep it alive | Review it once a year, and whenever the organisation, a partner or a major process changes. |
Mistakes to avoid
- Mapping the organisation chart, not the work. Start from real cases, or the RACI will describe how things should work and change nothing.
- Using names instead of roles. The RACI breaks the first time someone moves.
- Making the CIO accountable for everything. Keep the CIO as A for policy and exceptions; push routine decisions down.
- Stopping at the spreadsheet. A RACI that is not reflected in tools, contracts and role descriptions is a document, not a change.
- Forgetting the partners. Link the RACI to what each contract actually says the partner does.
Questions
What is the difference between a RACI and a decision rights matrix?
A RACI covers activities: who does the work and who answers for it. Decision rights cover decisions: who decides what, at which threshold, in which forum. They work together: the A in the RACI should match the decision rights for the same topic.
Can a role be both accountable and responsible?
Yes, written A/R, when the role that owns the outcome also does the work. It is common for small activities. It is a problem only when it breaks a segregation of duties rule.
How many activities should a technology RACI have?
Forty to sixty for a whole IT function is usually right. Detail below that belongs in process documents and tools.
Who should own the RACI?
The CIO office usually maintains it, with each domain owner confirming their rows once a year. Disputes go to the CIO for rows inside IT, and to the business sponsor or CEO for rows the business owns.