Skip to main content

Sooner or Later You Must Talk to the Users

No customer relationship management (CRM) implementation can succeed without user acceptance, and the best way to gain acceptance is to talk to users and take their suggestions into account from the beginning.

If this is the first CRM implementation at your organization, some managers will avoid or delay talking to users because they think that they cannot contribute useful input without prior CRM experience.  This is a mistake because it deprives the implementation of critical information on how business processes work without a CRM, and misses the opportunity to prepare users for embracing the system when it is rolled out.

In the end, users will be talking about the CRM system, and by talking to them throughout the process you can make sure that their comments are favorable.

For more information, see my post Getting Users on Board with Dynamics CRM. http://blogs.infostrat.com/2015/02/getting-users-on-board-with-dynamics.html

Popular posts from this blog

The DATA Act Driving Grant Management Automation

The Digital Accountability and Transparency Act enacted in May 2014 calls for making spending data available in open, standardized formats to be published online.  It is a continuation of transparency initiatives and lessons learned with experiences such as grants.gov, the 2009 economic stimulus under the Recovery Act and the spending site USASpending.gov.

Government grantees will have significant new administrative responsibilities.  Many organizations that were tracking grants in spreadsheets or documents will have to adopt more sophisticated automated grant management systems such as Microsoft Grants Manager to keep up with reporting rules.

For profit companies will lose some privacy as a result of this law.  Grant recipients will be required to disclose information including officer salaries.

Continued improvements to publishing grant opportunities such as grants.gov may make it easier to find grants. These reforms together are designed to improve the effectiveness of grant prog…

Dynamics 365 for Government Contractors (GovCon) Frequently Asked Questions (FAQ)

One of InfoStrat's most popular solutions is Dynamics 365 for Government Contractors (GovCon).



Here are some answers to frequently asked question on this solution:
Can I add new fields to the solution?  -- Yes, the solution is fully customizable and you can add your own new fields to any form, view or report.Does Dynamics 365 for GovCon work on mobile devices?  -- Yes, Microsoft offers mobile apps for all the most popular platforms including iPhone, iPad, and Android phone and tablets.Does Dynamics 365 connect with bid data systems such as Deltek and Onvia?  -- Some information services, such as Onvia, offer integration with Dynamics 365.  Others require third party solutions such as the InfoStrat integration with Deltek GovWin IQ.What do customers typically customize for their unique requirements? -- Not all contractors follow the same steps in the capture process.  Most clients will tailor the business process to add or remove steps in order to match their sales methodology.  Of…

Getting the Most from Dynamics CRM Online -- Synchronous v Asynchronous Workflows

This video shows highlights from the InfoStrat March 2015 seminar "Getting the Most Out of Dynamics CRM Online" presented by Dmitri Riz, the leader of the InfoStrat Dynamics CRM practice.  This is the second part of a series of blog posts.  The first is Benefits and Cloud Thinking.



In order to make your CRM workflows perform best, you need to understand the difference between synchronous and asynchronous workflows so you can choose which is appropriate for your applications.



Synchronous workflows are a new feature that was introduced in Dynamics CRM 2013.  Unlike asynchronous workflows which are sent to a queue, synchronous workflows execute in a single transaction. 

This means you can eliminate the need for many plug-ins which were created for previous versions of Dynamics CRM.

You may want to disable synchronous workflows during import operations, because they will could be triggered by each new record and significantly slow down the import process.