Business Needs and User Adoption – A subtle truth for CRM Implementation
We have implemented CRM for quite sometime now in multiple industries. As part of these implementations, we have interacted with lots of people, ranging from executive management, IT and Business Users. Generally, it is the executive management or senior executives that initiates the requirement for CRM implementation. Some of those needs that usually triggers a CRM initiative could be:
- When leads are not being tracked properly.
- When there is no data for pipeline projects and the company has no tracks of quotations that they have given to customers as an organisation.
- When the company has no idea on the number of issues being reported by their customers and do not know how to allocate or deliver the solution.
- When the invoice raising and tracking for payment is not efficient and when the company receives the payments late due to the absence of a systematic process for driving the collection mechanism in the organisation.
The list could be longer but once the management faces these challenges, a firm is compelled to consider CRM as the right solution. Generally, a responsible person from among the business users or the IT team heads the task of taking this initiation further. Even though the executive sponsor is involved in most of the activities, from the time of identifying the responsibility it might be the IT or Business user who takes control of the coordination and other aspects. This role played by the coordinator remains quite crucial in the whole implementation as it is this person who is liable to interact with Vendors, Business Users and the Executive sponsor team.
However, if the person identified for this responsibility is not a qualified and experienced CRM Implementation specialist, this may impact the implementation process. Even though the executive management felt the need for a CRM, we need to see the ground realities and check for challenges that needs to be given an immediate attention. There is a human element involved in it. If the company is dictatorial or a purely operational business company, sometimes a push from the top will work easily; such companies have a culture of following the decision of their top management.
But nowadays, the executives want to implement their own ideas and prefer to be a part of the process where they can give their opinion on the needs of a CRM. The main issue here is in identifying the person who can define the needs and accept the outcome. He/she must be accurate in specifying the exact needs to be delivered and then getting it accepted by the end user.In most cases as soon as a system is handed over by the IT Team / Vendor to the Business User Community, the latter can decide on the usability of the system only on checking the entire content of implementation. It is generally quite difficult for the end users to decide whether they are receiving exactly what they are looking for or not. If the system fails in meeting any of the business needs of the users, it is definitely considered as not delivered.
The best way to avoid this would be to involve the end users from the start and try to see the CRM requirement from their perspective. Although, from the perspective of the Executive Management, it may be fine, but it is equally important for us to know the feedback of the End Customers. Some of the challenges that might be faced by the end users are:
- Getting leads that are very old
- Delay in response like taking almost 2 days in responding on being asked about the stock available in the godown and so on. Users generally seek a system that can provide instant information on the query being made.
- No information and follow up on the bookings and orders being made. Users generally prefer a place where they can have immediate details on the orders being placed, instead of requesting the Execution team for more information.
Capturing these business needs from the perspective of the end user and addressing them during the CRM Implementation leads to greater success in CRM Implementation through User Adoption.