For many businesses, now is the time to move to Salesforce Lightning. But moving to Lightning can feel like a daunting task. Where should you start? How to you make sure you don’t disrupt the business? So in this first post, we will take a look at how to plan your move to Lightning Experience.
In the next post, we look at how to implement your plan and go-live! But in the meantime, if you have any tips of your own, feel free to add them in the comments section below. And let’s start planning…
Planning your move
Before we start, let’s just clear the air.
As an #AwesomeAdmin you probably already know there is planning required to make the switch over. The old adage – ‘failure to plan, is planning for failure’ – is never truer than when changing how a user works within a system.
But driving user adoption and making the transition as smooth as possible, doesn’t need to be overly complicated process though. And by planning your transition you set yourself up for the best possible result.
So let’s get started.
WIIFM?!… What’s In It For Me?
One of the first steps to planning any change should to be understand the ‘what’s in it for me’. It is the first question most users want to know about any change…
Sure Lightning Experience looks great. You can now customise the colours to match your company identity…
But that doesn’t really engage end-users in using the platform. After all we want them to use the system once we make the change, don’t we?…
Be honest with yourself. Would a typical sales, customer service or partner really care about that?
Answering this question for each type of stakeholder is one of the best ways to ensure everyone buys-in to making the move.
A great example is dealing with a stakeholder from Sales. Lightning offers many new features which benefit most sales users. Here are a few…. Sales Path to guide on what to do in the system to move to the next stage. Kanban board for managing your pipeline with drag-and-drop ease. What about Sales Console? Use of macros practically anywhere in Salesforce?
The point here is to you need to demonstrate you understand your end-users by understanding their problems. If you understand the problem, you can effectively position a feature or benefit that solves it. And this helps engage these stakeholders early on…
Why should we invest in making this change?
The next step is to develop a business case. It sounds horrible, but it can really help in convincing your senior stakeholders on why they should support the change. And to drive adoption when launched, you need their support…
This may not be applicable for all business, but I always try to work out a rough cost/benefit to any changes my team make. Even if it is just an estimate. And this loops back to understanding the WIIFM within your business.
Every business problem – and in turn the potential solution – have a potential time/cost associated with them.
This is the gold dust in developing your business case to answer the question most senior stakeholders within business would ask,
As an example, a simple cost-to-benefit calculation could be based on decreasing sales admin time. By improving the time taken to process and close a contract within the system, you can quantify the potential upside to the business.
So if an average salesperson closed an extra 2 deals a day/month/year due to improving the sales workflow in Lightning, how much is that worth to your business? (average contract value * extra deals per day = potential upside).
Keep in mind, this is only an estimate. But it can be a useful way to engage the business and to capture metrics relating to the success of the project once completed.
Mind the gap…?
Salesforce has spent the last couple of years attempting to make Lightning match the features of Classic. But there are still some gaps between Classic and Lightning Experience.
The next item on our list is to check what these gaps actually mean your org. By doing so you ensure your users can still use all key features they need.
If there is a feature gap or limitation, the next step should be to look at the publicly available roadmap. This outlines the upcoming features planned for release and may cover the feature that is a priority for you.
Also each published version of the release notes now include a section on what is and what is not included in Lightning Experience. For the Spring ’18 section, please have a look here.
Side note: The roadmap is scheduled to be updated after the Spring ’18 release, but a handy video to watch about the Force.com platform and upcoming features is the True to the Core video. Or there is a breakdown of the expected features in the 2018 predictions post here.
Salesforce is clearly invested in supporting all orgs to move to Lightning Experience. Releases now introduce most new features as Lightning Experience only. But to help, there is a wealth of content available for free to sink your teeth into.
For starters there is a great Trailhead module specifically on getting hands-on with a Lightning Experience roll-out. There is also a quick overview of the steps on the Admin blog. But personally I highly recommend jumping to the Power of Us site, which has been setup to cover best practice for making the jump to Lightning.
Each and every org now also has the Lightning Readiness Check built-in. And the check gets an update every release to give you more and more insight into your org’s compatibility into making the change.
If you want more information about how to take a business-first approach to rolling out Lightning, I found this article over on SalesforceBen.