When avoiding CRM is a rational response to bad design
Employees usually avoid CRM for one of three reasons: the system makes work harder, they are not confident using it, or nobody has made its purpose clear. The remedy depends on the cause. Redesign will not fix weak training, and more training will not repair a poorly configured workflow.
When employees return to spreadsheets, inboxes or private notes, leaders often describe the problem as resistance. That diagnosis may be wrong.
A salesperson who must wait for a form to load, re-enter information already held elsewhere, complete irrelevant mandatory fields and recover from unclear save errors is not simply refusing to change. They are choosing the quickest route through the working day.
That choice carries a wider cost. Customer history becomes fragmented. Pipeline updates become inconsistent. Tasks sit in personal systems. Management reporting draws on incomplete records, so leaders lose confidence in the CRM and start requesting separate spreadsheets. A usability problem has now become a control and decision-quality problem.
CRM usability is about movement, not appearance
Bad CRM design is not limited to untidy screens. It appears whenever the system obstructs a common task.
Typical signs include:
- forms that expose every field to every role;
- repeated entry across CRM, email and other systems;
- labels that reflect technical language rather than the user’s work;
- inconsistent filters, buttons or navigation;
- validation messages that identify an error without explaining the fix;
- dashboards filled with information that does not help the user act.
Established usability principles point in the same direction: systems should show users what is happening, use familiar language, behave consistently, prevent avoidable errors and reduce the need to remember information between screens.
The more useful measurement is not always the number of clicks. A seven-step process may work well when each step moves the task forward. A four-step process can be worse when users repeatedly return to earlier fields, correct failed saves or search for missing information.
Track the rework: repeated edits, save failures, abandoned records, duplicated entry and time taken to complete a routine task.
The first diagnostic question
Ask a trained employee to complete one high-frequency task without assistance.
Can they do it quickly, accurately and without opening a spreadsheet, email draft or private note?
If the answer is no, further training should not be the automatic response. Start with a role-based usability review covering forms, views, business rules, integrations, duplicated data and configuration debt. GO ERP’s position is straightforward: Dynamics 365 CRM should be shaped around daily work, with simplification treated as part of the business value, not as cosmetic polish.
The goal is not a large redesign by default. It is to isolate the points where the system creates unnecessary effort, then make the smallest changes that restore speed, data quality and trust.
Weak training turns uncertainty into inconsistent usage
CRM training is the likely problem when users can complete a task with guidance but struggle to repeat it alone. The system may be workable; the knowledge is not yet embedded. In that case, redesign wastes budget. The business needs role-based practice, clear process context and support that continues after go-live.
A product demonstration is not the same as operational readiness.
Showing employees where buttons sit may help them navigate Dynamics 365. It does not teach them how to manage an opportunity, record a customer interaction or progress a case correctly under real working pressure.
This distinction matters because users need two kinds of knowledge:
- Application knowledge: how to complete the action in CRM.
- Process knowledge: when to complete it, what good data looks like and which later decisions depend on it.
A salesperson may know how to change an opportunity stage but remain unsure when the stage should move. Two employees can then follow the same screen differently. The CRM records activity, but the pipeline no longer means the same thing across the team.
Role-based and continuous learning is more useful than a single broad session because sales, service, marketing and management users perform different tasks and need different context. Hands-on scenarios, concise guidance and reinforcement help employees apply the system to their own work rather than remember a generic tour.
Look for confidence gaps, not attendance figures
Training completion proves that someone attended. It does not prove that they can perform.
A better review examines whether users can complete priority workflows without help, whether the same basic support questions keep returning and whether new starters become productive at a reasonable pace. Other useful signals include inconsistent field use, missed process steps, reliance on a few experienced colleagues and heavy external support for routine administration.
These symptoms have direct business consequences. Poorly understood processes create inconsistent records. Inconsistent records weaken reporting. Slow answers increase support costs and interrupt experienced staff. New starters take longer to contribute because essential knowledge sits with individuals rather than inside a repeatable enablement model.
The confidence test
Choose one common task for each role and ask users to complete it in a safe environment without step-by-step prompting.
If the system behaves correctly but users hesitate, miss steps or cannot explain why the information matters, the dominant problem is probably training.
The remedy should combine:
- role-specific scenarios based on real work;
- guided practice before users touch live records;
- short task-level reference material;
- named super-users with clear ownership;
- refresher training after process or system changes;
- structured onboarding for every new starter.
GO ERP treats CRM training as part of the value model, not a handover item. Internal ownership and super-user capability protect knowledge after go-live, reduce routine dependence on external support and help good CRM habits survive staff changes.
The aim is not to train people once. It is to build enough confidence and process understanding for consistent use to become normal work.
Poor communication makes CRM feel imposed rather than useful
Communication is the likely problem when employees know how to use CRM but still avoid it unless managers are watching. The system may be usable and the training adequate. What is missing is a credible reason to change behaviour, reinforced by leaders who use the same system and expect the same standards.
When that reason is absent, CRM can feel like extra administration, a monitoring tool or an IT-led instruction with little connection to the user’s priorities.
That perception is often created before go-live. Employees hear that a new platform is coming, but not what problem it will solve, which old methods should stop or how their role will change. They are then asked to maintain CRM and continue producing the same spreadsheets, emails and manual reports as before.
The message they receive is clear: the CRM is additional work.
Employees need a business reason, not a launch slogan
Useful CRM communication should answer practical questions:
- Why is the business changing the current process?
- Which tasks should become easier or more reliable?
- What information must now be captured?
- Which spreadsheets or private records should stop?
- How will managers use the data?
- What happens when employees raise a valid concern?
These answers connect a CRM action to a visible outcome. Updating an opportunity is no longer “feeding the system”. It gives colleagues a shared view of the account, helps managers assess pipeline risk and reduces the need for separate status requests.
GO ERP’s CRM perspective treats the platform as a shared operating layer for customer-facing work, not a digital contact list. That value disappears when important sales knowledge remains in personal notes, inboxes and disconnected files.
Leadership behaviour either reinforces or weakens adoption
Employees pay closer attention to operating habits than launch messages.
If managers ask for spreadsheet updates after CRM has gone live, tolerate incomplete records or run pipeline meetings from offline documents, users learn that the platform is optional. No communication campaign can compensate for that contradiction.
Leadership sponsorship should therefore be visible in routine work. Pipeline reviews should use CRM records. Forecast discussions should challenge missing or unclear data. Managers should respond to feedback and distinguish between a genuine usability issue and a reluctance to follow an agreed process.
The purpose test
Ask users to explain why one priority CRM action matters to the business and to their own role.
If they can perform the task but cannot explain its purpose, or if management behaviour contradicts the stated process, the main gap is likely communication and change ownership.
The remedy is a practical communication plan: brief managers first, explain role impact, address objections openly, define expected behaviours and keep feedback channels active after go-live. CRM adoption improves when people can see what the system is for, what should change and how consistent use supports better customer decisions.
The aim is not enthusiastic messaging. It is shared understanding, reinforced by management discipline.
Diagnose the cause before buying the remedy
The safest way to improve CRM adoption is to separate friction, confidence and purpose before changing the system. Friction points to design. Confidence points to training. Purpose points to communication and leadership. Most weak adoption contains more than one cause, but one usually creates the greatest operational drag.
This distinction protects budget. A redesign will not teach employees when an opportunity should move stage. More training will not fix a slow form. A communication campaign will not remove repeated data entry.
The Friction–Confidence–Purpose Diagnostic
Use three questions against one high-value workflow, such as creating an opportunity, updating a forecast or recording a customer interaction:
- Friction: Can a trained user complete the task quickly and accurately without duplicate entry, failed saves or workarounds?
- Confidence: Can the user complete it without prompting and explain the correct process?
- Purpose: Does the user understand why the task matters, and do managers rely on the resulting CRM data?
| Evidence pattern | Likely cause | Business risk | First response |
| Slow forms, repeated fields, error loops, abandoned records | Design friction | Lost time, duplicate work, incomplete data | Role-based usability and configuration review |
| Inconsistent entries, routine support requests, weak new-starter performance | Training gap | Unreliable reporting, higher support spend, slow adoption | Scenario-led training and reinforcement |
| Shadow spreadsheets, low voluntary use, managers bypassing CRM | Communication gap | Fragmented customer knowledge, weak control, low trust | Leadership and communication plan |
| Symptoms across all three areas | Mixed adoption failure | Spending on the wrong fix | Structured CRM optimisation assessment |
A credible review should combine task observation, support tickets, field completion, failed saves, active use by role, training coverage and stakeholder feedback. No single metric proves the cause. Login counts, for example, show access rather than useful adoption.
GO ERP’s CRM approach starts with the business problem, then examines process, data, usability, ownership and enablement before recommending change. That matters because many requests for “more automation”, “better dashboards” or “a new CRM” are symptoms of a weaker operating model underneath.
CRM FAQs
Why do employees avoid CRM?
Usually because the system obstructs work, they lack confidence using it, or the purpose and expectations are unclear.
How can leaders tell whether training is the problem?
If users succeed with guidance but struggle alone, the primary gap is likely knowledge, practice or process understanding.
When does CRM need redesign?
When trained users still face slow screens, duplicate entry, confusing forms, preventable errors or workflows that do not match their role.
What should a CRM adoption assessment include?
Workflow observation, usability evidence, support data, usage by role, data quality, training coverage and management behaviour.
The next step should not be a predetermined redesign or retraining programme. A focused CRM adoption and usability assessment can review one or two critical workflows, identify the dominant cause and produce a prioritised improvement plan. The value lies in deciding what to fix first, before more time and budget are committed.
