DACIP is a decision-making framework that adds a fifth role to DACI: the Patron Advocate. DACI clarifies who drives, approves, contributes, and stays informed. Yet no role is accountable for speaking for the people a decision serves. As a result, a choice can follow the process perfectly and still fail its purpose.

The Patron Advocate fills that gap with evidence, not opinion. That evidence comes from sources like Jobs to Be Done interviews, usage data, and support patterns. Jeff Bezos famously left an empty chair for the customer. DACIP, by contrast, puts a person in it. In that sense, DACIP is the 5-Whos applied to decision-making.

The Patron Advocate can challenge a recommendation and request escalation. However, the Approver still decides. DACIP also scales with the stakes, from one quick question on routine choices to formal escalation rights on mission-critical ones.


DACIP at a Glance

DACIP, pronounced DAY-sip, keeps DACI’s four roles and adds a fifth, the Patron Advocate. Each answers a different Who.

RoleResponsibilityKey Action
DriverSteers the process, gathers information, and drives to a resolution on time.Coordinates stakeholders, frames options, and records the decision.
ApproverOne named person accountable for the final call and its outcome.Accepts or rejects the recommendation and explains why.
ContributorsSpecialists whose data, research, and perspectives shape the choice.Give input and challenge weak reasoning, without a vote.
InformedPeople affected by the outcome who do not help shape it.Receive the decision, its rationale, and what it means for them.
Patron AdvocateBrings evidence on customer Types and their jobs, so short-term internal goals don’t crowd them out.Writes a Patron Impact Statement and can trigger a Mission Breach Checkpoint.

Audio Dialog Overview of DACIP


Start with 5-Whos

Start with 5-Whys describes a practice of recursive curiosity. It takes the familiar 5 Whys in an entirely different direction. Rather than only tracing failures to root causes, the same inquiry can uncover the need beneath a request, a goal’s purpose, or a reaction’s meaning. It can also test whether a decision still serves its purpose.

Curiosity can travel outward, too. Start with 5-Whys describes five directions it can take: Whys, Whos, Types, Ways, and Hows. In other words, Whys take us deeper. Whos, on the other hand, take us broader by asking who else might matter.

5-Whos resists stakeholder blindness. That is the tendency to frame a choice around the most visible people while overlooking others. Notably, five is a rhythm rather than a count. The question is never finished. It simply invites us to look beyond whoever first comes to mind.

DACIP is what happens when we aim that question at decision-making itself. DACI already names four Whos that most teams can see. 5-Whos asks who else belongs in the decision. Very often, the answer is the Patron.


DACI: The Four Whos Teams Choose

DACI is commonly attributed to Intuit, where I recall first encountering it. It was later popularized by Atlassian’s Team Playbook. Essentially, it assigns four roles to any significant decision. The Driver moves it forward, and the Approver makes the final call. Meanwhile, Contributors supply expertise, and the Informed learn the outcome.

Its strength is clarity. Above all, DACI favors one named Approver, which keeps decisions from stalling in committee or devolving into a vote. As a result, teams spend less time arguing about who decides and more time deciding.

Yet DACI is silent about one thing. For instance, it never asks anyone to represent the people a decision serves outside the room. Customer insight may arrive through a Contributor, but only if someone thinks to invite it. When speaking for customers is everyone’s job, it can quietly become no one’s.


The Empty Chair Problem

Jeff Bezos's empty chair principle illustrates customer obsession and why DACIP gives customers an evidence-based advocate in organizational decisions.
Jeff Bezos’s empty chair represented the absent customer. DACIP builds on that principle by introducing a Patron Advocate who brings evidence about customer needs into decisions.

Amazon offers a famous response to that gap. Bill Price was an early Amazon customer service executive. According to his account, Jeff Bezos once left a chair empty in an executive meeting. The chair was for the customer, who could never attend. Over time, the empty chair became a widely repeated symbol of customer obsession.

Clearly, the symbol works because it names the problem. When decisions get made, the customer is rarely in the building, the room, or the chair.

Still, a symbol has limits. Some observers note that an empty chair can simply reflect the room’s own assumptions. Participants may imagine the customer values exactly what they already value.

DACIP puts a real person in that chair. Even so, a filled chair carries the same risk if its occupant offers only opinions. That is why the Patron Advocate’s voice rests on evidence rather than on claiming to speak for customers. For a closer look at both sides, see the Amazon case studies on this page.

At the same time, the chair raises a 5-Whos question. Who else deserves a seat? Beyond paying customers, a decision may affect students, patients, donors, partners, or whole communities.


Where DACIP Comes From

Riding the Train at Intuit

