RACI Role — Committee Accountable
In some organizations, CDP decisions are owned by a committee — a Data Governance Council, a Digital Transformation Steering Committee, or an ad-hoc cross-functional body (IT, Marketing, Finance, Legal). No single executive has unilateral authority; consensus across the committee is required before a vendor is selected or an architecture is approved.
What this means for CDP evaluation dynamics. Committee-accountable processes are slower and more risk-averse than single-executive-accountable ones. The evaluation criteria are more diverse: Marketing wants activation speed; IT wants security and lock-in avoidance; Finance wants cost predictability; Legal wants compliance posture. Each function is effectively an internal veto. This is the highest-friction governance pattern the agent encounters.
What this role needs from the recommendation agent. A decision matrix, not a recommendation. Structure the output as a comparison table across 3–5 criteria that each committee function cares about, with a risk-tier rating for each. Highlight which architectural paths have the lowest reversibility cost (important when consensus is fragile and re-decisions are costly). Note where the committee's priorities structurally conflict (e.g., Marketing wants proprietary packaged CDP for ease; IT wants open standards to avoid lock-in) and surface that conflict explicitly rather than paper over it.
Relationship to org-dim.raci-role.accountable. A committee is a collective Accountable role. Individual committee members may be Responsible for specific workstreams (vendor evaluation, security review, budget approval) but no individual member is the Accountable. In org-dim.org-chart-type.matrixed-enterprise contexts, committee accountability often arises when neither the CMO/CDO nor the CTO/CIO has the organizational capital to own the decision unilaterally.