I’ve been working on Salesforce configuration projects for a few years now, so in tech time, that’s forever right?
I thought I’d share some of the wisdom I’ve picked up over time:
- Just because someone is seemingly more technical or more experienced doesn’t mean they will be able to answer your question. A lot of Salesforce questions are based on product knowledge and if they haven’t worked with that product, then your guess is as good as theirs. Google is your friend. Use that and get answers from blogs, Stack Exchange, the Success Community.
- Ask for help from the Success Community. I’ve never been left hanging. Even if someone didn’t know the exact thing I was looking for, they replied, which always made me feel supported.
- Get requirements! Ask why someone needs something. You don’t have to agree to everything that’s asked if it’s not logical for the business or for Salesforce. Write down requirements so that future generations of people at your company understand what you’ve built.
- Keep it simple. I can’t stress this one enough! If someone asks for a new feature, implement it in a way that will make sense to people who need to upkeep the system.
- Document everything! It’s really fun to just build things, but explain why they’ve been built and make sure people have help docs that help them use it. I often write a document with all my config changes, a technical document, and then a user-facing document.
- Get involved in the community. Sometimes being one of the only “Saleforce people” at your company can feel isolating. Get involved in user groups if they’re near you, go to local events or Dreamforce, follow Salesforce-related people on Twitter.
- Keep learning! One great thing about Salesforce is there is always more to learn. This can sometimes feel overwhelming, but it’s also exciting. Since things are always changing, you won’t get bored. Learn about a new product! I just learned more about entitlements and that was actually pretty fun.
- Trailhead didn’t exist when I started using Salesforce, but I didn’t get into it when it was first launched and I regret it. Use Trailhead all the time. The writing is brilliant and it’s super fun to do interactive challenges. It’s helpful to go through a trail before implementing a related feature.
- Take a step back sometimes and look at what you’ve accomplished. It’s easy to get bogged down in the details when you’re working on specific projects, but take the time to celebrate your accomplishments. #treatyoself
- It’s okay to say you don’t know something. Users and stakeholders will ask things that you may need to research or get help on. It’s 100% okay to say you need to get more info any you’ll get back to them.