At Intuit, as I remember it, DACI brought welcome clarity about who decides. Yet the customer’s voice reached us through a different path, a daily practice Intuit explicitly called “Riding the Train.” Each morning, every employee was asked to pick up the desk phone and dial an extension. It dropped us, as silent listeners, into the next customer support call.

Like overhearing strangers on a commuter train, we heard lives and struggles quite different from our own. Above all, we heard what was getting in the way of the job each customer was trying to do. That habit turned Intuit’s customer empathy into a daily practice for everyone, not just product managers or researchers. After all, hearing a customer struggle firsthand is far more powerful than reading a summarized report. Fittingly, Intuit co-founder Scott Cook later co-authored Marketing Malpractice with Clayton Christensen and Taddy Hall. Published in Harvard Business Review in December 2005, it explores the jobs customers hire products to do.

Riding the Train had a limit, though. Many mornings, I landed on a call about a forgotten password. Hearing it again and again showed how many customers a better reset process could help, and it led to real improvements. After a while, however, each repeat taught us less. Random listening reveals what is common. Rarely does it reveal what is rare but blocking.

Monday Listening Sessions at Prosper

Later, at Prosper Marketplace, where I led engineering, we tried a different approach. Support agents already asked customers for permission to record calls. So we asked agents to flag recordings that seemed especially telling. Some were great examples of a common problem. Others were outliers, where something completely blocked a customer.

Each week, the head of support chose five of those recordings. On Mondays, the heads of support, design, product, and engineering listened to them together. Everyone else was welcomed and encouraged to join. Afterward, we discussed what we heard and what it meant.

Occasionally, we included a call in which a customer praised a feature. Such calls were rare, since few customers phone in to say thank you. That rarity made them valuable. They showed us what to protect, not only what to fix.

Prosper also invited borrowers to share short videos through its #MyProsperStory contest. In them, customers described how a loan changed their lives. Some escaped credit card debt. Others helped a child through college or paid for a parent’s medical procedure. Because entries competed for prizes, the stories were self-selected. Even so, they connected everyone to why the work mattered.

When Everyone Owns the Chair

At Prosper, keeping customers in mind was considered everyone’s responsibility. I still agree with that. Yet I also saw how closely it resembles the empty chair. Everyone can see the chair, but no one in particular feels responsible for filling it with facts. Even when a Product Owner carries that responsibility, naming it explicitly in the decision still adds value.

The same is true of every DACI role. In theory, it should be obvious who drives and who approves. In practice, teams name those roles anyway, because explicit roles hold up under pressure. The Patron Advocate deserves that same clarity. DACIP gives the evidence these rituals surfaced, from common problems to rare blockers to moments of praise, a named seat in the decision itself.


The Five Roles of DACIP

DACIP decision-making framework adds a Patron Advocate to DACI’s Driver, Approver, Contributors, and Informed roles.
DACIP applies the 5-Whos to decision-making, adding a Patron Advocate who brings evidence about the people a decision serves.

DACIP describes five responsibilities, not necessarily five people. On smaller decisions, one person may hold more than one role. For consequential choices, though, keeping certain roles separate is often worth the effort.

D: Driver, the Runner

The Driver moves the decision forward. They define what needs deciding, why it matters, and by when. Next, the Driver gathers options, engages Contributors and the Patron Advocate, and presents a recommendation. Afterward, they record the decision and coordinate follow-through. In short, they own the momentum and quality of the process, but not necessarily the final call.

A: Approver, the Signer

The Approver makes the decision and owns the outcome. To do so, they weigh the Driver’s analysis, Contributor expertise, and the Patron Advocate’s assessment. Then they decide within an agreed timeframe and explain the rationale. One clearly named Approver keeps accountability from blurring.

Importantly, the Approver may still accept a tradeoff that affects customers. DACIP does not forbid compromise. Instead, it makes the compromise visible and deliberate.

C: Contributors, the Experts

Contributors bring knowledge from engineering, finance, legal, operations, support, or other domains. In addition, they surface risks, constraints, and likely consequences. Equally, they challenge weak reasoning and overlooked options. Their influence is real, yet the decision is not a committee vote.

Expertise also has a blind spot. A team can hold deep technical and financial knowledge while understanding surprisingly little about how a choice affects its users.

I: Informed, the Audience

Informed stakeholders need to know what was decided, why, and what it means for them. Often, they implement the decision or adjust related work. Still, not everyone who needs to know must help decide. That distinction keeps decisions efficient, and it spares the people who live with them from surprises.

P: Patron Advocate, the Mission Anchor

