Skin in the Game

So as we’ve been telling our story about our Lightning implementation, it has become apparent that we aren’t alone in initially being scared of what seemed like a daunting task to move to Lightning.

Looking back on our prep, development and implementation I can see why we had those fears, but I can also see that most of them were due to not fully understanding some of the Lightning concepts. So it was hard to wrap our heads around them.

My fearless leader and product owner, Marshall King and I got to present our story on a recent Salesforce Admins podcast and it was clear in the questions we got after the webinar that this seemed to be a common thread.

One question we got a lot, that I wanted to see if I can help make a bit more clear, is about Lightning Record Pages. In our Webinar we indicated that we made our changes and adjustments to them in production and lots of people were shocked, or maybe surprised is a better word.Lightning Record Page

They wanted to know how we could do that in production and not effect the classic users and I think this very question points to the root of some misunderstanding.

So we all know that Page Layouts are what controls the fields displayed, the order and sections of those fields, what Related Lists show up, buttons, etc. This is true (with minor exceptions I’ll outline below) in Classic and in Lightning.

Lightning Record Pages are NOT the same thing as Page Layouts.

I repeat: Lightning Record pages are NOT the same thing as page layouts.

It took me a while to wrap my head around this but here is where I ultimately got the Ah Ha! moment:

The Lightning Record Page is a SKIN designed around the Page Layout.

  • Elements of the Page Layout (Details & Related Lists) are displayed using components you add to the Lightning Record Page
  • Those Components are like add-on features that give us more functionality to provide our users, in addition to the traditional Page Layout elements.

You could think of it like a car.

The Page Layout is the base model of the vehicle. You’ve got a general body type, you’ve got an engine that makes it run and the rest of the standard features.

The Lightning Record Page is where you get to customize the ‘Extras’ – add a Sunroof or a Navigation System.

Still the same engine and car underneath it all, but now it’s got some great new features that will make your experience driving a better one.

Or to make it super simple – it’s like the case (skin) you put on your phone. Didn’t do anything to the phone but changed the look and feel of it.

So don’t be afraid of working on those Lightning Record Pages in production in fear that your Classic Users will notice something! They will only notice if you actually drill into the Page Layout, rearrange fields, rearrange related lists or move the buttons. So stay away from that and you’ll be fine.

If your users are using mobile, there are a couple of minor things to be aware of:

  • The buttons/actions and order of those on your Lightning Record Page are the same as mobile. So if you make a change it will cascade to the mobile experience.
  • The fields showing on the Highlights Panel on a Lightning Record Page are also the same ones displayed on Mobile so if you rearrange those it will cascade to the mobile experience.

And don’t forget to create that Beta App (explained in my previous blog post) – where you can re-skin Lightning Record Pages to your hearts content and show all the awesome options to your test users and focal groups to help them visualize the possibilities!

Time to get your Skin in the Game!

Pile of hands isolated on white, Caucasian, African American, Hispanic race.

Posted in Salesforce Queen | Tagged , , , , , , , | Leave a comment

Getting Comfy With Lightning

“I’ll be honest, at first, working in Lightning was painful…I didn’t know where anything was. I didn’t understand fully how to manage object Lightning Pages and how to apply them to Apps and Profiles and Record Types. It felt like a LOT of work would be needed to get everything ready for our users.

But how do you eat an elephant? One bite at a time!” – Lightning or Bust

pexels-photo-731264.jpegIn the above blog post, I outlined the approach we took to launching Lightning in our org. Our first step was to get comfortable with Lightning ourselves.

I mean, who wants their wine pairing selected by someone who doesn’t drink wine? In order for us to roll out this new UX, we really needed to work in it, learn it, and be advocates for it. Otherwise are we really serving up the best experience for our users?

