Skip to main content

Keep It Simple in CRM: Five Reasons Why

Simplicity is one of the keys to successful sales force automation.  This is one of the lessons of implementing customer relationship management (CRM) that is good that I must keep learning it again and again.  

Here are my top reasons why it's better to keep it simple than to chase perfection:

  1. Sales people need to stay focused on sales.  The simpler your sales process and your tracking requirements, the more likely that they will be adopted by the sales force.  As requirements grow more complex, users will quietly revolt by failing to spend as much time as needed on data entry.
  2. Better compatibility with off-the-shelf CRM. Less customization can make it easier to handle upgrades and new features introduced by your CRM vendor. 
  3. Reduced implementation time. Less scope means less time and less cost before you go live. 
  4. Reduced training requirements. Fewer features reduces what you need to train and also leads to
  5. Reduced support and maintenance
Asking for simplicity and sticking to it are two different things.  The real question is how low you can go in terms of resisting the urge for customization. Thinking of a minimum viable product is a good place to target initially, and constraining new features through a governance process can help keep your CRM simple. 

What I can tell you from personal experience is that extensive customization often leads to neglected areas of your CRM which ultimately are abandoned, such as fields, forms, and reports that are no longer used and can make your system more confusing to new users. 

Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

Updated 8/15/2022 To understand Microsoft Dynamics 365 (formerly Dynamics CRM) and Power Apps, you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises.  These concepts also apply to Power Apps.  The main difference is that with Power Apps you are not starting with a Microsoft app but more of a blank canvas for your custom apps.  This post introduces some key terms and how these concepts are important for planning your implementation. While Dynamics 365 is still available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds in several countries. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uni

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source: by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do