Patrick, the Patron Saint of Customers, represents the DACIP Patron Advocate who brings customer evidence and Jobs to Be Done into organizational decision-making.
Meet Patrick, the Patron Saint of Customers. In DACIP’s 5-Whos decision-making framework, the Patron Advocate ensures that customer Types, Jobs to Be Done, and organizational mission have a meaningful voice in consequential decisions.

The Patron Advocate represents the people the organization exists to serve. Depending on the organization, Patrons may be customers, users, students, patients, donors, or communities. Above all, the role keeps their needs visible. It also asks whether a choice stays connected to the organization’s Shared-Core-Why. In that sense, the Patron Advocate speaks not only for customers but for the relationship between Patrons and purpose.

There is a playful way to remember the role. Think of the P as the Patron Saint of Customers. Of course, no sainthood is required. In fact, the role works best when its holder is humble enough to follow the evidence.

In practice, the Patron Advocate asks what customer problem a decision solves. Often, the evidence confirms that a proposal serves customers well, and saying so strengthens the decision. Challenge is the exception, reserved for concerns that remain unresolved. They also surface friction, unintended consequences, and overlooked customer Types. When a material concern remains unresolved, they can request reconsideration or escalation before approval.


Why Not the Product Owner or a Contributor?

A fair question follows. Doesn’t the Product Owner already represent customers? In many organizations, they are well placed to do so. Yet DACI never calls them into a decision in that role.

In practice, the Product Owner often serves as the Driver. As a result, they own the roadmap, the timeline, and the pressure to ship. Consequently, customer advocacy competes with momentum inside one person’s head. DACI separates the Driver from the Approver for a similar reason.

A Product Owner can absolutely serve as the Patron Advocate. On consequential decisions, however, it helps to ask whether they are also driving. If so, someone else may need to take the chair.

Similarly, a customer researcher could join as a Contributor. However, the difference lies in responsibility. Contributors offer perspective when invited. By contrast, the Patron Advocate is accountable for making customer impact visible and holds a defined right to challenge.


How the Patron Advocate Operates

DACIP comic: a team follows DACI, senses a gap, and a Patron Advocate brings customer evidence before the Approver makes a clearer decision.
DACI clarifies who decides. DACIP adds a Patron Advocate who brings customer evidence into the decision, so the Approver can weigh tradeoffs deliberately rather than by accident.

A role without real influence can quickly become ceremonial. Two practices help give the Patron Advocate substance.

The Patron Impact Statement

For consequential decisions, the Driver and Patron Advocate can write a brief impact statement. It might answer questions such as these:

  • Which customer Types and Jobs to Be Done does this decision affect?
  • How will each Type experience the change?
  • What friction, compromise, or unintended consequence might it introduce?
  • How does the choice connect to our Shared-Core-Why?
  • What evidence supports our assumptions, and what remains uncertain?

Sometimes a few sentences are enough. Either way, the value lies in making the customer perspective explicit before approval, not after launch.

The Mission Breach Checkpoint

Occasionally, a proposal creates serious tension with the organization’s purpose. For example, a change might cut costs while eroding accessibility, reliability, or trust. In such cases, the Patron Advocate can formally challenge the recommendation and request reconsideration or escalation.

This is not a second Approver or an unlimited veto. Instead, the organization agrees in advance on when concerns warrant review and who resolves disagreements. By default, the Approver decides, and the Patron Advocate’s concern is recorded alongside the decision. Even so, accepting a material mission compromise becomes a conscious choice rather than an overlooked consequence.


Patrons, Personas, and Jobs to Be Done

Customers are rarely one homogeneous group. For that reason, the Patron Advocate draws on 5-Types, another direction in Start with 5-Whys. It asks which meaningful differences might hide inside a single category.

Jobs to Be Done offers a shared language for those differences. Clayton Christensen and his colleagues describe a job as the progress someone seeks in a particular circumstance. For example, personas describe who customers are. Jobs, on the other hand, describe what they are trying to accomplish. Two customers who look identical on a persona card, say busy parents in their forties, may hire the same tax software for different jobs. One wants to finish fast. The other wants certainty that nothing was missed. Since one person can hold different jobs at different moments, the advocate represents jobs across Types, not just personas.

Representing every Type does not mean averaging them. When two Types’ jobs conflict, the Patron Advocate keeps that difference visible. It can show how many people each choice affects, how severely, and how reversibly. The Approver can then choose deliberately rather than by accident.

When Patrons Come in Several Groups

Some organizations serve more than one group of Patrons at once. Consider a nonprofit that connects teachers, individual donors, and corporate partners. Each group is a Patron in its own right, with its own jobs to be done. Teachers may hire the platform to get classroom resources quickly. Donors may hire it to see their gift make a visible difference. Partners, meanwhile, may hire it to advance their own giving priorities.

