Okay I can admit I have been a huge skeptic since Lightning was launched last year! I dragged my heels for over a year before I finally launched Lightning for all of my users. I was determined not to do it or at least put it off for as long as I could. It seemed that so much was missing for administrators and developers, it was easier to stay in the Classic UI. During the day I’m an advanced administrator working closely with my in-house developer and we use multiple sandboxes for development and testing. For us, accepting Lightning has been a slow process because at first it was not clear that the benefits outweighed the drawbacks.
Lightning was initially launched for the purpose of improving businesses that used Salesforce as a sales engine. The improved look and feel to Accounts, Opportunities and Contacts were the big leap forward for B2B companies or even B2C companies that have less focus on service features. Since we are more focused on Service Cloud and our Customer Experience, and on less forecasting and pipeline it didn’t make sense for us to make the leap right out of the gate. This excuse only carried us through the first 3 to 6 months, though. Once the subsequent releases starting adding features and fixing some bugs, we didn’t have much to left to hang onto as legitimate excuses for avoiding Lightning.
Our reluctance really comes down to habit. People get used to working and moving quickly in a particular environment. When the Lightning UI came out it was (and still is) beautiful, but it’s a massive change across the board. The setup section is completely different and there are still details that show up in the classic look and feel.
So here we are over a year later, and we finally unleashed a whole new intranet portal for our users built completely on Salesforce Lightning Experience, and launched primarily in Chrome. For us this browser works best and looks better then IE. In fact it has been a success. All of our users like the look and feel of it. I am actually doing administration in Lightning (shocker!).
Now that some additional bugs have been fixed and a few releases have come out, I have eased into Lightning and I am starting to feel more confident with it. Lightning has some features that are not available in Classic. These include the Kanban view, the Pathing concept (whether for sales or service), the calendar option, and being able to add charts to list views. These are just a few features that have improved the user experience and have potential to improve our level of customer service and even increase our sales.
Salesforce is good about delivering on their promises, which is one of the many reasons why I like the company and working on their platform. It is exceptionally rare to see a tech company actually pay attention to suggestions and recommendations from their community. Not only does Salesforce acknowledge their community, they follow through on the community’s input. Yes Lightning is a big change and that change was nerve-wracking because our environment is highly customized. Change is not always a good thing, but I firmly believe we have made the right decision to finally launch Lightning. But if you plan and launch the transition with the support of your team and your users, Salesforces Lightning Experience can be very successful.
Hey, I almost forgot to mention the Dashboards and Reports are just plain beautiful in Lightning!
Check out these other resources about Lightning:
- http://www.alliancetek.com/Blog/post/2016/10/18/Lightning-Experience-vs-Salesforce-Classic.aspx
- https://www.data2crm.com/migration/blog/salesforce-classic-vs-lightning-experience-quick-switch-to-maximize-user-adoption/
- http://advancedcommunities.com/lightning-experience-vs-salesforce-classic/
- https://salesforce.stackexchange.com/questions/130923/salesforce-lightning-vs-classic-experience
- https://developer.salesforce.com/lightning
- https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/intro_lightning.htm
- https://www.salesforce.com/blog/2015/08/future-of-crm-salesforce-lightning.html
- https://trailhead.salesforce.com/en/modules/lex_migration_introduction/units/lex_migration_introduction_whatis
- https://trailhead.salesforce.com/en/trails/lex_admin_migration
- https://trailhead.salesforce.com/en/modules/lex_migration_introduction/units/lex_migration_introduction_rightforme