Jessie joined Salesforce.org in 2018 to give introductory webinars to nonprofit customers. She now is a Senior Solution Developer supporting nonprofits and education customers at Salesforce. All opinions expressed on this blog are her own or those of the contributors. She's spent 17 years more or less in CRMs and databases, but didn't meet Salesforce until 2011. Jessie co-led the Seattle Salesforce Nonprofit User Group in 2015-2016. She wrote a sh*tty first draft of a novel and hopes to turn it into a screenplay!
I highly recommend The Power of HabitWhy we do what we do in Life and Business by Charles Duhigg to humans, particularly Salesforce administrators and architects.
As mentioned before, at Optimum Energy we have a self improvement book club and we just finished The Power of Habit. The first section of the book is about individual habit formation. The second part is building habits in an organization. Third part is how habits develop and are morally evaluated in society.
While I particularly enjoyed thinking about how to break my own personal bad habits, (Hang on. There are Top Pot Donuts in the kitchen)…. I found myself contemplating how to help users develop the habit of using Salesforce.
Yet across these stories one common theme stands out: community, or as we like to call it “Ohana.” It’s the family-feel of the Trailblazer Community that many Trailblazers cite as the biggest game-changer in their journey. And in no story is that more obvious than the story of Jessie Rymph and Zach Nostdal, two Salesforce Admins who chose to put a ring on it center stage at Dreamforce last November.
It’s not every day that we’re asked to help pull off unforgettable marriage proposals, so with Valentine’s Day around the corner, it seemed like the right time to check in with these lovebirds and ask them to share their story. Continue reading A Salesforce Love Story
You’ve probably heard of “lean management” or “lean manufacturing.” It feels like “lean” is ubiquitous in many industries, but I haven’t encountered the buzz word up here in the cloud. We have a self-improvement book club at my employer, Optimum Energy, and last week we discussed 2 Second Lean by Paul Akers.
“Lean” is the involvement of the entire company in continuous small improvements to remove waste and improve efficiency, as practiced by fanatic Paul Akers.
Good Salesforce administration is one of the most “lean” things you could do for your company.
Every day each of Paul Akers’ employees comes up with one process improvement that cuts out two seconds. 2 Second Lean claims you can revolutionize your company in these tiny increments. And I believe it, because that’s exactly what I do all day in SFDC.
At Optimum Energy, for every energy optimization project, a series of emails used to go back and forth between members of three teams until pricing was agreed upon. Now a user clicks a button, launching a flow which asks them a series of questions and starts an approval process. No information is misplaced in an email folder. All the right people are looped in. That’s efficiency! Continue reading Salesforce Admin: The Leanest Job Ever
Here’s an example of a “simple” flow that uses a Decision element. You don’t need to use flow to achieve the results – you could entirely stick to Process Builder. This flow is for educational purposes only.
Here’s the sitch: I want an automatic email to my customer when we quote a specific product. For example, “Dear Darnell McCustomer, for a limited time only, you can purchase the EDGE widget for $150!”
Caveat: I want this to be in an HTML template, not a Visualforce email, based on the Quote object. I can’t reach the price on the Quote Line Item from Quote in this format.
Flow took me from a “hmm…let me Google that” Salesforce admin to a confident “no record is too far out of reach” admin-eloper (admin/developer). Leadership changed at my company and I had to quickly differentiate myself from my new boss, a Salesforce administrator with way more experience than me. In our initial conversations, he made it clear he would prefer to have a developer working for him. Okay…. one developer, coming up!