Do you recognise these signals?
- Parallel spreadsheets replace features that were never assessed properly.
- Users follow different routes to achieve the same result.
- Training begins only when the project is nearly complete.
What may lie behind it
The same symptom can have different causes. Before choosing a tool or requesting development, distinguish at least these elements.
- Requirements and configuration were not tested against real work.
- Go-live was treated as the end rather than the start of adoption.
- Process problems are attributed generically to the tool.
How I approach the situation
I assess the gaps between process, configuration and actual use. I distinguish training, organisational, configuration and development needs, then guide responsibilities, testing and adoption towards an observable outcome.
Outcomes to make observable
Not absolute promises, but changes to define and measure within the real business context.
- More effective use of available functions.
- Fewer parallel spreadsheets and alternative procedures.
- Future investment based on demonstrated needs.