Looking back, there are some significant areas in setting up Lightning that we needed to learn how to use and really understand, not to mention functionality in Classic we needed to have an answer for in Lightning:

  • Apps: Whether to promote Classic Apps to Lightning or create new Lightning Apps
  • Classic Sidebar: Best way to replicate this functionality in Lightning
  • Lightning App Builder: Object Record Pages (this was a LARGE focus)
    • Lightning Page Templates (default vs. from scratch)
    • Standard Lightning Components
      • Quick Links vs Related List(s)
      • Highlights Panel (changing fields that display)
    • Buttons and Actions (where the heck did they go and how do I fix them?)
    • Activation Options (cause they are clear as mud aren’t they??)
  • As well as other features such as Home Page options, List View Considerations, Using the new Lightning Email Templates, and the upgraded Notes functionality

So we got out our plastic pails and shovels and applied the sunscreen liberally and jumped into our sandbox to play and LEARN! I’ll share below some of our thought processes as well as tips, tricks and links we learned along the way!


Apps: Whether to promote Classic Apps to Lightning or create new Lightning Apps

When we first began to test, we realized that the concept of the Lightning Apps was so much more important than how Apps work in Classic. In Lightning, you can use the Apps to drive how Lightning record pages appear. This really became the axis for how we approached our Lightning Rollout. Because of this we decided to focus on the ‘Personas’ our users take on every day – what functions they are using the system for and how we could design for those.

Our Classic Apps had become a bit of a mishmash of apps that no one really used (since they could customize their tabs anyway), so although we knew we could ‘upgrade’ a Classic App to Lightning, we opted to start fresh with new Functional Apps.

Another couple of reasons to consider starting fresh:

  • You can’t add a utility bar to an upgraded classic app (as of the writing of this post)
  • Your users can’t take advantage of customizing their tabs if the App is an upgraded Classic App (as of the writing of this post)

With brand new apps in the Lightning Experience we are also able to start turning off Classic Apps as we herd our users toward Lightning!

Here are some resources to learn more about Apps in Lightning:  Lightning Apps on TrailheadSalesforce App Considerations

Classic Sidebar: Best way to replicate this functionality in Lightning

This was a biggie for us. We had several links on our sidebar that were heavily used. And not just links to website, but links that opened reports in the context of the logged in user, as well as links for very specific tasks (example: Log A Timecard) that every single user accesses each week.

We actually tackled this one a couple of different ways:

Rich Text Lightning Component on Home Page: Many of the general links we were able to replicate by just creating a Rich Text Component and embedding the hyperlink as needed. Plop it on the Home Page and you are good to go!

Utility Bars in Lightning Apps: Similar to above, you get some great options with the utility bar. Just add a Rich Text Component here as well with the links you need. The great thing about the utility bar is it is app specific, so you can serve up links/info based on the function of the user rather than the security profile which is how the Home Pages are assigned. This gives you more flexibility to get people what they need as they wear different hats in your org.

For User Specific Reports we retooled some of the reports to make use of either the standard ‘My Records’ report functionality or adding some dynamic ‘My Record’ indicators using formula fields on the specified object. (We use this extensively – here is a great blog post that describes the use case.)

Lightning App Builder: Object Record Pages

This was really a big source for my anxiety. The thought of having to touch all of our objects to set up a Lightning Record Page, to know what will be useful to the users (not just what I prefer) and not be caught in some unending hell of Record Layout changes was a little bit daunting. Frankly it made me want to run and burrow into the ground somewhere where no-one will find me.

But my boss said I gotta eat the elephant so I’m taking this one bite at a time!

Lightning Page Templates (default vs. from scratch)

When you first turn on Lightning, your records default to a very slim Lightning Record Layout. It varies by object, but generally is a tabbed wide left panel, then a narrow right panel. The highlights panel isn’t there; if chatter or activities are enabled, then those components will be there along with the record details and related lists. And it’s not super-clear or obvious that you can choose a different template to start from.

What would be great is if there was some sort of emulator for the admin – where you could try out different templates and page configurations on the fly, then edit from there – almost like we got with the various default themes for MyLightning that we can use and test. But, alas, if it were just that easy admins like us would be out of a job!

