Most failed ERP or CRM rollouts start the same way. The company decides to “digitally transform.” Budget is approved. A vendor is chosen. The timeline is aggressive. Then comes the real decision: who leads the project.
That is where many programs break.
Not business owners. Not the people who know the process end to end. Not someone with digital street smarts. The project is handed to people who think software is screens with data, and that “everything is easy once it is in the system.”
Day one looks productive. Meetings. Decks. Green status. The hard work is skipped: process discovery, workflow ownership, dependency maps, data model understanding, real testing strategy.
Without that, the ERP becomes a guessing game. Vague requirements. Rushed configuration. Exceptions swept under the rug. Master data treated as a detail.
Then teams expect the system to fix broken processes. It does not. It exposes them.
Blame starts. Tech “makes it complicated.” The implementer is told to go faster. Change requests explode. Patches become the plan. Users are trained at the end, if they are trained at all.
Go-live arrives. Invoices do not close. Stock does not match. Orders get stuck. Finance cannot close the month. Operations returns to spreadsheets. The conclusion becomes automatic: “the system does not work.”
Usually the system never got a chance.
An ERP is not an IT project. It is not a shortcut. It is a mirror. Mirrors are uncomfortable when you do not know what you are looking at.
Before kickoff, ask:
- Who owns each critical workflow, by name, with real time?
- Is there a dependency map across sales, inventory, billing, and finance?
- Who defines and cleans master data?
- How do you test the end-to-end process, not just screens?
If your stack is Salesforce, a native ERP can remove a sync layer. It still cannot replace process ownership.
Longer Spanish version on Discover: https://discover.egafutura.com/erp-espejo-liderazgo-del-proyecto/
Top comments (0)