Sign up for our weekly newsletter, The Technopath Way Tips, here: https://www.technopath.ac-page.com/the-technopath-way-sign-up
Are you ready to take the Nonprofit Cloud Consultant Exam? Use our checklist to find out: technopath.ac-page.com/exam-readiness-checklist

This week on The Technopath Way, Sarah is flying solo with some common pitfalls many newer Salesforce Admins face when looking for experience by volunteering at nonprofits and 8 tips on how to avoid them.
Tip #1: To understand what the nonprofit needs you first need to understand nonprofits and the nonprofit success pack.
If you sit down to discovery with them and you don’t understand how nonprofits function, that’s like being unprepared for an interview.
Study how nonprofits work. This is why I teach about it in my training program. Nonprofits are scrutinized more than for profits — by the government, by the board, by foundations and grantmakers, by their donors, and a lot of information is public. A clean system can be the difference between getting a grant and not.

Tip #2: Start with something simple, choose one pain point
Know your time and how much you have to devote. If you bite off a big project and then realize you didn’t really have time to volunteer, you are leaving the nonprofit with a big hole. Even if your new and it is hard to gauge how long something might take, you may want to block off 4-6 hours on your calendar a week until you are done with the deliverables you’ve defined.
Bonus Tip: Once you have the one pain point you are going to solve for, make sure that the feature being requested isn’t already offered for free by NPSP. Some of the NPSP solutions are too complex or are add on features that cost money. The fees for Salesforce’s donation product, Elevate, may be something the Makerspace could afford, but in the case of integrations, you want to bring them a few options and do your research.

Tip #3: Don’t forget to ask them for a login!
This should be the first assignment you give to the nonprofit. You got to see what you are dealing with now that you know their pain points. You may need to send them instructions on how to create a user.
Bonus Tip: On a Salesforce Saturday for Nonprofits we hosted in the past, Paul Ginsberg talked about what you should do on the first day on the job of being a Salesforce admin for a non-profit. The first thing he said (and we think this is a really great tip) is to create a sandbox. This gives you a copy of exactly where the system was when you started. Also create a backup file of their data, this also gives you a file with the starting point. If you have an integration request like the one at Markerspace, create an integration user if they don’t already have one.

Tip #4: Don’t fear production

A big pitfall we see in a lot of new admins is that they’ve heard the advice about ALWAYS building in a Sandbox first so much that they are scared to do anything in production.
Do most things in a sandbox, but don’t be afraid to push to production.
Especially for nonprofits who are not yet using the system and don’t have tons of data, you are not going to screw what they have up that much, because they don’t really have anything yet.
Bonus Tip: Did you also know that if you really screw something up on you can call Salesforce and put in a case to have a system revert to a prior date. Avoid this like the plague, but know that it is possible.

Tip #5: Build some reports and dashboards

This is one of the first things you should bone up on. The only reason nonprofits want to have a system is for reports. They are scrutinized by so many different audiences and parties...