Moreover, 5-Types applies within each group, not only across them. A first-year teacher and a veteran teacher may be trying to get very different jobs done. Likewise, a first-time donor and a monthly donor may want different things from the same page. As a result, the Patron Advocate may need to hold Types at two levels.

Conflicts can appear at either level. For example, a partner might fund a match limited to certain subjects. That match serves the partner’s priorities and may draw more donors. Yet it may also steer donors away from teachers whose projects fall outside those subjects. In that case, the Patron Advocate does not pick a winner. Instead, they make the trade-off visible for each group and Type it touches. The Approver can then decide with every Patron in view.

Evidence matters here. In particular, JTBD interviews reveal why people choose what they do. Usage data, support patterns, and direct observation show how widely those patterns hold. Together, they let the advocate speak with grounded confidence.

The role also holds two responsibilities that can diverge. Serving today’s customers and staying true to the mission usually align, but not always. Likewise, a decision can affect people who are not Patrons at all. Naming these tensions openly is part of the work.


When the Numbers Look Good

Dashboards can make a decision look obviously right. Yet averages and proxy metrics can hide exactly what a Patron Advocate is there to notice. The examples below are hypothetical, but each rests on a pattern many teams will recognize.

Hypothetical: The Shipping Savings

Imagine a company that rents DVDs by mail while racing to build a streaming service. One day, an engineer finds a cheaper shipping method that cuts shipping costs by 10%. It needs little engineering work, and average delivery time barely changes. On the dashboard, it looks like an easy win.

A Patron Advocate would look past the average. Suppose the slower deliveries fall mostly on rural customers. Many of them have poor broadband, so discs remain their only option. Urban customers, already moving to streaming, hardly notice. As a result, the savings come almost entirely from the customers least able to switch.

The project also pulls some attention away from streaming, the future most customers are moving toward. On its own, each such win looks reasonable. Over time, though, many near-term wins can add up to death by a thousand cuts. The Patron Advocate keeps those hidden costs visible, so the Approver can weigh them deliberately.

A Real Counterexample: Blockbuster’s Late Fees

Blockbuster offers a documented case of near-term revenue working against customers. According to the Associated Press, late fees brought in nearly $800 million in 2000, about 16 percent of its revenue. Those fees could double or triple the cost of a rental. Netflix’s flat-fee model tapped into that customer anger.

Blockbuster later fought back with Total Access, which let online subscribers return DVDs to its stores. However, CNBC reports that each in-store exchange lost money, and board members installed by activist investor Carl Icahn opposed the strategy. Under a new CEO, the company even reinstated its unpopular late fees in its stores in 2010. That same year, Blockbuster filed for bankruptcy.

Many forces shaped Blockbuster’s decline, and no single decision explains it. Still, its late fees show how revenue a business relies on can erode the trust it relies on even more. A Patron Advocate could have kept that tension in front of every Approver.

Hypothetical: The Engagement That Wasn’t

Now imagine a mobile app for hikers that measures success by engagement: time in the app and screens visited. Over a year, the team ships a series of improvements. It moves popular features to places it believes are better. It also adds new features it believes customers will love. With each release, engagement rises.

Yet some of that engagement may be friction. Customers spend more time because familiar features have moved. They tap through new screens to reach what they have always done. Long-time users lose the muscle memory of where things live, while new users face a more cluttered first experience. At a trailhead with a weak signal, a hard-to-find map is more than an annoyance.

Interviews with new and existing customers could reveal growing frustration that the dashboard reads as success. Each frustration may be one more straw on the camel’s back. Eventually, customers leave, and a damaged reputation can be very hard to rebuild.

Jobs to Be Done gives the Patron Advocate a sharper question. A hiking app’s job is to get people onto the trail. By that measure, success might even mean less time in the app. When a metric drifts from the customer’s job, the Patron Advocate can ask what it really measures.


DACIP and OKRs: Measuring What Matters

Objectives and key results, or OKRs, and key performance indicators, or KPIs, give teams focus. John Doerr’s book and TED talk on OKRs share a telling title: Measure What Matters. Yet in that talk, Doerr warns that many organizations “set objectives and meet them,” while they “lack a sense of purpose to inspire their teams.” We can master the measures and still lose sight of what matters. His answer is to first ask Why. In his central example, Jini Kim bet her 15-person company, Nuna, on building a Medicaid database, because she knew firsthand whom it would serve.

DACIP helps inform Doerr’s Why. A mission’s why depends on whom we do the work for. That why is best informed by the people we serve, or those who speak for them, rather than by assumptions about what is best for them. The Patron Advocate’s role is to understand that why from the customer’s perspective and bring it into the room. It keeps Doerr’s Why grounded in real people, with evidence.

