Using DACI Framework for Better Group Decisions
DACI is a project management framework used to clearly define the roles of the various stakeholders on a project. DACI stands for Driver, Approver, Contributor and Informed. These roles, defined by DACI, make it clear who has authority in certain areas and situations. This allows a project to progress smoothly whenever group decisions have to be made.
DACI can bring clarification and unity to a team, enabling easy communication and a collaborative culture that works towards a common goal. So, if you’re struggling with getting decisions made in a project management environment, DACI can be right for you. Let’s take a closer look at the four parts of this decision-making framework.
The driver is the leader of the project. This is the project manager, and they manage the project from its inception to its completion. They are not always doing everything, but their hands are in all aspects of the project.
Initiation & Planning
The driver is usually the person who calls the initial kick-off meeting and explains the vision and purpose of the project. It’s defined through them. They’re leading these meetings, answering questions and generally offering guidance.
They also will gather ideas from project members and hear feedback from them about the progress of the project and how to deal with issues that come up over the life cycle of the project. They are also a soundboard for concerns expressed by those outside the organization.
The driver will create the plan, which is a detailed step-by-step task list for the project. This is usually done with a project management platform of their choice. Everything that must be completed in the project will be outlined here, including adding deadlines and noting how the progress with be measured.
Meetings & Communications
Meetings will also be the domain of the driver. The driver will meet with team members to make sure they’re accountable for the tasks they’ve been assigned and are meeting the progress milestones set up during the planning stage.
Communications, naturally, are also under the care of the driver, who must provide updates to stakeholders and teams on a regular basis. This is the vehicle to distribute information about the project’s progress and will address any issues that might arise.
There is going to have to be a person who pulls the trigger, so to speak. This stakeholder is understandably called the approver. That’s because they’re either the person or the group of people who have the authority to approve and veto in a project.
The approver is obviously in authority already. They tend to be either a manager, a founder of an organization or some group in an executive position. The size and structure of the company will determine who the approver is, as a smaller business is not going to have the staff and organizational structure to support a dedicated approver.
A driver doesn’t work in a vacuum. Any smart decision is fed by many streams, including experience, one’s gut and expert consultation. That’s where the contributor comes in.
A contributor is an expert in the field, one who will be consulted by the driver to offer their unique view on the problem and provide help with making the proper decision. This can be one person, but is usually a group of people, considering that problems range in type.
The driver is the one who assembles this group of expert consultants based on what is necessary in terms of experience and skill sets that are in the project. This might be one of the driver’s most important responsibilities, as the contributor adds the needed ballast to the project to keep it afloat.
Just as the name implies, the informed are those in the project who need to be informed. They’re usually the ones who just need to know about the progress of the project. This group doesn’t have any authority to affect the course of the project. They’re merely receptacles for information.
How to Use DACI
Now that roles are defined, it is likely becoming clear how this framework is going to assist in making the right decision the right way. It will also create efficiencies that will help move the project forward swiftly.
Basically, everything must be assigned to a driver. There is the overall project, naturally, but even each individual task should have a driver, so that when and if a decision must be made, the process is in place to do so.
Just as a driver must be identified, so must the approvers and contributors to give the driver the tools to make the right decision. Therefore, these positions must be assigned earlier rather than later. You want to have your groundwork done first.
The informed people on the project team can then be added to your project management software as observers to the tasks, so they’re either manually or automatically notified when a decision had been made. This keeps them updated on progress without adding another layer to the process.
Define the Framework
The driver will make these roles and set up the structure for DACI to work. By doing this first thing in the project, people are aware of their roles and there is less confusion when decisions are being made. Here, clarity is crucial.
The decisions as well as the roles must be defined, too. Creating a communication plan for the informed group is another responsibility of the driver. As noted, a project management software is a valuable tool, but there are many means of communication. Choose the one that best fits with your project, team and organization.
When a driver meets with the contributors, there also needs to be a way to collect their advice and form recommendations from the information. That information will be provided to approvers, who will then make the decision and the decision will be disseminated throughout the informed group.
What is a Stakeholder?
What is a stakeholder? A stakeholder is either an individual, group or organization who is impacted by the outcome of a project. They have an interest in the success of the project, and can be within or outside the organization that is sponsoring the project. Stakeholders can have a positive or negative influence on the project.
There are a lot of people involved in getting a project from inception to a successful completion. You’re going to have to know how to manage each and everyone one of them, even those who don’t work directly under you. One such person is the project stakeholder.
A stakeholder is a person, like any other member of the project, and some will be easier to manage than others. You’re going to have to learn to deal with a variety of personalities and make sure you’re in productive dialogue with them to know the project goals you’ve been hired to meet. But first, who is the stakeholder?
Identifying the Right Project Stakeholder
Now that we basically know what a stakeholder is, the next thing you need to do is identify who they are in your project. First, who can be a stakeholder? That’s a long list. Some examples are as follows.
- Project leader
- Senior management
- Project team members
- Project customer
- Resource managers
- Line managers
- Project user group
- Product testers
- Group impacted by the project as it progresses
- Group impacted by the project after its completion
- Subcontractors to the project
- Consultants to the project
Identifying who is the stakeholder in your project is key. The project’s success depends on it. If your stakeholder isn’t happy, then the project is not a complete success. So, you want to start this process as soon as the project charter has been created.
A good place to start figuring out who your stakeholders in are is by reviewing the project charter, which documents the reason for the project and appoints the project manager. Among the information about objects, budget, schedule, assumptions and constraints, project sponsor and top management, you can discern the stakeholders.
Also, review the contracts, as stakeholders might be mentioned in these documents. Are there environmental factors or other organizations with key ties to the project? Look those over too, as they might supply you with the names of stakeholders. For example, if there are environmental factors dictated by the government, then the government is a stakeholder. Review their regulations and standards to stay in good terms with them.
Managing the Stakeholder
A key question for anyone managing a project is how should you manage a stakeholder on the project? To complicate matters, there might be many stakeholders in your project. You should treat them like you would any other task on your to-do list: by prioritizing them. Over the course of a project, one stakeholder might be more valuable in terms of the project objections than another, whereas some stakeholders might demand more attention than others. So, you want to define who those people are and at what point in the project phase are might need to attend to them more, and build that into your schedule.
Now we’ve come to the second part of our question, which we’ve already started answering in the above paragraph. When we talk of stakeholder management what we mean is creating a positive relationship with your stakeholders by meeting their expectations and whatever objectives they agreed to in the project. This relationship isn’t just granted, however. It must be earned. You can earn the trust and build a positive relationship with stakeholders through proactive communication and by listening to their needs.
One way to do this is by interviewing the project stakeholders—not all of them, but certainly the most important ones. You might need to speak to experts to get the background you need for particular fields or groups, so when you do have one-on-one conversations with the stakeholders you’re well-informed and ready to get the most out of that time together.
But know that stakeholders aren’t infallible. Like we noted earlier, their impact can be negative as well as positive. Stakeholders might have inaccurate or out-of-date information. That’s where your stakeholder management part comes into play. You want to vet any data stakeholders give you as true and accurate so that you don’t make key project decisions based on the agendas of others.
There is a process for this, like there is a process for everything in project management:
Document Stakeholder Communications. Do this formally in your project plan. Note their names and their roles in the organization they represent. Document
every conversation you have with these key project partners, both to record their interests and requests, but also to be able to review their information later
for accuracy. If you’re conducting interviews, ask the stakeholders if you can record those conversations, as any record of interaction is important to document.
Enforce Process. Next you want to keep to a process of communications with stakeholders, and make sure that process is transparent, so everyone knows what to
expect. This includes project requests or feedback, and how you will document and respond to those requests needs to be subject to a formal process of review
and approval. This lets the stakeholders know that requests are subject to review, and that you have a process that you adhere to for those formal requests.
This protects both parties from scope changes and mis-communications that can impact the project.
Provide Frequent Status Reports. Providing regular and timely status reports that are appropriate for the stakeholders is crucial. You can go into details
with team members, while executives are going to want more of an overview. So, tailor the reports to the audience. Don’t forget to follow up with stakeholders
as well, asking questions to see if they have any feedback. That way you’re managing them, and you’re communicating with them proactively, to know if there’s
discontent or some decision has been made that will impact the project.
- Dispel Myths. Your stakeholder might be working on multiple projects, which means they’re not going to have the same closeness to the project as you. But that doesn’t mean they’re not getting other information about your project from other sources. You don’t want them to be subject to gossip or get incorrect information that might sway their opinions in the project. If they do make an assumption or get misinformation, you have to nip that poison in the bud and provide them with the truth. Sometimes they might not want to hear that truth, but better it comes from you, so you can control and manage it.
Executing the Project
Now you know what a stakeholder is, how to identify and manage them, but that is a process that must be carried through the entire life cycle of the project. You might have missed an important stakeholder in your initial research, and now you have a new person who is integral to the successful completion of the project. Worse, you can’t manage who you don’t know.
Therefore, it’s important to stay in constant contact with your stakeholders, as we suggested, and not only to know what they want. You can find out if there are new people who are in a position to influence the project. Get to know them, too. Things are always changing, and you have to manage that change or else you threaten the success of the project.
These articles were originally published by ProjectManager.com
Copyright 2018 © ProjectManager.com
3420 Executive Center Drive, Austin, USA 78731