Bordj Bou Arreridj, Algérie
contact@jilsystems.com+213667868834

An ERP project starts before the software.

Questions to address when defining scope, preparing data and involving teams.

An ERP project starts before the software.

Start with processes

List tasks, stakeholders and information flows. Identify specific difficulties: duplicate entry, approval delays and limited visibility. Use this baseline to prioritise the project.

Define a realistic scope

Separate essential needs from those that can wait. Agree responsibilities, acceptance criteria and deployment stages with the teams involved.

Prepare data and users

Review master data quality before migration. Plan testing and training around real workflows, followed by support after launch.

Use the demonstration to make decisions

Prepare representative scenarios: a full purchasing cycle, a customer order, a stocktake or a period close. For each scenario, identify the people involved, documents produced and control points. Then ask to see the workflow in the solution. This helps reveal differences between an advertised feature and how your teams will actually work. It also helps distinguish configuration, organisational changes and any development that may be required.

Plan for success after launch

Launch is the start of a new phase. Users encounter their first exceptions, managers refine indicators and some rules need clarification. Decide who collects questions, how they are handled and when a review will take place. A well-prepared project also provides working materials, internal reference people and training arrangements for new joiners. The system can then evolve with the business rather than relying only on the people present at launch.

JIL Systems editorial team

Articles and guides about business digitalisation.