So one of the first things we did was go to Settings>User Interface>Lightning App Builder where you can create a new Lightning Record Page from scratch and see which ones you have created so far. But that was pre-Spring ’18! Now you can get to New Lightning Pages directly from the Lightning App Builder (and see which pages are relevant for that App). For testing purposes, we created a Lightning Record Page for every template (wide-left/narrow-right, wide-right/narrow-left, 3-column, etc.), then started adding Lightning Components. It is always better to show something to your beta user group so we prepped all kinds of options!

Just don’t get stuck thinking that out of the box Lightning Record Page is what you have to work with! Here is a great Trailhead Unit on Lightning Record Pages.

Standard Lightning Components

 Next up was getting familiar with all of the Standard Lightning Components available. As I mentioned above, my team really just played with them all. Added them to page layouts, stacked components, used the Tabs on the wide panel, used them on the narrow panel, embedded tabs within tabs, and more! Here is a great blog post from Admin Hero about the out of the box components.

A few I’d like to focus a bit closer on here:

Quick Links vs Related List(s):

Prior to Winter ’18, we had a component for the Related Lists, and a component to show an individual Related List (that s is important). I love that you can display individual lists – this really allowed us to get the info our personas needed front and center without them needing to scroll through a set of lists. HOWEVER – one of the big drawbacks (IMO) about both of these is they only display 4 fields. Our users are used to seeing up to 10 across and we’ve worked hard to cultivate those lists to show the most important info. It was a big stumbling block of moving to Lightning.

But Winter ’18 gave us the Quick Links which was one of the tipping points for us. If you haven’t used them or thrown them on your page layout I encourage you to do so. You get the familiar ‘hover’ experience from Classic (making users feel more comfortable – bonus!), you get all 10 fields, and if you click on the name of the related list in the quick link section, it opens up on a new tab where you can scroll through all the records! WOOT! I can’t imagine life without it! (Dramatic, yes, but I can’t deny my truth!)

Highlights Panel:

You can add up to 7 fields on the Highlights Panel – the first field is the Header on your page, then the other 6 appear below. To add/change these fields, it’s not the section on the page layout labeled Highlights Panel. I repeat – it is NOT the section on the page layout called Highlights Panel. Why they are called the same thing but not used in the same way, I’m not sure. And to be honest it really bothers me. But surely it’s on someone’s list of things to address, right? Instead, you need to create a Compact Layout for the object.

A couple of things about compact layouts: You can’t edit the default compact layout. So you have to create a new one. Then you assign the compact layout by Record Type (not profile – which to me is SO strange – I really would prefer to assign by profile or even by App or page layout).  Also note – the compact layout drives the first four fields that highlight in the Mobile app, as well as the expanded lookup dialogs you see in both mobile and Lightning. So keep this in mind. Here is a help doc that explains Compact Layouts.

Buttons and Actions

So once you play around with Lightning Record Pages a bit, you’ll notice that the buttons and actions are hiding and you can’t figure out how to change/add them. (And along with that, your related lists for Activities and Activity History are not in the Related Lists Lightning Component you added – and the new Notes Related list isn’t here either! Weird.)

Buttons and Actions – these appear in the Highlights Panel – by default 3 buttons will show with a drop-down list – but you can display up to 10 at a time. So decide how many you want to display. If you want to change the order of your buttons and actions, you’ll need to go to each page layout and edit the section for Salesforce Mobile and Lightning Experience Actions. Here you can choose the buttons and actions and the order they display on the page.

To send emails and log tasks or create notes, since those Related Lists are no longer there with the applicable buttons, you have to add the appropriate Lightning Components to the page layout. Once you’ve added the Activities Component and the Single Related List for Notes, you might see the options to Log A Call, New Event, New Task, Send Email for activities, but you might not. Those need to be added to the same section as the buttons above. (So they make you think you are adding them as buttons, but these really appear as actions in the Activities Component. Clear as mud, right?) And the order in which you set them is the order in which they are displayed.

