DRI: The Directly Responsible Individual

Summary

DRI, the Directly Responsible Individual, is not a matrix but a rule: for every outcome that matters, exactly one named person is responsible, and everyone knows who. The practice became famous inside Apple under Steve Jobs, where meeting agendas list a DRI next to each action item, and it has since spread to companies including HubSpot, DuckDuckGo, and Flipboard. It attacks the diffusion of responsibility head on: when everyone owns something, no one does. Use it when ownership is the whole problem, when work falls into cross-functional gaps, or in remote cultures where informal nudges are lost. It says nothing about who advises, consents, or verifies, so pair it with a matrix or a decision-rights framework when finer role detail matters.

The idea

DRI stands for Directly Responsible Individual. Where every other matrix in this set distributes several roles across a task or a decision, DRI does the opposite: it collapses responsibility onto one named person for a given outcome. That person is the go-to contact, the one who takes decisions, unblocks progress, and answers for whether the thing gets done.

It is not a matrix and not a set of role letters. It is a rule: for anything that matters, there is exactly one DRI, and everyone knows who they are. Other people may contribute, advise, or help, but the DRI ties it together, makes the final calls, and delivers. If the work stalls, it is the DRI’s job to unstick it, and if it fails, the DRI is the one who needs a convincing answer.

Origin and history

DRI is Apple’s contribution to the responsibility vocabulary. The term became internal Apple language under Steve Jobs, and at Apple a meeting agenda will typically list the DRI next to each action item, so there is never ambiguity about who owns what. A common question heard around the company is simply “who’s the DRI on that?”

The practice was documented publicly through Adam Lashinsky’s book Inside Apple (2012) and through accounts from former Apple staff; Ken Kocienda, who worked on the original iPhone, has described how the team had no product managers and instead assigned a directly responsible individual to each important piece of work. From Apple, the concept spread widely: it has been adopted, sometimes under different names, at companies including HubSpot, DuckDuckGo, Flipboard, Tettra, and Levels. It is also closely related to Amazon’s notion of the single-threaded leader and to the more general idea of a single “owner” or “sponsor” for an outcome.

Unlike RAPID, DRI has no founding academic article and no trademark; it is a cultural practice that Apple made famous and that other organizations copied because it plainly works.

What problem it solves

DRI is a direct assault on the diffusion of responsibility: the well-documented tendency for people to do less, or to assume someone else will act, when responsibility is shared. When everyone owns something, no one does. DRI forces the uncomfortable but clarifying conversation of putting a single name on each outcome, which removes the hiding places that group ownership creates.

It solves this most powerfully in the gaps between roles and functions. The classic case is a cross-functional deliverable that falls between two departments, where each assumes the other owns it: a new feature that Product built but that Marketing usually announces, for example. Naming one DRI closes that gap. The model also addresses social loafing (there is no crowd to hide in), and it simplifies life for everyone else, who can rely on the DRI to integrate their contributions rather than each maintaining full awareness of the whole.

When to choose it, and when not

Choose DRI when you need ownership rather than a matrix, when work is falling into cross-functional gaps, and when speed matters. It is especially valuable in fast-growing organizations where important things get dropped simply because everyone is busy, and in remote or asynchronous cultures where you lose the informal in-person nudges that keep work on track. It is also a good delegation and development tool: making someone the DRI gives them real ownership and an early taste of management responsibility.

Do not use DRI as a substitute for the finer-grained clarity that a matrix provides on complex, multi-role work. Naming one owner tells you who is on the hook, but not who advises, who must consent, or who verifies, which on a regulated or highly collaborative deliverable still matters. DRI answers “who owns this outcome”; it does not, by itself, answer “how is the work distributed” or “who can veto”. For those, pair it with a RACI-family chart or a decision-rights framework.

Common pitfalls

• Hero worship. The gravest cultural risk. Over-celebrating the DRI as a lone hero erases the team around them and, over time, corrodes the culture, which is the opposite of the model’s intent.
• A DRI without authority, capacity, or the right capabilities. Responsibility without the power, time, or skill to act is a recipe for failure. The DRI needs enough standing and support to actually drive the outcome.
• Two people sharing the role. Two DRIs is no DRI. If two people must both act, give each a distinct task and make one of them the single owner.
• Scattered adoption. DRI works when applied consistently. If some teams use it and others do not, you get confusion and political friction over who really owns cross-team outcomes.
• Owner without the team. The DRI is accountable for the outcome, but usually does little of the tactical work. Forgetting that they depend on others, and failing to name those others, undermines delivery.

Worked example

A cross-functional feature launch that has historically fallen between Product and Marketing.

Each outcome has exactly one name attached. The launch announcement no longer falls into the gap between Product and Marketing, because the Product Manager is the named DRI even though Marketing does much of the drafting. Anyone unsure who is driving a piece can ask “who’s the DRI?” and get a single answer, which is the entire point.

Where it sits in the family

DRI is the minimalist pole of the whole set. If PARIS and the compliance variants sit at the elaborate end, adding roles and gates, DRI sits at the opposite extreme, reducing responsibility to a single name. It shares the “one accountable owner” instinct that runs through RACI’s Accountable, DACI’s Approver, and MOCHA’s Owner, but it strips away everything else. Use it on its own when ownership is the whole problem; layer it with a RACI-family matrix or a decision-rights framework when you also need to know who advises, consents, or verifies. Read this article last, as the deliberate simplification that the rest of the family exists to enrich.

Sources

Web sources

• Using the Directly Responsible Individual (DRI) concept, BiteSize Learning: https://www.bitesizelearning.co.uk/resources/directly-responsible-individual-dri-apple
• Directly Responsible Individuals: The What, How and Why, Tettra (Apple origin; Ken Kocienda on the original iPhone team): https://tettra.com/article/directly-responsible-individuals-guide/
• How Well Does Apple’s Directly Responsible Individual (DRI) Model Work in Practice, Forbes/Quora: https://www.forbes.com/sites/quora/2012/10/02/how-well-does-apples-directly-responsible-individual-dri-model-work-in-practice/
• Directly Responsible Individual, D. Brown Management (Lashinsky’s Inside Apple; Rickover on responsibility): https://dbmteam.com/insights/directly-responsible-individual-dri/

Academic sources

• Darley, J.M. and Latané, B. (1968) ‘Bystander intervention in emergencies: diffusion of responsibility’, Journal of Personality and Social Psychology, 8(4), pp. 377-383. https://doi.org/10.1037/h0025589 The experimental foundation for the failure mode DRI is designed to prevent.
• Podolny, J.M. and Hansen, M.T. (2020) ‘How Apple is organized for innovation’, Harvard Business Review, 98(6), pp. 86-95. The closest thing to an academic account of Apple’s organizational model, by the dean of Apple University and a co-author.
• Lashinsky, A. (2012) Inside Apple: How America’s Most Admired and Secretive Company Really Works. New York, NY: Grand Central Publishing. The book that documented the DRI practice publicly.
• Kocienda, K. (2018) Creative Selection: Inside Apple’s Design Process During the Golden Age of Steve Jobs. New York, NY: St. Martin’s Press. First-hand account of DRI-style ownership on the original iPhone team.