Every Monday morning at Apple, the executive team files into a conference room for a three-hour meeting. The agenda covers every significant product, project, and initiative across the company. Next to each item on that agenda is a name — not a team, not a department, not a committee. One name. The person who is directly responsible for that item. If the item is behind schedule, that person explains why. If a decision needs to be made, that person makes it. If the outcome is a failure, that person owns it. Apple calls this person the DRI — the directly responsible individual — and the system is the organisational architecture that turned a company ninety days from bankruptcy into the most valuable corporation on earth.
Steve Jobs didn't invent accountability. He engineered it. When he returned to Apple in 1997, the company was haemorrhaging cash — $1.6 billion in losses that fiscal year — with a product line so bloated that Jobs famously drew a 2×2 grid (consumer/pro, desktop/portable) and killed everything that didn't fit. But the product rationalisation was the visible fix. The structural fix was less dramatic and far more consequential: Jobs rebuilt Apple's operating system around the principle that every deliverable has exactly one person who is responsible for it. Not jointly responsible. Not co-responsible. Singularly, unambiguously, non-negotiably responsible.
The logic is precise and mathematical. When a committee of eight shares responsibility for a product launch, each member bears one-eighth of the accountability. That fraction is low enough to permit inaction, excuse delayed decisions, and enable the specific pathology that kills large organisations: the assumption that someone else is handling it. When one person owns the launch, they bear 100%. They cannot diffuse. They cannot assume. They can only act — or be visibly, specifically accountable for not acting.
The DRI principle solves three problems simultaneously. First, it eliminates diffusion of responsibility — the psychological phenomenon where felt accountability decreases as group size increases. Second, it accelerates decision-making because every question has exactly one person who can say yes or no without convening a meeting. Third, it creates an unambiguous accountability chain: when something succeeds, the DRI gets credit; when something fails, the DRI owns the diagnosis. There is no organisational fog in which failure can hide.
Adam Lashinsky, in his 2012 book Inside Apple, documented how the DRI system permeated every level of the company. From the executive team's Monday review down to individual engineering features, every item had a name. "At Apple there is never any confusion as to who is responsible for what," Lashinsky wrote. The system's clarity was not incidental. It was the product of Jobs's understanding that ambiguity in ownership is the structural precondition for organisational dysfunction. Remove the ambiguity and you remove the dysfunction — not by changing people's motivations but by changing the architecture in which they operate.
Section 2
How to See It
The DRI model is operating whenever an organisation has assigned clear, singular ownership of an outcome to a named individual — and that assignment is visible, enforceable, and unambiguous. The diagnostic is simple: ask "who owns this?" If the answer is one name, you're looking at DRI. If the answer is a team, a committee, or a vague reference to "leadership," you're looking at its absence.
Product & Engineering
You're seeing DRI when every feature in a product roadmap has one named owner who controls its specification, timeline, and trade-offs. At Apple, even individual UI animations had a DRI. When a stakeholder asked "why does this screen transition feel slow?", the answer was never "the design team is looking at it." It was "Marcus owns that transition, and he's shipping the fix in build 4.2.3 on Thursday." The specificity — a name, a build number, a date — is the hallmark of DRI operating as designed.
Corporate Operations
You're seeing DRI when every item on a leadership meeting agenda has a single name next to it, and that person is expected to report status, make decisions, and absorb accountability for the outcome. The DRI doesn't need to do all the work. They need to own all the accountability. A DRI for a product launch may coordinate fifty engineers, twelve designers, and three marketing leads. The coordination is distributed. The accountability is not.
Technology
You're seeing DRI when an incident response protocol designates a single incident commander the moment an alert fires. PagerDuty's on-call model is DRI applied to operations: one person must acknowledge the alert within a defined window, owns the resolution timeline, and bears accountability for the outcome. The model collapses the diffusion that shared on-call rotations create by default. When twelve engineers receive an alert, each assumes someone else is investigating. When one engineer is the DRI, that assumption is architecturally impossible.
Section 3
How to Use It
Decision filter
"For every initiative, deliverable, and recurring responsibility in my organisation, can I name exactly one person who owns the outcome? If the answer is a committee, a team, or 'we all do,' I've identified a structural vulnerability. Convert it to a name."
As a founder
Build the DRI principle into your company's operating system from day one — not after it becomes a problem. At ten employees, diffusion of responsibility is rare because everyone can see everyone else's work. At fifty, it begins. At five hundred, it is the dominant failure mode for cross-functional initiatives. The companies that scale effectively are the ones that assign DRIs before the organisation is large enough to need them, so the muscle is developed before the strain arrives.
Start with your meeting agenda. Every item gets a name. Not a team. Not a Slack channel. A person. That person reports status, makes decisions when consensus fails, and owns the post-mortem when things go wrong. The discipline feels heavy in a ten-person startup. It becomes indispensable at a hundred. Apple used the system at every scale — from the original Macintosh team of twenty to a workforce of 164,000 — because Jobs understood that the architecture that works at ten must be the same architecture that works at a hundred thousand.
As an investor
When evaluating a company's execution capability, probe for DRI culture. Ask the CEO: "Who specifically owns your retention metric?" If the answer is "the growth team," the metric is owned by no one. If the answer is "Jennifer, our VP of Product — she reports weekly in our Monday standup and has authority over the features that influence retention," the metric has a DRI and will improve.
The distinction predicts execution velocity with striking reliability. Portfolio companies with clear DRIs ship faster, resolve incidents faster, and course-correct faster than companies where ownership is distributed across committees. The reason is structural, not cultural: the DRI can make a decision in minutes that a committee takes weeks to debate, because the DRI doesn't need consensus — they need judgment.
As a decision-maker
The most impactful application of DRI in large organisations is at the interface between departments — the handoff zones where diffusion of responsibility creates its worst damage. When product and engineering share responsibility for a launch, and marketing and sales share responsibility for revenue, the interfaces between these groups are where problems go to die. Assign a DRI for every cross-functional initiative. Not a project manager who coordinates. A leader who owns the outcome and has the authority to make trade-offs across departmental boundaries.
The authority component is non-negotiable. A DRI without decision-making authority is a scapegoat, not an owner. Jobs understood this: Apple's DRIs had the power to make calls that affected other teams' timelines and resources. The system worked because the DRI's authority was backed by executive support and visible in the meeting structure. A DRI who must ask a committee for permission to act is a committee member with a fancier title.
Common misapplication: Assigning a DRI but not giving them the authority to execute. The model requires two components: accountability and authority. A junior product manager named as DRI for a strategic initiative but unable to allocate engineering resources, override conflicting priorities, or make trade-offs without three levels of approval is not a DRI — they are a coordinator with a label. The fix is to match the DRI's authority to the scope of their accountability, or reduce the scope to match the authority they actually have.
Second misapplication: Treating DRI as micromanagement. The DRI owns the outcome, not every task within it. A DRI for a product launch delegates engineering, design, QA, and marketing to specialists. What they do not delegate is the decision about whether the product is ready to ship, the accountability if it ships broken, or the authority to delay if quality isn't met. Ownership of the outcome is not the same as control of the process.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The leaders who built the most effective DRI systems share a conviction: that committees produce alignment at the expense of accountability, and that accountability — concentrated in one person with the authority to act — produces better outcomes than alignment ever will. Each of them designed organisations where the question "who owns this?" always had a one-word answer.
Jobs didn't just assign DRIs — he built an entire organisational topology around the principle. Apple's functional structure (design, engineering, marketing, operations) rather than divisional structure (iPhone division, Mac division) was a DRI architecture at the company level. Each functional leader was the DRI for their domain across all products. Jony Ive was the DRI for industrial design — not for iPhone design and separately for Mac design, but for design as a discipline. This structure meant that design coherence across Apple's entire product line was one person's responsibility. The visual consistency between the iPhone, MacBook, and Apple Watch was not the output of a design committee. It was the output of a DRI whose authority spanned every product.
The Monday executive meeting operationalised the system at the leadership level. Jobs reviewed every significant initiative weekly, and every initiative had one name. When the original iPhone was behind schedule in 2006, Scott Forstall was the DRI for the software. When MobileMe launched catastrophically in 2008, Jobs replaced the team's leadership — but the replacement was a new DRI, not a new committee. The response to failure was always the same: identify the DRI, assess whether they had the right resources and authority, and if the system was sound, change the person; if the person was sound, change the system. The DRI framework gave Jobs a diagnostic that cut through organisational noise in seconds.
Amazon's version of the DRI is the "single-threaded leader" — one person whose entire job is one business outcome, supported by a two-pizza team with the autonomy to execute without cross-team dependencies. The single-threaded leader does not split attention across multiple initiatives. Their calendar, their team, and their performance evaluation are all oriented toward one outcome. Andy Jassy was the single-threaded leader for AWS. The initiative grew from an internal infrastructure project to a $90 billion annual revenue business because one person owned it completely — not as a side project, not as a shared priority, but as their singular professional mission.
Bezos extended the DRI principle to decision-making through the six-page memo. Every memo has one author — and that author is the DRI for the quality of the argument on which the decision rests. The author cannot distribute responsibility for a weak analysis across a committee of contributors. The words are on the page, the name is on the document, and the accountability is singular. The memo format naturally produces DRIs for every consequential decision, because the act of writing forces one person to do the thinking that committees diffuse across their members.
Ed CatmullCo-founder & President, Pixar Animation Studios, 1986–2019
Catmull built Pixar's creative process around a DRI principle applied to filmmaking: the director has final creative authority over every frame of the film. The Braintrust — Pixar's celebrated feedback mechanism — provides candid input from senior creative leaders. But the Braintrust has no authority. It cannot mandate changes. The director absorbs the feedback, decides what to incorporate, and bears sole creative responsibility for the result. This structural separation between input and authority is the DRI principle in its purest form: many voices inform the decision; one person makes it.
The results validated the architecture. Between 1995 and 2010, Pixar released fifteen consecutive critically and commercially successful films — a record unmatched in cinema history. When films struggled in production (and Catmull was explicit that every Pixar film was terrible at some point), the response was not to replace the DRI with a committee. It was to ensure the DRI had better input. The Braintrust gave the director more data. It never took the director's authority. Catmull understood that creative accountability, like operational accountability, must be singular to be meaningful.
Section 6
Visual Explanation
Section 7
Connected Models
The DRI model operates at the intersection of organisational design, accountability theory, and decision velocity. It draws its power from concentrating what other structures diffuse, and its connections to adjacent frameworks reveal how singular ownership interacts with the group dynamics, communication systems, and authority structures of the organisations that deploy it.
Extreme ownership — the principle that the leader is responsible for everything in their world — is the philosophical foundation for the DRI. The DRI is extreme ownership operationalised at the initiative level: instead of a general stance that "I own outcomes," the DRI system assigns specific outcomes to specific people with named accountability. Willink's principle says the leader owns everything. The DRI system says here is the specific thing you own, here is the metric, and here is the deadline. The reinforcement is bidirectional: extreme ownership creates the cultural willingness to accept individual accountability, and the DRI system creates the structural mechanism for assigning it. Organisations with DRI architecture but no ownership culture produce scapegoats. Organisations with ownership culture but no DRI structure produce diffusion. The combination produces results.
The six-page memo is a natural DRI-creation mechanism. Every memo has one author, and that author is the directly responsible individual for the quality of the argument on which the group's decision rests. The writing process forces singular accountability by design: a committee cannot co-author a coherent narrative without one person synthesising the group's input into a unified argument. The author's name is on the document. The reasoning is permanently on record. The reinforcement is structural — the memo format converts every consequential decision into a DRI assignment, because the act of writing makes individual accountability inescapable in a way that verbal presentations and committee votes do not.
Tension
[Diffusion of Responsibility](/mental-models/diffusion-of-responsibility)
Section 8
One Key Quote
"At Apple there is never any confusion as to who is responsible for what. The accountability is clear."
— Adam Lashinsky, Inside Apple: How America's Most Admired — and Secretive — Company Really Works (2012)
Lashinsky's observation reads as praise. It is actually a structural diagnosis. "Never any confusion" is an extraordinary claim about a company of 60,000 employees (at the time of writing) operating across hardware, software, services, and retail. In most organisations of that scale, confusion about ownership is the default state — a natural consequence of complexity, cross-functional dependencies, and the human tendency to distribute blame across group boundaries. Apple's achievement was not eliminating complexity. It was eliminating the ambiguity that complexity typically produces.
The phrase "the accountability is clear" encodes the DRI's deepest principle: clarity of ownership is not a cultural aspiration. It is a system design choice — a decision about how the organisation's accountability architecture will function, enforced through meeting structure, org charts, and the weekly discipline of putting one name next to every agenda item. The companies that achieve this clarity didn't get lucky with their culture. They built the architecture that makes clarity the default output.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
The DRI is Apple's most underappreciated organisational innovation. The company gets credit for product design, for the ecosystem, for retail strategy. It rarely gets credit for the accountability architecture that made all of those things possible. Every great Apple product was great because one person — not a committee, not a cross-functional team, not a consensus group — was singularly accountable for making it great. The iPhone had Scott Forstall for software and Tony Fadell for hardware. The App Store had Phil Schiller. Each DRI had the authority to match their accountability, which meant they could make trade-offs without convening a senate.
The model's simplicity is deceptive. Assigning a DRI takes five seconds. Making the system work takes years of cultural investment. The hardest part is not naming the person — it's giving them genuine authority and protecting that authority when other senior leaders disagree with their calls. At Apple, DRIs could make decisions that affected other teams' timelines. That authority was real, it was visible, and it was backed by Jobs personally. In most companies that attempt to copy the system, the DRI is named but the authority is withheld — and the result is a person who bears accountability for an outcome they cannot control.
The pattern I see in companies that scale successfully: they assign DRIs before they need them. The ten-person startup where everyone knows what everyone else is doing doesn't feel like it needs formal ownership assignments. But the muscle must be built before the strain arrives. Companies that wait until they have a hundred employees to introduce DRI culture discover that the committee habits formed during the first fifty are extraordinarily hard to break. Jobs didn't wait. He installed the DRI system at Apple when the company was in crisis and maintained it as the company grew to become the most valuable in the world.
The comparison to Amazon's single-threaded owner is instructive. Both systems concentrate accountability in one person. The difference is scope: Apple's DRI owns a deliverable within a functional structure. Amazon's single-threaded leader owns an entire business outcome with a dedicated team. Amazon's version is more autonomous — the single-threaded leader controls their team's resources and roadmap. Apple's version is more integrated — the DRI operates within the functional hierarchy, which means trade-offs between products are resolved at the functional leader level, producing the cross-product coherence that defines Apple's ecosystem. Neither system is superior. Both are precisely calibrated to the organisational model they serve.
An organisation that assigns a DRI but then requires them to get approval from three VPs, present to a steering committee, and achieve cross-functional alignment before acting has not created a DRI. It has created a meeting coordinator with an accountability label. The test is simple: can the DRI make a consequential decision — reallocate resources, cut a feature, delay a timeline — without convening a group? If yes, the DRI system is real. If no, it's theatre.
Section 10
Test Yourself
The DRI model is often confused with project management, delegation, or simple task assignment. The distinction is structural: a DRI owns the outcome and has the authority to make decisions about how to achieve it. A project manager coordinates activities. A delegate executes a task. A DRI is accountable for the result — which means they must control the levers that determine whether the result is good or bad.
Is the DRI model at work here?
Scenario 1
A SaaS company assigns a 'product owner' to each feature. The product owner writes specifications and tracks progress in Jira. When the feature ships late, the VP of Engineering tells the board: 'The product owner should have flagged the delay earlier.' The product owner responds: 'I flagged it in three Slack messages and two status reports. Engineering didn't prioritise it.' The VP and product owner spend the post-mortem attributing blame to each other.
Scenario 2
Apple's Monday executive meeting reviews the status of a new chip design. The agenda shows 'A15 Bionic — Johny Srouji.' Srouji reports that the chip is on track for the target power envelope but that thermal testing revealed a 3% performance shortfall under sustained load. He has already approved a transistor layout revision that will add two weeks to the schedule. No committee reviewed the revision decision. Jobs asks three questions, accepts the timeline change, and moves to the next agenda item.
Scenario 3
A startup forms a 'customer experience task force' with representatives from product, engineering, support, and marketing. The task force meets biweekly for six months. They produce a 40-page report with 23 recommendations. Eight months later, three recommendations have been partially implemented. Customer satisfaction scores are unchanged.
Section 11
Top Resources
The DRI model draws from organisational design, leadership theory, and the specific operational practices of companies that have implemented singular ownership at scale. The strongest foundation begins with the Apple-specific documentation, extends through Amazon's operational variant, and connects to the academic research on accountability and group dynamics that explains why the model works.
The most detailed published account of Apple's DRI system. Lashinsky documents how every agenda item in the Monday executive meeting had one named owner, how the DRI principle permeated from the executive level to individual feature teams, and how the system created the accountability architecture that distinguished Apple's execution from its competitors. Essential starting point for understanding the DRI in practice.
Amazon's single-threaded leader is the DRI's operational cousin. Bryar and Carr detail how Bezos assigned one person — with a dedicated team and full autonomy — to every consequential initiative. The book provides the operational mechanics: how single-threaded leaders were selected, how their authority was scoped, and how the model scaled from a handful of initiatives to thousands. Read alongside Lashinsky for the most complete picture of how two of the world's most effective companies implemented singular ownership at radically different scales.
Catmull's account of Pixar's creative process illustrates the DRI principle applied to filmmaking. The director has final creative authority — a DRI for every frame of the film. The Braintrust provides input without authority, preserving the separation between counsel and accountability that defines the DRI model. The book demonstrates that singular ownership works in creative contexts as effectively as in operational ones, and that the principle scales from a chip design to a feature film.
Grove's management classic articulates the principle that meetings must produce named owners for every action item — the procedural ancestor of the DRI. His framework for decision-making at Intel required that every strategic output have one person accountable for its execution. The chapter on decision-making is directly relevant to understanding how DRI architecture interacts with meeting structure, planning processes, and performance evaluation.
Willink and Babin provide the philosophical foundation for the DRI: the principle that the leader owns everything in their world. While the SEAL framework emphasises leader-level ownership, the DRI system operationalises the same principle at the initiative level. The book's treatment of "decentralised command" — pushing authority down to the lowest competent level — maps directly onto the DRI's requirement that authority must match accountability. The combination of Willink's philosophy and Apple's system produces the complete framework: own the outcome, delegate the process, and bear the consequence.
Leaders who apply this model
Playbooks and public thinking from people closely associated with this idea.
Directly Responsible Individual — How singular ownership eliminates diffusion, accelerates decisions, and creates unambiguous accountability chains.
The DRI is the direct structural antidote to diffusion of responsibility — the phenomenon where felt accountability decreases as group size increases. Diffusion says: the more people who share ownership, the less any individual feels obligated to act. The DRI says: exactly one person owns this, and no one else can assume the obligation is shared. The tension is fundamental and irreconcilable — the two models cannot coexist for the same outcome. An initiative either has a DRI or it has diffusion. There is no middle state. Organisations that declare "we all own quality" have chosen diffusion. Organisations that assign a named DRI for quality have chosen the antidote. The choice between the two determines whether the organisation's accountability architecture produces action or paralysis.
Tension
[Span of Control](/mental-models/span-of-control)
Span of control — the number of direct reports a leader can effectively manage — creates a natural tension with the DRI model. As an organisation grows, the number of initiatives that need DRIs grows with it. If every initiative requires executive-level DRI oversight, executives exceed their span of control and become bottlenecks. The resolution is hierarchical DRI assignment: senior leaders own outcomes, and they assign sub-DRIs for component deliverables. The VP of Product is the DRI for the product launch. Under them, a product manager is the DRI for the feature set, an engineering lead is the DRI for the backend, and a designer is the DRI for the interface. Each level preserves singular accountability within its scope while cascading the principle through the organisation.
Leads-to
[Two Pizza Rule](/mental-models/two-pizza-rule)
The DRI model leads naturally to small-team architecture. A DRI operating with a team of fifty faces coordination overhead that slows their execution to committee speed — negating the velocity advantage the DRI structure was designed to create. Bezos's two-pizza rule ensures that each DRI operates with a team small enough that communication overhead stays below the threshold where it degrades decision-making. The DRI provides singular accountability; the two-pizza rule provides the team architecture that makes the DRI's authority actionable. The combination — one person responsible, six people executing — is the organisational unit that Amazon used to scale from a bookstore to a $574 billion company.
Leads-to
[Disagree and Commit](/mental-models/disagree-and-commit)
The DRI model requires disagree and commit as its execution protocol. When one person has decision authority, the rest of the team must accept decisions they may not agree with — and execute them with full commitment. Without disagree and commit, the DRI model degrades: dissenters undermine the DRI's decisions through passive resistance, delayed execution, or end-runs to higher authority. With it, the DRI absorbs input, makes a call, and the team executes at full speed regardless of whether the decision matched their preference. Bezos formalised this pairing at Amazon: the single-threaded leader decides, and the team commits. The DRI provides the "who decides" structure. Disagree and commit provides the "what happens after" protocol.
The failure mode is always the same: DRI in name, committee in practice.
The DRI principle extends beyond product development. Every recurring business function — customer retention, security response, regulatory compliance, employer branding — can and should have a DRI. The functions that decay fastest in large organisations are the ones owned by everyone, which means they're owned by no one. "We all own the customer experience" is a sentiment, not a strategy. Naming one person who owns the NPS score, with authority over the initiatives that influence it and a weekly reporting cadence that makes progress visible, is a strategy. The difference is the name.
