You’ve fine-tuned your Lightning environment, all Javascript buttons are gone, Visualforce pages have Lightning themes, users are trained, and you have turned Lightning on for all your users. So why are you still maintaining the org in both Lightning and Classic? Gain the confidence you need to bid goodbye to Classic forever with this step-by-step guide.
Help identify training, change management, and product gaps by enabling the Switcher Feedback app. Admins can capture valuable feedback from end-users and work quickly to address adoption challenges.
Learn more about this tool, including how to easily enable it for your users here.
Find your top Lightning switchers with the Lightning Usage App. This app is installed by default and gives you a list of the top 10 users that are switching back to Classic in your Org. Viewing this data will provide you with a great opportunity to reach out and ask why they are switching. Then, you can help them address those concerns in real-time. Ultimately, closing this gap will lead to higher adoption rates. If there is no specific reason for them to switch, like a missing feature or bug, consider disabling their ability to switch (see Step 2 below).
Need a list of users? An enhancement is coming with Winter ’19 release (forward-looking statement) to run this as a report. But for now, you can use “Workbench” to get a list of users by querying LightningToggleMetrics.
SELECT Action, Id, MetricsDate, RecordCount, SystemModstamp,Userid FROM LightningToggleMetrics
Learn the basics of the Usage App here!
When you talk to users about why they are switching, you may find that some users are switching simply because there is resistance to change. If that is the case, follow the first rule of change management 101 and Disable users’ ability to switch back to Classic with a permission set. Before you do that, make sure you understand the limitations.
Some Admins will also disable this by default for most users. That way, the onus is on the users to prove that they need the ability to switch back to Classic. Of course, you should make an announcement before implementing this type of change.
When you interview your users, you may find that some users feel they have to switch back. This may be because some features are not yet available in Lightning. If so, continue to monitor the roadmap and highlight your needs on the Lightning Success Community. And, continue to foster an ongoing dialogue with those users to create a plan for how they can switch when they’re ready.
That’s it! By making Lightning the ONLY experience for your users, you get to focus 100% on all the newer (and better!) features that Lightning has to offer, thereby increasing your users’ productivity and driving business value.
We have lots of resources to help you get the most out of Lightning Experience and help your users make the switch.
It’s tempting after seeing an Agentforce demo to want to immediately start building an agent in your org. The reality is there’s a step before configuration: making the metadata make sense. Why? Metadata gives Agentforce the context and structure it needs to understand and interact with your data accurately. But reviewing all your metadata can […]
Your first Agentforce use case does not need to transform the entire company. That was one of the clearest takeaways from my Salesforce Admins Podcast conversation with Kacie Molina. It’s easy to leave an Agentforce demo thinking you need to invent one big, impressive agent. A better place to begin is with a small problem […]
If you’ve already enabled the In-Person Meeting Assistant, you’ve solved the problem of capturing live meeting transcripts. But what happens when the meeting ends without one? Maybe the customer didn’t consent to live recording. Maybe the rep forgot to start it. Maybe it was an impromptu conversation in the lobby that turned into a real […]