Key results and KPIs are proxies for value to the people we serve. As Jeff Bezos put it in his 2016 shareholder letter, “As companies get larger and more complex, there’s a tendency to manage to proxies.” A Patron Advocate keeps asking whether each proxy still reflects the customer’s job.

Setting Objectives With a Patron Advocate

When teams set OKRs, a Patron Advocate might ask two questions. First, whom does this objective serve, and what job does it help them do? Second, does at least one key result measure that outcome directly, rather than a stand-in for it?

Internal objectives, such as test coverage or cycle time, rarely name a customer. Yet when we keep asking Why, they climb to the people they ultimately serve. Test coverage for a checkout flow, for example, protects the customers who rely on that flow.

Pairing Every Proxy

Andy Grove, who brought OKRs to Intel, advised “pairing indicators, so that together both effect and counter-effect are measured.” The Patron Advocate naturally owns the customer side of each pair. An engagement goal might pair with tasks customers complete. Likewise, a cost-savings goal might pair with the delivery experience of the customers who absorb the savings.

When Key Results and Customers Diverge

Sometimes a key result stays on track while the Patron Advocate’s evidence shows customers losing ground. That divergence is exactly when a Mission Breach Checkpoint helps. The owner still decides, and the Patron Advocate holds no veto. Still, the gap becomes visible instead of being celebrated on a dashboard.

None of this requires a new role in every OKR. One customer-outcome key result or guardrail per objective, plus a Patron check at each quarterly review, keeps the measures in service of what matters.

The Pandora Lesson: Opinions by Vote, Evidence by Advocate

In Start with 5-Whys, I discuss Marty Cagan’s account of a period at Pandora. As I summarize it there, the team often chose its next steps by vote. Each step seemed reasonable, yet together the steps did not compound toward a coherent outcome.

We should not assume Pandora used DACI or that DACIP would have changed its path. Still, the story illustrates two gaps that DACIP addresses.

First, a vote aggregates opinions. A single Approver, accountable to a clear direction, replaces that diffusion with ownership. Second, opinions about customers are not evidence about customers. A Patron Advocate equipped with JTBD insight can ask whether each step serves the people the product exists for.

Neither safeguard guarantees a better decision. Together, though, they make drift easier to notice before it hardens into a pattern. After all, a decision can follow the process correctly and still be wrong for the purpose.


Applying DACIP Without Adding Bureaucracy

Frameworks can grow until following them matters more than deciding well. Therefore, DACIP should avoid that trap. The right level of rigor depends on stakes, uncertainty, and reversibility.

Routine Decisions

For small, reversible choices, the Patron perspective may simply be a question. Does this serve the people we are trying to help? No extra meeting or document is required.

Consequential Decisions

When choices involve real tradeoffs, customer impact, or significant investment, name a Patron Advocate. In most cases, a short impact statement provides enough structure.

Mission-Critical Decisions

Some decisions could reshape the customer experience, erode trust, or change direction. Here, a formally designated Patron Advocate and agreed escalation rights are worth the effort. It also helps to note what evidence would justify revisiting the decision.

These are examples, not mandatory categories. The goal is to keep the fifth Who present without slowing every decision.


How DACIP Compares with Other Decision Frameworks

DACIP is one of many ways teams clarify decisions. Most well-known frameworks answer who decides, who acts, or how much rigor a choice deserves. Few assign anyone to bring evidence about the people a decision serves. The table compares several frameworks in common use.

FrameworkMain question it answersWhere the customer’s voice lives
RACIWho does the work, and who is accountable for it?Nowhere by design
DACIWho drives, approves, contributes, and stays informed?Only if someone invites it, often through a Contributor
RAPID (Bain)Who recommends, who must agree, and who decides?Through Input. The Agree role must sign off, usually for legal, regulatory, or other specialized concerns.
DRI (Apple)Which single person owns the outcome?In that person’s judgment
One-way and two-way doors (Amazon)How much rigor does this decision deserve?Not addressed directly
PR/FAQ, or Working Backwards (Amazon)Is this worth building for customers?In the document itself
Advice process (Dennis Bakke, AES)Whom must the decider consult?With those affected, if they are asked
Devil’s advocate or red teamHas anyone tested this argument?Only if that is the lens chosen
DACIPWho decides, and who brings evidence about whom it serves?In a named role, without a veto

Customer-centered methods also exist outside decision roles. Six Sigma’s Voice of the Customer, Quality Function Deployment, design thinking, and Jobs to Be Done all generate evidence about customer needs. DACIP does not replace them. Instead, it gives the evidence they produce a named seat when the decision is made.