Now this needs to happen for all Page Layouts on an object. (Oye, I know!) I strongly encourage you to decide on the order of the buttons, actions and the order of the activities actions and set them up the same way for each object. Nothing more frustrating to a user than to be on an Account record and Log A Call is defaulted first on the Activities component, but when they navigate to a Contact record, the New Event action is the first one displayed. Users will appreciate a seamless experience.

And here is another help topic on Finding Buttons and Actions in the Lightning Experience.

Activation Options


If you are like me, when you get to the point of activating your Lightning Record Page, this is where your eyes glaze over and you almost want to throw up your hands. The first time I saw the Activation options I pretty much wrote off the Lightning Experience. I was used to being able to assign a page layout to a record type and profile and that was enough! Now there are SO many options. And to have to make these decisions on an object by object basis really seemed like climbing up a steep hill.

But give yourself some time to play with it, tinker with the options and make a plan for your org. There is a big difference between the Activation options for the Lightning Record Page and Assigning security to your page layouts. In fact, that page layout assignment is still very vital – this drives what you see on the details component and in related lists by profile (and record types). The Lightning Page Activation, on the other hand, determines what Components are shown around those details and related lists.

We looked at this as a way to really enhance the ‘Persona’ experience we are cultivating with Lightning Apps and focused on activating most of our Lightning Record pages as App defaults. Let me give a detailed example to help explain: When viewing an Account record, depending on what hat you are wearing that day (what ‘Persona’ you are playing), you might want to see different information and you might be taking very different actions. If you are selling to that customer, you might want to see the Opportunities for that account front and center, you might want a chart or two about open opps and closed won opps and be able to quickly gauge where you are with that prospect or customer. If you are working on a project for that Account, you don’t really care about the sales, but instead want to quickly see customer contacts, active projects, and open cases. If you are in Finance and focused on billing for the Account, you might want to see an account balance, open invoices and have quick access to send emails for collection purposes.

So we created Apps for those functional ‘Personas’, then Lightning record Pages that met the needs described above and activated those pages for the applicable Apps. When I need to Manage Projects, I open the Project Management App and navigate to the Account; when I need to focus on selling, I can switch to the Sales App and voila, my Account view changes and I can now get to the info I need. I still see the same fields and details, but the components are rearranged in an order that better suits the functions I am performing based on the ‘Persona’ I am playing at the time.

You can get more detailed info about Page Activation here, but I also encourage you to just play with it, get comfortable with it and define how you will approach it in your org.

Other Lightning Features

alice-2902560_960_720There are SO MANY other features of Lightning to explore, you could easily fall down the proverbial rabbit hole. Since we had given ourselves a timeline to launch Lightning, we focused on a few features we know would give us some bang and deliver value to our users.

Along with those described above, we put time and effort into user Home Pages (since you can display whole dashboards on them and even have dashboards display or not display based on User fields – think of the possibilities!), and making sure we understood many of the new features such as List View Changes (Kanban view and displaying Charts), new Lightning Email Templates (these are tha-bomb-dot-com), and the upgraded Notes functionality.

Lightning Dashboards and Reports are vital to the Lightning Experience and provide a HUGE incentive for getting users into Lightning so clone a few dashboards, customize them in Lightning with new sizes, new chart options and color options (thanks Salesforce Wizard). These will help provide the ‘Wow’ factor.

I know the above seems a lot to digest – what did you expect when you tried to eat an elephant? Remember – one bite at a time.

For our Lightning Rollout we determined we needed

  1. Apps with Utility Bars for our Personas
  2. To setup Lightning Record Pages for the MAIN objects for those Apps
  3. Home Pages with functional Lightning Dashboard embedded on it
  4. A rollout and training plan that highlights how these changes delivered value to our users. How they could use Lightning to drive business decisions, to serve up the necessary information based on their persona, and how to create efficiencies so they can focus on their job, not trying to figure out the system.

