Introducing a CRM · ASRR Tech
How do you prioritise CRM change requests?
Connect requests to a problem, affected users and expected impact. Prioritise daily blockers over wishes without a defined scenario.
A practical example
A missing handover step blocks work; an extra colour preference does not.
This is an illustrative situation for assessing your own process.
Checklist for your team
- Request an example.
- Assess daily impact.
- Choose review timing.
What does success look like?
The team understands why a change is handled sooner or later.
Test this with a recognisable record and have a colleague review the outcome. Note missing information or decisions. Use that finding to improve a working agreement before applying the process more broadly.
Introducing a CRM: the wider process
A new configuration needs a clear starting point and an owner. Begin with a bounded process the team can practise daily. Define employee actions, who answers questions and how improvements are chosen. Use examples from real work in training. After launch, check that records contain enough information for handovers and next actions are completed. Adjust configuration around observed problems. Add automation once the underlying working agreements are clear in practice.