Back to all articlesCRM adoption

Diagnose CRM non-use before prescribing more training

Alactic Editorial9 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A manager sees incomplete opportunity records and schedules another CRM refresher. Yet the same missing updates could reflect several different problems: employees do not know how to enter them, cannot tell what belongs in each field, already record the information elsewhere, or face priorities that leave no realistic opportunity for administration.

To understand why employees are not using CRM, start with a recent task rather than a judgment about attitude. Observe the work, ask staff to explain their choices, and compare expectations with what the workflow supports. Training helps when someone lacks a necessary skill. It cannot resolve contradictory instructions or remove duplicate work.

The diagnostic table below turns visible behaviour into a testable explanation and targeted response. The aim is a reliable handoff, not simply more activity in the system.

1. Define the missing behaviour before investigating its cause

“Use the CRM more” is too vague to diagnose. Replace it with a specific action, a trigger, and a reason another person needs the result.

Hypothetical expectation: After a substantive customer conversation, the record owner adds the agreed next action and its due date before handing the account to a colleague. The receiving colleague uses that information to continue the work without repeating questions.

This identifies an observable task and gives the information a purpose. It also lets you ask whether the expectation is reasonable under actual working conditions. Agree on:

  • Trigger: What event makes an update necessary?
  • Owner: Who is responsible when several people participate?
  • Minimum information: What does the next person genuinely need?
  • Timing: When must that information be available?
  • Use: Which decision or handoff depends on it?

If managers disagree on these points, clarify the operating expectation before assessing employee capability. Staff should not have to infer a process from conflicting requests. Remove information requirements that nobody can explain before asking employees to complete them more consistently.

2. Observe a task, including the work outside CRM

Ask an employee to walk through a recent, ordinary task from its starting point to its handoff. Include email, notes, spreadsheets, and conversations where relevant. Looking only at the CRM screen can hide why information never reaches it.

Explain that you are examining whether the process supports the work, not conducting a surprise performance test. Use an appropriate record or sanitised example, and avoid copying unnecessary customer or employee information into diagnostic notes.

Ask the employee to narrate decisions. Notice pauses, tool switching, copying, requests for help, and postponed updates. Keep observations separate from interpretations.

Hypothetical walkthrough: The employee checks a spreadsheet before choosing a CRM stage. Observation: They consult a second tool before making the selection. Possible interpretation: The spreadsheet contains the stage definition. Ask what they are checking rather than treating the extra step as resistance.

A single walkthrough can mislead. Someone may choose an unusually clean record or work differently while watched. Compare the explanation with another recent task and, where appropriate, another person performing the same role. Differences between roles may be legitimate; unexplained differences within the same task deserve investigation.

3. Use short interviews to test explanations

Keep interviews anchored in a recent event. “Why don’t you use the CRM?” invites a broad defence. “Show me what happened after this conversation” produces something you can investigate.

  • What were you trying to finish at this point?
  • What did you believe needed recording, and by when?
  • Where did the information first get written down?
  • What made the CRM step difficult, uncertain, or less urgent?
  • What happens if you delay the update? What happens if you delay the customer-facing work?
  • Who uses this information next, and what do they ask you for anyway?
  • Could you show me how you would complete the step now?

The last question distinguishes knowing from doing. Someone who completes the task accurately without prompting may not need basic training. However, a successful demonstration does not establish that the workflow is practical during ordinary workload: a quiet walkthrough removes interruptions and competing deadlines.

Ask managers parallel questions about priorities and information use. If staff say updates are optional but managers describe them as essential, compare instructions and review routines. Do not settle the disagreement by choosing the more senior account.

4. A filled diagnostic decision table

Fictional worked example: A hypothetical sales team records next actions inconsistently and maintains a separate handoff spreadsheet. Every behaviour and evidence entry below is fictional, not an Alactic customer result. Each likely cause is a working hypothesis, not a finding that applies to every employee. Copy the table into a working document and replace its entries with evidence from your own investigation.