We sat in a room, made a list of the changes to make and got to work. We didn’t tackle all of the objects – just the objects that get viewage – we have plenty of objects that are supportive so people rarely click into them – those can get by with the default for now. Some of it was tedious (I’m looking at you Salesforce Mobile and Lightning Experience Actions on every page layout) but once we rolled through our list, we were experts at setting up Lightning Record Pages and really had a great grasp of how the Lightning UX is designed to work for our users.

Of course we aren’t done and will never be, but all of the extra goodness that we haven’t tapped into yet is just more opportunity to improve our user’s experience.

There’s nowhere to go but up from here.


Posted in Salesforce Queen | Tagged , , , , , , , , , , | 7 Comments

Be Relevant

So I’ve been a Salesforce Administrator for a little while. And by that I mean before there were custom objects and a certification program.

I’ve implemented and managed multiple complex orgs, designed processes, and have been around the block a few times so I feel as if I’m pretty knowledgeable about all the things an admin needs to know.

I recently decided to start studying to get my Certified Application Architect Credential. I have Admin, Adv Admin, App Builder and Sales Cloud Consultant so this seemed like the next progression.

As I reviewed the study materials for the two Architect Exams associated with this credential (Sharing & Visibility Designer and Data Architecture & Management Designer), I realized that much of what I was studying should be required knowledge for every Salesforce Administrator. In fact, I immediately began re-thinking/designing my Org based on what I learned.

I’ll give a few examples:

  • In the learning materials for the Sharing & Visibility Designer exam, I learned about how to manage my sharing model better to avoid sharing issues and things like lock contention and data skew as changes are made to the database. Sounds kinda greek at first but basically if you have a private sharing model, sharing an account with a Group will result in less recalculation required than sharing with individual users when child records are created/edited. Child records inherit the sharing of the parent, so pretend account ABC has 10,000 child records. You’ve shared the Account with Group-Analysts. If you want to share with another user and you do a Manual share with User-Ben, the sharing of every single child record has to be updated to include User-Ben. If you simply add Ben to the Group-Analysts instead, the sharing is already there. You can move people in and out of that Group and the system never has to touch sharing for those 10,000 child records. To expand even further, if you shared with User-Ben, then move Ben in the Role hierarchy, the system has to recalculate sharing again because everyone above Ben has to be given sharing access to those records too….if you have lots of records and lots of users and roles, the system could very quickly get bogged down with recalculating sharing rules and your users could experience loss of record access needlessly!
  • In the learning materials for the Data Architecture & Management Designer exam, I learned that formula fields could be the cause of timeouts when running reports. Since a formula field calculates at run-time, if you create a report and add that formula field to the Filter Criteria, the system has to filter on a that field and calculate it at the same time. So for things that you want to be able to run quickly and efficiently in reports you might want to consider using field updates (via workflow, process builder, visual flow or apex) rather than formula fields. (I had never thought about that!)

Those are just two examples of things I really felt like I should know as an administrator that I learned while studying for application architect.

remain-curious-and-keep-learningWhich goes to show HOW IMPORTANT it is to keep pushing yourself, to keep learning.

So my call to action for you (and myself) is to utilize the tools and resources and keep learning. Take the Trailhead trails for products you don’t use. Read blog posts on functionality you aren’t familiar with (even if you think it might not apply to you). Engage in conversations about topics think you already know everything about. Play around in your Dev Org. Click buttons, try settings you haven’t tried before. Read the help topics.

Be involved and engaged and eager to continue improving. Because once you stop doing those things, you become irrelevant.

(And this applies to all areas of your life, not just Salesforce.)

Be Relevant!

Posted in Salesforce Queen, Thrive Tribe, Working on Me! | Tagged , , , , | Leave a comment

Lightning or Bust

When you’ve been an Admin for a ‘while’, the prospect of using Lightning is daunting to say the least. In Classic I know where everything is. I know how everything works. It’s comfortable. It’s familiar. I can answer all the user questions and knock things out quickly and efficiently.

Enter Lightning.pexels-photo-355989.jpeg

