ERP Implementation Stakeholder Register
This is a practical guide to building a stakeholder register for an erp implementation project — a record of stakeholders, their influence and how to engage them, adapted to the realities of replacing or deploying an enterprise resource planning system across the whole organisation.
What a Stakeholder Register is
A stakeholder register is a record of stakeholders, their influence and how to engage them. For the full concept and how it works in general, see Stakeholder Register. On an erp implementation project it plays the same role, tuned to this kind of work.
Why it matters for an ERP Implementation project
ERP Implementation projects live or die on replacing or deploying an enterprise resource planning system across the whole organisation. A well-built stakeholder register gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how erp implementation projects drift into avoidable delay and cost.
What to include
- Stakeholder name and role
- Power and interest
- Attitude
- Engagement approach
ERP Implementation-specific considerations
Tailor the stakeholder register to the risks that most often derail erp implementation projects:
- Under-estimated data migration
- Business-process change resistance
- Customisation over-reach
Example
On a real erp implementation project, the stakeholder register would be shaped by replacing or deploying an enterprise resource planning system across the whole organisation. In particular, it should explicitly account for the project’s biggest risks — under-estimated data migration, business-process change resistance, customisation over-reach — rather than treating them as afterthoughts.