DACI is a responsibility matrix used to determine what roles team members will perform in decision making or when working on projects. This decision-making framework is designed to significantly improve a team’s effectiveness and speed on projects.
Let’s look at an expanded view:
A Brief History of DACI
This model was originally developed by Intuit as a variant of the responsibility matrix known as RACI. RACI gets its name from the descriptions of each of the four types similar to DACI: Responsible (those assigned to do the work), Accountable (who owns the success or failure of the project outcome), Supported (in the case of RASCI – Individuals identified who are needed to support the task by providing resources towards completion of the task), Consulted (the experts providing knowledge on the project) and Informed (persons who need to be regularly updated on the project).
RACI (and its variant RASCI) work incredibly well for many types of business projects. There was one area though where a slight deviation would better serve projects and that was with product management. These particular teams face additional challenges as they are continually pushing forward on many levels simultaneously where strategic decision-making is needed. As the focus in this area is on specific individualized decision clarity, the DACI model better represents the framework to be used by product managers.
DACI Decision Model’s Roles and Responsibilities
This is the project leader in the DACI model
This person serves more as a project manager but does not have approval authority as that belongs to the Approver. An example would be a Driver who may schedule and run project meetings, assign tasks, gather ideas and distribute accordingly and maintains a record of the team’s progress.
The Approver in the model has the final say on a specific aspect of a project.
Any given project may have more than one Approver on the team. For example, a company may have two co-founders and to increase decision making velocity, one will make the decision on specific aspects. Ultimately with the DACI model, the fewer Approvers, the better.
Those persons who have been identified, that may be consulted upon for their expertise, opinions or because they have a unique vantage point that would help with project decisions.
The Driver is the one who will select Contributors and determine how they will participate or be incorporated in the decision-making process. As an example, the Driver would decide whether to invite a contributor to project meetings to share thoughts or gather their insights separately offline.
Informed persons are not directly involved with the project daily operations. They also do not have authority over the teams’ decisions. This group needs to be updated though as the projects outcome will affect their own work output.
Product management teams working on a product, might include customer support, sales & marketing, or other teams not directly involved with the project. This is because those departments will need to do their own planning or resource allocation based on the schedule of the products development timeline.
DACI Model: How its Used in Group Decision-Making
- Create sub-tasks of the overall project and assign them to a Driver
Once DACI roles have been established first, the next move is to assign the Driver to spearhead the project overall.
From this point you will want to break the project down to create a task-level plan. It is not required at this stage to create deadlines or assign resources yet. Your goal is getting the teams buy-in to agree on prioritizing the tasks to start moving forward on the project.
This is also the setting where you will want to assign a Driver to each task. By doing this, tasks are less likely to fall between the cracks because each one is being championed and an advocate has been assigned to keep it in motion.
- Assigning specific tasks to Approvers and Contributors
The team should now identify and agree on one Approver per task (ideally) and the Contributors who will be assigned.
The Driver will control at all times whether to add or remove Contributors as the team makes headway on the project and milestones are met. It is important though that at the start of each task, expert sources are identified and ready to consult at any time.
- Defining the workflow
The Driver will begin their action plan development at this point. This is a good time for the Driver to reflect on answering certain questions related to a project startup:
- Is a kick-off meeting needed and who will be attending?
- What would team meetings schedules look like? How often will we meet?
- What is the expectation of working with our Contributors? What is the best use of their time?
- What will we use to track task progress? Will we use a project management application? Can our own software in-house handle the product project management needs?
- What’s the schedule of updating Informed persons look like? How often?
- What will be our decision-making process? Will the Driver pass on the teams input to the Approver and wait for a decision? Is it better to have the Approver and Consultants sit for a brief meeting to make immediate decisions on each task?
RACI and DACI: Using them effectively in a project
DACI – Great for Product Management (Decision making on a product project)
RASCI – Great for Process Management (Responsibilities of tasks & approvers on all projects)
The beginning of any project is the best time to create a RACI and DACI chart. Program management can be called in to help work through the details if required. Proceeding after conflict occurs will make coming to an agreement much harder to reach. Plan a working session to detail each task that needs to be completed and identify who is responsible for each. If your team is having great difficulty in achieving decision-making progress, then a DACI meeting may be needed to hash out any issues.
When it comes to product management, DACI’s framework can help team’s complete projects with increased efficiencies by bringing on a clear and definitive decision-making process to group decisions. By virtue of its unique position related to product managers facing strategic decisions on many fronts, the DACI model would help product managers processes in this specific area.
For every project though, a RACI (or RASCI) chart will always show if there is an imbalance in the workflow and help identify where overall pain-points can be avoided. RACI identifies who is responsible to complete specific tasks while DACI decides the course of action for a specific task or function. It is well within the scope of RACI to identify the overall responsibility matrix that DACI will perform under. DACI as it turns out, is an excellent compliment to the RACI responsibility model framework.