An ERP case-study reading worksheet
An ERP or commodity-trading systems case study is most useful when it explains the starting problem and how results were assessed. Use these questions to examine the evidence.
Work through the checklist
Identify the business process, company size and implementation scope. Note which modules and integrations were included and what remained outside the project.
Look for the baseline, comparison period and measurement method behind each result. Distinguish the customer's reported experience from independently checked outcomes.
Ask about data migration, user training, ongoing administration and unexpected work. Record unanswered questions before using the case study to support a purchasing decision.
A useful question
Does a successful case prove the system fits my business?
No. Use it to develop questions for your own requirements review. Similar industry labels can conceal very different workflows and constraints.
Test one reported result
Choose one result and work backwards through the case study. Write the outcome measure, the earlier baseline, the measurement period and the process changes that occurred. If a field is missing, label it not stated. Then ask whether other changes could have contributed, such as staffing or a revised workflow. This does not disprove the result; it identifies what additional information would make it useful when assessing a different organisation's project.