Our manufacturing firm is migrating to a cloud-based ERP, and I’m struggling to map the 'As-Is' state against the 'To-Be' requirements. What are the best frameworks or templates to ensure no functional gaps are missed during the elicitation phase? I want to avoid scope creep during implementation.
3 answers
To successfully bridge the gap during an ERP transition, you must start by documenting your current workflows in exhaustive detail using BPMN diagrams. Once the 'As-Is' state is clear, map it against the standard features of your new cloud ERP. I highly recommend using a Traceability Matrix to link every business requirement to a specific functional capability. This prevents the "missing link" scenario where a critical process is overlooked until the UAT phase. Focus heavily on data migration gaps and user permission deltas, as these are often where projects fail.
This is a great start, but have you considered the "Soft Gaps" such as organizational culture and team skill levels? Technology is only half the battle in an ERP migration. What specific methodology are you currently using to categorize your findings—is it a simple SWOT or something more robust?
Start by identifying your "Must-Haves" versus "Nice-to-Haves." Use a standard Excel template to list requirements vertically and the ERP features horizontally to find the voids immediately.
I agree with Jessica. Prioritizing via MoSCoW is essential here. By labeling gaps as 'Must-Have,' you can focus your development budget on critical custom builds instead of aesthetic changes.
Michael, I find that using the McKinsey 7S framework alongside the functional gap analysis helps address those cultural shifts. It allows you to see if the staff's skills align with the new automated workflows, which is a major "soft gap" that often stalls ERP adoption in large firms.