DRASCI: Adding a Driver to Keep Momentum

Summary

DRASCI builds on RASCI by adding a Driver: the person who coordinates the work, chases progress, and unblocks dependencies without owning the outcome. It fills the gap that appears in large cross-team programs, where the Accountable owner is a senior sponsor too remote to run the work day to day. The matrix contains three roles that can look like leadership at a glance, Driver, Responsible, and Accountable, and it earns its keep only if the team keeps coordinating, doing, and owning genuinely distinct. Its commonly repeated origin story, three theorists in a Whitehall context, is thinly sourced and should be treated as tradition rather than fact. For small or single-team work, where owner and driver are the same person, stay with RASCI or RACI.

The letters

DRASCI takes RASCI and prefixes it with a Driver role.

The subtle and important point is that DRASCI now contains three roles that can all look like “leadership” at a glance: the Driver who coordinates, the Responsible party who does, and the Accountable owner who answers for the result. The matrix earns its keep only if those three are kept genuinely distinct.

Origin and history

DRASCI is a niche but documented member of the family, and unusually it comes with a named origin claim. The most-cited account, recorded on CIO Wiki and echoed elsewhere, attributes it to three theorists working in a Whitehall (British civil service) context, named as Kane, Jackson, and Gilbert, who adapted RASCI for matrix-management environments by adding the Driver role and tightening the definition of Support.

A note of intellectual honesty is warranted here. That attribution is thinly sourced: it circulates through wiki-style references without an easily traceable primary publication, so it should be treated as the commonly repeated origin story rather than a firmly documented fact. What is well established is that DRASCI is consistently described the same way across independent project-management sources, that it is a real if uncommon extension of RASCI, and that the Driver concept it introduces is genuinely useful. The matrix is legitimate; the precise provenance of its name is less certain than, say, RAPID’s.

What problem it solves

DRASCI solves a coordination gap that appears in large, cross-team work. In RACI and RASCI, the Accountable person is expected to both own the outcome and keep the work moving. In big organizations those two jobs frequently cannot sit with the same person. The Accountable owner is often a senior figure, a director or sponsor, who carries the outcome but has neither the time nor the proximity to chase daily progress, unblock dependencies, or corral contributors across teams.

The Driver fills that gap. It names the person who does the coordinating, the chasing, and the day-to-day integration, while leaving ownership of the result with the senior Accountable party. This lets accountability rest at the right level of seniority without leaving the actual momentum of the work unowned.

When to choose it, and when not

Choose DRASCI for cross-team or cross-functional programs where the Accountable owner is too senior or too remote to run the work day to day, and where you already need the Support role that RASCI provides. It fits matrix organizations, large change programs, and any setting where “who owns this” and “who is chasing this” are legitimately different people.

Do not use it on small or single-team work where the owner is also the person driving progress. There, the Driver and Accountable roles collapse into one and the extra letter adds confusion rather than clarity. And if the real problem is a decision rather than delivery, note that the Driver concept also lives, more cleanly, in the decision-rights framework DACI, where Driver and Approver are the two headline roles.

Common pitfalls

• Driver, Responsible, and Accountable blurring together. The central risk of the matrix. If people cannot articulate the difference between coordinating, doing, and owning, DRASCI is worse than RACI because it implies a precision it is not delivering.
• The Driver without authority. A coordinator who can chase but cannot make anyone act is a nag, not a driver. The role needs enough standing to unblock, usually through the sponsor’s explicit backing.
• Two drivers. As with Accountable, momentum diffuses if more than one person believes they are steering.
• Origin overconfidence. Do not present the Kane-Jackson-Gilbert attribution as settled fact in a formal document. Cite it as the commonly repeated origin.

Worked example

A cross-functional regulatory-change program with a senior sponsor.

Reading the “Redesign the process” row: the Program Sponsor owns the outcome and carries it to the board (A), the Program Manager drives the work day to day, chasing contributors and unblocking dependencies (D), the Analyst does the redesign (R), IT and Ops actively help (S), and Compliance advises (C). The Sponsor never has to chase a meeting; that is the Driver’s job. This is the geometry DRASCI was built for.

Where it sits in the family

DRASCI is a specialized extension at the richer end of the task family, built on RASCI rather than on plain RACI. Its defining contribution, the Driver, is the same idea that anchors the decision-rights framework DACI, which is why the two are often mentioned together. Think of DRASCI as the task-centric home for the Driver concept and DACI as its decision-centric home. Choose DRASCI when the coordination gap sits in the delivery of a complex, multi-team deliverable; choose DACI when it sits in the making of a decision.

Sources

Web sources

• RACI Matrix, CIO Wiki (records the Kane, Jackson, Gilbert / Whitehall origin claim): https://cio-wiki.org/wiki/RACI_Matrix
• RASCI Matrix in Project Management, EPAM SolutionsHub (notes DRASCI as a RASCI variation with a dedicated Driver): https://solutionshub.epam.com/blog/post/rasci-matrix
• RAPID vs RACI (RASCI, RACI-VS, RACIO, DRASCI, DACI, RATSI), Interfacing: https://interfacing.com/rapid-vs-raci

Academic sources

No peer-reviewed work documents DRASCI itself, and its origin attribution circulates only through wiki-style references. The integrator role it names, however, is one of the best-studied ideas in organization design.

• Lawrence, P.R. and Lorsch, J.W. (1967) ‘Differentiation and integration in complex organizations’, Administrative Science Quarterly, 12(1), pp. 1-47. https://doi.org/10.2307/2391211 The foundational study of why organizations need explicit integrating roles as work spans functions.
• Galbraith, J.R. (1971) ‘Matrix organization designs: how to combine functional and project forms’, Business Horizons, 14(1), pp. 29-40. The matrix-management context in which coordinator roles such as the Driver arise.