Before ERP: map the work that matters

An ERP discussion often starts with a list of modules. A readiness assessment should begin earlier: which decisions are delayed, where information is duplicated, and which handovers depend on one person’s knowledge? These questions reveal the work a system needs to support.

Map a few representative processes from beginning to end. Record the people involved, the information they receive, the approvals they need, and the outputs used by another team. Note inconsistent definitions and unclear ownership before treating them as software requirements.

Use the findings to identify a manageable first phase, the information that needs preparation, and the training the organization will need. This sample research framework is a starting point for investigation, not a completed institutional assessment or an assurance of implementation results.