How do you effectively conduct a Gap Analysis for an ERP implementation?

All answers to this question.

For an ERP project, the most effective framework is the "As-Is vs. To-Be" model. Start by mapping your current processes using BPMN 2.0. Then, evaluate the "Standard" processes within the new ERP. The "Gap" is where they don't align. For every gap, you must decide: Change the business process to match the software, or customize the software to match the business. I recommend a "Fit-Gap" spreadsheet that categorizes each gap by its business impact and cost of customization. This provides a clear roadmap for the project team and helps manage executive expectations regarding "Vanilla" implementation goals.

   Answered 2025-06-07 by Linda Garcia

The "Fit-Gap" approach is standard, but how do you handle the "Shadow Processes" that aren't documented? Are you finding that end-users have manual Excel workarounds that they didn't mention during the mapping sessions, which only surface during the final testing phase of the ERP rollout?

   Answered 2025-06-09 by Richard Scott

• Richard, we find those "Shadow Processes" by performing "Walkthroughs" with the end-users. We literally watch them perform their tasks. In our last project, we found a critical manual calculation they did in Excel because the old system was too slow. We made sure to automate that directly in the new ERP, which became one of the biggest "wins" for the project.

     Commented 2025-06-11 by Michael Stevens

Always involve a "Technical Architect" in your gap analysis. They can tell you if a gap can be closed with a simple configuration or if it requires a complex, expensive code customization.

   Answered 2025-06-13 by Jessica Williams

• Great point, Jessica. Having an architect present during our Fit-Gap sessions saved us from promising a "simple" change that actually would have broken the core ERP upgrade path.

     Commented 2025-06-15 by Linda Garcia