Skip to Content

RACI d’un projet ERP : qui décide vraiment ?

Un seul responsable final par activité, et des décisions écrites.
September 30, 2026 by
RACI d’un projet ERP : qui décide vraiment ?
OdooBot

Four roles

  • R — responsible: does the work.
  • A — accountable: answers for the result and decides; only one per activity.
  • C — consulted: gives an opinion before the decision.
  • I — informed: is kept up to date after the decision.
Diagram — Who approves what in an industrial ERP project: a single “A” per activity.
  • Client leadership

    • A: scope and budget
    • A: cutover decision
  • Business owners

    • A: data and acceptance of their flow
    • C: configuration
  • Provider

    • R: configuration, migration, tests
    • C: technical trade-offs

Common mistakes

Two “A”s on the same activity, an integrator approving its own deliverables, a business owner merely “informed” of acceptance testing: these situations produce disputed decisions and delays.

A minimal matrix

List the activities that commit the project: scope, data, acceptance, cutover, gaps. For each one, name the client-side “A”. The provider carries out the work and advises; it does not approve on the client’s behalf.

Limits

A matrix does not replace people’s availability: an “A” missing from committees blocks the project as much as a badly built matrix.

See project governance

La bascule ERP : un plan heure par heure
Geler, reprendre, vérifier, décider : la bascule se prépare comme une opération.