Salesforce

Salesforce Lightning Experience provides so many configuration options that it's hard to know where to start. I'd like to share how I build Lightning Record Pages to help get you started. I create Lightning Record Pages with 3 key concepts in mind: Consistent design Speed Everything they need is in one place Building a Lightning Record Page that delivers these concepts will enable your users to have ultimate productivity. Let's Take a Look: Account Lightning Record Page Contact Lightning Record Page Opportunity Lightning Record Page Notice Anything? They all look the same. I know, that's on purpose 🤓 Here are a few key similarities: 1. Activity and Chatter are in the same place It's common to develop a "muscle memory" when doing repetitive tasks like logging calls or posting to Chatter. ⚡ Put components used for repetitive tasks in the same place. ⚡ 2. Record Details load first Salesforce does not recommend this

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: Classic loads faster Their workflow is slower in Lightning 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

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 Experience Configure Lightning Experience Document all Salesforce processes Create training and support materials Lightning 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  e