Everyone is involved in the decision. But no one knows who actually decides.

This is one of the most common problems in project management.

A project can have a strong team, clear goals, and a well-planned roadmap and still slow down because decisions take too long. Meetings multiply, stakeholders give conflicting opinions, and important questions remain open because nobody is sure who has the final say.

The DACI Matrix is a simple decision-making framework that helps Project Managers create clarity around exactly this problem.

It answers four important questions:

Who drives the decision? Who makes the final decision? Who contributes expertise? And who simply needs to know the outcome?

What Is the DACI Matrix?

DACI is a decision-making framework that defines roles and responsibilities for important project decisions.

DACI stands for:

• D - Driver
• A - Approver
• C - Contributors
• I - Informed

Instead of allowing every stakeholder to participate equally in every decision, DACI establishes clear ownership.

The goal is not to exclude people from the process. The goal is to involve the right people at the right level.

D - Driver

The Driver is responsible for moving the decision forward.

This person coordinates the process, gathers information, communicates with stakeholders, organizes discussions when necessary, and makes sure the decision does not remain unresolved.

In many projects, the Project Manager may act as the Driver, but not always.

The Driver does not necessarily make the final decision.

Think of the Driver as the person asking:

“What do we need to do to get this decision made?”

Example

Imagine a software team needs to select a payment provider.

The Project Manager could be the Driver.

They might:

• identify the available options,
• collect technical and commercial information,
• involve relevant stakeholders,
• organize the decision meeting,
• document the recommendation,
• and track the final decision.

The PM drives the process but may not have authority to approve the provider.

A - Approver

The Approver is the person who has final decision authority.

This is the person who ultimately says:

“Yes, this is the option we are choosing.”

Ideally, there should be one clear Approver for a decision.

Why?

Because if three people all have final approval authority, you may not actually have clear decision ownership.

Depending on the decision, the Approver might be a:

• Product Manager,
• Department Head,
• CTO,
• Project Sponsor,
• Business Owner,
• or another senior stakeholder.

The Approver should consider the available information and contributors' input, but they remain accountable for making the final call.

C - Contributors

Contributors provide knowledge, analysis, recommendations, or expertise that helps the Driver and Approver make an informed decision.

They participate actively, but they do not have final decision authority.

For example, when selecting a payment provider, Contributors could include:

• developers assessing integration complexity,
• security specialists reviewing risks,
• finance evaluating fees,
• legal reviewing contractual requirements,
• and customer support considering operational impact.

Their input can significantly influence the decision.

However:

Being consulted does not mean having veto power.

This distinction is one of the most valuable parts of DACI.

I - Informed

The Informed group needs to know about the decision but does not need to participate in making it.

They receive the outcome and any relevant implications.

For example:

“We selected Provider B. Integration starts October 5, and the target release is November 10.”

The Informed group could include:

• other project teams,
• senior management,
• customer support,
• sales,
• operations,
• or external stakeholders.

Keeping people informed is important.

But inviting everyone into the decision-making process usually is not.

A Simple DACI Example

Imagine your team needs to decide whether to delay a product release because of a security issue.

Receive the final decision and understand its impact

Without DACI, you might have 10 people discussing whether the release should move forward.

With DACI, the process becomes clearer:

PM drives → experts contribute → Product Director decides → affected teams are informed.

DACI vs. RACI: What Is the Difference?

DACI and RACI are often confused, but they solve different problems.

RACI primarily helps clarify responsibility for work.

It defines who is:

• Responsible
• Accountable
• Consulted
• Informed

DACI focuses specifically on decisions.

It clarifies:

• who drives the decision,
• who approves it,
• who provides input,
• and who needs to know the result.

A simple way to remember the difference:

RACI = Who does the work?

DACI = Who decides?

A project can use both.

For example, you might use RACI to clarify responsibilities across a product launch and DACI for major decisions that arise during that launch.

When Should Project Managers Use DACI?

You do not need a DACI matrix for every small decision.

If a developer needs to choose the name of an internal variable, creating a DACI would probably create more bureaucracy than value.

DACI becomes useful when a decision:

• involves several teams or departments,
• has multiple stakeholders,
• has significant business impact,
• repeatedly gets stuck,
• involves conflicting opinions,
• requires specialist input,
• or has unclear decision authority.

Typical examples include:

Which vendor should we choose?

Should we delay the release?

Which feature should receive priority?

Should we change the project's scope?

Which technical solution should we implement?

Should we accept a particular project risk?

These decisions can affect scope, budget, timelines, customers, and business outcomes, so ownership of decisions matters.

The Biggest Mistake: Too Many Approvers

One of the easiest ways to slow down a project is to create a situation where everyone needs to agree.

Consensus can be valuable, but requiring universal agreement for every important decision can create a bottleneck.

Imagine this situation:

Engineering says Option A.

Product wants Option B.

Finance prefers Option C.

Operations doesn't like any of them.

Everyone keeps discussing the problem because nobody knows who can close the decision.

DACI changes the conversation.

The goal becomes:

Collect the right input → understand the trade-offs → let the designated decision-maker decide → move forward.

Not everyone needs to agree.

But everyone should understand how the decision will be made.

How to Create a DACI Matrix

A Project Manager can build a DACI matrix in a few simple steps.

1. Identify the decision

Be specific.

Instead of:

“Payment integration”

write:

“Which payment provider should we integrate for the first product release?”

The clearer the decision, the easier it is to assign roles.

2. Assign the Driver

Choose one person who will actively move the decision toward resolution.

3. Identify the Approver

Ask:

Who actually has the authority to make this decision?

Avoid assigning multiple Approvers unless the organization's governance genuinely requires it.

4. Select Contributors

Identify the people whose expertise is necessary.

Be selective.

Adding more Contributors does not automatically create a better decision.

5. Define who should be Informed

Think about who will be affected by the outcome or needs visibility into it.

6. Set a decision deadline

DACI defines ownership, but ownership alone does not guarantee speed.

Add a clear target:

Decision required by September 30.

Now the Driver has both responsibility and a timeline.

7. Document the final decision

Once the Approver makes the decision, document:

• what was decided,
• why it was selected,
• major trade-offs,
• relevant risks,
• who approved it,
• and when the decision was made.

This creates valuable project history and prevents teams from reopening the same discussion without new information.

DACI Is About Clarity, Not Control

A good Project Manager does not need to make every decision.

In fact, one of the most important PM skills is understanding which decisions you own and which decisions you facilitate.

Sometimes you are the Driver.

Sometimes you are a Contributor.

Sometimes you simply need to be Informed.

And sometimes you may also be the Approver.

What matters is that the team understands the difference.

When decision ownership is unclear, projects often experience delays, repeated meetings, stakeholder conflicts, and unnecessary escalation.

When ownership is clear, teams can spend less time asking:

“Who should decide this?”

and more time actually moving the project forward.

The next time an important project decision gets stuck, don't immediately schedule another meeting.

Ask four questions:

Who is driving this?

Who has the final approval?

Whose expertise do we actually need?

Who only needs to know the outcome?

That is the DACI Matrix.

And sometimes, four letters are enough to turn weeks of discussion into one clear decision.

👋 Hi, I’m Anzhela, a PMP-certified Project Manager. I make project management simple and help beginners build practical skills to start their PM journey. Want to learn with me? My live IT Project Management course takes you through the basics step by step, with real examples. DM me “PM” for course details 💬