A directly responsible individual, or DRI, is the single named person accountable for an outcome. The DRI does not have to do the work alone. They make sure it gets done, and they are the person everyone goes to with questions about it. The model fits product teams because most product leaders have no direct authority over the people doing the work.
Product leaders do not approve anyone's time off, raises or reviews. Their influence runs sideways, which is the central problem of product org structure, so accountability has to come from clarity. I have used DRIs at early-stage startups and at public companies, and they pair with the rule that most decisions are two-way doors: name the owner, let them decide, and correct course if the call was wrong.
When everyone is responsible, no one is. A DRI is the one person who cannot say "that is not my call."
Where the DRI comes from
The term comes out of Apple. Adam Lashinsky's reporting in Inside Apple quoted a former employee: "Any effective meeting at Apple will have an action list. Next to each action item will be the DRI." If you did not know who to ask about something, the question you heard was "Who's the DRI on that?"
A name, one name, next to every action. A team or a department in that column means nobody.
What it felt like to be the DRI
I first worked this way at TripAdvisor during the Instant Booking build. Nobody had written it into a playbook. If something important needed to happen, someone owned it, and everyone could see who.
I said yes to owning things I was not sure I could pull off. Sometimes the yes came with a groan: "Alright, I guess that's mine." Once my name was on it, other people planned around it, and that was the point. The discomfort was the system working.
How a DRI team behaves day to day
The habit shows up in small places first. The DRI goes on the To: line of an email and everyone else on CC, so a reader knows in two seconds whether a reply is expected from them.
Ownership gets assigned at the start of a fuzzy project, before a deadline slips. "Who's the DRI here?" belongs in the kickoff.
Meetings end with actions that have names next to them. A meeting that ends with agreement and no names produced a nice conversation and nothing else.
When an ambiguous request lands in a shared inbox, people ask "is this mine?" instead of waiting to see who blinks first.
Two ways the model breaks
The first is treating the DRI as a solo act. A good DRI pulls in collaborators, delegates pieces and asks for help. Their job is to get the work across the line.
The second is using the name as a blame target. If a missed outcome turns into "well, that was your name on it," people stop volunteering, and the next fuzzy project goes back to having no owner. DRIs need a team where taking the hard item is rewarded even when it goes sideways.
What happens without them
Teams without named owners drop tasks, skip follow-ups and leave meetings with a shared feeling of progress and no next step. Leaders start stepping in to assign work and settle confusion. That slows everyone down, burns out the managers doing it, and teaches the team to wait for escalation. Accountability becomes a team sport only after each piece of it has one name.
How to introduce DRIs
Start with your own meetings. Put a name next to every action item you leave with, and when something lands on you, say out loud that it is yours.
Use the term. "Who's the DRI on this?" lands faster than "does anyone want to pick this up?" and borrows a vocabulary many people already know.
Add one question to retros: did anything slip because ownership was unclear? The answer tells you where to name owners next time.
Keep it light, and call out good ownership when you see it. It takes one habit and no new process.
For a product team, the payoff is visibility with no new layer of hierarchy: everyone can see who owns what, and stepping up never means stepping into a vacuum.
Building accountability into your product org?
The DRI model is one of the strongest accountability structures a product organization can run, and it works only when ownership is clear and the owner has room to decide. I help product leaders put it in place. Let's talk.