When Lightning was first announced and we got a sneak peak, I was intrigued by the interface. I played with it a bit at the time, but some of the changes felt like hills too steep to climb. On it’s initial release, the trusty tabs were flipped vertical down the left side of the page with a panel opening up – very similar to the Salesforce1 mobile interface. It almost felt like they were making mobile the standard. You had to know the Object Icons to know whether to click on the Star (Leads) or the Coins (Opportunities) since the names were no longer readily visible. This in itself was a hard stop for me and our Org. It was just too foreign and different.

Soon, though, the Tab interface was changed back to the horizontal view we are used to so we decided to take another look. We first focused on where parity didn’t exist between Classic and Lightning. We felt like the only way we could move our users to Lightning was when there would be minimal loss of use. With the Winter ’18 release preview we realized that this might be the time to move.

You see, our Company had been acquired a year before. We were able to bring our legacy technologies with us, but were beginning to have to justify staying on our systems (at considerable cost) versus moving into existing systems where there would be virtually no additional licensing charges. We are firm believers that our growth over the years, including and up to the acquisition is in part a result of efficiencies and insights we have been able to create on the Salesforce Platform. But after being swallowed up like Jonah in the whale, we needed to get our defenses ready to prove that our business unit needs to stay on this platform.

As we prepared to upgrade our FinancialForce PSA installation to the latest release, we decided to test both the upgrade and the Winter ’18 release of Lightning in our sandbox.

I’ll be honest, at first, working in Lightning was painful (see the first paragraph of this post). I didn’t know where anything was. I didn’t understand fully how to manage object Lightning Pages and how to apply them to Apps and Profiles and Record Types. It felt like a LOT of work would be needed to get everything ready for our users.

But how do you eat an elephant? One bite at a time!

Here’s how we turned on Lightning, Beta tested and launched it for our users in a 2 month time-frame:

First, my team (myself, my co-admin and our manager who is the executive sponsor of our system) holed ourselves up in a conference room, got in the sandbox and created a list of the things we needed to do to prep Lightning. It included items like identifying what Apps we needed, which users would get which Apps, and what tabs each App should start out with. We opened up the Lightning Page builder and pored over how it worked. It was easy to figure out the components and how to use/change those, but things like adding fields to the Highlights panel, how buttons are displayed, and how to display/rearrange the tabs on the Activities component are not readily obvious or particularly simple to figure out.

We determined that based on our use of the system we had 4 main ‘groups’ of users: Users who participate in Selling, Users who manage Projects, Users who manage Billing/Accounting and Users who only access the system to log time and maybe use chatter. So we created 4 apps for these user types and then called on Beta-testers from each of these groups.

We held several working sessions with each of the Groups where we spent an hour or two walking through the new/changed functionality, opening up the Lightning Page Builder for the objects they use frequently and making changes/tweaks on the fly. It really grabbed their interest and got them engaged in really caring about how their pages were laid out.

In order to keep these Beta users involved, we flipped on Lightning in production, gave these beta users access to it and setup the new apps and UI for them to use in their daily work. We encouraged them to work in Lightning as often as they could and used a chatter group for questions/comments/feedback. I think we were pleasantly surprised by the amount of feedback we got. Once they began using it regularly they really began asking for things to be moved on pages, related lists made more prominent, etc. They were not shy in giving us feedback. We continued to hold sessions with these users over several weeks. Meanwhile, our sandbox was upgraded with Winter ’18 which was like a manna from heaven! Quick links for the related list really sealed the deal for me and our user base – the standard Related List/Lists components only show 4 fields which is pretty much un-usable to people who are used to seeing 10 across. Without the Related List Quick Links, they were getting frustrated with not being able to easily see the information they needed to do the job.

While our Beta users were testing and providing feedback, we were working on upgrading our most used Dashboards to lightning. We really found that the Lightning Dashboards are a huge hit and being able to add dashboards to the home page was just icing on the cake.