The Patron Advocate in Other Frameworks

The Patron Advocate also need not stay within DACI. Teams that use RAPID, RACI, or a single DRI could add the role on its own, without renaming their framework.

FrameworkWhere the Patron Advocate fits
RAPIDHeard before the recommendation reaches the Decider, like the Agree role, but without the power to block it
RACIA distinct role for decisions within the matrix. Unlike someone Consulted, the advocate is accountable for bringing customer evidence.
DRIThe single owner names a Patron Advocate to hear from before consequential calls, keeping ownership with one person (see the DRI + Patron Advocate one-pager)
One-way and two-way doorsSets how formal the role should be: one quick question for a two-way door, a named advocate and impact statement for a one-way door

Frequently Asked Questions About DACIP

What is DACIP?

DACIP, pronounced “DAY-sip,” is a decision-making framework that extends DACI with a fifth role. The letters stand for Driver, Approver, Contributors, Informed, and Patron Advocate.

Who developed DACIP?

Chris Dolezalek (CD) developed DACIP as part of his Talent Whisperers coaching and leadership ecosystem. It builds on DACI, which he recalls first encountering at Intuit, and on customer-listening practices he helped implement at Prosper Marketplace. DACIP applies the 5-Whos from Start with 5-Whys to decision-making.

How is DACIP different from DACI?

DACI clarifies decision rights. In contrast, DACIP keeps those rights and adds explicit, evidence-based advocacy for customers and mission.

How does DACIP compare with RACI?

RACI usually assigns responsibility for tasks and deliverables. By comparison, DACI and DACIP focus on who makes and shapes specific decisions. For a broader view, see how DACIP compares with other decision frameworks.

Is the Patron Advocate a veto?

No. The advocate can challenge and escalate material concerns. Nevertheless, the Approver keeps final accountability.

Is the Patron Advocate a devil’s advocate?

No. A devil’s advocate challenges by design. The Patron Advocate represents the people a decision serves, so their evidence may just as easily support a proposal as question it. Their intent is to solve for the customer, not to oppose the decision.

Who should be the Patron Advocate?

Ideally, someone with credible evidence about customer Types and their jobs. A Product Owner, researcher, or support leader may fit, especially when they are not also driving the decision.

What are the 5-Whos?

5-Whos is a practice of asking who else might matter in a situation. DACIP applies it to decision-making by adding a Patron Advocate, who brings evidence about the people a decision serves into the room.


Case Studies: Two Sides of Amazon’s Empty Chair

Amazon offers a rare chance to see both sides of the empty chair. Its best-known customer-serving decisions come from Jeff Bezos’s own shareholder letters. Meanwhile, one of its costliest controversies involved how customers were kept as subscribers. Together, they show what a 5-Whys chain looks like when it reaches the mission, and when it breaks.

Amazon empty-chair 5-Whys comparison: an instant-order warning protects customer trust, while alleged Prime cancellation friction illustrates mission drift and DACIP's role.
Two sides of Amazon’s empty chair: a customer-protecting purchase warning and the FTC’s allegations about Prime cancellation friction. The contrasting 5-Whys chains illustrate how DACIP’s Patron Advocate can challenge decisions that lose sight of customer needs and organizational mission.

First, a note on evidence. The positive examples are largely self-reported, written partly to shape how Amazon is seen. By contrast, the counterexample rests on allegations that Amazon settled without admitting wrongdoing. Neither side makes Amazon a hero or a villain. Instead, each illustrates a pattern worth recognizing in any organization.

Case Study 1: Warning Customers They Already Own It

In his 2003 letter to shareholders, Bezos described a feature called Instant Order Update. It warns customers when they are about to buy something they already own. Amazon measured the feature and found it slightly reduced sales. Even so, Amazon kept it, calling it good for customers and, over time, for shareholders.

A 5-Whys chain shows why the choice holds:

  1. Why warn customers they already own it? To prevent accidental duplicate purchases.
  2. Why does that matter? A duplicate wastes the customer’s money and creates a return hassle.
  3. Why accept a measurable drop in sales? Amazon’s value lies in helping customers decide well, not in any single sale.
  4. Why does helping them decide matter? Trust brings customers back, and that loyalty compounds over time.
  5. Why is trust the goal? Because Amazon says serving customers is how it creates lasting value.

The chain reaches the mission. Notably, the decision cost something measurable, which makes the commitment credible.

Case Study 2: Publishing Negative Reviews

Amazon let customers post product reviews from its early days. According to the same 2003 letter, vendors complained that this made no sense for a seller. Bezos acknowledged that negative reviews cost some sales in the short term. However, he argued that helping customers choose well pays off.

