Go-live feels like the finish line, but it is the start of the part that decides whether the project paid off. Many companies stop paying attention once the system is running, and months later discover that half the team still uses spreadsheets alongside it. A short, structured review at thirty, sixty and ninety days protects the investment. This guide gives you the questions, the numbers and a simple routine.
Decide the measures before you launch
The best time to define success is during planning. Pick three to five measures tied to the reasons you bought the software, and record the starting figure so you can compare.
| Goal | Example measure |
|---|---|
| Faster work | Hours from order received to invoice sent |
| Fewer errors | Credit notes raised for pricing or quantity mistakes |
| Better cash flow | Average days to collect payment |
| Better stock control | Stock count differences, and slow-moving stock value |
| Less manual effort | Time spent producing the monthly report |
| Adoption | Share of staff using the system daily, and tasks still done outside it |
The thirty, sixty and ninety day routine
Day 30: stability and gaps
- List every bug and workaround raised, with owner and status
- Check that data entered in the first weeks is clean: duplicates, missing fields, wrong categories
- Confirm that key reports are accurate by comparing them with an independent figure
- Identify people who are struggling, and book short coaching sessions
Day 60: adoption and habits
- Review usage by role: who logs in, what they do and what they avoid
- Find tasks still done in spreadsheets or messages, and decide whether to fix the system or retrain
- Check whether approvals are flowing or stuck with one person
- Collect structured feedback from each team: what works, what annoys, what is missing
Day 90: results and next steps
- Compare the measures with the baseline and report the change honestly
- Rank the top ten requests by value and effort
- Agree the next improvement release, with an owner and date
- Update training material and the quick reference guides
Ask the people who use it
Short interviews beat long surveys. Sit with three users for twenty minutes each and watch them do a real task. Ask what they do when the system cannot do something, and where they feel slowed down. Their answers usually point to small changes, such as a missing field, a confusing label or a report in the wrong format, that remove a lot of friction.
Do not confuse a bug with a training gap
When someone says the system does not work, check four things in order: is it a defect, is it a configuration, is it missing training or is it a real missing feature. Treating a training gap as a software fault leads to unnecessary changes, and treating a real defect as a training issue frustrates staff. Keep a simple log with the category for each item.
Keep improving in small steps
Business needs change, so plan for steady improvement instead of a one-time project. A monthly or quarterly release of a few agreed changes keeps the system aligned with the business and keeps users engaged. See our guides on ERP user adoption and training, the go-live week checklist and support contracts. If you would like an independent review of a system you already run, contact us.
