In the first two blog posts in this series, I discussed the need for focusing on data quality and best practices for creating high-value dashboards as a way to continuously improve the value of your CRM system. In today’s post, we will look at how to automate routine tasks.
Automation is important because it solves two major problems within your organization: efficiency and consistency. In any organization where diverse groups of people are responsible for various aspects of product or service delivery, it becomes very difficult to provide consistent service without consistent processes reinforced and automated through CRM. CRM process automation offers great opportunities to drive organizational efficiency by removing routine tasks from the workloads of busy employees whose time is better spent on higher value customer-oriented tasks.
The key to looking for automation opportunities is understanding your customer journey. Much has been written about the benefits of a customer journey map so I won’t repeat that content here. Instead, let’s focus on why a customer journey map is helpful with process automation. By tracing each major step in your customer journey, from the time a prospect first contacts you through the implementation and support of your product or service, we can find great opportunities for automation. Specific opportunities will vary from company to company, but here are some good places to look:
This list offers only a few ideas to get you started. As each business is different, spend some time thinking about how your customer progresses on her customer journey and how you can use process automation to improve this journey and make it more efficient.
Once you have a short list of processes to automate, it's time to make sure you have a detailed understanding of how the process actually works and what needs to be done to make it better. Often, in customer discovery sessions, we find that different team members have a different understanding of what a particular process should be. When you ask a team of people to describe how leads are assigned to sale reps (to pick an example) you will often get a wide variety of answers, all from people who are actually performing this work every day.
Don’t get discouraged if you find that different team members have a different understanding of the ideal process. This is your time to streamline, update processes to make them more efficient, and document processes so that everyone is on the same page with how things should be done moving forward.
All of this should be done before attempting to automate a process. A consultant friend of mine uses the term “paving the crooked road” to describe attempts to automate processes that are not well thought out or optimized. Making changes to a process is easy and inexpensive at this point in the process. But once that process is automated, changing it or optimizing it becomes more difficult and time-consuming
Deciding who to involve in a process automation project can be tough. You need the people most intimately involved in executing the process you are automating. But those people also need to understand the big picture and how one process impacts and interfaces with another.
Bring in subject-matter experts in the area you are trying to automate. Seek their guidance and buy-in but don’t make this group too large. Keeping it a relatively small, committed group of experts will allow you to make faster progress and avoid the “design by committee” syndrome that too often plagues design initiatives with a large number of participants. Also, make sure you have a capable meeting facilitator running your design sessions. It’s important to have someone who can enforce a meeting agenda, keep discussions on track, and make sure the team is adhering to time constraints.
The actual implementation of an automated process in your CRM is often the least challenging part of the entire project. Most modern CRM’s have great tools built-in for process automation. Many of these use flowchart-based, graphic user interfaces to speed process design and development. When possible, make use of these tools, document your work, and remember that someone other than you may be the next person to update or fix a process automation that you build.
In some cases, a programmer may be needed to implement especially complex processes that cannot be built using graphics-based tools. An added benefit of doing the upfront work to document your process first is that it will provide a great starting point if you need to bring a programmer into the picture. Keep in mind that a programmer may not have a complete understanding of your business or how this particular process fits into the overall picture. By having clear and simple documentation, much guesswork is eliminated and the programmer will have a much higher probability of delivering what you really want.