In one interview, Bezos recalled a publisher urging Amazon to post only positive reviews. He declined. As he put it, “We make money when we help someone make a purchase decision.”

The 5-Whys chain lands in the same place as the first case. Why publish reviews that hurt sales? Honest reviews help customers decide. And why does that matter? Amazon sees helping customers decide, not each transaction, as its real job.

Case Study 3: Refunds Customers Never Asked For

According to Bloomberg’s report on Bezos’s 2012 shareholder letter, Amazon built two automatic refund systems. One refunds customers who paid more than the lowest available price. The other refunds customers when streaming video plays poorly. In both cases, customers receive the refund without asking.

Here, the Why is visible in the design itself. A business optimizing only for revenue would wait for complaints. By contrast, a business optimizing for trust looks for problems customers may never notice.

Case Study 4: The Prime “Iliad”

In 2023, the U.S. Federal Trade Commission sued Amazon over Prime enrollment and cancellation. It alleged confusing sign-up flows and a deliberately long cancellation process. According to the FTC, Amazon internally called that process the “Iliad,” after Homer’s epic poem. The agency also cited internal documents in which employees called unwanted subscriptions “an unspoken cancer.”

In September 2025, Amazon settled for $2.5 billion. That total included a $1 billion civil penalty and $1.5 billion in customer refunds. Amazon admitted no wrongdoing and said it had always followed the law. These remain allegations, not findings.

If the allegations are accurate, a 5-Whys chain shows where the reasoning breaks:

  1. Why make cancellation harder? To reduce churn.
  2. Why reduce churn? To protect membership numbers and revenue targets.
  3. Why do membership numbers matter? They are meant to show that customers value Prime.
  4. Does retention through friction show that customers value Prime? No. Instead, the metric now measures difficulty, not loyalty.
  5. Can the choice be traced back to the mission? It cannot.

That broken link is the signal described in Start with 5-Whys. A choice that cannot connect to what matters deserves curiosity. So does a metric that no longer measures what it was meant to.

What These Cases Teach About DACIP

Amazon is famous for the empty chair. Yet, by the FTC’s account, evidence of customer harm was already inside the building. What appears to have been missing was a role with standing to bring that evidence before an Approver.

That is exactly the gap DACIP addresses. A Patron Advocate could have drawn on cancellation complaints and employee concerns. Likewise, a Mission Breach Checkpoint could have forced an explicit choice about the tradeoff. We cannot know whether that would have changed the outcome. Still, the case shows why a symbol alone is not enough.

Meanwhile, the first three cases show the role’s positive side. In each, someone asked what served the customer and accepted a measurable cost. A Patron Advocate makes that question a responsibility rather than a matter of culture or luck.

Slide Deck – DACIP: Beyond the Empty Chair


Who Is in Your Patron’s Chair?

Knowing who makes a decision is not the same as remembering whom it serves. Sometimes the most important person in a decision is the one who isn’t in the room.

DACIP is itself a hypothesis, held lightly. No evidence I know of yet shows that a fifth role improves outcomes. Where customer obsession is already deeply lived, it may even prove redundant. That is why it deserves testing, perhaps through a learning loop like THRIVE, rather than adoption on faith.

So here is a small experiment for your next consequential decision. Before approval, ask who is sitting in the Patron’s chair. Then ask what evidence they brought with them. If you try it, I would love to hear what you notice.

To make that easier, bring the one-page DACIP guide to your next consequential decision.

DACIP 5-Whos decision-making framework: Driver, Approver, Contributors, Informed, and Patron Advocate, with responsibilities and mission alignment.
DACIP extends DACI with a fifth role, the Patron Advocate. This one-page guide explains all five decision-making responsibilities and how customer evidence, Jobs to Be Done, and mission alignment inform better decisions.

Glossary of Terms

5-Types

5-Types asks which meaningful differences might hide inside a category like customers. Types can reflect people, situations, or Jobs to Be Done. In DACIP, they help the Patron Advocate avoid treating all customers as alike.

5-Whos

5-Whos is a direction of curiosity from Start with 5-Whys that asks who else might matter. It resists stakeholder blindness. DACIP applies it to decision-making by adding the Patron Advocate.

DACI

DACI is a decision-making framework with four roles: Driver, Approver, Contributors, and Informed. It is commonly attributed to Intuit and was popularized by Atlassian.

DACIP

DACIP, pronounced DAY-sip, extends DACI with a fifth role, the Patron Advocate. It keeps DACI’s decision clarity while making customer and mission advocacy an explicit responsibility.

Jobs to Be Done (JTBD)

