Build a DACI to help all members of an integration workstream have knowledge transparency.
Ever wonder who the players are during an Integration? At times it can seem like tribal knowledge. Other times it is a makeshift org chart with cursory effort. The merit behind building a proper DACI will go a long way to emboldening a strong culture of accountability.
A Drive, Approver, Contributor and Informed (DACI) matrix is not a new concept. Project managers have used it for a decade or more to get through complex business and technical problems. However, applying it to the Agile approach for Integrations is new. A DACI can prove to be strongest when:
During the normal course of Integration, team members will fixate undoubtedly to other teammates whom they work with closely. But that is not the extent of your responsibility in the IMO.
You need to know and understand all the moving parts of the Integration. And a DACI helps you cement the appropriate pathways to the decision makers who keep progress moving forward.
Additionally, the DACI drives accountability at all levels. I know it’s an intangible argument but when teammates see their names in the DACI matrix then an inherent ownership sets in from the expectation of their role and responsibility.
Having a solid DACI template ready is great first step. Below is a sample.
Also, make sure to acquire a member list even though it may not be complete. Remember, you will never really be complete since participants during an Integration will fluctuate.
The member list is a step forward to knowing already participants who can be assigned to the DACI. Now, there will be a natural fit of teammates to the DACI roles.
So I am not saying that you need to overthink the assignments. Rather, having the member list ahead of time will skip the cycles of ambiguity.
Head of Integrations, Workstream Leads
Team member list, DACI matrix template
Planning: 20 minutes | Design: 60 minutes
There is a reason to start with the DACI legend rather than filling in the matrix.
By defining and cementing what you want each role to do then you set the guidewires by which team mate personality, ability and accountability fit into the role. If you did it the other way around then there will be too much ambiguity and flexibility that you will likely spend cycles redefining the roles to fit the people you want in the role itself.
This is a major flaw and should be avoided at all costs because this is fraught with conjecture and indefensible. And believe me when I tell you that you will get second guessed on your decision to put names into the roles.
But having the definition predefined then you can stand fast with the IMO’s definition, and let the proper team mates fall into the roles according to the appropriate criteria to driving success of this Integration.
A good DACI legend will:
Feel free to look at other resources to help you define the proper DACI legend for your organization. Here are a few examples I’ve found useful:
Now that your DACI legend is complete, we can get to the assignment of teammates to the roles.
The sample in Table 1 can be expanded to include all the departments in your Integration. Or you can modify the sample to be just Workstreams. In either case, it is recommended that you bring together your Workstream Leads into workshop to complete the effort of assigning teammates to the roles.
This design exercise can take about 60 minutes depending on how large of an Integration team you have.
At the completion of the design, make sure to get sign-off on this draft with your Workstream Leads. This is important when you bring up the matrix to your Steering Committee. The SteerCo too should get a readout on the assignments before communicating it to the general audience.
Here are a few hints to running a good workshop when assigning the teammates to the DACI roles:
Shortly after the workshop should be the chance to present to the SteerCo the draft of the DACI matrix assignments.
Typically, the SteerCo will not make major changes to the assignments once they know you’ve had sign-off from the Workstream Leads. And as key stakeholders, they have a vested interest in having the right team on the Integration to which they often rely on the opinions of their Leads.
The approval can be a simple verbal approval and documented in the meeting notes after the SteerCo.
It will not take too long after the SteerCo’s approval that teammates will begin asking for the DACI matrix. Feel free to make it publicly available in your IMO Document Repository. Often this is the easiest way to get the word out without a heavy communication effort on your part.
What you will find is that the DACI matrix will find its way naturally into most conversations during the early weeks of the Integration. And take note of which teams go through the five stages of group development.
Some will start earlier than others. You may consider stepping in to create formal ties between the teams who are behind.
A couple of ideas to try are:
Remember that most acquiree’s still feel nervous from the transaction. Helping them feel welcome through introductions will go a long way. The DACI matrix is a good start of the acquiree team to know who the players are on the acquirer side.
Closing out on this play, the DACI matrix will become perishable over time. Yet when done well in the beginning, it will create a level of structure and preparedness that is worthwhile for the longevity of the Integration program.