If salespeople record visits in a separate file and then retype them into CRM, buying another system may not be the first useful step. Integration, reduced entry or a clear management decision might help. Low usage describes a symptom without diagnosing its cause.
Before replacing CRM, commission diagnosis of a recurring task in the existing system. Distinguish users unable to complete it, those completing it at excessive effort and those finding little value in the current process. Fewer logins cannot automatically justify blaming staff or more generic training.
Follow the whole task
Consider a fictional equipment-maintenance subscription company. After a visit, staff write a file summary, complete CRM fields and message a supervisor because reporting still happens elsewhere. This is neither a customer case nor an actual study; it illustrates diagnostic scope.
Ask who uses each information item, when and for which next action. Duplicate entry could serve another system, reflect distrust of reporting or preserve an old process after launch. These possibilities cannot be reduced to a different interface color or button.
A barrier register instead of general complaints
| Illustrated observation | Diagnostic question | Intervention requiring evidence |
|---|---|---|
| Staff cannot see the task | Are account, role and assignment correct? | Access or process correction before generic training |
| Information is entered twice | Who needs the second copy and why? | Approved simplification, integration or removal of duplication |
| Fields contain arbitrary values | Is the information available when entry is required? | Review field timing, meaning and required status |
| Supervisors request external reports | Does internal reporting answer their question? | Report definition or management-process change |
Add the role, task, evidence, alternative explanation and post-change verification owner. This proposed table cannot diagnose every organization. A complaint alone does not justify deleting a field; its purpose may be misunderstood or require another approver's involvement.
Collect evidence from several angles
Microsoft adoption guidance combines interviews, feedback and usage or transaction evidence. Login counts cannot establish correct follow-up or explain abandoned tasks. Compare records with suitable task observation and conversations under agreed access boundaries.
GOV.UK guidance describes observing realistic tasks with neutral instructions. Telling staff where to click cannot establish independent understanding. Record assistance and unobserved aspects, using appropriate privacy-preserving data without claiming that a limited sample represents everyone.
Avoid selecting only the most experienced users to represent the problem. Define included roles, shifts and task types, recording groups absent from the sample. An experienced employee may rely on a personal workaround while a newer colleague needs steps the system never explains. Preserve this distinction instead of averaging it away and concealing the actual need.
Connect the cause to a specific purchase
If users understand a task but permissions prevent it, discuss role correction rather than replacing the platform. If required information is unavailable, review its source and timing. A genuine skill gap may warrant targeted training, supported by observation rather than assumption.
Request separate alternatives: configuration, integration, interface improvement, training, process change or replacement assessment if the current solution cannot meet a demonstrated need. State the expected effect, review method and unresolved concerns instead of accepting an open-ended repair proposal with no explained starting point.
Review after a suitable work opportunity
Agree to repeat the task after intervention, recording comparison conditions, included requests and staff or channel changes. Later improvement cannot be presented as confirmed causation without a suitable measurement design. One removed barrier may still leave another management dependency unresolved.
The CRM implementation scope covers project deliverables, while sales-stage acceptance explains transition meanings. Send the barrier register when requesting CRM configuration from Nextwave to compare justified interventions before committing to replacement.
Diagnostic references
Microsoft post-transition adoption guidance and GOV.UK observation guidance were opened on 4 November 2026. The original example and register involve no staff-account inspection or measured adoption rate. AI assisted preparation, with information and translation review.
