ERP Discovery: Aligning Stakeholders Before Selection
The manual reconciliation of sales order data between the CRM and finance systems, often requiring multiple team members to spend hours correcting discrepancies each month, is a surprisingly common symptom of misalignment during ERP selection. This points to a deeper issue than just system integration; it highlights a fundamental lack of shared understanding regarding business processes and requirements that frequently derails even the most well-intentioned ERP projects.
Beyond Vendor Demos: Why Requirements Drive Platform Fit
Too many organisations approach Enterprise Resource Planning (ERP) selection as a product comparison exercise, attending vendor demonstrations and assessing features based on superficial comparisons. While understanding functionality is important, it’s secondary to ensuring the platform genuinely aligns with documented business requirements. A compelling demonstration showcasing impressive capabilities doesn’t guarantee suitability; in fact, it can actively obscure underlying misfits.
The Pitfalls of Feature-Driven Decisions
Focusing solely on vendor demonstrations encourages a feature-driven decision-making process. Teams become enamoured with bells and whistles that may seem attractive but ultimately don’t address core business challenges. This leads to scope creep, unnecessary complexity, and a system that doesn’t truly support operational efficiency.
Furthermore, relying on vendor presentations creates a perception of functionality that often isn’t fully realised during implementation. Promised integrations might prove problematic, customisations become essential, and the overall project cost spirals out of control. A structured requirements discovery process mitigates these risks by establishing clear expectations upfront.
Defining ‘Current State’: Mapping Processes and Pain Points
Before even considering potential ERP platforms, it’s crucial to thoroughly document your organisation’s ‘current state’. This isn’t simply about listing existing processes; it’s about understanding the pain points, inefficiencies, and operational challenges that currently exist. A detailed mapping exercise should encompass all relevant departments and functions.
Process Mapping Techniques
Several techniques can be employed to effectively map current state processes. These include:
- Swimlane diagrams: Visually represent process flows, highlighting the different teams or individuals involved in each step.
- Value stream mapping: Focus on identifying and eliminating waste within a specific process.
- “As-Is” documentation: Detailed descriptions of current processes, including inputs, outputs, responsibilities, and systems used.
The goal is to create a shared understanding among stakeholders regarding how work currently gets done – and where the opportunities for improvement lie.
Identifying Stakeholders & Their Unique Perspectives
ERP selection impacts every department within an organisation, making stakeholder alignment paramount. However, different departments often have conflicting priorities and perspectives.
Sales might prioritise lead management capabilities, while finance focuses on robust reporting and compliance features. Failing to acknowledge these differing viewpoints can lead to compromise solutions that satisfy no one.
The Importance of Inclusive Participation
A successful ERP discovery process requires active participation from a diverse group of stakeholders, including:
- Executive sponsors: Provide strategic direction and ensure alignment with overall business objectives.
- Department heads: Represent the needs and priorities of their respective teams.
- Key users: Offer practical insights into day-to-day operations and potential challenges.
Facilitated workshops, like those offered through SmartStep, are invaluable for fostering open communication and resolving conflicts among stakeholders.
Documenting Future-State Priorities: A Collaborative Approach
Once the current state is thoroughly documented, the next step involves defining future-state priorities. This isn’t about simply wishing for a better system; it’s about articulating specific, measurable goals that an ERP platform should help achieve. These goals should be aligned with overall business strategy and address the pain points identified during process mapping.
Prioritisation Frameworks
Several frameworks can aid in prioritising future-state requirements:
- MoSCoW method: Categorises requirements as Must have, Should have, Could have, and Won’t have.
- Impact/Effort matrix: Evaluates potential improvements based on their impact on the business and the effort required to implement them.
The key is to involve stakeholders in this prioritisation process, ensuring that everyone understands the rationale behind the chosen goals.
Delivering Tangible Outcomes from ERP Discovery
A well-executed ERP discovery process delivers tangible outcomes beyond simply a list of requirements. It creates a shared understanding among stakeholders, reduces ambiguity around scope, and provides a solid foundation for informed decision-making.
Key Deliverables
Typical deliverables from an ERP discovery workshop include:
- Documented business processes: Detailed maps outlining current state operations.
- Prioritised requirements list: A clear ranking of essential and desirable features.
- Stakeholder alignment document: A record of agreed-upon goals and priorities.
- Preliminary platform fit assessment: An initial evaluation of potential ERP platforms based on documented requirements.
These deliverables provide a roadmap for the selection process, ensuring that the chosen platform aligns with business needs and delivers measurable value.
If you’re facing challenges aligning stakeholders or defining your ERP requirements, discover how SmartStep can help.