Filled hypothetical CRM non-use diagnostic decision table
Observed behaviourQuestions to investigateHypothetical evidenceLikely causeTargeted response
A. Updates happen only with helpCan the employee find the record, interpret the field, and complete the update independently?The employee explains what belongs in the next-action field but cannot repeat the entry sequence without prompting.A task-specific skill gap.Demonstrate the task, provide supervised practice and a concise task aid, then check independent completion on a different example.
B. Employees interpret one field differentlyWhat does the field mean? Do examples and manager instructions agree?Staff can operate the form, but one manager expects internal reminders while another expects customer commitments.An unclear operating definition.Agree on the purpose, provide contrasting examples, and clarify where other information belongs. Review sample entries together.
C. The spreadsheet is current; CRM is notWho requires the spreadsheet? What does it provide? Which record does the receiving team use?The receiving team requests the spreadsheet, and employees must enter the same next-action text twice.Duplicate work with competing records.Name the authoritative handoff record and test it with the receiving team. Retire the duplicate step only after the handoff works.
D. Required fields encourage guessesIs the information knowable yet? Why is it required now? Who relies on it?A customer has not discussed timing, but the workflow requires a date before the record can proceed.An information requirement that arrives too early.Review when the date becomes necessary and how uncertainty should be represented. Test changes before relying on the resulting data.
E. Updates happen just before management reviewWhen is the information used? Which work takes priority during busy periods?Employees demonstrate the task independently. Managers request immediate outreach throughout the day and inspect records only at review time.Conflicting priorities and a reporting-only incentive.Clarify handoff priorities, provide a realistic update opportunity, and use records in operational decisions rather than only reporting.
F. One role cannot complete its assigned taskIs the role authorised? Does the available workspace support the task? Is the workaround intentional?A coordinator understands the update but cannot access the relevant action with their assigned role.A mismatch between responsibility and access.Ask the system owner to review responsibility and appropriate access. Do not share credentials or broaden permissions simply to remove friction.

Similar symptoms can have different causes. A blank field in row A calls for practice; a blank field in row C calls for examining the duplicate process. Do not assign a cause from the behaviour column alone. The evidence column is what makes the intervention defensible.

5. Choose the smallest intervention that addresses the cause

A useful diagnosis links a response to a failure mechanism. Avoid a broad training programme when the evidence points to one ambiguous field or duplicate handoff. Equally, do not redesign a whole process when someone needs focused practice.

For a skill gap, teach the actual task and check independent performance. For unclear expectations, resolve conflicting instructions and publish a short definition with examples. For duplicate work, redesign the handoff with its receiving team. For competing priorities, change the management request—not just the employee reminder.

State trade-offs openly. Removing a field may simplify entry but deprive another team of useful information. Making one record authoritative may shift work onto colleagues. Tightening an update deadline may compete with urgent customer work. Test the downstream task, not just the ease of entry.

Check the workspace and current plan before assuming a software change is available. These are operating recommendations, not claims about specific Alactic controls. If a task is unsupported, define an explicit interim process and its owner. For access changes, follow least-privilege principles: provide only the access appropriate to the responsibility, rather than blanket permissions.

6. Test the diagnosis with a narrow pilot

Change one main condition where practical, then observe whether the specific failure becomes less frequent without creating another problem.

Hypothetical worked pilot: The manager investigates row C and confirms that both teams understand the next-action definition. Duplicate entry appears to be the main obstacle. For one working week, a small handoff group uses one agreed record instead of copying the same text into a spreadsheet. The receiving team has a temporary fallback if information is missing.

Hypothetical results: Of ten eligible handoffs, eight contain an understandable action and named owner when needed. Two still require clarification because responsibility is unclear when multiple people join a conversation. Employees report no duplicate entry during the pilot, and the receiving team identifies no missing spreadsheet-only information.

This supports removing the duplicate step for that tested workflow, but it does not establish that adoption is solved. The remaining failures suggest an ownership rule needs attention. The manager should test that rule next rather than prescribing navigation training.

Use this filled pilot record as a reusable companion to the diagnostic table. All its details remain hypothetical:

  • Behaviour: Next-action details are missing at handoff.
  • Working diagnosis: Duplicate entry delays the CRM update.
  • Intervention: Use one agreed handoff record for the pilot group.
  • Owner: Sales operations lead, working with the receiving-team lead.
  • Review point: End of the one-week pilot.
  • Observable outcome: The recipient can identify the action and owner without a separate explanation.
  • Evidence against the diagnosis: Missing updates persist without duplicate entry, or recipients still need information available only in the spreadsheet.
  • Decision: Retain the tested single-record route provisionally; clarify shared-conversation ownership before extending it.

A filled field is not automatically useful information. More logins would not demonstrate that this handoff improved.

7. Recover when the first fix fails

If training improves performance during practice but not during work, revisit timing, interruptions, access, and competing requests. Repeating the lesson may only confirm a skill the employee already has.

If removing duplicate entry does not improve record quality, check ownership and whether anyone uses the remaining record. If a clarified field still receives inconsistent answers, test the definition against awkward cases rather than continually adding wording.

Several causes can coexist. An employee may need practice while the team needs a clearer handoff rule. Track which change addresses which problem. When a pilot creates missing information or a broken handoff, restore a known workable route temporarily and investigate before extending the change.

8. Assign ownership and a review point

Before closing the review, name the intervention owner, set the next review point, and record what evidence would overturn the diagnosis. Give that owner responsibility for collecting the evidence and deciding whether to retain, revise, or stop the intervention—not merely for sending another reminder.

CRM adoptionWorkflow designTeam management

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications