Subscribe to new Sugar News posts
Blog Details
Recent Sugar News
Related
Recommended

A GREAT CRM STARTS WITH GREAT DATA

Michael Baecker
Less than one minute read time

If people don’t use the CRM, or use it incorrectly, the data becomes stale and – over time - inaccurate. When CRM users are creating a report or a mailing list and they find that data is incorrect or incomplete, a spiral of mistrust begins.

 People stop investing time and energy to use the CRM – “why bother if it’s wrong anyway?”

 The topics of Data Quality and User Adoption are deeply intertwined.

Learn how to stop bad data before it enters your CRM system.

Parents

  • Hi Michael,
    Thank you for the additional comments. I totally agree with your opinion about the usage of hard input restrictions. In many cases, it leads to users' resistance.

    In my opinion, much more efficient to use not only "hard" but and "soft" validations with notification and the possibility to save data.

    "Soft" validation helps to pay user's attention to possibly bad data and correct if it's necessary but at the same time gives a chance to save data if everything is correct or data can't be entered by objectives reasons (like your case with a phone number).

    Of course, it opens a way to save bad data but works well in combination with user training and following some technical rules:
    - show the clear and useful for user notification on "human language."
    - use one notification about all identified situations before data save because often data of one field should be analyzed in combination with other fields, especially for forms with many fields
    - grant a way to see a text of notification during data editing after getting of notification

Comment

  • Hi Michael,
    Thank you for the additional comments. I totally agree with your opinion about the usage of hard input restrictions. In many cases, it leads to users' resistance.

    In my opinion, much more efficient to use not only "hard" but and "soft" validations with notification and the possibility to save data.

    "Soft" validation helps to pay user's attention to possibly bad data and correct if it's necessary but at the same time gives a chance to save data if everything is correct or data can't be entered by objectives reasons (like your case with a phone number).

    Of course, it opens a way to save bad data but works well in combination with user training and following some technical rules:
    - show the clear and useful for user notification on "human language."
    - use one notification about all identified situations before data save because often data of one field should be analyzed in combination with other fields, especially for forms with many fields
    - grant a way to see a text of notification during data editing after getting of notification

Children
No Data