DACI Framework: a Tool For Group Decisions
The scenario will be something like 一 you have a new project, you and your team have the kickoff meeting, everyone is excited, but after the kickoff meeting no one takes action because they’re unclear of what they’re supposed to do and who is the driver.
After multiple meetings, the team members understand a little bit more of what they’re supposed to do, but after a while you and your team can’t get a consensus.
This scenario is super common, and one of the main reasons this happens is because the team is unclear on who is the project driver or who is responsible for giving actionable feedback or approving it.
What is DACI?
DACI is a framework used to make decisions that involve multiple team members and stakeholders, are complex, and/or have a huge impact on customers.
The DACI framework can help you and your team make decisions efficiently because each team member will have a clear vision of their roles, responsibilities, and expectations.
DACI is nothing more than a structure for group decision making. This sounds amazing, right? I do need to mention this framework will only work if you and your team follow their roles and responsibilities.
What does DACI mean?
- D (driver): The person responsible for managing the team and guaranteeing that everything will get done. Essentially the driver is responsible for coordinating the entire process with the cross-functional team and making sure the decision is made by the agreed timeframe.
- A (approver): The decision maker and the person accountable for the decision.
- C (contributor): The person or group of people knowledgeable enough to influence the decisions with her/their perspective and experience. They give advice. For example, the legal team can be an example of a contributor.
- I (informed): The team member who will be informed of the decision because in one way or another they’ll be impacted by it. Informing the right team members can help you with the decision adoption and support.
When should I use it?
- Working with cross-functional teams
- Making complex decisions
- Making decisions that impact customers and team members
- Making decisions that have high influence on the business
Benefits
The DACI framework helps to build trust and make sure everyone on the project understands their roles and responsibilities. It makes it easier to ask for help and clarification, and also to give and receive feedback.
Since it’s almost impossible to get consensus, it’s important to make sure the team understands that. I like the idea of “disagree and commit” to make sure all team members while they may disagree will help to make it work instead of playing the blame game.
Building trust and transparency will help the contributors to share their perspectives, concerns, and experience. The approver will consider all feedback to decide what on the best course of action.
Template
I created a Google Docs template to help you use the DACI framework. I recommend to include the information in the template in all projects you’re initiating. Just copy and paste, and of course, make adjustments as needed.
Define the roles
- Driver: The sole person responsible for driving the project/ decision. You can have a Driver for each decision if needed.
- Approver: One person responsible for approving the decision.
- Contributor: Team member and/or stakeholder helping the project/ decision with expertise enough to add value.
- Informed: Anyone on the team that will in one way or another be affected by the project/ decision.
Tips
- Remember that there’s only one Driver in the DACI framework.
- Ideally you’ll also have one Approver.
- In some other places they call the C as “Consulted” instead of Contributor, but the meaning is similar.
- The Contributor may have expertise and a voice, but they’re not the decision maker. The approver is the person with this power.
- You can include the N representing the Next Steps.
- If your team starts to run in circles, make sure the Driver, Contributors, and Approver are working together to solve that.
- Create an environment where people feel comfortable to share their ideas and concerns.
- You should consider having a Driver for each decision instead of a Driver per project.
Bonus: Next Steps
At Twitter, we included an N in the framework representing the Next Steps, and we call the framework as DACIN.
The Next Steps are a valuable asset that will help you and your team have a broader vision of the project/ decision.
You’ll include the Next Steps needed to reach the decision until the execution phase.
👋 Feel Free to Clap and Share your Thoughts!
Find more at our LinkedIn, Instagram, and Twitter. Check our podcast. Follow our LinkedIn page and Newsletter!
Disclosure: At PM101, we strive to provide our readers with valuable and honest information on Product and Program Management. As a way to support the blog and continue providing valuable content, some blog posts may contain affiliate links or promotional content. By clicking on these links and making a purchase, the writer may receive a small commission at no additional cost to you. This commission helps to keep the blog running and allows the writer to continue providing valuable content and increasing her coffee and kombucha consumption. Rest assured, we will always provide honest and informative content and use affiliate links and promotional content only as a means to generate revenue to support the blog.
