Thu, 31 December 2020
It’s the final episode of the Salesforce Admins Podcast for 2020, and this week, we’re bringing you the monthly retro, with a holiday haul of December Salesforce content. We’ll spotlight all the great blog posts, videos, and everything else from this month so you don’t miss out.
Join us as we talk about everything neat and new in Salesforce content from December and a look back at all the things we’ve found that gave us joy in 2020.
You should subscribe for the full episode, but here are a few takeaways from our conversation between Mike and Gillian.
One of the bright spots of this year is it marked the first time anyone from anywhere could participate in Dreamforce. Mike put together a bunch of great videos for the Admin channel, including presentations on Tableau, #LowCodeLove features, and security and privacy center. The best thing is that because the entire event happened online, you can go back and watch anything you missed and still get the full experience.
The New Essential Habits
Essential Habits has gotten a makeover and there’s so much more beneath the surface. We’ve combined the succinct, top-level themes you love with deep dives into everything that goes behind it.
Blog highlights from December
Mike highlighted Flow Orchestrator in a blog post you shouldn’t miss. “This is really what we’ve wanted as admins for a long time,” he says, “the way that Orchestrator is set up helps us automate an entire business process.” Gillian, meanwhile, wants to make sure you don’t miss Lizz Hellinga’s roundup of low-code features you can use right now in your org.
Podcast highlights from December
If you haven’t yet caught Mike’s episode with Madeleine Coutanceau, who has really embraced new features with a declarative approach that lets them get the most out of Salesforce without accumulating technical debt. Gillian spoke to Mary Crozier, a military spouse who created a team to build the Ombudsman Cloud Care app to help manage communications with the families of 5,000 sailors on an aircraft carrier. If you don’t know what an ombudsman is, check out the episode.
Listen to the full episode to hear about our favorite shows, podcasts, recipes, and everything else we’ve been doing with ourselves during the rollercoaster ride that has been this year. Also, our favorite Salesforce features of 2020.
Full Show Transcript
Thu, 24 December 2020
For this episode of the Salesforce Admins Podcast, we’re joined by Mary Crozier, Salesforce Consultant and the Ombudsman Cloud Care Founder. She tells us how she created the incredible app she’s created to champion volunteerism and service.
Join us as we talk about what an Ombudsman is and what they do on a ship, how she saw an opportunity to overhaul the Ombudsmen team’s workflow with Salesforce, and the power of the Salesforce community.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Mary Crozier.
What is an Ombudsman?
Mary came across Salesforce when she was working as a consultant in Japan. As a military spouse, building a career with remote opportunities was essential because frequent moves come with the territory. “Two years ago, I started on my Salesforce journey,” she says, “three months later, I was certified.” At the same time, she was moving to San Diego where her husband took command of the USS Theodore Roosevelt, a Nimitz-class aircraft carrier with a crew of 5,000. While she was to build up her Salesforce experience, she also got to know the ship’s Ombudsman.
“An Ombudsman is a liaison between the command and the families,” Mary says, “not just the immediate families of the sailors on board, but also the extended families—they all rely on getting information from command, and that happens through the Ombudsman.” This is a volunteer role on a ship and with 5,000 sailors, it can be a lot of work. Mary got thinking, wouldn’t this all be a lot easier with some sort of case management tool? She started working on the project in January, without knowing how the pandemic would make the need for a tool like this that much more acute.
How Ombudsman Cloud Care creates digital transformation
When Mary first started working with them, the Ombudsmen had nothing automated, not even an autoresponder on their inbox, so it was an absolutely enormous amount of work for a volunteer position. They were relying on sticky notes and notepads and in the face of COVID-19 that had to change.
Mary created Ombusdman Cloud Care, which is not just an app but a broader initiative to retool the way Ombudsmen work. Previously, they alternated weeks, but crises don’t happen that way, and they had no process for how to work together if a deluge of communications suddenly came in.
The app is primarily focused on case management, making it much easier to track everything, automate key processes, and report on communications to command. This cut down on a lot of phone calls, time spent tracking down information to put into spreadsheets, and a whole lot more. Long story short, Mary and her team brought digital transformation to the Ombudsmen team.
The keys to creating an app quickly
To help this project off the ground, Mary created a tiger team to get things done fast. She had Michael Kolodner, who could really help with the implementation and getting everything working; and Shelley Bolt, who was able to work with the Ombudsmen to understand what they needed and how to help them even more.
The Salesforce community also was a big help, especially for giving the app a security review. “If you’re not reaching out to them for help, then you’re definitely missing out because they’re such a resource—it’s a whole community of go-givers,” Mary says.
Thu, 17 December 2020
A Declarative-First Approach with Madeleine Coutanceau
This week on the Salesforce Admins Podcast, we’re talking to Madeleine Coutanceau, Global Head of Systems & Processes and Salesforce Administrator at simPRO Software. We learn how her company has taken a declarative-first approach to implementing Salesforce wall-to-wall.
Join us as we talk about all the different roles admins have in a business, the importance of having key champions in your organization, and why it’s so important to align what you do in Salesforce with your organizational goals.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Madeleine Coutanceau.
Why it’s so important to be fully involved with your implementation.
“I’ve always worked with the business on the side of processes and moved through to the systems side,” Madeleine says, “so naturally, I fell into the system administrator role with our implementation.” At simPRO, that means she’s in charge of every piece of software that isn’t the product they develop. That means they’re running systems like CPQ, Chat, Pardot, Engage, Knowledge, Adobe Sign, Zinc, Exactly, JIRA, and more.
The secret behind managing so many different Salesforce systems is a great implementation. “We were told to drop everything and be part of this implementation, 24/7,” Madeleine says, so they were involved with everything from training to putting together procedure documents. That really gave them the expertise they needed to lead and train teams across the world.
How to automate without a developer.
When Madeleine’s company decided to adopt Salesforce, she was told from the start that she wouldn’t have a developer to work with. “We develop systems for our own clients,” they said, “we’re putting you on Salesforce so that we can manage this internally, not have developer resources that take up a lot of time.” That meant they needed to build everything with minimal code so they wouldn’t need extra help, so they leaned on Flows.
“I feel like my life changed at work once my Flows clicked into place for me in Salesforce,” Madeleine says, “suddenly, I realized I had all these processes I could just automate—I got a little bit Flow crazy.” This process didn’t happen overnight, however, as it involved a lot of trial and error and really digging into the nitty-gritty to understand Flows from the ground-up.
The magic of Flows.
When you get Flows working for you, it can seem like magic. For Madeleine, a big challenge was removing users from the org for a company with offices not only in Australia, but also in New Zealand, the UK, and the USA. This process used to involve setting alarms for the middle of the night, but she was able to make it happen automatically without writing a single line of code.
Communicating process changes can always be tricky, especially in a large organization with a multinational presence. Madeleine and her team solved this problem by setting up private Chatter groups for each country that are used just for communicating process changes. Whenever they create a new user, they simply log in and subscribe them to the appropriate channels to make sure they get the notifications they need to see.
Love our podcasts?
Subscribe today or review us on iTunes!
Full Show Transcript
Mike: Welcome to the Salesforce Admin's podcast, where we talk about product, community and career to help you become an awesome admin. This week I am talking with Madeleine Coutanceau, global head of Systems and Processes and Salesforce administrator, about how her company has taken a declared first approach to implementing salesforce wall to wall.
Madeleine Couta...: Thanks for having me.
Mike: Let's start off, I love talking about this idea of declared it first, but before we dive all the way deep into that, why don't we get started with what you do.
Madeleine Couta...: Sure. So I'm the Global Head of Systems and Processes at simPro, and I am one of a team of two of admins for the business. I've worked at simPro for about nine years now in a couple of different roles, and this is my most recent role that I've been in for probably about five years, six years or so. I've always worked with the business on the side of processes and sort of moved in through to the system side, so naturally I sort of fell into that system administrator role with our implementation.
Mike: Wow. So if I'm looking through and I see your title as head of sales, you're also the salesforce administrator?
Madeleine Couta...: Head of Systems-
Mike: Head of Systems.
Madeleine Couta...: ... and Processes, not sales.
Mike: Systems. Sorry, I heard you wrong.
Madeleine Couta...: Yeah.
Mike: That sounds even bigger.
Madeleine Couta...: So Head of Systems and Processes.
Mike: Okay. All right. I'm always interested in what admin titles have, right, so I like that. So you mentioned head of systems, what kind of products and systems do you use?
Madeleine Couta...: So I look after the systems on the side of our internal systems on the operational side. So we are a software company, there is a big side of the business that I don't really deal with on the systems side, that is of course our developers and product. But when it comes to the operational side of our operational entities in the different countries, I look after those internal systems. So we're talking about salesforce and its sort of connected ecosystem, so we use a lot of salesforce products, all the way from sales, service, CPQ, Chat, Pot-Ot, Engage, Knowledge. And then we have those installed apps across the host system as well like Adobe Sign, Zincked, Exactly, we connect with Jira, Rollout Palpa, that kind of thing. So it's quite a big sort of suite of systems that I essentially look after.
Mike: I would say. I feel like when I look at the customer 360 wheel, you're coloring in all of our products.
Madeleine Couta...: Yeah, yeah.
Mike: You're getting close to collecting them all, good job.
Madeleine Couta...: Yeah, I feel like I should get a prize at the end, where've you got them all.
Mike: Oh you do, you do. So with all of that and all of the users that you have across many continents, how do you build and manage this robust system?
Madeleine Couta...: It's tricky, but I think we really had a really fantastic implementation. And not only did the team that implemented for us do really well, but I guess we were a part of that journey the whole time. So me and my other admin, we were pretty much told to drop everything and be part of this implementation, and do it 24/7. Every day we were in on the project, making sure that we were learning the whole the system. And then across, we essentially ensured that we did all the training, we put together all the procedure documents, any kind of LMS learning we put together as well, and essentially documented the whole system on a training level and how it was all put together.
Mike: Yeah, wow. Wow. Right now admins are all jealous that you've got a bunch of users that are embracing change like, "How do we sprinkle them around the world?"
Madeleine Couta...: I think I feel like I've been spoiled to be honest.
Mike: Absolutely. So being a software company, I'm guessing you were all about code with salesforce then?
Madeleine Couta...: No, not at all. So I was pretty much given the approach of, "You will not have a developer, we develop systems for our own clients. We're putting you on salesforce so that we can essentially manage this internally, not have developer resource that takes up a lot of time. You guys are admins." I don't know code, my other admin doesn't know code. "You guys are going to have to ensure that you guys can administrate it without a developer," and that's what we've pretty much done from the beginning.
Mike: Wow, so wall to wall with all those products, and you haven't written a line of code.
Madeleine Couta...: Well, we maybe have one little bit of code with our action plans, I think.
Mike: There's always a little bit.
Madeleine Couta...: It's a tiny bit.
Mike: [crosstalk] had a little bit, right?
Madeleine Couta...: It's biting me in the butt thought, it's causing me problems. Yeah, I don't have a resource, so I have pretty much tried to go as much no code as possible.
Mike: So then I'm guessing a lot of what you do is through flows?
Madeleine Couta...: Yes. I think my... This sounds a bit silly but, I feel like my life changed at work once my flows clicked into place for me at salesforce. And all those things that I had been wanting to do for the last couple of years, that I was like, "No, I can't automate, sorry," saying sorry to users, "I know that's a lot of clicks, I know that this is a big process." Suddenly it was like, "Oh my goodness, I have all of these processes that I could just automate with flows," and it was very exciting. I got a little bit flow crazy, now I'm just trying to tidy them up a little bit.
Mike: Yeah, I believe the official term is flownatic, that's what I've heard.
Madeleine Couta...: Oh, I like it, I like it.
Mike: So I'm sure there's t-shirts out there to be a flownatic. Brian Kwong can probably... He has a wizard cast, you should be on his wizard cast because he will talk to you about being a flownatic. I'd be curious to know, I want to dive a little bit deeper into that flow, because I would like to know what you mean by, when flows just clicked for you.
Madeleine Couta...: I started learning on flows with the classic version, so before they brought the lightning improvements and changed-
Mike: Oh, the hard version.
Madeleine Couta...: Yeah. So I found it was really difficult to find a lot of documentation on it, to be honest. I had to watch a lot of YouTube videos to sort of understand variables, and the elements, and all that kind of stuff. And it wasn't laid out very nicely, and a lot of the lightning side of things now, they create all these variables and record variables for you and everything, which is fantastic. All of the things that I was like, "Why doesn't it do that," it does it now, which is great. But I think because I'm a logical person, it just took me a lot of goes to really and just try and try and test the process to really finally have all the pieces click together for me.
Mike: Yeah, I feel flow builder is very much a learn by doing.
Madeleine Couta...: Yeah.
Mike: I've done a few of the trailhead modules, and I was, "I have no idea what that was. Oh, that's neat. Oh, that makes sense now." And it's one of those where until you do it, do you really understand it, and you almost just have to absent of what the tool can do, just think of, "What is something I'm trying to solve for, and what is something I've never been able to do?" I thought it was so fascinating that you could do decisioning, and screen flows, and loops, like you could have a look to see if a record exists. And I was like, "Oh man, that's all the stuff admins have so wanted at our fingertips," and looked at all of these 400-line triggers on stack issues, like, "Okay, well I've got to figure out a way to put that in my work."
Madeleine Couta...: Yeah, it really makes you feel like the possibilities are, maybe not endless, but close to when it comes to doing something without code. And just those little things where a user has to click or create these records that look really, really similar every time, and you'll suddenly be able to create a flow to be able to solve that, which feels really good and the users love you for it too, and you look like a magician.
Mike: I'm telling you. Now, I think a lot of, and true to kind of the admin mantra, you're always thinking about how you can improve things for the user. I'd love to know, have you used flow to help your daily job be any better?
Madeleine Couta...: Yes. Yeah, so there's one that didn't take me long to create, was actually probably one of the quickest flows I've created, but it has a really bit impact on me and my admin. So we are located in Australia in Brisbane, and our head office is here and we have one of the businesses here as well, but we're also located in New Zealand, U.K. and the U.S. and those guys of course are on a completely different time zone, or you guys are on a completely different time zone to us. So we're dealing with users that are all around the world, and we're only admins in Australia. So we used to when there was a termination or something like that where we had to freeze a user, or deactivate a user, sometimes it would be a 3:00 AM or a 5:00 AM wake-up call on a Saturday morning to set an alarm-
Mike: Oh no.
Madeleine Couta...: ... we'd get a chat, or you'd set an alarm to quickly wake up, bleary-eyed, open up your cellphone admin app and freeze them, then go back to sleep. It's not fun. So I created a flow, which I push from my salesforce admin cases, that essentially allows me to assign a user to a case, and then uses that user to then book in a time and date to freeze them, and it's awesome. So I use a pause element, and then essentially I create a screen flow. I've got two flows, screen flow that essentially allows me to input the details, the user, the time, the date, I submit that and then it pushes through to a second flow which does a pause and waits until that date, and then freezes them.
Madeleine Couta...: It's awesome.
Mike: That's just wonderful anytime. And speaking as somebody who I once had, I think a few weeks of scrum calls, where I had to be on at like 4:00 or 5:00 AM, I actually brought, at the time I was working in office, I actually brought a coffee maker into my office, because I was like, "I don't want to have to... I want to sleep the maximum amount of time at home, get up come to the office and not have to waste time making coffee at my house. And I can do it during the call."
Madeleine Couta...: Any way to save time.
Mike: Any way to save time, yeah. And lo and behold, I should've had flow. So one of the things that you talked about early on is, rolling things out and being declared of, I'd love to jump into how you tackle documentation-
Madeleine Couta...: Yeah, sure.
Mike: ... and how you kind of bring those changes to your ever-happy, always open to change users.
Madeleine Couta...: Okay. Okay, maybe I put them in too much of a good light. No, no, no, they're great.
Mike: They're all going to listen to this and be like, "We're not going to do any of the things she sends from now on."
Madeleine Couta...: They're going to be horrible.
Madeleine Couta...: Like, "Oh, we're too easy, let's challenge them more."
Mike: Arms folded, "Oh, I need 10 check boxes."
Madeleine Couta...: No, no more check boxes. Okay, so documentation. We deal with our documentation using Docs, but also then publishing them through salesforce using Files to Library. So we have Library set up for each of the different teams, we have general libraries as well. We share those out with the teams, and then we upload new versions depending on changes. We also manage some of our projects through a little project management tool on the side, outside of salesforce as well, using Asana. I really like Asana. And managing different tags, how different pieces of the system and a bunch of different projects and little changes all happen, and we just make sure that we update all the procedure document that relates. If we've got email templates, we realize we need to change all of that as well.
Mike: So how do you find time to create all this documentation, because that's the question that I think only do Markle have essential habits that we do on Fridays, and you can watch that on Trailhead Live.
Madeleine Couta...: Yeah.
Mike: And we talk about documenting, right? Like, when you make changes to your org, document it so that you know you made the change, and your users have insight to what this field is and what that field does. And inevitably, and I'm the same way, it's like eating your broccoli.
Madeleine Couta...: Yeah.
Mike: You're like, you just want to make the change move on, "Oh, now I've got to write down how we did it." How do you quantify that or work that into your day?
Madeleine Couta...: To be honest, I'm probably not so good at that piece. So not every... I mean, when it comes to procedure change and your process change for the users, we're really great at documenting that, but when it comes to really minor edits or changes in our org for our own salesforce documentation, I have to say that is a grind. That is really hard to get done. I try to put aside time every week to ensure that we get that done, but I know I'm well-behind. So I think I have the same issue as probably every admin, including yourself.
Mike: Yes, absolutely. And I think just because the amount of... Well, for me it was the speed, like the ability to go into a Sandbox, make a change, you're like, "Oh cool, is that what you want?" "Yes." Okay, and then push production and everybody's happy, right?
Madeleine Couta...: Yeah.
Mike: It feels a little bit sometimes like being an admin is like working in an emergency room,-
Madeleine Couta...: Yes. Get it done.
Mike: ... like you want to triage everything and fix it and get it done, and it needs to be a little bit more methodical like building a house, you've got to have blueprints, and plans, and...
Madeleine Couta...: Yes. And I think because being one of a small team and having that very agile approach, I probably don't have enough experience in that more methodical way, but I probably just need to actually find out what is the best way to do that and be a bit more... thinking better about what I'm doing in my org to then document that. But I mean, I try to do it as much as possible, but you're right, "Here's a problem, oh, I've got to solution." And I love pushing out a fix, because I love solving those problems. But as everything gets bigger, you definitely need to make sure that you are doing the best thing for your org overall.
Mike: Yeah, absolutely. So I would love to kind of wrap on, you've been in the salesforce community for a while, you've been on a journey, you have an amazing resume. I mean, you manage a lot of systems. It sounds like you have a receptive user base, you're doing documentation, at least as well as we can, but what advice would you give to admins who are maybe just starting at a new position or coming into an org, based on your experience?
Madeleine Couta...: Well, definitely if you're being assigned as an admin on an implementation, I would definitely make sure that you are pushing yourself into that implementation as much as possible. I found that knowing exactly how things are set up is really crucial to your full understanding of how the org is created. I mean, I've only been in one salesforce implementation, and I've only been on salesforce org, so I only know from my experience, right? But if you're coming into a business that already has salesforce, I mean, you'd hope that that was documented well, but I guess that's a luxury probably with a lot of implementations. But I just think take stock of what you've got, see how the business is running.
Madeleine Couta...: It's an ever-changing challenging role, but it's very, very interesting I have to say. Being a salesforce admin is never boring.
Mike: I would agree, and I also think to me that's really, I don't want to say fun, but the part that excites me the most is, it's a job where you're not sure what tomorrow looks like, but you're confident that you have the skills. And if you don't, it's a new challenge, right, and it's something to try and you're always building on what you've done. I feel even when I worked really hard on Sales Cloud roll-outs, "Okay, now we're doing Service Cloud." "Oh boy, I don't know Service Cloud," "Okay, well, but you know the fundamentals and you've done Sales Cloud, right?" And so it's not like you're starting from scratch with a new adventure, right? It's almost like-
Madeleine Couta...: Totally.
Mike: It's like getting a new modified job every single day. And then the business process changes, and you're like, "Okay, cool. Well, here's everything I learned from the last time I built this app, and now I can move those experience and that lesson into the next app that I build, so I'm excited." That's what I loved about it.
Madeleine Couta...: Yeah, yeah. And it always presents with new challenges every day, and it's really good and keeps you on your toes for sure.
Mike: Absolutely. Madeleine, I want to thank you for taking time out to join us, and it sounds for sure like you're going to be busy today, whatever day it is with all of those users, and especially when the podcast goes live, they'll find out how incredibly exceptional they are.
Madeleine Couta...: They are, they really are.
Mike: Shop them around, and maybe we'll have them all get on the podcast and give advice to the other salesforce admin users about their receptivity to change.
Madeleine Couta...: Yeah. And I think having those key sort of salesforce champion people within each team, really, really helps that as well, because without them and without managers flowing all that information up from their users, it would just be chaos I think. So that's important for us as well, especially since we're such a small team. So yeah, they are great.
Mike: Yeah, absolutely. Yeah. Having your users voice every day all the way up to the admin, is key, so fabulous. Well, this was super fun chatting with you, I'm so glad we got... And it sounds like probably in a year from now, we'll have 10 times as much for you to talk about.
Madeleine Couta...: Hopefully.
Mike: And we'll have you back on the podcast.
Madeleine Couta...: That would be amazing.
Mike: So it was great having Madeleine on the podcast. Three things I learned in our discussion, first, you know what, salesforce admins have different titles. How cool is it that she is the Global Head of Systems and Processes? I love it. Two, she mentioned key champions are super helpful as they roll out different features and functionalities, and I think that's super important too. In fact, in the show notes I am going to link to a blog post I did about building your internal advocates. And then three, and boy do we bring this home in a lot of our presentations, I love how Madeleine pointed out aligning salesforce goals to the goals of the organization. That was a key driver in all of the successful things that they have rolled out at that organization, and I just think it's super, super important for every admin to do.
Direct download: A_Declarative-First_Approach_with_Madeleine_Coutanceau.mp3
Category:general -- posted at: 3:00am PST
Thu, 10 December 2020
This week on the Salesforce Admins Podcast, we’re joined once again by Shannon Hale, Platform Product Leader at Mulesoft. We learn what Mulesoft Composer is and what it can do, why she’s so passionate about making admins’ lives easier, and what the Shannon Hale Salesforce SWAT Team is.
Join us as we talk about what Mulesoft Composer can do for you and your org, and why admins hold a special place in Shannon’s heart.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Shannon Hale.
Integrating multiple systems
“It’s always a challenge when you have data in one system and data in another system but your workflow doesn’t necessarily take that into account,” Shannon says, and if you don’t have any sort of integration you’ll find yourself manually entering data from one to the other. Not only is that highly prone to error, but it’s time-consuming. “Anytime you can automate those processes,” she says, “you can save yourself time and you can streamline those business processes.”
To solve this problem, Shannon and her team are building a new Design Time tool, Mulesoft Composer, for building integrations across different systems to connect your data sources together, developed specifically for admins. “You’re just a person, trying to do a job, and your job happens to have data in two systems and you want them to talk to each other,” she says.
Why Mulesoft Composer makes Integrating easier
When it comes to how to put Mulesoft Composer to work for you, Shannon says to start with the things that are time-consuming or error-prone in your org—anything that happens frequently. So you can identify where you need your integration to happen, then which data you need to move over and whether or not there are multiple steps involved (like sending an email or Slack message), then switch over to the composer.
Mulesoft Composer comes as a Managed Package, so it’s embedded directly into Salesforce, so the next step is to start a new flow and create your integration. From there, you log into both systems, choose the fields, objects, and triggers you want to work with, and then choose an action and a system to do it to. Think about it like Flow Builder, but for creating integrations between two systems. At the end of the day, this is about putting tools that were previously only in the purview of developers into the hands of admins to help them work their magic and make things easier for everyone.
Listen to the full episode for more info about how to get executive buy-in and why Mulesoft Composer is a lot like the point-and-click tools you’re already used to using.
Wed, 2 December 2020
On this episode of the Salesforce Admins Podcast, we’ve got Sarah Pilzer, Director of Operations at Country Dance and Song Society and Golden Hoodie winner. She tells us how she uses automation to serve her users.
Join us as we talk about why it’s always best to start with standard functionality, how to borrow from what people have already built, and how she checks in with users to make sure she’s building what they need.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Sarah Pilzer.
How Sarah puts Salesforce to work for her organization.
As Director of Operations at the Country Dance and Song Society in Massachusetts, Sarah is in charge of all office procedures, including running their Salesforce instance. “I am the in-house Admin, as well as doing all of the building and architecting necessary to create the systems we need,” she says.
Sarah’s organization uses Salesforce in a bunch of different ways depending on the department (sound familiar?), including registration and staffing for their arts education classes and fundraising. Making that work involves a mix of using what’s already in the Nonprofit Success Pack and building some custom solutions.
When to use standard vs. custom functionality.
To figure out what will work best, Sarah recommends sitting down with your users to find out what they do now and how it’ll best translate to Salesforce. “I try to start with an out-of-the-box feature if that’s possible,” she says, “if it’s already built, we should take advantage of that. We can save our time to work on other issues at the nonprofit like our mission and vision and really get to the programming if we’re not spending all of our time building tools.”
Sometimes that means trying a standard feature and seeing what the limitations are. For their program registrations, they started out using campaigns to track who was in which program but ran into some limitations when they also wanted to track donations. In the end, Sarah ended up building out a custom camp program object that fit their needs better. “My advice would be to start standard if you can, and if you find that’s not fitting your needs you can go custom,” she says.
Verify that automation helps your users.
One thing that helps Sarah help her team is leaning on the automations already built into Salesforce. Flows are a big part of that, including Screen Flows that walk her users through the automation. For the camp registration example, they have a Screen Flow that they expose to external users to create a self-service feature. This frees up time on the backend as they previously had to rely on paper forms that would be manually entered into the system.
“I think it’s really important that the automation works for who’s using it,” Sarah says, “so if I’m going to build out automation, I need to talk to the end-users first and make sure that what I’m building isn’t going to make their lives harder.” That’s a combination of conversations with her internal people, and beta testing on forms that go out to the community before they go live. Sarah isn’t afraid to call a quick twenty or thirty-minute meeting to make sure she understands what her users want, and she’s established an internal Salesforce user group to check in every month.
Direct download: Building_Automations_That_Work_with_Sarah_Pilzer.mp3
Category:general -- posted at: 12:20pm PST