Another thing we did, after realizing that our Beta Users really cared about how the pages were laid out but couldn’t envision different ways of doing it, was to create a new App called ‘Beta App’ (clever, I know). In that App we created from-scratch Lightning pages of all kinds for the objects. wide-left/narrow-right, wide-right/narrow-left, 3 column layouts, you name it. We used tabs, we didn’t use tabs, we put record details prominent, we hid them behind things, and we really just explored the possibilities with page layouts. We were able to use those as examples when we would hold our Beta group meetings to show them different options. Then we would re-build their object page on the fly to meet their needs. One thing that isn’t obvious to an admin is that the first time you click on ‘Edit Page’ in Lightning, you get a page with a pre-set template (wide-left/narrow-right) – while you can’t currently change the template on that default page (vote for the idea here), you can start from scratch and build a brand-new page for that object using the templates provided (or a custom one if you are so inclined). That opened up a whole new world for us. Each of the Beta groups has different layouts for the same object based on how they use that object so we are able to really tailor the experience.

We identified a few things that would need more work to be lightning ready (Conga, I’m looking at you), but they weren’t game changers. Then we scheduled the FinancialForce PSA upgrade in production to happen the same weekend as our Org was getting Winter ’18. On that Monday morning we did a quick fire-drill to add the Related List Quicklinks to all of our object pages, added dashboards to the various home pages and made Lightning available to all users. We then held several Webex sessions to announce the Lightning launch and FF PSA upgrades over the next several days.

Overall, feedback has been great. Lots of compliments on the reports/dashboards particularly. We are currently preparing sessions on Tips and Tricks to make the most out of Lightning for our users to attend where we’ll go over some of our favorite features and let them ask questions and get immediate assistance. We have about 20% of our users in Classic now. The reasons vary – some users claim they are ‘too busy’ and they need to find things fast so classic is easier. Some users didn’t attend any training and/or don’t remember how to switch to Lightning, some users are using IE11 so Lightning isn’t supported. We are working through all of these cases by reaching out to the users themselves and asking how we can help get them on Lightning. We’ve even turned off the ability to switch back to Classic for our Time Entry only users and plan to do this for other groups over the next few months.

Yes, Lightning is different.
Yes, the prospect of tackling all those object pages is daunting.
Yes, you’ll get frustrated with having to relearn things yourself.


Lightning is a super-awesome UI that really focuses on getting the user to the information they need when they need it.
Lightning pages offer SO much flexibility that once you get the hang of them you will never want to go back.
Lightning offers you, super awesome admin, more to learn, investing in your company, your org and your own career!

When you bought your last car, did you wait to find the one that had EVERY. SINGLE. FEATURE. you wanted, or did you compromise on something for another reason (other features, price, availability, etc)?

If you always wait for the one that has everything, keep waiting…I suspect you’ll never be happy with Lightning, but if you can see past the one or two things that you aren’t in love with, enough to take it for an extended test drive, you might just decide to keep it and you may, like me, fall in love with it, faults and all!

Posted in Salesforce Queen | Tagged , , , | 4 Comments

Count the Ways

So on Twitter, the Salesforce twitter account put forth the question: How has Salesforce changed your life for good?

Life Changing

As I’ve read the responses over the past few days I’ve thought over how to best answer the question. There are SO. MANY. WAYS. in which being a part of the Salesforce Ohana has changed my life for the better.

The first and most obvious is my Career Path. But that is really just the tip of the Lightning Bolt.

And because I like alliteration I decided to stick with the letter C! So below is my quick list of the ways in which Salesforce has changed my life for good.

  • Career Path
  • Confidence
  • Challenge
  • Creativity
  • Cooperation
  • Commitment
  • Concentration
  • Curiosity
  • Compassion
  • Collaboration
  • Connections
  • Community
  • Contentment

And if I haven’t mentioned it before, I am convinced all of these are a direct result of the Salesforce Ohana. Of the Community built around Salesforce. Of the Leadership provided by Co-Creators Marc and Parker!

Once again! Thank you! Proud to be #SalesforceOhana

Posted in Salesforce Queen | Tagged , , , , , | 2 Comments