Adoption
Part of CRM adoption and operating routines
Finding workflow friction behind low CRM usage
Diagnose low CRM usage by following a customer task, separating rule, access, screen, skill and handover problems, then checking a fix.
If an expected CRM update is missing, trace the customer task that should have produced it. Note where the person stops, switches tools, enters a placeholder, or cannot see the result. Then determine whether a rule, screen, access, skill or handover issue is the obstacle before choosing a fix.
Choose one missing outcome
“Low usage” is too broad to diagnose. Choose a concrete result: accepted enquiries without owners, visit updates arriving too late for a handover, or revised proposals colleagues cannot find. Define the affected role, records and point in the work when the update is needed.
Ask people who do the task to show an ordinary case and an awkward one with their usual permissions. Observe how they find the customer, choose the record, enter the change and check that it saved.
Ask about any parallel register or message needed to finish the job. Record the obstacle and its consequence for customer work, without scoring the person.
Observation / Question to investigate
- Repeated “TBC” values
- Is the information actually known at this step?
- ---
- ---
- Update sent in chat but absent from the CRM
- Can the recipient find and act on the CRM record?
- ---
- ---
- Wrong opportunity selected
- Are names, links or search results ambiguous?
- ---
- ---
- Work entered twice
- Which system is authoritative, and who needs each copy?
These are possible clues, not findings about a particular team.
Match the fix to the cause
People may disagree about what a field means or when to update it: that calls for a clearer rule. A person may know the rule but lack access or face an impractical screen: inspect the configuration. If the route works but is unfamiliar, a short task-based aid may help. If an update is saved but the next colleague cannot find it, investigate the handover and record link.
Causes can overlap: a field may be difficult to find and required before the customer can supply its value. Explaining where the field is will not resolve its timing. Microsoft’s Dynamics 365 implementation guidance recommends feedback through interviews or observation and says severe process issues may require redesign.
Record the proposed change and its owner. After the change, have the usual user repeat the affected task and ask the receiving colleague to find the result. Attendance at training or another login does not establish that the missing customer update now reaches the right person.
