How do you ask Salesforce users for feedback? The topic came up during the most recent #AdminHour, when I mentioned asking for user input could actually be quick and painless. The response: but how?
I also have a few new tech tips to help you conduct your surveys:
So, by popular demand, I'm reprinting this blog post from 2015:
If you’re a busy nonprofit Salesforce administrator, developer, or consultant like me, you may be more comfortable creating new fields and planning what Dreamforce sessions to attend instead of consistently and thoroughly prioritizing user feedback.
But listening to users is at the heart of what we do.
Salesforce is easy to customize to meet the needs of our organizations. In order to do that, we need to know the needs of our colleagues, and actively measure whether we are meeting those needs.
A five question survey that takes less than five minutes to fill out, that you send out about every five months, will give you a great baseline of ‘customer satisfaction’ and allow you to track trends over time.
Here’s my proposal for questions (all are on a 1 to 5 scale, with a 1 being ‘not at all’, 3 being Neutral, and 5 being ‘definitely’):
1. Salesforce makes my job easier.
2. I understand how to use Salesforce to do my job.
3. I log in to Salesforce X times per work week on average to do my job (including accessing contacts). Note: In this case, the 1 to 5 scale is used to indicate how many days per work week the user logs in to Salesforce.
4. I have access to the reports, dashboards, and other data I need in Salesforce to make decisions for my job (or I know how to build my own custom reports).
5. My team uses Salesforce to inform our work and decisions.
BONUS: I know how to access support resources when I have Salesforce questions.
These questions can be asked in a Google Form or your preferred survey format. I have had the most success keeping surveys open for about two weeks (making the deadline clear in all communications) and sending several email reminders to encourage completion.
How do you solicit feedback from staff? How often do you ask for structured or unstructured input? What questions work best for you? Inquiring minds want to know!
Let's talk about what every nonprofit wants: free tech support! In this video, I'll walk you through the benefits of joining and being active in the Power of Us Hub. If you're not logging in on a regular basis to take advantage of the ability to get your questions answered, you're missing out! Watch the video and check out these links that I mention in the video:
Are you hesitant about moving to the Salesforce Lightning Experience? Me too. I've been using the current Salesforce user interface (UI) for years, and the nonprofit clients I work with here at Longshore Consulting just need a functional, affordable CRM. A lot of the bells and whistles offered by Salesforce Lightning seem great but two questions remain:
1. When will I have the time to make the switch to Lightning?
2. How do I do my job in Lightning?
In other words, I know I need to make the switch to Lightning, and I don't want to fall behind, but my main goal is social change (and fundraising, programs management, civic engagement, etc.), not running the world's greatest database (although of course I love Salesforce). Sound familiar?
To help your journey to Lightning (which, it's true, will basically be inevitable at some point*), I've curated these resources to help you out - please feel free to contribute more in the comments so I can update this post!
*While technically Salesforce will not retire Salesforce Classic (sometimes referred to as the Aloha UI), all webinars and demos you see from Salesforce, for example at Dreamforce, and all documentation, are quickly being moved to Lightning. Even more important is that no new features are being developed for Salesforce Classic (or at least, the bare minimum of features/improvements are being made to classic). Salesforce wants to do as much as possible to entice everyone to make the switch to Lightning.
1. Review this handy list of Lightning vs. Classic Features. It will super quickly allow you to see what's available and what's not in some areas you may have heard conflicting information about, like reports (and of course keep in mind more functionality is added each release). So as you can see, if you're ride or die with pie charts, you may need to wait or just plan on switching into classic to use those (but P.S. you shouldn't be using pie charts anyways - read 'death to pie charts'). While you're on this page, be sure to Preview Your Org in Lightning Experience and run the Lightning Experience Readiness Check - two great tools that take no time at all!
TIME REQUIRED: 5-10 minutes to review the list, 30 minutes to preview your org, 1 minute to run the readiness check (then 5-30 minutes to review the report).
2. The Lightning Roadmap: That's right, Salesforce has actually posted on the Internet when they're doing what with Lightning, so you can know when you really need to make the switch and can plan accordingly. A few that stand out to me as coming in the 'future', meaning beyond Summer '17, that may be important to nonprofits, include:
- Lists - Mass Inline Edit
- Reports - Search within Folders
- Reports - Printable View
- Dashboards - Scheduling
Just remember, you can always switch back to Classic at anytime to access these features!
TIME REQUIRED: ~10 minutes to review the roadmap
3. Understand what changes you would need to make for the NPSP to work. AKA 'known limitations,' some things will function differently in Lightning if you use the Nonprofit Success Pack and it's important you review the link to see what changes you might need to make so you can continue to be awesome (and do things like create Donation records as easily as possible).
TIME REQUIRED: ~15 minutes to review the list; ~2 hours to make the changes depending on your skill level (instructions are provided).
4. Trailhead Don't get overwhelmed that this trail has 7 badges. You can pick and choose individual units as you need them and remember to use Trailhead to train your end users, too!
TIME REQUIRED: I recommend ~15 minutes a day in the two weeks before you go live with Lightning.
TIME SAVED: All the hours you would have spent writing training materials to train your staff on Lightning!
5. Lightning Resource Inception: There's a lot to learn about Lightning, so it's a good idea to benchmark this post and other resources that you find most helpful. Here are some fantastic resources you'll want to come back to again and again:
- The Salesforce.org Webinar: Migrate to the Lightning Experience
- Healthy Org: Migrate to Lightning Experience
Of course, I most want to know what *you* think of Lightning and all of Salesforce. Longshore Consulting's second annual Nonprofits who Salesforce survey is happening right now, and if you take five minutes to fill it out you will be entered to win over $600 in prizes! Thanks!
You are awesome. You like fun things. Perhaps even Salesforce things. And I like making Salesforce things for you. But I can't make awesome Salesforce things for you if we don't get to know each other better. So...
I'd like to introduce you to the Longshore Consulting second annual Nonprofits who Salesforce Survey. It takes 5 minutes to fill out, and I'll hugely appreciate you if you do! Still not convinced? Here's 5 reasons why you should spend the next 5 minutes sharing your knowledge with the community:
1. Visiblity = Power. Your feedback will allow the Salesforce nonprofit community to understand on a large scale what is working well and what could be improved.
2. It will help you. When you check out the results, you'll know how other nonprofits are thinking and feeling about Salesforce. It'll be like you'll be able to read minds!
3. You can win stuff. Seriously. To thank you for your 5 minutes, you can optionally enter to win one of 19 prizes (!) valued at a total of $600 (!!!). Check out all of the prizes here.
4. You'll get more awesome free stuff! When Longshore Consulting offers free training, affordable coaching options, blog posts, and additional resources to the nonprofit Salesforce community, the number one resource I use to determine what topics I should cover is the Nonprofits who Salesforce Survey.
5. Did I mention I would appreciate you? For real for real. Want to take your awesomeness to the next level? Click here to tweet a message to your friends to invite them to take the survey too!
Happy Birthday Salesforce! As Salesforce turns 18 today, it's important to remember that as any adolescent emerges into adulthood, there will be growing pains. And so that's what we're seeing with Salesforce a bit, as the company-wide keynote events need to serve larger and larger audiences... a few of us are bound to get left out. What am I talking about? On March 7, 2017, Marc Benioff, Parker Harris, and other Salesforce executives held a fiscal year 2018 kickoff event that showed the power of Salesforce to 3 million viewers from Salesforce offices and user groups around the world. Here's a full recap and link to the video.
It was inspirational and fun as always, but the two companies featured, Coca-Cola and Amazon Web Services, might be harder for nonprofits and small businesses to relate to. That left me wondering: how much of what is generally available with Salesforce Einstein is now applicable to nonprofits?
My answer: not a lot, if anything.
There's an extra cost for a lot of the (i.e., most exciting) new Einstein features, including:
Most of the features are designed for Sales.
What is ready for nonprofits that takes advantage of Einstein AI?
Special thanks for Adam Olshansky's excellent Spring 16 recap blog article for helping me to understand all there is to know on this topic! Would you like to learn more? Adam and I did a great overview of the Spring '17 Salesforce release and Salesforce Lightning which you can watch right now here:
One of the most popular blog posts in the Longshore Consulting blog archives is this article, "5 Tips on How to Use Salesforce Sandboxes for Nonprofits" (re-posted below). While it's still a great article, a few things have changed since I first wrote it two years ago, so I thought I'd republish it here to make it easier to find on this site and to offer some new tips and resources.
Here are four additional big improvements and tips to help you use sandboxes with ease:
1. Nonprofits now get a free Partial Sandbox! This is an amazing way to include some data in your sandbox so you don't have to type a bunch of test records. Not sure how to do this? Check out this #AdminHour, starting at 23 minutes in, where I walk you through how to set one up (there's also a ton of great tips about how to test whether your nonprofit is ready to switch to Lightning in that webinar recording, by the way).
2. You can now learn more about Sandboxes with Trailhead! Get tons more Sandbox details and earn some awesome points, and be sure to check out the extensive list of resources to learn more, on this unit of the Application Lifecycle Management trail.
3. There's now an Apex class screen that comes up when you're creating a sandbox that's a little confusing: just ignore it and click 'Create.'
4. Sandbox access: if you have a user who can't access the sandbox, you'll typically need to go in and: a. change their email to their actual email address, b. have the user click through on the email getting them to verify the change to their email address (and on the subsequent screen have them log in with their sandbox username, i.e. being sure to append '.sandboxname' to their email address), c. confirm with the user they're now able to log in to the sandbox, and if not send them a password reset (from within the sandbox setup screen), and d. tell the user to set their sandbox password to the same as their production password for ease of use. Ideally, before generating the sandbox, you should make sure all users are created in production to have as few issues as possible with sandbox logins. Also be sure to have people login to the sandbox the day *before* your staff training so you don't have to spend precious group time troubleshooting login issues.
Good luck on your sandbox journey! For ongoing tips and Salesforce support in an interactive format, be sure to sign up for #AdminHour, which is free the first and third Thursday of every month at 10am PT/1pm ET. Hope to see you there!
5 Tips on How to Use Salesforce Sandboxes for Nonprofits
Salesforce Sandboxes are super fun and helpful places to test out changes to your Salesforce system before you put those changes in place in your live production environment. But when and why should you use them? What do you do with them if they’re blank? When should you refresh your sandboxes? Here are five tips to help you use them without fear: 1. Don’t be afraid – they’re meant to be played in! Just click: Setup –> type ‘Sandboxes’ in the Quick Find –> click ‘Sandboxes’ –> click ‘New Sandbox.’ You’ll likely have Developer and Developer Pro sandboxes available (assuming you’re a nonprofit). Type in an easy name to append to your Salesforce user name, like ‘test.’ Remember when you log in to go to https://test.salesforce.com/. To log in, use: firstname.lastname@example.org and your regular password. 2. Discuss before refreshing. When you refresh a sandbox, you push a new copy of your production environment’s metadata into the sandbox, completely writing over everything that’s in the sandbox already. In English, that means if you added a new field in your Salesforce instance called ‘My New Field’, then refreshed the sandbox, you would now see that field in the sandbox (but not the records or values you had entered into that field). If you have more than one Salesforce administrator at your organization (like most nonprofits), be sure to communicate clearly before you refresh the sandbox. Otherwise, if you refresh it without asking, you could erase the workflow rules, applications, or code another team member is testing out in the sandbox. 3. Use one sandbox as a documentation resource – after all, nonprofits get 7 free sandboxes! Just be clear in the sandbox description field. For example, one sandbox could be named ‘backup’ and the Description could read, ‘Backup of our organization’s Salesforce instance as of February 2015, before we upgraded to the Nonprofit Starter Pack v 3.0, in case we want to refer to any of the configuration before upgrade.’ Note it’s a good idea to log in to your backup sandbox at least once to check all your metadata (configuration) is there before you perform any major changes in production. 4. Know what can and can’t be moved into production. Apps from the app exchange, for example, can’t be moved, but it’s still a really great idea to test them in the Sandbox to see if they’re a good choice for your organization. The full list of what can be moved using a change set can be found here. 5. Quickly create test data if your sandbox is empty. Unless you pay for a partial or full sandbox, your sandbox will not have any records, so be sure to quickly enter a few test records when you login for the first time after creating or refreshing your sandbox. Remember to start with Organizations, then add a Contact, and then add a record to the new custom object you just created if needed (e.g. lookup relationships). This part can be frustrating because each time you refresh the sandbox you’ll need to start over and create these test records again. To make it easier, I keep a few test names on hand (think ‘Kermit de Frog’ and ‘Test Testerson’) and only fill in the required fields. Have any other tips or suggestions? Leave them in the comments!
If these cats are the closest you've come to seeing Salesforce Service Cloud in action, don't worry! #AdminHour is here to show you the basic concepts of the Service Cloud, give you resources to learn more, and encourage you to get paws-on with this fascinating part of Salesforce that's right under your whiskers.
Of course, one of your best resources for learning and getting hands on with the Service Cloud is Trailhead, where you can check out the entire Service Cloud Trail.
Two other things that may surprise you:
1. Many elements of the Service Cloud, like Cases, are free!
2. Many nonprofits can use the full Service Cloud for free!
For more information, check out #AdminHour, explore Trailhead, check under 'Company Information' in setup to see what licenses you have, or check with your Account Executive. You can also comment here and I'll do my best to help!
Want to keep learning more about Salesforce? #AdminHour is fun, free, and interactive the first and third Thursday of every month at 10amPT/1pm ET. Upcoming topics include Salesforce consulting and the Spring 2017 release. Learn more, register, and catch replays right here.
A lot of nonprofits I talk with are absolutely terrified of data migration and data importing. I was at first too when I first started using Salesforce. It's understandable - it feels permanent and like a big project! But with all of the available tools, resources, and support available to you (none of which were around when I started out, I might add, when we had to walk to school uphill both ways), you can totally do this. Just remember to practice in the sandbox and take it one step at a time. With that in mind here are a few additional tips:
1. Clean your data! If you're taking the time to move your data from one place to another, you certainly want it to look sparkling fresh so people will use it, right? Here are some tips:
2. Format your data! Again, watch this video for tons of tips to help make this easy (hint: filters in Excel really help with this!). You'd be surprised how many phone numbers, email addresses, states, etc. need to be cleaned up. Make sure your data will match the data standards and validation rules that you've established - for example, where do you put extensions for phone numbers? Are you using state abbreviations? What about US vs. USA for country?
3. Map your data! I like to keep this simple by using an Excel or Google spreadsheet where the top row has my legacy database field names and the bottom row has my new Salesforce field names (the goal is to have a 1:1 relationship between your legacy fields and new fields in Salesforce, assuming you're importing all of the old data). Then I use the data validation feature in Excel to restrict my data input to just the correct Salesforce values as appropriate (i.e., the right picklist values). I put all of the data to be imported into this spreadsheet in the appropriate Salesforce format for each field.
4. Figure out the import order of your data. Should you put in your Accounts first, by themselves?When in doubt, ask! Note you may need to split up your spreadsheet from step 3 into multiple objects, and confirm that you have at least the required fields from each object included. This step is heavily dependent on which tool you're using, so my advice is to draft a plan and then confirm that plan in the Power of Us Hub. It's typical to start with Accounts (Organizations), then add Contacts, then Opportunities (Donations), but this is different if you're using the Nonprofit Success Pack (see resources below). Some tools can also handle importing to multiple objects at a time, which is great and can save you a lot of stress! The Salesforce Importing Data Quick Start should be able to help, but does not address the NPSP. Don't worry, you can do it!
5. Again, practice in a sandbox! A Salesforce sandbox exists so you can test something before you do it in a more permanent way in production. Data migrations involving multiple objects can be tricky to undo, and you're given about 30 free sandboxes, so test out your skills before you move forward and ***be sure to check your work*** before and after you put it into production.
What's your experience with Salesforce data migration and importing? Favorite tools? Let me know and be sure to come to #AdminHour the first and third Thursday of ever month at 10am PT/1pm ET to continue to build your Salesforce skills in a fun and interactive way!
If you'll be importing into the Nonprofit Success Pack, be sure to watch this webinar and check out this page.
How's your week been? Feeling a little stressed and anxious? As I write this, I just got home from a friend's housewarming party, where the typical response to: 'How are you doing?' was 'I'm ok, considering...'
The 'considering' was code for 'I never thought a Trump Presidency would be this bad.'
So keeping in mind this is a professional blog for social change oriented Salesforce folks, I thought I'd take a technology perspective on what technology ties are to the Trump Presidency, if any, and/or what those of us who work in technology or use technology can do when a new policy takes effect, say to defund the Affordable Care Act or ban Muslim refugees, that we do not agree with. Here are a few thoughts:
1. Hold your technology company's leadership accountable: I could not have been more proud to see that Marc Benioff, CEO of Salesforce, attended the women's march in San Francisco on Saturday, January 21, to advocate for equality. Marc is consistently vocal in advocating for equality, which matters because as a business owner his voice resonates loudly in audiences that are conservative and liberal. He also represents thousands of jobs in dozens of countries. The CEO of Uber, by contrast, has come under criticism for joining President Trump's economic advisory group. Work at Twitter? Maybe the next time you're housing a Republican victory party you could tweet your CEO and suggest it be moved to another locale.
2. Get on the Trail! That's right, there are Salesforce Trailhead modules that can help you be an awesome ally for equality! Check out the new Equality Ally Strategies badge and all of the diversity focused badges! Use the knowledge you learn to support and advocate for your colleagues of all backgrounds at all levels of the organization, in addition to encouraging your organization's leadership to take action like you did in tip #1.
3. Use technology to make social change! In addition to using Salesforce itself to organize your data, members, donors, actions, campaigns, and more to change the world, a barrage of new apps and web sites have flooded the market encouraging you to contact your elected officials and take other steps to stay engaged. But what apps can you trust? What apps won't crash? Only time will tell, but please let me know what you're having success with! Two that I have found so far are: Showing Up for Racial Justice (primarily white people organizing for racial justice; has chapter organizations across the country; why not start one at your company?) and The Indivisible Guide (for organizing to get your message through to elected officials, written by former congressional staffers). I've tried several other mobile apps and online petition sites and many have unclear information about who the founders are and what their affiliations are, and most ask for detailed personal information in order to send a canned email to an elected official, which does not seem to be an effective means of persuading an elected official but is a more effective means of gathering personal contact information to send endless emails that the signer may or may not wish to receive.
4. Take care of yourself. Getting enough rest, limiting screen time and news/media exposure to certain hours, doing activities that bring your joy and fulfillment, and staying connected to community/ pets/family are important. You are worth it. The more healthy and sane you are, the better you will be able to reflect that to the world, and the world could use as much health and sanity as you can spare right now.
What ideas do you have? What apps have helped you change the world? What do you see as the role of tech in the new administration? Good luck out there!
I often encourage the nonprofits I work with to avoid using multi-select picklists, and I always get the same question back: Why? Here are a two of my many reasons why I personally advise against using multi-select picklists whenever possible, why do you use or not use them?
1. They are really difficult to work with in formulas. Example: I wanted to use values from a multi-select picklist field as part of a naming convention for cases. There's not an easy way to do this. In fact, Salesforce help points out there are very few formulas where multi-select picklists can be used. Here they are:
2. They are hard to work with in reporting. Example: I wanted to use race as a multi-select picklist field to allow people to self identify in whatever way they choose. This is great, until I realized that to accurately capture people and that myriad ways to self-identify, I'd have to create a report for each picklist value (e.g., African American, Asian, Latinx, etc.) and then people would be double counted across the reports (e.g., someone who multi-selected African American and Latinx). I would then also need to create reports with all of the possible permutations or report on each person individually to allow for their full individual expression. Instead, I opted to use checkboxes which make reporting much more clear. Also, to be clear, to be able to report on one option in a multi-select picklist requires a super annoying workaround! Ugh! Read how to do that here. How this makes me feel:
So, what are your thoughts? Are there times when you don't need to report on multi-select picklists so you just use them anyways? Are there times when you've used one only to realize later you would have preferred checkboxes? Let me know!
Missy (@missylongshore on Twitter and Periscope) writes this blog just for you!