What Is a DRI? The Directly Responsible Individual vs RACI

A DRI, or directly responsible individual, is the one named person who owns a decision, project or area of work and answers for how it turns out. Others can help, advise and disagree, but when the question is "who owns this?", there is exactly one answer.

The idea is often credited to Apple, and it has spread through engineering teams because it fixes a common problem: work that belongs to a group belongs to nobody. When three people share ownership, each assumes another is handling the hard part.

What a DRI does, and what a DRI does not do

A DRI makes the final call within their area, makes sure the work happens, and is the person others go to with questions. That does not mean they do all the work, or that they decide alone. A good DRI asks for input, weighs it, decides, and then explains the decision.

A DRI is also not the same as a manager. A manager is responsible for people. A DRI is responsible for an outcome. An engineer can be the DRI for a migration while their manager is the DRI for the team's hiring plan. On a healthy team, ownership sits with whoever is closest to the work, not with whoever is most senior.

What RACI stands for

RACI is a responsibility model that assigns four roles for each task or decision:

• Responsible: the people who do the work.
• Accountable: the one person who answers for the result and signs off.
• Consulted: the people whose input is needed before the work is done.
• Informed: the people who are told about the result.

Some teams add a fifth role, Supportive, and call it RASCI or RASIC. A RACI chart is a table with tasks down the side, people across the top, and a letter in each cell.

Where RACI breaks down

RACI works well for large programs with many teams and clear phases, such as a data center move or a compliance audit. For everyday engineering decisions it tends to be too heavy. Filling in a chart for every change is slow, so the charts go stale. The "consulted" column grows until everyone is consulted on everything. And the chart says who is accountable without saying who decides when the accountable person is away.

DRI vs RACI

The two models agree on the most important point: one person must be accountable. The "A" in RACI and the DRI are the same idea. The difference is weight.

	DRI	RACI
Roles named	One owner	Four roles per task
Best for	Projects, areas, day-to-day decisions	Large programs with many teams
Effort to set up	A sentence	A chart per program
Main risk	The owner becomes a bottleneck	The chart goes stale
Answers "who decides?"	Yes	Yes, through the A

Many teams use both: a DRI for each project, and a RACI chart only when a program spans several departments. For recurring types of decision, such as adding a dependency or changing an API, a decision authority map is often the better tool.

Why committee and consensus decisions stall

Consensus decision making means the group decides together, and a decision stands only when everyone agrees, or at least nobody objects. Committee decision making gives the call to a group that votes or agrees. Both have a place: values questions, hiring bars, and choices that need broad buy-in.

For most operational and technical decisions, though, they slow everything down. Meetings get scheduled to ratify choices that one person could have made. A single absent member can hold up a decision for a week. And when things go wrong, nobody is accountable, because everyone was. A DRI keeps the benefits of input from the group while putting the final call with one person.

How to make "who is the DRI?" easy to answer

A DRI only helps if people can find out who it is. Three habits make that easy:

1. Write the DRI at the top of every project doc and ticket epic, next to the goal.
2. Keep a short list of standing DRIs for each area: the payments service, the hiring loop, the release process.
3. Record the DRI on every entry in your decision log, so the owner of a past decision is never a mystery.

Who decides when the DRI is off

Ownership models usually assume the owner is always reachable. They are not. People take holidays, get sick, and sleep in a different time zone from half their team. When the DRI is unreachable and nobody else is named, work stops or someone guesses.

Name a stand-in for every DRI, and say what the stand-in may decide. A common rule is that the stand-in may make any decision that can be easily undone, and holds anything costly or permanent until the DRI is back. Write it down before the DRI leaves, not after the first blocked question.

What happens to a DRI's knowledge when they leave

When a DRI moves teams or leaves the company, the role can be reassigned in a minute. Their reasons cannot. The new owner inherits decisions they did not make and cannot explain. A written record of what the old DRI decided and why is what lets the new one carry on rather than start over. The guide to a system of record for decisions covers how to keep that record.

Where StandIn fits

With StandIn, anyone on a team can ask who owns a call and get an answer sourced to the person who did the work. When the DRI is away, their StandIn answers from what they wrote down, in their words, and points to the named stand-in for anything it cannot answer. It never guesses. See how StandIn works.