Jobs to Be Done describes the progress a person seeks in a particular circumstance. In DACIP, jobs give the Patron Advocate a shared, evidence-friendly language for customer needs.

Mission Breach Checkpoint

The Mission Breach Checkpoint is a defined right for the Patron Advocate to challenge a recommendation. It applies when a decision creates serious tension with the organization’s purpose. The Approver still decides.

Patron Advocate

The Patron Advocate represents the people an organization exists to serve. They bring evidence about customer Types and their jobs into decisions. Informally, they are the Patron Saint of Customers.

Patron Impact Statement

A Patron Impact Statement is a brief assessment of how a decision affects customer Types and their jobs. It also notes how the choice connects to the Shared-Core-Why and what remains uncertain.

Shared-Core-Why

Shared-Core-Why is a group’s evolving understanding of why it exists and what it hopes to contribute. In DACIP, the Patron Advocate checks decisions against it.


See Also

Start with 5-Whys: From Root Cause to Root Meaning

This is the parent page for the 5-Whos idea behind DACIP. It explains how 5-Whys can reach beyond root-cause analysis toward needs, priorities, and purpose. You will also find the five directions of curiosity: Whys, Whos, Types, Ways, and Hows. Its sections on Shared-Core-Why and drift give the Patron Advocate’s mission role deeper context. The page also includes the Pandora story referenced here.

THRIVE

THRIVE is a Talent Whisperers learning loop for turning intentions into tested experience. A DACIP decision is, in many ways, a hypothesis about what will serve Patrons. THRIVE offers a way to test that hypothesis and learn from what actually happens. It can also help a Patron Advocate decide when evidence justifies revisiting a decision.

DACI Decision-Making Framework, Atlassian Team Playbook

Atlassian’s play is one of the most widely used guides to DACI. It explains each of the four roles and how to run a DACI session. You will also find templates for documenting decisions. Reading it alongside this page shows exactly where the Patron Advocate fits.

Three Powerful Ideas From a Former Amazon Exec, Shep Hyken

Shep Hyken interviews Bill Price, an early Amazon customer service leader. Price confirms that he attended the first meeting where Jeff Bezos left a chair empty for the customer. The article also explores Price’s idea that the best service is no service. It offers firsthand context for the empty chair that DACIP turns into a role.

Why You Need an Empty Chair at Important Meetings, Cultural Intelligence Center

This article examines what makes the empty chair practice work and where it falls short. It argues that participants need perspective-taking skills to imagine what customers actually value. Without those skills, the chair may only echo the room’s assumptions. That caution reinforces why the Patron Advocate relies on evidence.

Know Your Customers’ “Jobs to Be Done,” Harvard Business Review

Clayton Christensen and his co-authors introduce Jobs to Be Done to a broad business audience. They argue that circumstances explain customer choices better than demographics do. The article also highlights the social and emotional dimensions of jobs. It provides the vocabulary a Patron Advocate can use to describe customer Types.

Product Strategy: Focus, Silicon Valley Product Group

Marty Cagan writes about why product strategy depends on focus. He treats strategy as deciding what not to do. That discipline complements DACIP’s single Approver and Mission Anchor. Together, they help keep a sequence of decisions pointed toward a coherent outcome.

Amazon 2003 Letter to Shareholders, U.S. Securities and Exchange Commission

This is Jeff Bezos’s own account of several customer-first decisions, filed with the SEC. It describes Instant Order Update, which Amazon kept despite measurably lower sales. Bezos also explains why Amazon published negative reviews that cost short-term sales. Reading it in full shows how Bezos connected these choices to long-term value. It is the primary source behind two of this page’s case studies.

Amazon Reaches $2.5 Billion Settlement over FTC’s Prime Lawsuit, Axios

Axios reports on the September 2025 settlement of the FTC’s Prime case. It covers the civil penalty, the customer refunds, and Amazon’s response. The article also notes that Amazon admitted no wrongdoing. It offers useful context for the Prime “Iliad” case study and its limits as evidence.

Appendix: DRI + Patron Advocate One-Pager

Many teams already rely on a directly responsible individual, or DRI, to own each outcome. They need not switch frameworks to bring in the voice of the people they serve. This one-page guide shows how a DRI can add a Patron Advocate while ownership stays with one person. It also scales the role to the stakes, from a single question on reversible decisions to a Patron Impact Statement on one-way doors. You might download the PDF to share with your team.

DRI plus Patron Advocate: adding the customer’s voice to the directly responsible individual model, part of the DACIP decision-making framework.
A DRI keeps one owner for every outcome. Adding a Patron Advocate brings evidence about the people a decision serves, with rigor scaled to the stakes and no veto.