Skip to main content

Why Users Switch Back to Classic

When rolling out Lightning Experience, people are constantly switching back to Classic. Even after the initial rollout it's common to see people switching back and forth.

The most common reasons someone switches back to Classic are:
  1. Classic loads faster
  2. Their workflow is slower in Lightning
  3. They just don't want to switch to Lightning
Overcoming these objections will be key to a successful rollout. Let's dive into each one in more detail.

Classic Loads Faster

It does. 😢

And when you hear someone complain about this, take their side. 
Agree with them. 
Make that ironic joke, "haha, yeah Classic is faster than Lightning". ⚡⚡⚡

Then overcome this by highlighting how their overall workflow is faster in Lightning.

The page takes longer to load because each page is made up of many components. Once it has loaded, someone can complete their task on a single page.

Their Workflow is Slower in Lightning

It probably is. At least until they get used to it. 👨‍💻👩‍💻

Similarly, it's probably slower for you to build stuff too. You're both learning something new.

Use this commonality to gain an ally. Be vulnerable and remind them that this is new to you too. Talk about how things just seem slower now because it's something new for both of you.

Take this opportunity to tell them that Salesforce is investing in features for Lightning, not Classic. Pick a few roadmap features and get them excited!

They Just Don't Want to Switch to Lightning

Yeah... You'll get these people. 🙄

The most stubborn of them tend to be folks who have used Salesforce for a really long time and Classic is all they know. Teaching old dogs new tricks is hard.

Overcome this by telling them about the journey Lightning Experience has taken. You know how the story goes:

Salesforce launches this new UI and says they will no longer build features for Classic.

"Lightning is the Future", they say.
We all just had to go out and learn Lightning. 
Literally the whole ecosystem took a productivity hit.

But when things started to click, companies saw a 4x productivity gain or better. Your goal with telling this story is to convey that we are playing the long game.

If they're not onboard after your motivational speech, just pull a Salesforce on them. You know how Salesforce is turning on Lightning for all orgs as part of the Winter 2020 release? Follow their lead and force them over to Lightning.

Okay, I'm joking. Well, half-joking.

If they really don't have a good reason to switch back to Classic, it doesn't hurt to push them into the deep end.

You can make this happen either via a Permission Set or Profile. I prefer the Permission Set route because the granularity makes it easier to add or remove until it's time to lock everyone into Lightning. 

More info on how to do this can be found here: Make Lightning Experience the Only Experience for Some Users


Popular posts from this blog

Salesforce Lighting Migration: Plan for Success

In April 2018, I led the Salesforce Lightning Migration at Postmates. This is how I would do it over again if I could.

Define Goals The goals of a Lightning Migration are: Enable Lightning ExperienceConfigure Lightning ExperienceDocument all Salesforce processesCreate training and support materialsLightning Experience is adopted Easy enough right? Let's go though the plan to see how we accomplish each one. Enable Lightning Experience Just turn it on right? Well, kinda.
Although it may be controversial, I recommend turning it on and hiding the option from all users. This can be done by removing the Lightning Experience User permission from your custom profiles. 
And yes, turn it on in production
Why? You're going to turn it on anyway. Salesforce has declared this as the path forward, so you either turn it on now or wait until they flip the switch for you.
Plus, turning this on ahead of time will make deploying from a sandbox much easier. Trust me.
Goal #1 Enable Lightning Exp…

SOQL from the Command Line

SOQL and the Command Line go together better than peanut butter and jelly. Here's why.
Once upon a time, I got tired of running Salesforce Reports to get miscellaneous data. I found Workbench and started using their interface to run SOQL queries. This was great for a while, but I knew there was a better way.

Pro-tip with Workbench: If you set a browser bookmark after your query runs, you can return to that bookmark and it will re-run your query!

Enter the SFDX Command Line Interface (CLI). Get ready to take your productivity into hyperdrive! 🚀🚀🚀
sfdx force:data:soql:query If there's one command you learn, this is the one. All you have to do is pass a query string into the -q parameter and you're in business. Check it out:
-r | --resultformat This is my 2nd favorite thing. How often do you need to export a csv from Salesforce? And how annoying is it to make throwaway Salesforce reports each time? Yeah, it's the worst.
-r to the rescue! Just add "-r csv" to …

Why should I use SOQL?

You need data, fast!
Whether it's exporting a csv or answering a question, SOQL can get you the result much faster than creating a Salesforce report.

My top 3 reasons to use SOQL are:
Get data fastGet answers fastFlexible access Get Data Fast How often do you find yourself making a throwaway report to check what is happening in the system? For example, you updated your Lead routing and want to see if it's been assigning Leads as you expect. Well you could make a report, run it and review the results. Or you could run a SOQL query.
The benefits of running a SOQL query in this case is that you can retrieve different data sets much quicker. In a Salesforce report, you are stuck with the Report Type you selected when creating the report. With SOQL, you can traverse object relationships in a much more natural way. Get Answers Fast Have you ever been in a meeting and someone asks a data question that no one has the answer to? Well SOQL comes in handy here because you can run a quick …