Aller au contenu
Radio Logo
PodcastsBusinessSalesforce Admins Podcast

Salesforce Admins Podcast

Mike Gerholdt
Dernier épisode

100 épisodes

  • Salesforce Admins Podcast

    What Salesforce Admins Trust AI to Do Now (That Seemed Outlandish a Year Ago)

    19/11/2026 | 18 min
    Today on the Salesforce Admins Podcast, we talk to Jennifer Lee and Kate Lessard, Lead Admin Evangelists, and Joshua Birk, Senior Director of Admin Evangelism at Salesforce.
    Join us as we chat about how our relationship with AI has changed over the past year.
    You should subscribe for the full episode, but here are a few takeaways from our conversation with Jennifer Lee, Kate Lessard, and Joshua Birk.
    AI has gotten better at building things
    For Kate, the biggest difference when it comes to AI is that she trusts it to do more things. While she used to make sure that an agent never did anything without her approval, she's much more confident in relying on the guardrails she's put in place.
    Jen has had a similar experience. "A year ago, if AI asked me if it could create a record or touch my Salesforce org I'd say no way," she says, "I'm going to need to see everything." Nowadays, she just needs to make sure it's on the right track before letting it go off and create something. But AI has been amazing for creating demos, especially for testing and creating dummy data.
    Trusting a personal assistant agent
    Josh, meanwhile, has been taking advantage of AI as a personal assistant. It's allowed him to reclaim his inbox and stay on top of things. "I can use my inbox on a daily basis, without having to spend the morning deleting hundreds of emails before I can read something that is actually useful," he says.
    However, he's quick to note that his personal assistant agent has very clear boundaries on what it can and cannot do. "If it goes wrong, how quickly can you recover from it?" he asks. An empty bank account is a lot harder to fix than an email that went to the wrong person.
    Getting financial advice from an agent
    For me personally, this is the year that I've felt comfortable having an AI look at my finances and make some suggestions. It's helped me adjust my retirement savings and plan for the future, and I couldn't say I would have done that a year ago.
    What about you? What are you doing with AI that would have seemed ridiculous to you a year ago? Make sure to listen to the full episode for more from Josh, Jen, and Kate on how they're working with agents. And don't forget to subscribe to the Salesforce Admins Podcast to catch us every Thursday.
    Podcast swag
    Salesforce Admins on the Trailhead Store

    Admin Trailblazers Group
    Admin Trailblazers Community Group

    Social
    Josh on LinkedIn

    Kate on LinkedIn

    Jen on LinkedIn

    Salesforce Admins on LinkedIn

    Salesforce Admins on X

    Mike on Bluesky social

    Mike on Threads

    Mike on X

    Full show transcript
    Mike:
    This week on the Salesforce Admins Podcast, we're doing a November retro with three of my Salesforce admin evangelist teammates, Jennifer, Josh, and Kate. Now, here's what I asked them. I wanted to know what they trust AI to do today that would've sounded just a little outlandish a year ago. And I think you're going to be surprised maybe what the answers are.
    We also talk about where everyone's going to draw the line with AI, and Josh shares a simple test for deciding how much access to give an AI agent. So, if you're a Salesforce admin figuring out your own comfort level, you'll probably recognize yourself somewhere in this conversation. And in case you haven't already, make sure you follow and subscribe to the Salesforce Admins Podcast, whether you're listening to us on iTunes or on the podcast app, or if you're watching this on YouTube, be sure and subscribe to the Salesforce Admins YouTube channel.
    So, with that, let's get my fellow teammates on the podcast. So, everybody, welcome to the podcast. It's November and time to talk some AI with fellow admin evangelists. So, we'll get started. Jen, could you do a brief introduction of what you do at Salesforce?
    Jennifer:
    Sure. Oh, I do all sorts of things at Salesforce, whether it's blogs, presentations, videos. I've been doing videos galore. You probably are sick of seeing me with AIforce in Action, but that's been my thing lately.
    Mike:
    Never sick of AIforce in Action. Josh?
    Josh:
    We all have very similar roles, but humorously I've had a couple of conversations this week alone about how do you keep up with the platform? And it's like, well, thankfully a large part of our job is research, right? We get time to actually go in and research and to keep this on topic. Gosh, AI is making that so much easier. So, talking to AI and creating content, that's what I do.
    Mike:
    Oh, I thought you were going to say pressing two.
    Josh:
    There's a lot of pressing two, yes.
    Mike:
    Pressing two. And Kate, certainly last but not least.
    Kate:
    Oh, well, thank you. I do a lot of the same things just mentioned. I have not been doing videos galore lately. I think the thing on the team that I do that's maybe a little bit different is that I own the workshops for our team. So, I've been spending a lot of time on our hands-on workshops lately and creating new AI force content to get more admins hands-on.
    Mike:
    Mm-hmm, fun. Obviously, it's crazy because just a few years ago we were barely talking to AI and then we had some workshops where we had thousands of prompts that we were building. And now I feel like every day there's at least every part of what I do, AI touches some part of it. Either it's advice that I need or research on something or to Josh's point, I'm just telling it to go do something while I switch a screen and go tell another AI to go do something.
    I think it's fascinating how with very little training or no training, AIs just permeate our lives and especially as Salesforce admins. So, the question that I'm going to pose to everybody, and Kate, we're going to start with you, is when you look back a year ago, what's something you trust AI to do now that a year ago just seemed outlandish?
    Kate:
    Man, and it really does come down to trust, right? I think that over the past year for me, the biggest shift has been how I interact with AI. I think I've gone from just asking how to do something and asking a question to actually having a level of trust to have AI go and do the work for me. And I think a lot of that really comes down to the capabilities of the headless toolkit and still being able to have that kind of direction and judgment and that control over what's going to happen.
    But while I can provide that direction and judgment, I don't necessarily feel the need to execute every single step anymore. And that's been a really big mentality shift over the past year.
    Mike:
    Mm-hmm. Wow. Okay. We'll continue on. Josh, I feel like you're probably doing more with AI than all of us combined, but-
    Josh:
    Yeah, I recently made the joke. Somebody asked if I use an agent at work and I'm like, "No, I don't use an agent at work. I use five, some of them simultaneously." I just had one agent, one AI proof the other AI's work and it actually found a whole bunch of flaws on it, which I wouldn't say is something I wouldn't trust AI doing in the past. Although I think previously, I would force myself to be the human in the loop and not necessarily put AI, checking AI, checking AI kind of thing.
    So, that's sort of new. For me, the big revelation that I'm so comfortable with is the surprise to me is AI is in my inbox. AI is in my Slack. AI is in my calendar. And if you had gone to early AI Josh in his speeches, I would be like, "Why would you even want that?" But I use a personal assistant and I've reclaimed my inbox. I can use my inbox on a daily basis where it used to be I would spend a morning just deleting hundreds of emails before I could even read something that was actually useful.
    Now I wake up, Slack is actually in my inbox and it's like, "Hey, here's all the important things you actually need to address right now." And for somebody who sometimes has a little bit of an attention deficit problem, AI adding a little bit of focus has been very helpful to me.
    Mike:
    Oh, sometimes.
    Kate:
    I remember those early Josh AI speeches about that.
    Josh:
    I have been the warning sign in the past. It's true.
    Mike:
    I was, as you were explaining that, Josh, thinking of all of my friends that easily a year ago were just tired of everything, every application having an AI component to it. And I think it's because it didn't do anything, anything better than the search bar already done. But that was a year ago. Now, now it's almost the starting point for every application that you launch on your phone or on your desktop. Jennifer, how about you?
    Jennifer:
    It's really been a productivity booster for me. I think a year ago, if AI asked if I could create a record or touch my Salesforce org, I'd be like, "No way, dude. I'm going to need to see everything." You make the recommendations like Kate, I will go in and do it. And I've been using a lot of Claude lately to do some of my demo work. And first I had it set to show me what you're about to do, get my approval.
    And then after just reviewing it, I'm like, "Okay, you know what you're doing. I'm going to let you go ahead and do." And it's just been amazing having it just thinking about the idea, sharing it with Claude, and then it just doing things. Sometimes, it's not perfect. You still have to go in and make some tweaks, but it's pretty close and I love the fact that it goes and does testing for you and it tells you what it's going to test.
    And then in terms of your demos, you want to make it look real, full of data. And I love the fact that it goes and creates the data and loads it in for you. So, that's been a huge saver for me and something that I wouldn't have done a year ago at all. No, no way.
    Josh:
    Right. Yeah. I actually got called out by the community on a video I did about hooking Claude web browser, the web version to Salesforce. And somebody was like, "Why isn't that dangerous?" And the first speech I ever gave earlier was, I don't know if it was a user group that I did with Mike here in Chicago, and I gave the example of people putting in internal code and then OpenAI basically just owned that proprietary data. And yeah, that was true at the time.
    And I think part of the reason trust with AI is so hard is because it is moving so fast and the goalposts do shift drastically. And all of these big players, OpenAI, Facebook, Anthropic, they knew they had to get the enterprise market, right? And so, they also knew that they're not going to get those customers if you don't trust them with hooking something up like to a Salesforce org.
    But honestly, it happened and I didn't even see it. It wasn't until I was told, "Hey, go make a video hooking it up to Salesforce," that I double checked that I'm like, "Is there privacy guidelines? Are there guardrails?" And there absolutely are these days.
    Mike:
    Yeah. I had to think about this question because I also wanted to answer it, and my answer is probably not what everybody expects, but this year, and I would say since probably June forward, I felt comfortable having an in AI, I won't mention which one, look at my finances, like my pay stub and help me adjust my retirement savings amount and the amount that I'm saving to hit different targets.
    Josh:
    Interesting.
    Mike:
    And I say that two caveats because the second one is a question, will be a question. First of all, I 100%, here's the pay stub, it's a PDF, and you don't know a single checking or any account. I am not there yet. The second that leads to my second question is I feel like I'm seeing more and more commercials where people are asking an agent to find this hotel and book it or find this trip and book it. Or one of them is they take a picture of a bill and they ask the agent to pay it.
    In realistic terms, because we live in the real world, how comfortable do you think you are? And do you think maybe a year from now we'll look back and be like, "Wow, I can't believe we said that"?
    Jennifer:
    I'm just shaking my head. Nope, no way.
    Kate:
    We were just talking about how worried I am in general about just everything in life. So, that's a no for me at this point. Talk to me in a year. We'll do a recap and see where we're at, but-
    Josh:
    Yeah. I have a very good friend. He's a technical architect and we're very like-minded when it comes to things like applications and AI and security and stuff like that. And I told him I started using this personal assistant and he thought it was insane, but it does not have access to any of those things that you just... It does not have access to my credit card. It can't buy anything. It can't book anything.
    It is a wonderful little research assistant and helps me on my day-to-day, but it can access my email and send emails on my behalf and also send texts on my behalf, but it does follow the right guardrails, right? It does not do it without my permission and without me reviewing and all of that kind of stuff. I think it's a very slippery slope. And the thing is what you're describing, Mike, is that's very much where the big players are going.
    That's how they want to really get a personal AI into your day-to-day life is to make these things so easy that it's like using a calculator with math, right? You're not going to book a trip anymore because the AI is just going to do so much of the day-to-day for you and so much of the to-do list. My two thoughts on it is, first of all, I don't think they're there yet when it comes to actually have access to a banking account and actually spending money and having things that would be if it goes wrong, put this on the list.
    If it goes wrong, how quickly can you recover from it? If my AI was like, "I am sorry, I sent an email to that person, I thought we were talking about it," I can send an email follow up and be like, "I'm so sorry, my AI screwed up." If my bank account goes empty overnight, that's a little bit harder to fix kind of thing. So, I think right now it really is, there's a personal question to it of is this going to make your life easier versus the risk involved if the AI actually does make a mistake?
    Mike:
    Yeah, it's interesting because you think of you want that to happen. It's such a time saver, but the trust factor of the money is real and does the AI feel like the money is real? I've also run into, I feel like we're at this convergence point where a lot of people are safeguarding against AI's hitting AIs, makes it sound like I'm 72 and setting the VCR clock, the AI's hitting their website.
    So, I asked one, I have this rug in my living room that I love, but it's starting to get worn out and I really want to replace it. And I asked to find me another one and it searched for three hours and it came back and it said, "Look, I can't get to any of these sites. They're blocking my ability to pull up the website." And I feel like it's a push-pull, right?
    We need to safeguard that and people rightfully so with the website, I don't want this type of traffic, but also there's people like me that I really want this to be able to search this site and crawl and it's not. So, it hits that kind of barrier for me.
    Josh:
    Yeah. And it's strange because they're different in their approaches and I won't call out specific AIs, but earlier today I was trying to get cloudy into an image and one AI told me I cannot recreate brand and logos for you now that you've told me this is an official mascot conversation over. And so, I went down the street to one other AI and I was like, "Hey, can you do this?" And it was totally no problems.
    And remember, there's all these guardrails that are totally human created, and there's a line in one guardrail list and there's not in another one. So, it's an interesting mix of possibilities right now.
    Mike:
    You went down the street, you mean you just turned down the dark alley where they just relaxed their guardrails.
    Josh:
    Exactly.
    Mike:
    This will be the example I use for a long time, but I still remember Josh showing up on a team meeting and I forget what you were using, but you were like, "We can just ask it to generate a cat as a pirate on a ship in the middle of the ocean." What? That was the coolest thing. So, I was all ready to go for AI. Great. Well, it'll be interesting to see a year from now if we're telling a bot to update our checking accounts or not.
    I had somebody in the grocery store pay with cash the other day, and the poor lady at the register looked at it as though she was being handed Mexican pesos, Kate, because I'm old enough to remember being at the grocery store and begrudgingly writing a check and being like, "Oh, if you just had cash, this would go so much faster." And now it's just-
    Kate:
    Even better, being the person at the cashier stand trying to run the check through the little scanner thing.
    Josh:
    Right. Oh my God.
    Kate:
    I remember that.
    Mike:
    And you had to make the cross, fill things out.
    Josh:
    Yeah. Yeah. Or the [inaudible 00:16:09] credit card readers.
    Jennifer:
    Yes.
    Kate:
    Yes.
    Mike:
    I was part of the [inaudible 00:16:12] credit era.
    Josh:
    Thank you. Thank you for that.
    Mike:
    Yeah. Now, Josh, you just tap it. It's a chip.
    Josh:
    You tap it and you go. Sometimes, I just tap it.
    Kate:
    Here's your watch.
    Mike:
    Oh yeah, I know. Yeah. That to me still feels a little magical to tap a phone.
    Josh:
    Yeah. I moved back in time over the weekend because I was running around doing chores and realized one of my tires had almost like 10 PSI, dangerously low pressure. And so, I went to the most Chicago experience of getting this fixed because the actual garage was an actual garage behind the office building that they reside in. You have to go through their Chicago Bears paraphernalia in order to get into the garage, and then the whole thing turned into just a cash transaction.
    There was no cash register. I'd have to go all the way back to the other building in order to do it.
    Mike:
    Wow.
    Josh:
    So, I just gave them 40 bucks and got 15 bucks back. And I was like, "When was the last time I got change? Actual change."
    Mike:
    Yeah. Well, there's no pennies now.
    Kate:
    It costs that much. You need your own air compressor.
    Mike:
    There's no pennies. You do, Josh. I can recommend some for you.
    Josh:
    Nice.
    Mike:
    They're not that bad. Well, appreciate you all coming on the podcast and sharing what you do and don't use AI for, and of course, building really cool AI projects. So, thanks all.
    Josh:
    Cheers everybody.
    Jennifer:
    Thanks.
    Kate:
    Bye. Thanks.
    Mike:
    Thanks again to Jennifer, Josh, and Kate for joining me. And I think the idea I keep coming back to is the one that Josh questioned about recovery and that's if your AI gets something wrong, how quickly can you fix it? An email to the wrong person is just one apology, but a bank account being emptied overnight is a different story. And that's a useful way to think about how different requests could get handed over. And I think it's also why we saw four people can have four very different answers about what they thought AI would do for them now versus a year ago.
    So, if this conversation sounds like something you enjoyed having, thanks for watching. And if it sounds like something someone else would enjoy watching, be sure to share that out on social. We'd love to have more people listen to the podcast, whether you're listening on iTunes or you're watching this on the Salesforce Admins YouTube channel. So, with that, until next time, I'll see you in the cloud.
  • Salesforce Admins Podcast

    How Builder Central Is Changing the Way Admins Build

    12/11/2026 | 39 min
    Today on the Salesforce Admins Podcast, we talk to Tiaan Kruger, Senior Director of AI Product Management, and Daivat Dholakia, Product Manager for Builder Central at Salesforce.
    Join us as we chat about how admins can use Builder Central to create better solutions, faster, for their organizations.
    You should subscribe for the full episode, but here are a few takeaways from our conversation with Tiaan Kruger and Daivat Dholakia.
    What is Builder Central?
    Every admin has a backlog of ideas that are good but never quite urgent enough to build. Builder Central, now in beta, is here to help you take those ideas into production. This week, I sit down with Salesforce product managers Tiaan Kruger and Daivat Dholakia to find out what it's all about.
    With Builder Central, you can go from describing an idea to a working solution on the platform without using code. You can use the agent-powered tools that you love while keeping your data on the platform you trust, grounded in the context of your business and configuration.
    Most importantly, it's delightful to use. "I have not had this much fun building on the platform in probably 16 years," Tiaan says. With Builder Central, you can build things in hours that used to take days or even weeks.
    See what you're building before publishing to a sandbox
    Obviously, we want to test things out in a sandbox before pushing them to production, but that can mean making changes to your metadata as you're building. It's cumbersome, time-consuming, and sometimes dangerous.
    That's why Builder Central lets you work things up in a virtual environment before pushing them to your sandbox. You can explore an idea and hash things out without having to roll back metadata. Similarly, visualizers let you see how a flow you're building looks in your org before it ever gets there. 
    By the time something hits the sandbox, it's already working the way you want it to, and you can focus on the finishing touches to push your solutions to production.
    How Builder Central helps you with tech debt
    With 10 years under his belt as an admin and developer, Tiaan understands that a big part of the job is fixing, maintaining, and improving existing infrastructure. So how does Builder Central help with that?
    Because it has access to all of your metadata, you can refactor or test existing flows. If you have tech debt in your org (and who doesn't?), you can probably get an agent to help you with that. You can refresh existing apps with a modern UI and your brand's colors, then make modifications to your heart's content.
    Finally, everything you create in Builder Central follows your security settings and naming conventions, so your solutions are secure and easy to maintain.
    Make sure to listen to the full episode for more from Tiaan and Daivat about Builder Central, and check out the video to see the demo. And remember to subscribe to the Salesforce Admins Podcast to catch us every Thursday.
    Podcast swag
    Salesforce Admins on the Trailhead Store

    Learn more
    Salesforce Admins Blog Post: Streamline Your Path to Production with Builder Central

    Salesforce+: Builder Central: Deploy in Minutes

    Admin Trailblazers Group
    Admin Trailblazers Community Group

    Social
    Tiaan on LinkedIn

    Daivat on LinkedIn

    Salesforce Admins on LinkedIn

    Salesforce Admins on X

    Mike on Bluesky social

    Mike on Threads

    Mike on X

    Full show transcript
    Mike:
    This week on the Salesforce Admins Podcast, we're talking Builder Central, and I'm going to admit upfront, I'm its biggest fan. I'm joined by Tiaan Kruger and Daivat Dholakia from the platform product team, who spent the last couple of years really figuring out how to bring AI to low-code builders without putting your sandbox at risk. Now, we're going to get into why you build in a virtual environment and how you can scrap everything if it goes sideways, and really how it helps with that 90% of your job, which is just fixing and maintaining what already exists. Not to mention what's coming in terms of governance and policies. Now, if you're in and you enjoy the show, make sure you follow and subscribe wherever you're watching, wherever you're listening. So with that, let's get Tiaan and Daivat on the podcast. So Tiaan, Daivat, welcome to the podcast.
    Daivat Dholakia:
    Thank you.
    Tian Kruger:
    Thank you, Mike.
    Mike:
    Good to see you. Long time since we've talked, I think it was what, Dreamforce just a few months ago, which in Salesforce terms is like 14 years, because months are years at the rapid pace that things are innovating. For those people that haven't met you at Dreamforce or one of our events, Tiaan, let's start with you. What do you do at Salesforce?
    Tian Kruger:
    Thank you, Mike. So I am in the product group in platform, been here about seven years, I have built a bunch of different things, but I've really spent the last couple of years focusing on how we bring AI to our low-code audience. It's a very big challenge, it's something we want to do really well. And before that, I was actually a developer and an admin. So I actually worked in the industry for 10 years. So before I came to Salesforce, actually did the job that I'm trying to make easier for people.
    Mike:
    Which is awesome. Diva, I had the pleasure of meeting you this Dreamforce. You thankfully were on our Salesforce Plus feed, as I can't put Tiaan everywhere because he's also in the keynote.
    Daivat Dholakia:
    Yes, thank you, Mike. Yeah, it was an amazing experience being on Salesforce Plus. Just to give a brief background about myself, I've been with Salesforce almost five years at this point, I've done a couple of different things, including working on identity and also working on the Salesforce authenticator app that we still have around and it's still being used by a lot of people. And I also worked on mobile before I started working with Tiaan on Builder Central and helping out our admin persona to reduce the amount of time it takes them to get to build, and then soon we'll have a lot of additional things as well that we'll probably talk about in here as well. But super excited to be talking with you on this podcast.
    Mike:
    Yeah. So the cool thing about this, is you have the number one fan of Builder Central hosting this podcast with you. I saw it a little bit before Dreamforce, but I got my hands on it after Dreamforce. And let me tell you, I am the happiest, one of the happiest admins on earth. I can't wait until this gets unleashed for people to try. But let's talk about that because this is the most fun podcast I'm going to record all year because we're going to talk about Builder Central, and I can't build enough things with Builder Central. If you follow me on LinkedIn, you know that I've already built an app and I'm a kid of the '80s, so I built a Knight Rider dashboard, and then I built a car dashboard. I do have plans for a Goliath dashboard, so I'll sneak peek that just because I like building dashboards. But let's talk about quite possibly in my opinion, the coolest thing Salesforce has ever released, which is Builder Central. Tiaan, tell me what Builder Central is.
    Tian Kruger:
    Absolutely. So by the way, I loved your enthusiasm. It's hard to get somebody who works on the platform all day long, to be this excited about something. So I'm enjoying your enthusiasm so much.
    Mike:
    Good.
    Tian Kruger:
    But Builder Central is the end result of about two and a half years of work internally to figure out how we build on the platform with AI in a constructive way. How do we go from idea, describing it, to a working solution on the platform? And not just using any process, but making it no-code, low-code friendly, taking an admin and giving them the same tools that developers have been enjoying for the last two years, and creating things on the platform. It's built on top of all of the hard work the team has put in in their headless story, trying to figure out how do we make it easier for you to build with agents on the platform, do everything from MCPs, do it using skills, all of this stuff that we've been doing for vibes and we've been doing for frontier models. How do we take advantage of all of that, but then bring it in a package and an easy to use kind of experience that makes it delightful to use. And I think we actually managed to achieve it. The experience of-
    Mike:
    Oh, you did, in my opinion.
    Tian Kruger:
    The experiences, I've been on the platform for 17 years, I have not had this much fun building on the platform in probably, I don't know, 16 years, because it just takes so much of the pain out and that's really the goal. The goal is just to be delightful, to be fun, to be visual, take the schlep work out of it and just make it fun to create on the platform again and just unleash it for your business.
    Mike:
    Yeah. I will say it's never not been fun to build on the platform. I think it's rewarding and I think that's why people come in, because I can tell you exactly how I felt the first time I created Dependent Picklist. And Dependent Picklist sounds like the easiest thing in the world to make, until you get in the Wayback Machine and you go back to 2007 and CRM and everything was hard and Salesforce Dependent, this, this, next save. Oh, oh, oh, it's there. And I remember showing it to people because the first Picklist had three ideas and then it depended on the answer, and everybody in the office was like, "Wow, Mike, you did really good." I was like, "Yeah."
    Builder Central is the next evolution of that. The last time I was this excited was when we introduced branding and themes, because I was really big into the show Top Gear, and I created an entire org to track cars and episodes and lap times and podcasts. And I was like, "This is amazing. This is the best thing I've ever built in Salesforce." And then Builder Central came along and it's scratched an itch I didn't know I had.
    Tian Kruger:
    I think it's time for a reprise of that app, don't you think?
    Mike:
    Oh, you have no idea. I have so many plans to build things. Daivat, tell me a little bit about you were at Dreamforce and got some customers sharing their experiences and talking about stuff that they were building. What was some of the stuff that you heard and have heard while it's still in beta?
    Daivat Dholakia:
    Yeah. The feedback from the customers that have tried it has been phenomenal. It's very similar to what you have also been sharing, which is it's opened up new possibilities that they did not even think were even in their realm of what they could do within Builder Central. For example, we have had a couple of different customers that have said that, "Hey, what used to take us about seven days, 10 days worth of time for multiple people to do, now a single person can do it in like two to three hours at most." The way they are thinking about solving problems is changing now because they were previously dependent on, "Hey, do we need to have the right prioritization for this?" This goes into this bucket list of, "Yeah, it would be great to have this, but we don't have the bandwidth and it's not high enough in our priority list." Versus now they're like, "Yeah, let me just go ask this and get this done in Builder Central and show what is possible."
    And when everyone's aligned, they're like, "Yeah, this is great. Just let's push it out into production and get it to work." So it's changing how they're working as well. We have one customer that has been very, very engaged in the product and for them, their primary use case is how do they go about building an entire service portal, for example, for internal as well as external? And that is also, they're trying to do a POC on that to show that, hey, today in the traditional world, it takes about six to eight weeks for that to get done, versus now they were able to actually build something within a couple of hours as a prototype, and now they're iterating on it to be able to see how far they can push just by having a natural conversation without them having to know every nitty gritty detail of how that is getting done under the covers.
    Mike:
    Yeah. No, I agree. Tiaan, I don't know if you baked this in, it's got a little bit of attitude. I love how it sometimes comes back. When I was building the Knight Rider dashboard, it was like, "Ooh, I like this idea." And I was like, "Well, hello, how are you?" And it's not a lot, but it's a little bit of something that was just enough to be like, "I'm with you on this. I'm not just a robot doing what you tell me to do." And it kind of felt like it was on the path. So I had to tell you about that because I thought it was pretty cool.
    Tian Kruger:
    There's a little SaaS in it.
    Daivat Dholakia:
    Yes.
    Mike:
    Oh, yeah.
    Tian Kruger:
    And it's not a lot, but it just reminds you that SaaSy is still alive somewhere out there. And it cracks me up because it does feel a little bit like a coworker at times in a positive way. It sometimes challenges you sometimes. My favorite moment was I was asking to build an agent for me and it said, "Can I build an employee agent?" And I said, "No, no, I want you to build a customer service agent." And it's like, "But that's a lot more metadata." And I said, "Yes, it is." And it said, "Okay, if you really want me to build it, that's the right thing to do, I'll go do it." But it just cracked me up, because I was like, "Really? Does it really make a difference?"
    Mike:
    I know.
    Tian Kruger:
    Just a little personality, it makes it a little bit more fun, but it'll do what you want it to do ultimately for sure.
    Mike:
    Yeah. No, it did for me. When I went back into the dashboard and I said, "Hey, I need to add an exit button because I realized I don't know how to get out of the dashboard without just closing the tab and I think that's really bad," and it replied, it was like, "Yeah, we probably should have done that to begin with, shouldn't we?" And I was like, "Folks, thank you for baking that in." Talking about building something new though, I know you guys have a demo and we'll put the demo in here in a little bit, but before I get to the demo, I do want to talk about one thing that you both pointed out to me, which is when you tell Builder Central to do something, it doesn't actually build it in your org. Can you explain that?
    Daivat Dholakia:
    Yeah. So historically, what we have done is if you are trying to build something new, you go to your sandbox and you're making changes to the metadata as you are building. Now the problem with that is rolling back metadata is extremely hard and extremely dangerous. So in order to avoid that, what we did in Builder Central is build this whole concept around how you can build in sort of a virtual environment, so that you can keep vibing on it, you can keep exploring, you can keep trying out new things, but at any point you're like, "Yeah, this is not going in the direction I wanted or actually I do not want this to affect my sandbox," you don't have to worry about it because it did not change any of your sandbox metadata.
    At any point you're like, "Yeah, this looks perfect to me now. I'm ready to push this into my sandbox," You hit a button and it publishes your project essentially the same as how you would in an Agentforce vibes project as a developer would do it. It pushes all of that into your sandbox and that's it. It gives you the peace of mind so you're not worried about like, "Oh, I'm going to mess up my sandbox." And that means that you can work, you can vibe, you can play around with it, you can explore and push it hard as much as you can. And then when you're ready, it is available for you in a single button.
    Tian Kruger:
    And I want to point out there's a really key piece to this. One of the number one questions we get, is "I already have Claude Code. Why do I need this?".
    Mike:
    Good question.
    Tian Kruger:
    Like, "What does it really give me?" I had two customers, we did a big workshop that started with that question. And after two hours of using it, they both said, "This is revolutionary. This is amazing." And I said, "Why? I love it. Yes, I agree. But why? Why do you say that?" And they all were in agreement that the fact that we give you visualizers and previews, so this means concretely, and you'll see it in the demo, concretely, when you generate a flow, even though it's just local, it's your project, you can actually see it. We actually load up a visualizer, you can see the flow just as if it's in your org. So that gives you the ability to visually see the way that you're used to seeing a flow, it looks just like a flow than it does in the org. You can see what you're building before it's ever in your org.
    This is a superpower, because it allows you to, as Daivat just said, vibe and revibe and tweak things and whatever, ever before it ends up in your org. In fact, one of our early renditions of the product about a year and a half ago, I actually found out that there's a custom object limit in the org in about two hours. I managed to fill up an entire org with custom objects in about two hours. So that's when we realized, we're like, "Metadata can be created, like it's no longer a difficult thing to produce." Producing the right metadata is important and producing it as efficiently and with as little impact as possible in your org is actually really important to help that flow feel more magical.
    And so yeah, it was really interesting to me to watch both of these customers go, "Oh, this is different. This is a different experience." And I was like, "Yeah, those visualizers." And we're adding more, by the way. We're adding more visualizers constantly to help you. So if people have strong opinions about which visualizers they'll use, tag me or Daivat on LinkedIn and say, "Hey, they help me visualize X, Y, and Z." We're looking for that input.
    Mike:
    Cool. Well, we've teased out the demo enough. So do you want to introduce the demo? And then for everybody listening on audio podcasts on iTunes, there'll be a video version of this over on YouTube, two versions actually. One will just be a replay of the audio and the other is actually the video one that you'll get to see the demo in. So I'll let you guys introduce the demo.
    Daivat Dholakia:
    Awesome. So the demo that we're going to have is about a branded customer that wants to create a site for support so that the users in the field that are customers, end users essentially, are able to go to this portal, able to ask questions about whatever problems they have, and at the same time, interact with an agent. The other piece that you will also see is a way where when you are trying to work on building out the agent, all you need to do is do inline editing. And this is one of the critical pieces, because what Claude cannot give you is a way to say, "Hey, I want to change this one very particular thing in this agent or in this flow or in the UI." Every time you are asking to make a change in Claude, for example, you have to put the entirety of the text saying, "Hey, on this particular page, on this particular agent, I want this exact change." And that means you're having to type out a lot of text to try and tell Claude that this is the exact change you want to do.
    Versus in Builder Central, because we have visualizations, because we have a way to edit in line, all you do is say, "Hit edit at the top," and then you will select a specific component you want to change and just say, what do you want to change over there. And the change can be as simple as, "Hey, I want to change colors of this particular component, or I want to change the text of this particular component." Or it can be, "Hey, I want to add this particular piece in this flow." Or it can be, "I want to change this particular agent to do an additional action." All of that becomes possible because of this editing piece that is extremely pinpointed, which no one else offers you today. And this saves you so much more time, because you're not having to type out everything and you're not going back and forth with the Claude agent or Codex or any other tool to say, "I actually want to make this change, but I need to tell you all of my details around it." It simplifies the whole process.
    And as we add more visualizations, we will have more ways for you to do pinpointed changes, and that's a massive differentiator.
    Mike:
    Yeah. Cool. Well, let's go to the demo. Okay. So we spent the beginning part of this podcast talking about building stuff, because it's called Builder Central. But I think it's important, it doesn't just build scratch new. So Tiaan, we're not going to immediately sit down and within a few hours fill our orgs with custom objects. Oh, man. But you can also go back to other projects and improve things. And I realized this immediately after I built my Knight Rider dashboard of like, "Oh, I need an exit button and then while I'm here, maybe I should be able to click through and improve on things." So tell me how that works in Builder Central. Tiaan, I'll start with you.
    Tian Kruger:
    Sounds good. So first of all, interesting nugget, Builder Central, the builder in Builder Central actually refers to the people who build.
    Mike:
    Oh.
    Tian Kruger:
    Anybody who builds on the platform. Not the central builder that is a single builder who rule them all. All right. So when we talked, we talked about over 50 customers, and the one thing that came from every single customer is, "I wish I built new stuff every day. It'd be really, really nice. But you know what? 90% of my job is actually fixing, tweaking, maintaining, improving, refactoring existing stuff." So we fully understand that that is a very important part of the story. We are actually going to make what I'm about to describe even stronger as we get closer to TDX. So expect the story to get better, but we fully understand that builders don't just get to build new stuff. I mean, as much as we all would like to build Knight Rider dashboards every day, most of the time we're adding a button to our opportunity page to help you add products in a different way or giving you recommended products.
    And how does Builder Central help with that? Well, there's a couple different ways. Builder Central has access to all the metadata in your org, so you can actually start by asking the agent to help you do something like refactor or test existing flows. And I actually have a demo we could potentially consider showing, that actually shows you how you can just be talking to the agent in the Builder Central today, pull flows from your org and then test them, get flow tests created for it, you can be cool too, you can have flow tests without having to build them. Even the flow test PM looked at the flow tests that were built and said, "Ah, these are actually really good." He was very surprised by the way. I was slightly offended. But no, it was great, it was absolutely fantastic because FlowTest is a brand new capability and Builder Central did a great job building those.
    So when you have that tech debt, you have that difficult thing in your org that you want to fix, simply start by asking the agent to help you with that. Now, we're going to put some enhancements in place by TDX that's going to help you actually go grab metadata from your org and say, "Hey, grab this app, this old app that I have, bring it in. It's ugly. I want to make it pretty. I want to make it be more user-centric. I want to bring our brand colors and we'll let you quickly pull that into the project and then go to town." And I'll tell you what, you have not seen beautiful lightning apps like what Builder Central can create. I have seen some of the most extraordinary, beautiful lightning apps in the last two months that I've seen probably in all my career here at Salesforce.
    It's absolutely extraordinary what it can create. So we fully understand that most of people's jobs are modifying what's there. And so we're going to make that journey better and better. Right now it's Builder Central, it's built first, but we're bringing so many more capabilities to help you bring the stuff that you already have, into the latest technology, refactoring, reformatting, beautifying. Come on, your users deserve a beautiful app. You can do it now with just describing it and giving it a brand kit and saying, "Hey, follow this design and make our app look amazing."
    Mike:
    And sometimes even a screenshot. So my question on the edit part, and maybe Daivat, this is you, you talked about it doesn't really do anything in your production environment. And I think we've talked a lot about building. The one thing I haven't said is I love how before it does anything, it's like, "Do you approve this? Is this okay?" I want to make sure that we're not saying all you do is give it two sentences and then off it goes and magically you come back from lunch and it's done all this without your approval. It keeps you in the loop the entire time. But you mentioned when we're building something new, it's building it in a virtual environment. So when we're editing something, does it edit in that virtual environment or how does that work?
    Daivat Dholakia:
    Yeah. So the same concept applies when you're trying to edit as well, right? And the human in the loop piece is very critical over here, right? What you're trying to say over here is, again, when you're trying to make a change to an existing stuff, you still want to make sure that you're not making changes, because again, you're working with an agent over here to be able to make these changes, and the agent may do something that you did not intend it to do. So to make sure that you're not going down the path of then having to roll back a flow change that got deployed, for example, you always want to make sure that you're working in a virtual environment before the changes get pushed out. And again, the agent will never, never automatically push the change without asking for your approval. So there are two ways that you can push this.
    One is you can ask the agent to do it, or the second is there is a button in the UI that you can use to be able to push the change to the org as well. But in both of these scenarios, the user is explicitly saying they want this change to go out into the org.
    Mike:
    Cool. That's super helpful to know because I didn't understand. I'm fine building stuff in a sandbox, but then as I was listening to you, I was like, "Oh yeah, I could completely mess up a sandbox pretty fast if that's all it's doing in there." And I do love the idea of scrapping something. I think the aha moment came for me was when I gave it something, it built it in like 12 minutes. And I thought in the span of a workday, it was pretty common for me to have a 9:00 AM meeting where people were like, "Show me Salesforce." That's literally what it was. And I could just sit there and gather requirements. Over lunch, I could have Builder Central build stuff, because I'll be honest, I didn't know there was a visualizer because I was so caught up in watching the chat work through what it was doing, that to me was the interesting part.
    And I was like, "What's this? Oh my God, there's a whole thing over here." It was too much. But you could do that over lunch and you could literally contact that stakeholder and say, "Hey, I got a prototype I want you to just click through." And they could click in the visualizer, done. Within a day, you could sit down and comfortably have something, a V1 to deploy to somebody. I was blown away.
    Daivat Dholakia:
    I do want to add one more thing that is actually rolling out this week, which is previously what used to happen is when you gave in the prompt initially, it would go and ask you a couple of follow-up questions. The agent would ask you a couple of follow-up questions and then it would start building. What we are changing now is when you given that initial prompt, agent will still get that clarification, but it'll build a project plan for you to then review and approve before it starts building.
    Mike:
    Oh, that's huge.
    Daivat Dholakia:
    And this actually is a very important change, because what happens now is you are in control of what exactly the agent builds before it starts building rather than after.
    Mike:
    Right.
    Daivat Dholakia:
    So you have a chance to say exactly what you want the agent to build. If you want to say that, hey, there's a particular object you want to use, there's a particular flow you want to use, you have a way to specify all of that and make sure that that's part of the project plan, and then the agent will use that as part of the building process.
    Mike:
    Yeah. And sarcastically, we're all really good at building project plans.
    Tian Kruger:
    You know, Mike, I want to throw a challenge at you.
    Mike:
    Yes, please.
    Tian Kruger:
    When you have that 9:00 AM meeting, take your transcript from the meeting, shove it into the build agent and tell it as an attachment and tell it to help you figure out what you need to build out of it.
    Mike:
    Yeah, that'll be the next thing I should try. So one more topic to cover, but I know you have a demo that I want to put in for this podcast on showing Builder Central edit something. Do you want to set that up now?
    Tian Kruger:
    Yeah. I think that the best example, it's not the most beautiful example, but it's a very practical example, is I'll walk you through in this demo, a flow improvement scenario that I had, where I had a bunch of existing flows, I wanted them to get hardened, I wanted to get flow tests created. And so I'll take you through that project and show you how I used the agent to actually improve my project. It actually found a bunch of bugs in the flow. So it's more of a walkthrough of what I had done as opposed to an interactive walkthrough, but I think it'll inspire you and making you think what tactic in your org can you actually go do this with?
    Mike:
    Like it. Well, let me put that demo in here. All right, so we covered a lot, we covered building, we covered editing, but I think Tiaan, you said it best. We'd all love to live in a world where we built Knight Rider dashboards. I would. But the reality is, in a lot of big organizations and small, there's governance, there's procedures, there's policies. I think my job gets to be a little bit of the fun creator in that I'm trying to show people different possibilities, but also I know there are people out there that have watched my video and been like, "Cool. In order for me to build a dashboard, it has to do X, Y, and Z, and then A, B, and C have to approve it." So I'd love to talk about what for Builder Central we have or we have coming in terms of governance and policies, and I'll kick off that topic here. So I don't know which one of you would like to tackle that.
    Daivat Dholakia:
    Yeah, I can take it. So we are today in beta, as we all know. And even in beta, we do have integration with Governance Org or DevOps Center, which is now rebranded to Lifecycle Center. And as part of that, what you can do is set up policies that flow down from that governance org down into every sandbox that you have. So as soon as you open up Builder Central, it'll say, "Hey, there is governance attached to this, governance org attached to this, so you need to log in first so that you can connect those two." And as soon as you do that, all of the policies immediately apply to whatever the agent is building within Builder Central. Now this is very important because you have probably a group of admins that are saying, "Hey, here is how we want the org data model to behave, the naming of it or for the flows." And then you have a bunch of architects that also are putting in their policies to make sure that how should new stuff get built in the org before they get deployed, right?
    And then you have a whole bunch of testing policies and a whole bunch of different policies that you can have today out of the box. And then Lifecycle Center is also planning to add custom policies, which means that now you can decide what is the specific policy you want to use that gets applied across your entire ecosystem of orgs, regardless of whether it's your production org, your sandboxes, your partial copy, full copy, UAT environments, all of them apply the same policies. So as soon as Builder Central starts building something, it uses the policies out of the box without you having to do anything additional.
    And as soon as you then publish, all of these are Already built with those policies in mind, so there is no refactoring work that needs to be done. You don't have to change any object data names or any flow names. Everything works as what you would have wanted it out of the box. And at the same time, the admins that actually set up these policies don't have to worry about what happens in those environments. They can set it up once and then it gets applied automatically.
    Mike:
    Yeah, that's super important. I know having watched presentations that Jennifer Lee gives, she always gives a best practice on how she names her flows. And I think it's one thing, I've had orgs where I've had everything beautifully named, and then I could come in and Builder Central's like, "Cool, I just threw all this pasta at the wall." But you got your app and you're like, "Oh, I got to rename things."
    Daivat Dholakia:
    Yes.
    Mike:
    And I like that you can actually give it some kind of guardrails to follow.
    Tian Kruger:
    And that's actually a fairly fundamental thing that we are trying to build into the product, which is kind of lead you into the bit of success. We're trying to help implement best practices everywhere we can. This means we are going to be natively integrated with Lifecycle Center, so that if you just follow what the agent's telling you to do, we're going to make sure that you set up pipelines and drive your change management process the way it is if you don't have it set up. We're going to streamline it for you, help you get to that kind of best practices. And that's very much tied to the, let us help you get some of the pain out of the way so that you can just focus on the creative aspect, the understanding the business aspect, the focus on the fun part of getting that dashboard perfect for your customer, and not have to worry about as much of the foundational plumbing.
    The more we can set up for you, so it's kind of a little bit of a picture into where we're going with the product. And there's also something that's fundamentally different when you use something like Claude Code directly. Policies are implemented automatically, you don't have to do anything. Any kind of skills that's coming from your org is automatically included in Builder Central, you don't have to do anything. We have our best practices built in automatically, we're going to be doing code scanning for you to make sure that any code that's produced is secure as best as we can. So you are building with all the power of something like Claude Code, but you're building with it, trying to do its best to set you up for success every step of the way. And by the way, you may wake up tomorrow morning and it's a little better without you having done anything.
    And it's kind of magical. We've all used phones that update overnight and you wake up the next morning and you're like, I got this brand new feature that I didn't have yesterday. Imagine that for building on Salesforce. That's what you're going to have, and that's what you have already today. I mean, Daivat literally just called out when people wake up this morning, this week and they open up within this week or two, they open up Builder Central and they start building, they're going to actually start with a spec, with a one pager where they can understand what's going to be built. That's a change from yesterday.
    Mike:
    Wow.
    Tian Kruger:
    It's better and it's going to help you get to that better success. So it's very fundamental to understand that's the magic that this thing brings. We are constantly making it better so that you have to do less to be successful.
    Mike:
    But I mean, that's also, I remember I used this analogy in another blog post, the way that Salesforce did releases, on-prem IT releases, those guys, hey, we're here for the weekend, camping out, we're ordering pizza, we've got sleeping beds and cots and stuff. And I remember leaving Friday and I told somebody, "Well, Salesforce has a release this weekend." "Oh, are you going to be up?" "No. I'll come back Monday and it's all there." And so all of that just feels natural in the Salesforce world.
    Tian Kruger:
    Yeah.
    Mike:
    Last question that I thought of, and I'm wondering we have the answer, because I think people are probably going to ask this after hearing this entire podcast. When I build something in Builder Central and then I love everything it did, I press deploy, it goes to production, what does it say, who built it?
    Daivat Dholakia:
    Yeah. So essentially it still uses the same user that actually is using Builder Central, because the deployment to the org and then into the production will come through that same chain. Right?
    Mike:
    Okay.
    Daivat Dholakia:
    Even though the agent is building it, that does not take away the testing and who owns it. Essentially the same user that built it in Builder Central and then pushes it in the org and then pushes it into the production org, is still owning and responsible for that particular project and everything in it.
    Mike:
    Okay, cool. So I get all the credit.
    Tian Kruger:
    You do. You do get all the credit. I do want to call out though that this will change as we move forward over the next couple of months. A very foundational thing that's changing in the platform is as agents become more and more autonomous, doing more work, we want to make sure that we understand when work was done as you, when work was done for you by an agent. Right?
    Mike:
    Right.
    Tian Kruger:
    So you still get the credit, but you get the credit for asking the agent to do the right thing sometimes, right?
    Mike:
    Right.
    Tian Kruger:
    And so there's a foundational shift that's happening in the platform with agent identity, where the platform at its most foundational layer understands that sometimes that change that was made was made for a person by an agent. So this is not imminent, it's not coming like tomorrow, but it is coming. And so if it's something in the back of people's minds where they're like, "I need to be able to understand from a traceability, from an auditability standpoint, what did I build, what did an agent build?" that is coming. That being said, something that we kind of glossed over, but it may not be completely obvious, I wanted to call it out right here at the end, is the metadata we produce is standard metadata.
    There's nothing magical about it. Once the agents built it and deployed it's just traditional metadata. And this is really important. We're not inventing a new way to build a platform. Yes, we are too, but not for this one for Builder Central. We are just leaning into where the platform' already great. So if you're used to using pipelines, you're used to using DevOps Center, you're used to using one of our ISVs that actually help you do change management, all of that still works. Your developer can pull down that same source and work with it and help you figure out, make sure that this Apex is perfect. None of that is broken or changed with Builder Central. So you build with the latest and magical technology that AI is providing for you, but you can still use the metadata and all of the experience and the history that you have.
    Mike:
    Awesome. I love it. Thank you guys for coming on the podcast. I think I can't wait to see all the changes that come to Builder Central perfectly fine by me right now. I think it's a great V1. Every improvement is just going to be that much cooler. So you guys are rock stars in my opinion. Thanks for building this stuff and empowering people.
    Tian Kruger:
    Thank you for getting the word out there, Mike. We love being on your show.
    Daivat Dholakia:
    Yeah. Thank you, Mike.
    Mike:
    Big thanks to Tiaan and Daivat for coming on and for showing us what Builder Central can do, and really just making me super happy. The idea I keep coming back to is that Builder Central doesn't touch your sandbox until you tell it to. So you can explore things, you can scrap ideas, you can try again, all without worrying about how you have to do a rollback. Now Tiaan reminded us that most of our jobs are fixing and improving what's already there. And you know what? Builder Central does that really well too. And I think for the exit of this, I'm going to just try Tiaan's suggestion and feed Builder Central a transcript of this podcast and see what it builds. So if you follow me on LinkedIn, I'm going to post it there. And if you watch this on YouTube, I'm going to post it after the close of this video.
    So let's see what Builder Central can do. But the cool thing is as Salesforce admins, we still get credit for all of that we've told Builder Central to do, which is really nice. And it looks like they're going to improve that to add for auditing and clarification purposes. So I love that. If you have opinions on what visualizers Builder Central should add next, be sure to tag Tiaan and Daivat on LinkedIn, because they said they're listening and I can affirm to that, because I gave them ideas after this podcast. So we'll see if those get worked in. Anyway, thanks for listening. Until next time, I'll see you in the cloud.
  • Salesforce Admins Podcast

    What Does an Admin Certification Prove in the Agentforce Era?

    29/10/2026 | 40 min
    Today on the Salesforce Admins Podcast, we talk to Stacy Jacobs, Partner Ecosystem & GTM Leader at Salesforce.
    Join us as we chat about why certifications and knowing how Salesforce works is even more important when AI is helping you build.
    You should subscribe for the full episode, but here are a few takeaways from our conversation with Stacy Jacobs.
    Why Admins need to see the big picture
    Certifications are a rite of passage for every admin. But now that AI can walk just about anyone through how to build a custom object, are they still worth pursuing? I sat down with Stacy Jacobs, Partner Ecosystem & GTM Leader at Salesforce, to find out why certifications still matter and how AI can help you prepare for your exams.
    One thing that Stacy emphasizes is that as powerful as AI tools are, getting the most out of them requires a solid understanding of how Salesforce operates within your specific business context. Agentforce can help you put together all of the pieces, but it's up to you to decide what the puzzle looks like in the first place. 
    Investing in the human in the loop
    Certifications are more than something you put on your resume to get your first job. Even if you're a veteran of the ecosystem, they can help you get up to speed with best practices for things like security models, native features you might not be using, and how to confidently build with AI.
    "We are the gas that's powering AI," Stacy says, "we have the long-term knowledge, the history of our organizations, the history of our industries, our platforms, and we have that common sense that maybe AI is lacking."
    Certifications are an investment in the human side of this equation, and by deepening our knowledge of the platform we expand the possibilities for what we can accomplish with Agentforce.
    Building the right solution
    With Agentforce, it's never been easier to build whatever we want. But how do you know if you're building the right thing? Are you making an app that fulfills the requirements? Or are you making something that actually solves the problem?
    Many Salesforce certifications focus on the soft skills that help you make sure you're building the right solution. As Stacy explains, these skills are more important than ever. In a world where AI can help you build just about anything, admins are there to build the best solution suited to their specific business problems.
    Make sure to listen to my full conversation with Stacy for more on certifications and how to prepare for them. And don't forget to subscribe to the Salesforce Admins Podcast for a new episode every Thursday.
    Podcast swag
    Salesforce Admins on the Trailhead Store

    Learn more
    Trailhead: Salesforce Certified Business Analyst

    Trailhead: AI Associate

    Admin Trailblazers Group
    Admin Trailblazers Community Group

    Social
    Stacy on LinkedIn

    Salesforce Admins on LinkedIn

    Salesforce Admins on X

    Mike on Bluesky social

    Mike on Threads

    Mike on X

    Full show transcript
    Mike Gerholdt:
    This week on the Salesforce Admins Podcast, we're talking about certifications and with AI making it easier than ever to get answers, build apps, and figure things out on the fly, you might be wondering, does certification still matter? Well, my guest today, Stacy Jacobs has some thoughts on that. Stacy works with Salesforce partners on certification and learning programs, and she's been a part of the ecosystem since the ExactTarget days. We're going to talk about why knowing how Salesforce works is even more important when AI is helping you build. How to use AI to prepare for your next certification and why experience and credentials aren't competing with each other. Plus, Stacy manages to beat me to a food analogy on my own podcast. I don't even know if I've still recovered yet. So let's get to our conversation with Stacy.
    So Stacy, welcome to the podcast.
    Stacy Jacobs:
    Oh, thanks for having me.
    Mike Gerholdt:
    Well, I think it's a really cool article that you also put out on admin.salesforce.com about certifications in the AI era. And I think I've thought a lot about this. I think we're seeing AI disrupt. Are we still disrupting? I feel like disrupting was a very 2010 word when we were coming out with apps, but maybe AI is also disrupting a lot of things. And certification is definitely one of them, but maybe not in the way that I'm thinking. So first off, I think let's start with what do you do at Salesforce around certifications and how did you get into the ecosystem?
    Stacy Jacobs:
    Oh yeah. So I've been within the ecosystem for several years. In fact, most of my career is within the partner ecosystem outside of Salesforce, and I've always wanted to be part of the mothership, and I've been here about seven years. Came in as a technical architect in ProServe, and now I am running programs to enable all of our partner audiences. And certification is a big part of that. So we run programs throughout the year to help enable, educate, motivate all of our partners within the ecosystem to get certified and learn more about our products. So that is a little of what I do.
    Mike Gerholdt:
    That's really cool. ProServe, what does that stand for?
    Stacy Jacobs:
    Yeah, it's professional services.
    Mike Gerholdt:
    Ah, okay. It's not like the tennis machine.
    Stacy Jacobs:
    No. Never been a tennis player.
    Mike Gerholdt:
    Me either.
    Stacy Jacobs:
    Ball [inaudible 00:02:53].
    Mike Gerholdt:
    That's why I was like, wow, we have a whole department of people that just sell. Nevermind. People that listen to the podcast know there's always going to be a few bad jokes right away and then probably some food worked in somewhere, although everybody's going to be at the edge of their seats to see how I work food into an AI certification podcast.
    Stacy Jacobs:
    Maybe also [inaudible 00:03:14] too.
    Mike Gerholdt:
    Buckle up. Just wait for it. It'll be there. So I think what's interesting is when you first came to us and started talking about certifications and AI, I immediately went to, oh, well, obviously people are just using AI to pass the certification, but I think it's a little bit different than that. It's also getting certified in AI, correct?
    Stacy Jacobs:
    A little bit, yeah. We have a lot of AI aspects to all of our certifications and it is definitely sprinkled in as a common theme around the board for our products. So naturally it's going to be part of our certification process and I think we need to embrace that.
    Mike Gerholdt:
    Yeah, absolutely. Now, so I was looking back a few years ago because I remember the first time I was introduced to a cassette tape, my mom showed it to me and how you could rewind it with a pencil. So everybody that's my age and older knows what I'm talking about and everybody younger is like, "What are they doing? Thought this was a Salesforce podcast." I also remember the first time I was kind of, I'll call it introduced to AI, and it was Josh Burke got on a team call and he talked about, I forget what it was called, but he's like, "I just told it to render a cat on a pirate ship and here's the image." And I was blown away because up until that point in my life, if I wanted a cat on a pirate ship, I would've had to Photoshop or do some work. And this was just a prompt that he told me.
    And I look back at that now as like, wow, that's so easy to do because I think my understanding of AI, I know my understanding of AI has increased, but also the tools have gotten so much stronger and so much smarter, I'll call that. How in the certification world do we keep up with certs and the rapid pace of how AI is developed?
    Stacy Jacobs:
    Oh man, one step at a time. I mean, one of my most favorite sayings is asking somebody how they multitask and nobody can do everything altogether. We always do one task at a time. So it may be overwhelming at first seeing how many certifications we have out there, the advances we're making in all of our products. But I guarantee you, if you learn little bits here and there, you can reach any goal that you set your mind to.
    And I've actually used AI to help study for certifications and I encourage a lot of folks to do that as well. It's not as much of what questions are on the exam and how do I get answers to all the questions on the exam? That is not something that anybody should be doing. But for the matter of gathering all the materials that we have out there to help enable not only any audience out there, anybody looking to learn more, that is a powerful thing that we have now that we did not have back when I started my career. And I was reading PDF documents and printing out papers and taking notes here and there. But now we have wonderful skills in Slack that can help you study for exams as well. So little bits at a time, you can't multitask everything and definitely just do one thing at a time.
    Mike Gerholdt:
    Right. Yeah, no, that's actually a really good point because a lot of the AI, I always feel like I sound old, like the AIs out there. There's a comedian that's like sound old, you just add the and pluralize it. The AIs out there. But they have access to a lot of information and you think of they could pull all of that together and then start quizzing you to really help you prepare. Because I know when I read material, I consume it a certain way, but then I never think back to, well, how will the question come that's going to quiz me on this? So very good point.
    Stacy Jacobs:
    Yes.
    Mike Gerholdt:
    One thing that as we kind of head into this, so it's a brave new AI world, there's a huge maturity curve in our Salesforce ecosystem that I think a company we're just starting to really realize Salesforce is 27 years old. Which is nuts because I remember starting working in the ecosystem and I was like, oh, Salesforce not even 10 or whatever. But because of that, there's a lot of people that have been doing Salesforce for a long time. They've seen the evolution of, they were around when Chatter was launched or Service Cloud and they've seen the tools released, they've seen the features come about. They've implemented them, they've seen them sunset, their skillset is pretty solid. Why would somebody like that go and get just any Salesforce certification, let alone an AI certification?
    Stacy Jacobs:
    Yes, this is something that I hear a lot too, Mike. And first off, I never downgrade any experience anybody has regardless if it's with Salesforce or not. I think that's what makes us human and being a human is a big part of this AI world we're living in. So what I would recommend everyone thinking about, encouraging them to be open-minded about is that you may learn something. If you're somebody who's been within the ecosystem for the 27 years, you might be surprised at what might be under the hood that you can turn on out of the box and all of that.
    So when you're fine-tuned in one organization, in one org or one mindset, it's really hard to see what you're missing. And certifications really help you hone in on the fuller picture. So understanding more of those security models, the native features that maybe you're not using because we all have bad habits and we're not adopting best practices, but certifications help you stay on top of what those best practices are so that you can scale even easier for the AI future we're in.
    There's a lot of things that we're building on top of, especially the platform that AI is loving. And if you are using it now and if you can massage your organization into some of these standards, you'll be able to scale and go way further with AI. So that's why you should get certified.
    Mike Gerholdt:
    So let me ask you then, because I can see people sitting back and saying, "Well, I mean, if there's apps out there that'll help me, I could just go to any one of these AIs, ask it a question, how do I build a custom object in Salesforce?" And it'll tell me that and I can kind of prompt my way through building an app. What's the benefit if AI is available to bring us all of that information on demand at my fingertips, do I really need to spend all that time studying for a certification?
    Stacy Jacobs:
    Yes, I think you do because we are the gas that's powering AI. We have the long-term knowledge, the history of our organizations, the history of our industries, our platforms, and we have that common sense that maybe AI is lacking. I don't ever recommend an AI situation where a human is not in the loop. And so us understanding what the platform is, how it works, and being a Salesforce admin really sets you up for success. It sets your organization up for success, and it sets the AI that you are buddying with, becoming your coworker with, up for success too, because you have that knowledge and that experience that you've had for years that you can bring to the table and fine tune the AI logic in ways that even it couldn't even imagine, right? We're in this together. So absolutely, it's definitely worth getting certified.
    Mike Gerholdt:
    Yeah, and I didn't mean to impromptu put you on the spot, but the other thing I would add to that, again, Josh pointed this out to me, I feel like this podcast is, here's what Mike knows in terms of what Josh has taught him. Mike's learned other things. For a long time, if you asked a model how many Rs were in strawberry, it told you one or two and there's three, and then you'd ask it to spell it for you and it'd spell it with three Rs and it would still confidently respond, "Well, there's only one or two." And I think that's also part of the difference of getting that certification and going through and getting that experience. Of I hear what you're saying the answer is AI to building this app, but you're making this part up because you don't know and you're doing it. And I feel like there's a term for this, I should look it up, but there's a term for when AI tells you something so confidently, even though it's making it up.
    Stacy Jacobs:
    Yeah, it's hallucinating. It's definitely hallucinating. So the way I look at it this, and Mike, I'm going to beat you to this food insert to our podcast today.
    Mike Gerholdt:
    Oh, look at that. That doesn't happen.
    Stacy Jacobs:
    But here's how I think about it. So we are starting to speak the same language as AI. We are definitely in this together. We need to be coworkers, we need to be colleagues, we need to be best friends with AI because you're starting to speak the language of AI. Now, I like to think of this as you're ordering food. Let's say we go to a restaurant, you might have a general idea of how a pizza is made, but if you don't know the typical ingredients, you might really be surprised once it comes out and there's cheese on it. And if you have a dairy allergy, that is a huge problem.
    So once you know it comes with cheese, once you know you're speaking the same language as the pizza makers, you have a general idea of what a pizza consists of, then you can start customizing it. You can order it any way that you want with, even without cheese, you can add items on there that you enjoy, maybe your audience enjoys. You can customize all of that and get exactly what you need.
    So AI really works the same way. So let's take this and transfer from pizzas into the platform. So if you ask it to build a flow, if you ask it to design a data model and you really don't know what any of that means, you're going to take whatever it gives you and it might hallucinate. It might pull in personal information that should not be there. So thinking of highly regulated industries, but these are all things that you learn when you go and get certified. You understand the components of the platform, you understand what it's built up, you know what an object is, a custom one, a standard one. You know how it all fits together, and that's how you can work with AI to kind of build your pizza.
    Mike Gerholdt:
    Yeah. That's a really good analogy. I can't believe you beat me to the food analogy. I'm stumped. So there's a TikTok I keep seeing where a guy walks in, orders pineapple on his pizza. Where do you fall? Are you pro-pineapple, not pineapple?
    Stacy Jacobs:
    Maybe once a year I'll do pineapple, but only because I'm really hungry.
    Mike Gerholdt:
    Yeah. Yep.
    Stacy Jacobs:
    But I don't order it.
    Mike Gerholdt:
    I've done it once.
    Stacy Jacobs:
    If it's in front of me, I'll eat it just to be polite, but I don't go out and say I want it.
    Mike Gerholdt:
    No, there's five people in the world that crave pineapple and ham pizza. Just made me think of that. You really brought up another interesting point, which is once you're certified, it's kind of like the beginning of your learning because we also have maintenance exams, right? I mean, actually they're Trailhead modules now.
    Stacy Jacobs:
    Right. And they are so nice in Trailhead. And those are really, really important too. I always encourage everyone, if you're going to spend so much time studying and learning and applying yourself to something that stays with you, you better keep it. And these modules only take minutes to complete. They don't take months, in some cases, to study for some of these exams. They can be quicker than that, but keep what you earn and definitely stay up in the know with the latest and greatest because it really prepares you and all of your decisions in the future when it comes to career. Yeah.
    Mike Gerholdt:
    I mean, and getting certified, I know the few times I've been certified, getting there and then taking that exam is not cheap. I don't want to scare people away with price, but to your point, if you're going to spend money on the investment, don't just do it for a one-time thing, do it because it's durable and you can maintain it. I think the coolest thing that we did was moving to Trailhead for the maintenance part of it because you can get hands-on and actually see some of it.
    I know some of it is just multiple choice answers, but some of it you can really get hands-on and do and actually, oh wow, be a part of that. Whereas a hundred years ago, we would just get a developer org that had the newest release enabled, and then it was up to you to figure out a scenario to use it.
    Stacy Jacobs:
    Yeah, absolutely. It was such a game changer, especially in the marketing cloud world where I come from. But really having everything in there in an easy to digest and kind of a fun format, right? Everyone likes to get points and earn badges and things like that. It definitely changed my perspective and my willingness to go and keep my certifications because it is an important piece of our ecosystem pie here. You know, you have your experience, you have your certifications, and then we have AI and all three together, just kind of a super place to be right now. And that's what motivates me and my role and how important it is for all of our ecosystem to understand we're in this together and all these three things definitely do matter.
    Mike Gerholdt:
    Yeah. You bring up a point that I can't believe we didn't talk about, but you're not just at Salesforce having been part of the ecosystem and, oh, now I'm on this team and cheering for certifications. You're actually certified.
    Stacy Jacobs:
    Oh yes. Yeah, absolutely.
    Mike Gerholdt:
    What was one of the driving factors for you to get certified even before you joined Salesforce?
    Stacy Jacobs:
    Yeah. Back in the day, I was a marketing cloud administrator back when it was ExactTarget before the acquisition. So that kind of time stamps me here, but I knew there was more that we could do with the organization I was a part of. I knew personalization was really important. I knew because of my marketing background, a target audience and understanding what they want and listening to their needs and what they value in the messages they were receiving. Whether it was marketing or... I'm sorry, through emails or through SMS, I knew that we could do more than just blast emails out, but I didn't have the eloquent ways to talk about it then.
    I just knew that the platform controlled and had this power that I wanted to unlock for my marketing audience here. And so I decided to step out of my comfort zone, understand what it was the platform was. And mind you, this was way back in the day when Marketing Cloud was acquired by, or ExactTarget was acquired by Salesforce. And so I wanted to know more about Salesforce. And the very first admin or certification I got was Salesforce Admin because I learned the basics. I learned how we could pull in all of this great information about our audience at the time that it mattered and then extend the conversation with Marketing Cloud.
    So target audiences, hitting them in time periods that made sense, right? I worked for a travel agency company and we had a publication line as well. So print magazines, if those are still a thing out there where you could hold them, you can feel them, you can smell them. We also ran the digital side of all of that. So hitting our audience, the moment really, really mattered when it came to events and travel packages and things like that.
    And I knew to unlock all of that experience and make it better for the end users, our customers, and better for the business, I needed to learn more. I needed to understand what needed to be unlocked with the platform and core and that I did just that. I studied, I went, I passed, and then I was able to connect the pieces for my team and it was a great experience.
    Mike Gerholdt:
    Wow.
    Stacy Jacobs:
    Yeah.
    Mike Gerholdt:
    I remember this would've been 2008. I got my first certification and I remember walking into the president's office because I reported to the president of the division and saying I was certified and they were like, "So what does that mean?" And I thought to myself-
    Stacy Jacobs:
    What'd you say?
    Mike Gerholdt:
    Funny you should ask.
    Stacy Jacobs:
    What did you say?
    Mike Gerholdt:
    I told them, I said, "It means that the company that builds the product that we use has faith in me to configure the product in a manner that's the best possible way for our use." And I kind of always leaned against that. I would also say I want to bounce this idea off you because my entire Salesforce career changed and it was like October, ironically. It was October of 2008 because I finally felt like I had the confidence in what I was doing as opposed to just the ability to do it.
    And so I didn't feel like I was impersonating anybody. I was no longer impersonating a Salesforce admin. I was a Salesforce admin. And I was a Salesforce admin, not because the certification said so, but because it told me back that this is the skill level you're at and it's the skill level measured, not just one you think you can do. I don't know, you think you could run a 10-minute mile, but you've never ran a mile.
    Stacy Jacobs:
    Yeah. I mean, there's a sense of validation in getting certified, especially for those individuals who have worked in an org or several orgs for several years and then they aren't certified. But there's a validation that goes with it and you get to keep that as long as you maintain your certification. And when you are presenting yourself and your brand, it does have volume to it. I'm not saying experience is higher or anything like that than certification. They go together and your exam, your certification definitely doesn't replace experience. Absolutely not.
    There's so much I have learned by messing up email sends, by using the wrong merge field, but your certification really shows you what you can do on the platform as a whole in any org, right? And yeah, it is a very powerful piece and you need to advocate for that too. I love that you answered the way that you did with your employer because we also need to advocate for ourselves and say, "This does matter. I can do this." And that's what I urge everyone out there listening to just take it one step at a time because it does matter and AI is here and knowing the base where we crawl, walk, run is definitely going to set our whole ecosystem up for success in the long run.
    Mike Gerholdt:
    Yeah. It just felt like, I really felt like it's not that I didn't have to explain myself. I didn't have to explain myself as much.
    Stacy Jacobs:
    Yes. I loved getting my first cert. Oh man, that feeling of relief when I left the center, I don't know if you did. Back then we couldn't do it virtually, right?
    Mike Gerholdt:
    Oh, no. I had to drive-
    Stacy Jacobs:
    We had to get into the center.
    Mike Gerholdt:
    I had to drive an hour and a half. I had to drive all the way to Des Moines and I remember it was, I forget what kind of testing center it was. I was the only one in there because this is also 2008. Computers had barely been invented and they were like, "Oh, you're here to take a Salesforce test." And I was like, "Yep." I think probably that was their third one they'd ever administered. And I got done. And at the time, do you remember this? They used to end the test and yes. And then there would be a preview screen that would come up and it would show you all your answers.
    And you don't remember the questions, like question 49, C, awesome. I guess so. I picked C back then. I'm still going to go with it. And it would give you all your answers and you're like, "Okay, I'm going to click submit, submit." And it turns for a second. And then it's like, "Before we give you your results, they'd like feedback." So I'm like, "No, God." Because hitting submit, it felt like it's like the first time you pay online with your credit card, you're like, "Well, here goes the whole world."
    Stacy Jacobs:
    Yeah, there's no turning back.
    Mike Gerholdt:
    And then it came back with that prompt of, "Give us your feedback." I was like, "Can I give you my feedback after I find out if I pass?" But I hit that button and I just remembered I stood up. I was like, "Yes, I passed." And the instructors, because it was glass in between us, they looked like they were scared because I knocked the chair over. I was like, "No, I'm fine. I'm okay."
    Stacy Jacobs:
    Oh, wow.
    Mike Gerholdt:
    I'm fine. It's okay.
    Stacy Jacobs:
    Oh, but that feeling, and now it's yours. And how many release cycles have you been through with that one and maintaining?
    Mike Gerholdt:
    Oh yeah. I mean, three a year. Yikes. A lot. But yeah, I mean, I've maintained my certification. I'm sure there's always stuff you can learn, but I feel like having got that first credential, it also... I didn't get the bug like some people of I have to keep getting a lot of credentials. I was good at two or three. Mostly because I really enjoy being proficient and having the credentials in the space that I'm working in the most. And at the time, some of the credentials like your Marketing Cloud, the organization I was at didn't have Marketing Cloud. Now, it wasn't on the roadmap. If it was on the roadmap, I definitely would've sat for it.
    Stacy Jacobs:
    Yeah. Marketing Cloud is one of the harder ones to get in, but with our newer products and whatnot, Trailhead is really the place to be for all of our products now. But I do remember that same feeling back in the day, especially with Marketing Cloud engagement, having your hands in an org. Oh, it was like gold. It was a wonderful place to be. But we have made strides to get Marketing Cloud more hands-on, and that's part of where my role here at Salesforce comes into play too, is making sure that we can get enabled in these products. And we have safe places to do that too.
    I think a lot of it is having that safe place, your Sandbox, a different business unit. Now we have data spaces. All these things matter and just keep looking. If you're not in there, I would always recommend folks who wanted to learn Marketing Cloud. Where can I get started? How can I do this? Well, now there's a lot of options out there. And I definitely remember that survey pop-up as well as trying to find your-
    Mike Gerholdt:
    You thought it was your score for a second. You're like, oh, no. I feel like I need to fill this out. Maybe you guys got to calculate some stuff back there.
    Stacy Jacobs:
    Yeah. Yeah. But to your point, you bring up something interesting, and I do get asked a lot about this as well is, well, what's next? I can go get my Salesforce Admin certification, or maybe I already have one that's in Marketing Cloud or Tableau, but really what's next? Where should I go from here? Because we have several paths to follow, and I think you need to start with your persona. What are you comfortable with? It doesn't all have to be technical. You don't have to know a single piece of code to get certified in many cases, but we also have our technical paths as well.
    So I think it's coming down to what you want to specialize in. Marketing Cloud, I have a small bias towards it because it has powered my entire career up from that first... Surprisingly, my first certification was not Marketing Cloud though. And so it really propelled me forward. And I think you need to look at where your comfort levels are, the industries you're interested in and where you want to specialize. Because those basics like the Salesforce Admin, Data Cloud is a great place to be, those AI specialists, all of them have value, but perhaps looking at what you want to specialize in would be my recommendation.
    But I don't know if you have any extra insight on that or what you say. What do you say is the next one?
    Mike Gerholdt:
    So I think a couple of things. One, I would read into the certifications because I think everybody thinks they're all technical. And one thing that I learned with Sales Cloud Consultant, I don't know if that's what it's still called, what I really enjoyed about that certification was it taught me how to ask better questions of my users and it taught me how to almost act as a third party when working with my company and not assume answers. And all of that was in the certification before we ever got to anything technical.
    And I think that's the part that makes you a little bit more whole is the certifications aren't just, do you know the clicks? Do you know the config behind it? But it's, do you know how to get there? And do you know how to get there in a way that the organization is going to really be useful from? Are you going to create an app that is exactly what they ask or are you going to create an app that peels a couple layers deeper and actually uncovers the problem that you're going to find out three months later? And I think that's what the certification did.
    The other thing, and this is kind of attuned to what you said, a lot of people look at it as, well, I have the experience. I could just top off my life with the certification. It's not the end. When you graduate from college, you aren't like, cool, all done learning work life stuff. That's the beginning. Because now you're going to shop around that college degree and get jobs and then build your career. And to me, that's the same thing as the certification. Once you have that certification, cool. Now the really fun part begins because now it's you have something really firm to stand on and build the rest of your career upon.
    As opposed to it being the capstone of your career. It's not. It's where you go to build the rest of your career and you use it as a foundation because you can just say, well, I'm certified in these three things as opposed to, well, what does it mean when you say you have 10 years of Salesforce experience?
    Stacy Jacobs:
    Yeah, absolutely. I mean, it doesn't tell me if you have a certification, it definitely does not tell me how you handle those real world, real org situations. How do you handle the unclear requirements? And I love those consultant exams because they absolutely do what you said. They get you to think more about the holistic approach to how this product or this scenario fits into a use case. And so that's something certifications don't give you. They don't give you a clear road into how you handle gathering requirements, technical debt, all of these things. But that's where all the experience and you being human with judgments come in.
    And so when I meet somebody and we're talking about their career paths and we're talking about what's next, because to your point, we get degrees, we earn our accomplishments, but it never stops. Learning never stops. I really treat certification as a strong starting signal. It is something that you dedicated yourself to. You learned, you earned and you've kept it. And then I want to hear how you've applied it. So I'm always looking for those wonderful scenarios and I learn a lot by making mistakes. So I also want to learn how you've made mistakes on how you've applied that certification thus far. And yeah, that's a very, very good point. Those consultant exams are great at handling some of those logical thinking points.
    Mike Gerholdt:
    Right. Yeah. There's no exam that sets you up for everything you can possibly run into. I equate it to driver's ed. They can't possibly teach you how to handle every situation on the road. And passing driver's ed and getting your driver's license doesn't mean you'll be a good driver. But what it does mean is they've at least equipped you with enough of the critical skills and ways to think through solutions and challenges that when something does come up, rather than it being completely foreign to you, you're like, "Okay, I have a methodology to work through."
    There's a place in Denver that has, I want to say it's like a six-way stop or a five-way stop. I think it's five, five points. It's the neighborhood. I went to a jazz festival there. There's no driver's ed manual that tells you what to do at a five-way stop.
    Stacy Jacobs:
    No, there's not.
    Mike Gerholdt:
    Who goes? I don't get who goes. You on the left? But at least you have a methodology when you get there to say, "Okay, I should always yield to the people on the right or yield to the left." You have at least something to start with to work through that problem as opposed to nothing.
    Stacy Jacobs:
    You have a general idea.
    Mike Gerholdt:
    Well, you got to pull up your phone and ask Claude, "Hey Claude, I'm sitting at a five-way stop sign. What should I do?"
    Stacy Jacobs:
    Yeah. You have a general idea of how the pizza's made.
    Mike Gerholdt:
    Right. Whether or not it's coming with pepperoni.
    Stacy Jacobs:
    Or cheese or white sauce or red sauce.
    Mike Gerholdt:
    I was shocked. You went to cheese first. I was like, "I never really thought of it being an option to get a pizza without cheese, just a slab of dough and sauce."
    Stacy Jacobs:
    I know, right?
    Mike Gerholdt:
    Man.
    Stacy Jacobs:
    And then we layer AI on all of it. I mean, before we know it, robots are going to be delivering all our meals.
    Mike Gerholdt:
    I mean, yeah. I feel like that's probably a whole thing, those little food delivery things getting stuck everywhere. Well, Stacy, thanks so much for coming on the podcast and beating me to the food analogy. You win.
    Stacy Jacobs:
    Oh, thanks so much.
    Mike Gerholdt:
    Not that it's a contest, but I can't believe you beat me there.
    Stacy Jacobs:
    Well, it is now.
    Mike Gerholdt:
    I suppose I'll take that. That and I need to know how many people like pineapple on their pizza. I'm not opposed to it. Of all the fixings, it seems to be the most controversial.
    Stacy Jacobs:
    It is, yeah. I also want to know how many people know about this five-way stop sign.
    Mike Gerholdt:
    I think it's five points. It is the coolest area outside of Denver. I was on a vacation in Denver and I stumbled on a jazz festival and I had to look it up when I got back to the hotel room. But yeah, I want to say it's five points and there's five streets that converge right there. They had a whole festival. There was two stages and food trucks.
    Stacy Jacobs:
    Fun.
    Mike Gerholdt:
    It was awesome.
    Stacy Jacobs:
    That is great.
    Mike Gerholdt:
    Well, thanks for coming on the podcast.
    Stacy Jacobs:
    Yeah, thanks so much for having me. I really appreciate it.
    Mike Gerholdt:
    Big thanks to Stacy Jacobs for joining me today. One thing that really stuck with me from this conversation is that getting certified isn't the finish line. It's really the starting line. I mentioned how getting my first certification back in 2008 changed the way I thought about myself. I didn't suddenly know everything about Salesforce, actually far from it, but I had the confidence that I knew what I was building and more importantly, I had a foundation of knowledge to build on. And I think that's more important even today. Yes, AI can give you the answer, but you still need the knowledge and experience to know whether it's the right answer. So whether you're thinking about your first certification or wondering what comes next, I hope this conversation gives you something to think about. And if you know somebody who's been putting off a certification, well share this episode with them.
    Until next time, I'll see you in the cloud.
  • Salesforce Admins Podcast

    Winter '27: What Admins Should Check Before Their Org Upgrades

    15/10/2026 | 27 min
    Today on the Salesforce Admins Podcast, we talk to Jennifer Lee, Lead Admin Evangelist at Salesforce.
    Join us as we chat about all the cool new features coming in the Winter '27 Release, including Builder Central, Setup with Agentforce, and what's new with Flow.
    You should subscribe for the full episode, but here are a few takeaways from our conversation with Jennifer Lee.
    Admins are agent-powered with Builder Central and Setup with Agentforce
    First of all, this is the first week with our new format, there will be a video version as well. Coming soon to the Salesforce Admins YouTube channel to see demos, clips, and visual explainers for each episode. Today, we're looking ahead to the Winter '27 Release with Jennifer Lee to find out which new features admins need to know about.
    One thing that generated a lot of excitement at Dreamforce is Builder Central. It's an intelligent, agent-powered workspace where you can build, test, and deploy solutions using natural language. You really need to see it in action to understand how powerful it is, so check out the video for this episode, where we have a demo for you.
    Setup with Agentforce is also now generally available (GA). This tool simplifies so much about managing users, configuring your org, and troubleshooting user access issues. Jen's found it to be especially helpful for reorganizing role hierarchy and, in general, taking control of permissions in your org.
    Three Flow enhancements to make your life easier
    Jen highlights three Flow enhancements that she thinks will have a big impact for admins:
    Edit History allows you to review, restore, and reuse past versions of a flow. If you've ever found yourself staring at a broken flow and asking yourself why you can't just go back to a version that worked, this enhancement is for you.
    Also new in Winter '27, you can now process multiple records with Screen Flows from List Views and Related Lists. This makes it easier than ever for your users to do bulk updates with a quick mass action, without having to leave the screen flow they're already working in.
    Finally, Test Mode (Beta) allows you to debug and test in Flow Builder in one place. You can save manual tests so you're not entering the same criteria over and over again, and use them to build an automated testing suite.
    Jen's steps for release readiness
    The wonderful thing about Salesforce is that a new release is always around the corner. For Jen, release readiness comes down to four steps:
    Plan and learn

    Get hands-on

    Test

    Communicate with your team and users

    The good news is that by reading this post, you're already doing step 1. So my advice is to pick one new feature for this week's episode and spend some time exploring it. As admins, we learn so much more when we get our hands dirty and start building.
    Make sure to listen to my full conversation with Jen for more highlights from the Winter '27 Release. And don't forget to subscribe to the Salesforce Admins Podcast to catch a new episode every Thursday.
    Podcast swag
    Salesforce Admins on the Trailhead Store

    Learn more
    Salesforce Admins YouTube Channel: @SalesforceAdmins

    Salesforce Admins YouTube video: A 4-Step Release Readiness Guide for Admins

    Salesforce Admins Blog Post: Jen's Top Winter '27 Release Features For Admins

    Salesforce Admins Blog Post: Introducing Setup with Agentforce: Your New Admin Superpower

    Salesforce Admins Podcast Episode: September Monthly Retro

    Admin Trailblazers Group
    Admin Trailblazers Community Group

    Social
    Jen on LinkedIn

    Salesforce Admins on LinkedIn

    Salesforce Admins on X

    Mike on Bluesky social

    Mike on Threads

    Mike on X

    Full Transcript


    Mike Gerholdt:
    Welcome to the Salesforce Admins podcast, this week I'm joined by Jennifer Lee to walk through Winter '27 Release readiness, including Builder Central setup with Agentforce Flow and some of the features that admins should be paying attention to after Dreamforce.
    Now, hey, quick heads up, if you're listening on Apple Podcasts, Spotify or wherever you get your podcast, there's a video version of this episode over on our Salesforce Admins YouTube channel and this time it matters because we're actually dropping demos and clips into the conversation. Now, don't get me wrong, you'll still get the full discussion right here but you're going to miss out on some really fun stuff by not seeing the video one. So, go check out that video version on YouTube, let me know what you think, in the meantime, let's get Jennifer on the podcast.
    So, Jennifer, welcome to the podcast.
    Jennifer Lee:
    Thanks for having me.
    Mike Gerholdt:
    Yeah. Well, it's October, it's post Dreamforce time which means we got to start paying two releases and you put out an amazing release readiness blog. We've also gone through Dreamforce, there's been iterations of stuff being updated so I figured why not have Jennifer back on the podcast to talk about everything that we saw at Dreamforce, everything that was in the release and maybe, I think, some stuff that missed your blog or needs to be updated. Does that sound current?
    Jennifer Lee:
    Yes, that makes sense.
    Mike Gerholdt:
    Okay, perfect. Well-
    Jennifer Lee:
    And I had to get all dolled up for this episode.
    Mike Gerholdt:
    I know. It's a video podcast so, for those of you listening on iTunes, there's a video version of this over on YouTube where hint, hint, there will actually be GIFs and video demos to watch so stay tuned. Hopefully it turns out, it's early, here we go.
    First thing I want to talk about is one of the cool ... There's a lot of cool stuff that we launched at Dreamforce but Builder Central. It was right after the keynote with our Salesforce live content, it was featured in the admin keynote. I hadn't had a chance to really play around with it until after Dreamforce which is now. You've had a chance to see it and interact with it but tell people about Builder Central if they skip past it.
    Jennifer Lee:
    All right. So, what Builder Central is, basically, it's a tool where you go in and describe what you want. You can describe the app or the agent in plain language and then the build agent goes and does all these things and it creates this plan for you, describes all the requirements and then it goes and builds all the things and you can go in and preview the items and make tweaks to it. And then, when you're ready, you can go, say, deploy from your sandbox to production.
    Mike Gerholdt:
    Yup. Yeah, it builds it. So, I talked to the PM just this morning, it builds it in a virtual environment because I had no ... I was like, "How is it doing this thing? Is it changing stuff already?" He's like, "No, it's a virtual environment and it doesn't change anything until you deploy." Even in a sandbox, you deploy it. So, I used it, it was so cool. I think it was so cool because it's just top of mind, you're like, "Hey, could you give me this?" And, spoiler alert, I had it create a screen flow. Not that I can't create screen flows, I can, it just takes me a little bit and Builder Central just cranked it out, no problem then it was like, "Hey, do you want to add this to a page?" and I said, "Yes."
    And then I could go back ... The cool thing is then I could go back in and I could actually see the flow components that were built, to me that was like, "Ugh." This is so much easier not because it's building it for me, it is, but because now I can learn and go back and see what are the components I should have built as opposed to getting frustrated that I don't know what the right thing is to build next.
    Jennifer Lee:
    Yeah. The great thing is, in that preview mode, you can go in and drill into the data model and you can actually see the things versus it just coming back and saying like, "Oh, I did these things for you and here's just a list."
    Mike Gerholdt:
    Right, yeah.
    Jennifer Lee:
    The fact that you can actually drill into it and look at it is really cool.
    Mike Gerholdt:
    Yup. And it doesn't just duplicate stuff. It looks at your org and says, oh, well we have this, let's integrate this. It really feels like, man, if I would've had that as a new admin, it would help me jumpstart all of the things that I need to build. And could you go over your skis building a little bit? You could but I think the onus is then on you to go back and learn all the things that it built and why it built it.
    Jennifer Lee:
    And I love that it puts that human in the loop piece, it just doesn't just do it for you. You're going in and you're like, "Okay, this wasn't quite right so I'm going to tweak this a little bit," but, yeah.
    Mike Gerholdt:
    Right. It's currently in beta, right?
    Jennifer Lee:
    Correct, correct. So, this is the time where folks can go in and just kick the tires and check it out.
    Mike Gerholdt:
    Yeah, I can't, I can't wait. Actually, one thing we're going to do so, if you're listening to the audio version of this, jump over to YouTube because right now I'm going to put in a demo of Builder Central.
    Okay. So, that was the demo that the PM team put together of Builder Central, I think it's really cool, it's also the demo they showed in the connected content. It only begins to scratch the surface, I think this is the strongest V1 product I've seen us come out with in terms of just admins having a superpower. It needs a cape, Builder Central should get its own cape.
    Jennifer Lee:
    Let's totally make one.
    Mike Gerholdt:
    I know. So, there's a lot of other tools. Set up with Agentforce is one of them, let's talk about that.
    Jennifer Lee:
    Yeah. So, folks, if you're in my release notes blog, notice that I don't nearly have as many of the setup with Agentforce features that are currently in the release notes so don't come at me for that but let me just highlight a few that weren't in my blog. So, Data 360 is no longer required so that's great but do note that there are some specialized tasks such as, if you're using related list enrichments and custom report types, that will still need Data 360 so just keep that in mind. They also streamline the enablement page so it's easier to enable set up with Agentforce in your org and, previously, you needed to separately assign two permission sets to each user and now they bundle that in a perm set group. So, you just need to assign the perm set group and you're all set to go with your users.
    Mike, back in the day, I would've loved to have this and have an agent do this but now you could manage your users in bulk, you could freeze a bunch of users, unfreeze a bunch of users or specify here's these users that need their password resets instead of doing it one by one by one because who has time for that.
    Mike Gerholdt:
    Period. Just that alone would make me happy.
    Jennifer Lee:
    Mm-hmm. So, for your profiles, you can go into the setup agent and you can say does this user profile have added access opportunities or which profiles have the customized application permission and it'll come back and surface that for you like just asking an agent. You don't even have to go through and click every single profile page, that's time-consuming. So, with summarizing permission sets, permission set groups and having it surface up the information you need without having to, again, do those manual clicks. Another thing is, if you have a major reorg in your role hierarchy, you can just subscribe it to the agent and then it'll just reorganize your role hierarchy for you. Can you imagine back in the day you have to manually row by row, yeah.
    Mike Gerholdt:
    I'm just thinking of, of all the parts of my Salesforce org that got the most stale, role hierarchy was it. You almost set it up and then you get elbows deep in building apps and onboarding users and role hierarchy is the first thing that gets out of date.
    Jennifer Lee:
    Yeah. And then one last feature I'll mention for setup with Agentforce which I do mention in my blog is the org health and usage metrics dashboard. Now, we provide all sorts of metrics to you but now you can go in and say these are the ones that are important to me so I could favorite those and you can say these are the ones that I don't care about and then they're hidden so that you basically customize it to what's important to you which is really cool.
    Mike Gerholdt:
    I like that. Was that in the admin keynote? I feel like a version of that was.
    Jennifer Lee:
    A version of that ... So, I think you're thinking of security center essentials.
    Mike Gerholdt:
    Oh, essentials, yup. Look at that, we have more than one tool for a thing.
    Jennifer Lee:
    Imagine that. So, should I continue on with a couple of other features for-
    Mike Gerholdt:
    Oh, please.
    Jennifer Lee:
    Okay.
    Mike Gerholdt:
    Because I think there's other stuff that you wanted to talk about.
    Jennifer Lee:
    Yes, absolutely. So, in a record, when an owner leaves the company, you naturally will assign a new owner to that record. Now, if that record had any manual shares with it, those manual shares just evaporate into the ether when you assign it to a new user so then you're going to have John Smith knocking at your door as an admin saying, "Hey, I had access to this record, now I don't." But in this release, you can go into sharing settings and then enable keep manual shares when transferring records and enable that checkbox. And then org-wide, once that happens, it will take that manual share and move it along to that new owner so you don't lose any of that record access so that's great.
    Mike Gerholdt:
    Oh, my God. Yeah, nobody keeps track of that.
    Jennifer Lee:
    Exactly.
    Mike Gerholdt:
    When a user asks another user, "Hey, can you share this?" and they click share, there's no log for that.
    Jennifer Lee:
    Nope.
    Mike Gerholdt:
    Oh, man. And what's crazy is you wouldn't know it until somebody has to go to that record which could be eight months after a person left.
    Jennifer Lee:
    Right, right. And then you're like, "Well, how did you get that access?"
    Mike Gerholdt:
    Right. What have you been snooping around on?
    Jennifer Lee:
    And then digging through the setup audit trail to figure it out, yeah.
    Mike Gerholdt:
    Oh.
    Jennifer Lee:
    Yeah, no.
    Mike Gerholdt:
    Just don't set up audit trail into an AI and be like, "Help."
    Jennifer Lee:
    Mm-hmm. Or you set up with Agentforce.
    Mike Gerholdt:
    Right.
    Jennifer Lee:
    So, another feature for reports is that now you can preview a record within the report and it doesn't jump out of the report, you can preview it within the context of the report. Now, to use that, you need to enable it so you need to go to the reports and dashboard settings page and then there's a feature called show record previews on lightning reports beta. So then, once you do that, when you're in the report mode, you have to click on this little icon that looks like an eye and then you click on any of the record links and then they'll open up in the side panel.
    Mike Gerholdt:
    That's cool, wow. It's been a while since I've built reports, that was probably the one thing I always tried to shy away from as much as possible.
    Jennifer Lee:
    Same.
    Mike Gerholdt:
    Thankfully, now we can just have Coworker build things for us, I don't know. We would be remiss to ... I'm surprised we've made it this far and haven't talked about Flow. Everybody's sitting here like, "You awesome, you have Jennifer Lee on the podcast and for 12 minutes you don't talk about Flow."
    Jennifer Lee:
    Well, I saved the best features for last.
    Mike Gerholdt:
    I know. I was going to say, right, you got to ... Ironically, it's why they put the milk at the back of the grocery store because everybody needs milk and they just want you to walk past the aisles of canned chili to get milk.
    Jennifer Lee:
    So, as always, kudos to the Flow team because, with each release, they're rolling them out, there's just a lot of them.
    Mike Gerholdt:
    Yeah.
    Jennifer Lee:
    I'm not going to possibly go through all of them, I'm just going to pick three that I'm going to highlight.
    Mike Gerholdt:
    Okay.
    Jennifer Lee:
    So, the first one is being able to review, restore and reuse past Flow versions. It's 4:00 p.m. on a Friday, you're looking at a Flow that's broken and then you're trying to figure out where it went wrong and who changed it and what happened, well, now you can go into the edit history when you're in Flow Builder and you can see every single change that was made. You can see which elements were changed, you're able to then restore to a previous version or copy the logic into a new Flow. So, that just really makes the troubleshooting and whatever changes you need to make so much easier instead of back in the day where I had different versions of flow and trying to figure out is this different, is this not?
    Mike Gerholdt:
    All of us did.
    Jennifer Lee:
    Crazy.
    Mike Gerholdt:
    I know. And the number of times that I would have to ping Jennifer Lee and be like, "Why doesn't this Flow do this thing?" And she'd be like, "Because you didn't check a box," ugh. Just go back to the version that worked before I broke things. What else can we do in Flow?
    Jennifer Lee:
    Well, on Screen Flows now. So, from a list view or related list, you can check the records so check the records and then specify the Flow action and then that will take those selected records and process them in bulk. So, instead of having, for example, you're on one record and you're clicking a Screen Flow or autolaunched flow and having it processed for that one record, you're on a list view and you're like, "Okay, well, I want it to happen to these multiple records so I'm just going to select them," and, boom, it just happens for all of them instead of having, again, to go one by one by one. So, this is something I'm really excited about because I wish I had this when I was back as an admin way back when.
    Mike Gerholdt:
    I could imagine.
    Jennifer Lee:
    Because I told my users, sorry, you have to do it one by one, can't put it on a list view.
    Mike Gerholdt:
    Yeah, nope. We have some stuff in beta for Flow as well, right?
    Jennifer Lee:
    Yeah. So, the last thing I'm going to talk about is Test Mode which is in beta. So, in Winter '27, when you're building your Flows, you're going to have a little build tab and then a test tab and all your testing and debugging is now going to be in one place which is great. And so, there are a bunch of features that come with Test Mode. So, when you're working through a Flow and you're having to iterate through and test and test and test, know that now you could save that manual test so you're not entering the same criteria for your records over and over again, you save it and then you just reuse that. So, there's a lot of reuse so that's great for as you're building a Flow.
    And then, when you're ready to activate it, you don't want to lose any of that test so then you could promote it to become an automated test where you have assertions. So, assertions are a developer term but essentially what it means is you test for something that is positive. So, if your Flow creates a task, you want to test that as part of your process, a task was created. So, the great thing about automated tests is, once you built them, it's there forever so then, when you go and test your Flows, when you make a change to it, you want to then go and test to make sure nothing breaks, you don't have to manually test them, you can now go and say, "Oh, I want to run this entire suite of tests for this one given flow or I just want to run these couple," and it does it for you. You don't need to manually go in and manipulate records, it just remembers it.
    Now, another thing is if you have Flows that call another Flow or maybe you have an HTP call out, when you do your testing, you want to isolate those other pieces because those would've been tested elsewhere, you don't want to test an integration every single time and a subflow would've been tested in and of itself so you want to isolate those out and really focus on the main flow. So, now you can do that with specifying mock outputs for your actions and subflow elements. And then, lastly, when you're testing records, there are records that aren't easily searchable. So, examples would be case or campaign but you know the record ID so you have the option now, instead of searching for a record, if you have that record ID, you can pace either that 15 or 18 character ID and then use that to test your Flows.
    Mike Gerholdt:
    Ooh, that's easy, I like that.
    Jennifer Lee:
    Yeah.
    Mike Gerholdt:
    You could keep some record IDs around to test against all the time.
    Jennifer Lee:
    Mm-hmm.
    Mike Gerholdt:
    Yeah, those are cool. It's funny, Flow testing to me is still creating it in a sandbox and going to a record and trying to make it work as opposed to properly running the test, I don't know. It's like, "Come on, please, screen, I like this." That's really cool. I feel like a lot of the release this time was solving things that we were willing to work around but it's made it so much easier, all of the testing, all of the bulk updates. Bulk updates, I don't want to sound old but I remember having 12 workflows in an org and thinking, boy, that's a lot and now how many flows per object aren't people trying to manage and test and iterate on and fix and update, the same with users so I think that's really cool.
    One thing that's different about when you become a Salesforce admin is really getting used to, hey, releases are coming and the cool thing is you don't have to do anything, you can just chill out. I remember I had a user once ask me something, they were like, "What are you doing this weekend?" I was like, "Oh, this and that, I'm going to write a blog post and Salesforce has a release coming so our instance won't be available from 2:00 a.m. to 3:00 a.m. or something." And they're like, "Oh, do you have to be up during that time?" I was like, "Nope, sure don't have to worry about it." But you have to prep and I think that's something new for me when I got started as an admin.
    So, tell me a little bit more, help people understand, do we have some stuff that they can help get ready or what should they do? Because I'll link to it in the show notes and include it with this blog post.
    Jennifer Lee:
    Yeah. So, we have best practices for getting ready for a release. So, with this release, I went through and took a look at the blog post that I wrote in 2022, it seems like a long time ago.
    Mike Gerholdt:
    Oh, wow.
    Jennifer Lee:
    So, a lot of the same concepts still apply but I added a few new things or things that you should be aware of. So, I freshened that blog post up and then I also recorded a new video. So, depending on what method you're better at learning, whether it's reading through a blog or watching a video, you're still going to get the same type of content. So, essentially it comes down to four foundational steps, I have plan and learn, get hands-on, tests, and there are different levels of testing, and communication, communication within the team that's building Salesforce as well as your users.
    So, within that plan and test section, I do really ... That's the biggest of the four steps and I talk about sandbox strategy and how that's important and why you need both a preview sandbox and non-preview sandbox and here are the reasons why you would use each one and things to consider and also talk about the different levels of testing as well. So, whether you're a new admin, just getting started, that releases happen throughout the year and they're going to happen whether you're ready or not. So, I recommend either reading the blog, watching the video and just knowing what you need to think about to get your org and your users, your team ready for a release.
    And then, if you're a seasoned admin, sometimes you just need a refresher. You've been doing it for a while, you might pick something up that you're like, "Oh, yeah, I forgot about X, Y and Z." So, yeah, take a look, we'll have it in the show notes, either the blog and the video.
    Mike Gerholdt:
    Yeah. No, I think it's a really good point is sometimes you take things for granted. I think for me it was always the sandbox refresh schedule. What do I need to refresh now for current, to stay current and to make sure that I'm doing both? And so, yeah, if you're not used to it, it's a new thing and, if you are, this is really good because it helps you, oh, maybe you forgot about this and got to pick it up so this is great.
    Jen, your mega blog, everybody loves it, we love that you publish it, I'm glad that you pour through the release notes for everybody. And thanks for coming on the podcast and updating us on some stuff but also walking us through what was really cool with all of the AI that we launched at Dreamforce and, of course, Flow because Flow, right?
    Jennifer Lee:
    And speaking of AI, so this time around I had AI help me through the process.
    Mike Gerholdt:
    Oh, oh.
    Jennifer Lee:
    So, I trained it, yeah. So, instead of me combing through all 600 plus pages, I told Claude, I fed the release notes into Claude and I said here are the sections that I care about, focus around admin but also, if it's in that category and you don't think it's applicable for admin, still list it so I see it. So, I didn't have to review everything, I saw what Claude returned and then I looked through the list of the things that it didn't think applied to admins and there were some that I'm like, "Oh, well, not necessarily directly but they should be aware of it," so I did that human in the loop piece where I'm like, "Okay, I'll pull these things back in because I think it's relevant." So, it did speed up the process so I highly recommend it to use it to customize your release notes.
    Mike Gerholdt:
    Yeah. Dealing with large amounts of data, that's what AI does really well and I don't know if ever I've read all the release notes.
    Jennifer Lee:
    No.
    Mike Gerholdt:
    But to have a tool, any tool just at least give one pass of a filter and you can accept or reject its ideas but at least it's got you ... Feed it the release notes, go grab a sandwich, 20 minutes later, hey, it's got a pass on 600 pages for you, now you know what to pay attention to. I think that's a great tip. So, thanks for coming on the podcast and helping admins out for this release.
    Jennifer Lee:
    I always love being on here.
    Mike Gerholdt:
    Well, that was a lot to cover and I think my biggest takeaway from this conversation is just how much easier some of these new features are going to make our lives as admins, whether it's Builder Central helping you build faster, set up with Agentforce cutting down on repetitive tasks or some of those improvements in Flow, there's plenty to explore. And a big thanks to Jennifer Lee for joining me and walking us through everything, be sure to check out her Winter '27 mega release readiness blog along with the other resources that we have linked in the show notes.
    And you know what? Here's my challenge to you. Pick one feature we talked about today and spend some time exploring it because reading about new features is one thing but figuring out how it could make a difference in your org is where the fun really begins. I'm Mike Gerholdt. We'll see you next week in the cloud.
  • Salesforce Admins Podcast

    How Do I Decide If a New Salesforce Feature Belongs in My Org?

    01/10/2026 | 36 min
    Today on the Salesforce Admins Podcast, we talk to Alastair Dinning, Senior Solution Architect at Salesforce.
    Join us as we chat about the process of adding new features to your org, from what to look for when you're reading through release notes to rolling something new out and driving adoption.
    You should subscribe for the full episode, but here are a few takeaways from our conversation with Alastair Dinning.
    Which new features should I pay attention to in the release notes?
    The exciting thing about working in the Salesforce ecosystem is that it's continually evolving. A new release is always around the corner, chock-full of new features that could improve your org. But how do you sift through everything to figure out what will add value and what's just a shiny new toy?
    My guest this week is Alastair Dinning, a Senior Solution Architect with Salesforce Professional Services. He has 14 years of experience as a consultant for businesses of all sizes, helping admins change their orgs for the better.
    For Alastair, the most important thing when you're looking through release notes is to have a clear understanding of your business processes and problems. Do any of these new features address a pain point? Whether you practice SABWA, run a steering committee of power users, or use a case management system for feedback, you need to have your finger on the pulse of your users.
    Three pathways for adding a new feature to your org
    Once you've identified a problem you'd like to address, Alastair lays out three options: you can build a declarative solution yourself, you can buy a solution off of the AppExchange, or you can work with a developer to code something custom.
    Building your own declarative solution means that you end up with something that's tailored exactly to your specific business requirements, but it also costs you resources in terms of time.
    Buying something off the AppExchange, on the other hand, costs you money up front, but you're saving a lot of time and can deploy the change quite quickly. Even if the solution isn't 100% right for your specific problem, Alastair encourages you to reach out to the AppExchange partner because they're often willing to make improvements.
    Finally, coding a custom solution is probably the most expensive in terms of internal resources, but gets you exactly what you want. The drawback here is flexibility. You don't want to end up with a solution that you can't update if your business context changes in the future.
    Know when to keep Salesforce steady for your users
    If you've spent time with your users and really understand their pain points, adoption should come easily. But at the end of the day, the job of the admin isn't to constantly roll out new features—it's to make life easier for your users.
    Sometimes, the best thing you can do is to keep your Salesforce environment consistent and stable. That means not only identifying which new features could possibly be helpful for your org, but having proactive conversations with leadership about the bigger picture. 
    Make sure to listen to my full conversation with Alastair for more about how to roll out new features to your org and how admins can best work with consultants. And remember to subscribe to the Salesforce Admins Podcast so you never miss an episode.
    Podcast swag
    Salesforce Admins on the Trailhead Store

    Learn more
    Salesforce Admins Podcast Episode: September Monthly Retro: What Changed, What Matters, and What Admins Should Do Next

    Admin Trailblazers Group
    Admin Trailblazers Community Group

    Social
    Alastair on LinkedIn

    Salesforce Admins on LinkedIn

    Salesforce Admins on X

    Mike on Bluesky social

    Mike on Threads

    Mike on X

    Full show transcript
    Mike:
    This week on the Salesforce Admins Podcast, I'm talking with Alastair Dinning, a senior solution architect with Salesforce Professional Services about how admins can decide if a feature is right for their org. We're going to dig into how to spot the business problem behind a feature, when to click, buy, or code your solution, how to prototype before making a big investment, and why timing and support ability matter just as much as functionality. So next time you find yourself reading the release notes and thinking, "Oh, that looks cool," you'll have a framework for deciding when to implement it. With that, let's get Alastair on the podcast. So Alistair, welcome to the podcast.
    Alistair Dinning:
    Thank you, Mike. It's good to be here.
    Mike:
    We connected ironically over Slack. Not ironic. Is it ironic? I always get hung up because I'm afraid I say ironic because I learned irony from Alanis Morissette, but we connected over Slack because you're a fan of the podcast and you work at Salesforce. And I was like, "Hey, I have this topic that I think you're perfect for." So let's start off by you letting everybody know what you do at Salesforce and how you got there.
    Alistair Dinning:
    So I am a senior solution architect with Salesforce Professional Services. I've been at Salesforce for give or take five years. I've been working in the ecosystem for 13 and my entire career has been as a declarative consultant and into being in the architect world. And I came to Salesforce through the acquisition attraction on demand and having spent my whole career, my Salesforce career in Salesforce consulting. So I've worked with a good number of organizations, whether they be small business, medium business, large business, government. I'm working currently with the Canadian federal government. I've worked with education, with nonprofit. And I mean, as a consultant, that's my approach to this job. And it's like, how do we as admins do things declaratively and do things well? And what can we bring to the table?
    Mike:
    Yeah. Wow. Worked with government. You must have a lot of scissors to cut all the red tape.
    Alistair Dinning:
    Yeah, government does bring a lot of red tape with it, but you make sense when you're talking about taxpayers' money.
    Mike:
    Yeah, no. I mean, it's all intentional for a reason. So let's talk... One of the biggest questions I always get, and it's a question I had as a Salesforce admin, which is how do I decide if this feature is right for my org? And feature could be anywhere from the biggest feature do we flip on? At one time we had customers had a choice of turning on lightning all the way down to the smallest little checkbox that maybe we added. And I was reading through some of the stuff that you do at Salesforce and I thought it'd be great to have that conversation with you about helping admins figure out if a feature is right and maybe give them some of your thought process into that. So I think that's where we'll start.
    Alistair Dinning:
    Absolutely. So one of the fun things about Salesforce that I've always appreciated is the three releases a year and the fact that we get new functionality every four months or so, and there's always something that's in those release notes that's exciting. And again, the advantage of having been a consultant is I've seen all of these different organizations and I see these new tools coming from the release notes and I'm like, "Oh, that's cool. That's really fun, and I think that's going to add value."
    But to your question, is it just this shiny new toy or is it actually going to add some real value into the solution? I think I always start with, "Okay, so that looks cool, but how is the business going to utilize it?" From two points, either is there a business value that we can add with this new feature or is there a pain point that I as an admin have seen, I've heard from my users time and time and time again where they're all like, "I don't like this. I don't like this. This is a slow process. This is in my way," boom, boom, boom. And does this new feature address that pain point?
    So if I was to take Dynamic orms in the Lightning Page Builder, they're super cool because we could do all sorts of fun things with it. But it's only useful if, for example, the business say to me, "Hey, my page layout is completely cluttered with all this stuff that I don't use at the beginning of a opportunity process. So why do I have deep fields on or a whole ton of fields on opportunity development when really we're just trying to identify what the opportunity value might be, value prop might be for this customer?"
    Mike:
    I think that's a great start. And I know I thought of that. I'll say this, I would really love it if the business was as explicit as you say they are like, "Oh, there's really this problem with too many fields." I think oftentimes you have to peel back a layer and listen to users say, "I'm just struggling to find the right information on this page." Or I remember when I was an admin, we brought on a different business unit and I remember the business unit asking why there was this entire section of the account page and it was kind of in the middle and it was above all of the information that they needed. And I said, "Well, if you don't like it, you can just collapse that section." And they said, "Yeah, but shouldn't it know whether or not it should show that to me?" And this was before Dynamic Pages.
    And so I bring that up to say, I hear you. I wish it was that explicit, but sometimes you almost have to listen and put two and two together for them.
    Alistair Dinning:
    That's right. It can be hard for the business to know how to articulate what they want from the solution. But as an admin, there are a couple of tools you've got. One is you could spend some time desk side with your key users or have a steering committee of users who are giving you feedback on a regular basis on what they're using, what they like, what they don't like. The other option is that if you have an ITSM light solution where you've got case management, so your users are providing functionality cases or technical cases on Salesforce, on their usage of Salesforce, then you can actually scroll through the data and see what people are saying, "This works for me. This doesn't work for me." And I mean, if all the cases are coming around a particular topic, then you know that there's a problem there and that's got to go in your admin backlog of things to address in due accord.
    Mike:
    Yeah. And I think you mentioned the three releases a year. Obviously we're always working to solve issues that enough customers have brought up, maybe not specifically in your case, but somebody has that issue. That feature didn't just get born out of a wishlist. It got born out of somebody really had that pain. I also think you bring up an interesting point of, so when you're looking at, should I just implement this feature? Is it actually solving a real problem or do I have to invent the problem or is there a better way to solve that problem?
    Alistair Dinning:
    So when we come to, is there a better way to solve that problem, there's a three step process that I've always applied to implementing functionality in Salesforce. And there's two steps to this process. One is those, are we going to click it? Are we going to buy it? Are we going to code it? In terms of solving the problem for the business requirements? We've identified a business requirement. We've said, "We need to fix it." Can I declaratively solve this problem? Can I just build it out of the box with the tools that come? And I mean, I'm a declarative consultant. I don't write code. So could I do it? Can I build a piece of functionality that's going to allow me to do that? Do I want to buy it or do I want to install it? So do I want to go to the AppExchange and pull something from the AppExchange that's going to solve the problem because this is a problem, to your point, this is a problem that multiple people have had.
    And so somebody else already went and built the solution and put it on the AppExchange. So we already know that those requirements exist. We already know that the solution exists and somebody's taken the onus of really digging through that solution and thinking through the problems and debugging the solution, whether they've built a very comprehensive declarative solution or they've coded a solution and they've put it on the AppExchange and just made everybody else's life easier. And sure, do you have to pay for that product? Most of the time, yes. But does that take away from you having to invest in development time? Also, yes. So paying somebody for a solution off the shelf can be a lot easier than coding it, but then coding it is our third option.
    So you've looked at the declarative solution, you've gone, "This isn't quite going to solve the problem the business has brought to me." You've looked at the AppExchange and there's nothing quite there that's going to fit the bill. Again, this isn't solving the problem the business bought to me. So then yes, then you're into the point where you want to code a solution and work with your developers, work maybe with your UX team, work with your testing team on actually coding out a comprehensive solution to solve the problem, solve that business requirement that was there in the first place. But that's a heavy investment.
    So the flip side to that is that if you were to declaratively build it, can you get 80% of the way to the business requirement, whereas a coded solution would get you 100% of the way there? If you declaratively build it and you get 80% of the way there, what you also get is a lot of feedback from the business before you make a big investment in coding a solution. And that accelerates your development path, gives you a lot of feedback into what your coded solution might look like, but it does help you mitigate the cost and stop you going down the wrong path because your view as an admin as to what the business is after versus their feedback when they start road testing something in production is going to be two different things.
    So either declarative and be done with it or declarative and use that as the prototype to inform your development path, again, assuming there was nothing on the AppExchange that met that requirement.
    Mike:
    Right. Or a hybrid of the two. I know there's some AppExchange apps that you can even add on to.
    Alistair Dinning:
    Oh, yeah.
    Mike:
    And that would help out. I think that you bring up a good point and it's one I never brought up when I was an admin, but not everything on the AppExchange is free. There's a cost to it, but the cost would be ongoing as opposed to massive upfront that they would spend on you and it's a small monthly fee. And you also benefit from, then they get time to upgrade it. Whereas if you've built something, who knows if you're going to have time to upgrade it.
    Alistair Dinning:
    All of the above is true. The other thing with the AppExchange, which has blown my socks off in such a good way in some occasions, is that I found a product on the AppExchange that met 85%, 90% of my business requirements, presented it to the business, the business, "It would be nice if... I really needed to do X plus." And I've actually been able to go back to the AppExchange partner, have a conversation with them because some of these... These are not giant software houses that are difficult to talk to. Some of these are very small independent consulting shops or software development shops and they will take your feedback and they'll go, "Oh, that's a good idea. That's not on my product roadmap," or, "That is on my product roadmap. Let me accelerate it." Or, "Let me bring that into my roadmap and we will bring it to you as part of the product." And they will actually take that feedback if you ask.
    And I think the important thing to consider there is don't assume that what's in the app exchange is locked and finite and immutable, but it could be a discussion. And they will take that feedback because they want their product out there as much as anybody else does.
    Mike:
    Yeah. And if it's a feature you're requesting, who's to say it's not a feature that a lot more of their customers aren't requesting? I like that. One thing I wonder in your day-to-day, because you have a really cool title of senior solution architect, how much, when you sit down with an organization or you sit down with an admin and the people that use Salesforce, how much do you talk to them about the amount of change that's going on outside of just implementing Salesforce?
    Alistair Dinning:
    It can be some very extensive discussions because when I get pulled in to work with a customer, we're typically doing a technology overhaul or a migration from a legacy platform into Salesforce. So there's a lot of business process change that has to happen to make sure that Salesforce meets those requirements, but also make sure that the business users understand that Salesforce is going to support them and how Salesforce is going to support them. And these requirements will... The method of working can change quite drastically, even if the end goal is the same. The process of spending time and training people and understanding what motivating them before you actually even get into making any development change is really important.
    So I try and step out of the weeds of, I need a form that asks X, Y, Z and fields, but what are we trying to achieve with this form? What are we trying to achieve with this business process? Or maybe even what is the metric that the business users are being evaluated on or being comped on? Because if you understand how people are being evaluated or how people are being compensated, that will drive and you can build a platform that will support those behaviors that will drive adoption and that will bring people into your world or into your process.
    Mike:
    The second you talk money, that's when it becomes real for people, especially compensation. For every time I've rolled out a sales process, the salespeople want to know if X, when, Y, what's my pay? Because A, that's why we work, but also I want to make sure that I'm doing things right. And the reason I ask that is for the longest time as an admin, if I was pushing out new features, I felt I was doing my job. If I was constantly giving, and not constantly, not every day, but on a regular basis, if I was giving my users new features, I felt like I was doing my job. And it didn't really dawn on me until one of the organizations I was working at went through a massive leadership change. And here I am pushing out new features on opportunities for salespeople and stuff across the board, and everyone else is kind of grappling with also massive organization changes.
    And I remember I sat back for at least two months and just didn't push anything new because if I could control that environment and give my users a sense of normalcy when the rest of the organization is changing, then I wasn't contributing to their stress.
    Alistair Dinning:
    That's a very reasonable way of moving things forward and allowing the team to stay on an even keel.
    Mike:
    Well, I mean, part of, I think, understanding and thinking through is this feature right, is, is this feature right right now? Or would it be more right later given where everything's at? The last thing, the cliche of that is you don't want to push something new the last two weeks of a quarter because you're radically changing a possible sales process or something that could affect books and numbers. So obviously that seems to make sense, but the same also holds true for other parts of the year when other parts of the organization are maybe going through a different change.
    Alistair Dinning:
    And this taps onto another point, which has just occurred to me. So yes, absolutely. When we are making changes in the Salesforce platform, we've got to be organizationally aware to, for example, to your point, where salespeople are in their sales cycle. Are we at the end of the month? Are we at the end of the quarter? Is this the end of the fiscal? I mean, everything should be end of fiscal. Big sales organizations that I've worked with or worked at, you don't make any changes in the last month of the fiscal because the sales people are always focused on a single task and that is getting to their number. And we're talking about salespeople, but it could be any other organizational goal and team where you need stability because there is a bigger goal to move to.
    The second thought, when we look at how do we implement major change or how do we bring new product forward, it's being organizationally aware in terms of understanding where the business is going and having conversations with leadership about, "Hey, we've got these brand new features, but are they going to be relevant in six months? If we look at a new quoting system to bring in new products, are we still going to be selling this line of product or do we need this level of complexity? Is this still going to be a thing? Is this worth the investment in the time and the change and the development if this doesn't line up with the strategic objectives of the business?"
    So being organizationally aware to what your changes are doing, how your business users are in their, not their life cycle, but their business cycle and where the business is going. These are all important points when we look at how do we bring new functionality forward.
    Mike:
    Yep. You talked in the future and roadmap and boy, every release, every time we have a major event, there's always roadmap sessions, people want to look ahead. I know for a few times there's been times where I've looked at a feature and thought, "Oh, I really want to implement it now, but if I just wait three months, they're going to have this functionality and it's going to be a lot easier for me." And I think knowing that and being able to have your organization on pause to say, "No, let's let the future mature," then we'll be ready for it as well, as opposed to implementing it too early.
    One of the things I think we're thinking about is taking that inventory of your own skill and thinking, "Once I implement this, is this something I can support?" And as somebody that helps architect solutions, at what point do you think through how much features can be deployed versus if a customer organization just doesn't have the people power to support it?
    Alistair Dinning:
    So having been a consultant for 13 years, 14 years, whatever it is now-
    Mike:
    Your consulting is a teenager right now.
    Alistair Dinning:
    Basically, yes. Having been a consultant for quite a while, I've worked with a lot of small organizations and one of the things I've learned in that process is you can build, as an architect, I can design and build a really fancy whizbang solution that'll really knock the socks off the business users, but for that thing to have legs, for that thing to have durability down the road, I need to trust that the admin team in the organization that I'm working with can keep it going. I've always kept an open door to any admin I've worked with, but at the end of the day, as a consultant, I'm in there for a period of time and then I do my job, I deliver my functionality and I leave. And it's always the bit about my job that I like and I don't like. I get to work with lots of great companies, but I also don't see where things go six, 12, 18 months down the road.
    So it is a concern that we make sure that the admin team, the development team have enough handover and enough technical capability to maintain any solution we deliver because we don't want them looking at this in six months time or 12 months time thinking, "Oh my God, this was great at the time, but they didn't know..." I mean, nobody's got a crystal ball when you build functionality. You don't know where companies are going, you don't know what's going to happen in the market, you don't know how product's going to get adopted and unpacked by your business users. So things have to be built scalably and things have to be built with the intent that somebody can maintain and continue to use it going forward. Because if it's too complex, the admins that, as a consultant, that I've left behind are going to be cursing my name down the road.
    They'll be like, "What did he build me? This worked to begin with, but now I need to make some change. I don't understand how I expand on this." And so I'm really conscious of making sure two things. One is that the solutions I build are scalable, but two is that I have empowered the team that I'm working with, the client team, the admin team, that they have the tools to carry that product forward and they have the documentation to carry that product forward and they don't inherit a bunch of tech debt and that they're in a good place where they can understand it and debug it and enhance it and move it forward as their business dictates.
    Mike:
    So let me ask you this, because I think it's very poignant. As having been a consultant and done that for a while-
    Alistair Dinning:
    A while.
    Mike:
    ... what are questions that you really wish the Salesforce admin had asked you across the table?
    Alistair Dinning:
    I think it's about understanding what the Salesforce admin skillset is and what their background is and what their appetite to learning Salesforce is. Actually, sometimes the other thing to know, and it's not directly answering your question, but what I look for in that relationship with the admin is to understand their skills, their capabilities, their bandwidth for Salesforce, because in some smaller organizations, the Salesforce admin is not just the Salesforce admin, they're doing other things too. They may be an operational support person, they may be a financial support person, they may be a sales admin type individual on top of having to learn Salesforce.
    So again, it's making sure that they've got the tool sets and that we've had a conversation about, "Hey, are you understanding that this is how this is built? Do you have access to resources? Do you have access to a local user group, a local admin user group to help you get support? What are the other resources and tools that you've got that we can make sure that you are good to go with this product once it's gone? Do you understand how it's built? Do you have the documentation? Do you understand the designs? Do you have this in a sandbox? Have you unpacked it in a sandbox or maybe a POC environment where you can really play with this thing without breaking what's in prod?
    Mike:
    That's really good. I mean, I think back to the consultants I've worked with and the really good ones, part of their pitch for that solution was, "And here's how you configure it as an admin." One of them was just a matter of changing some static resources and then you didn't have to touch code.
    Alistair Dinning:
    Yeah. So static resources, custom metadata, custom labels, these are really important tools because you make all of the scalability of that buried, not buried, available to the admin in simple tool sets, which to your point, you don't have to touch code, you don't have to go and unpack a flow and rewrite business logic in a flow. You don't want to be doing that.
    Mike:
    Talk to me about, have you ever had an inside group of a handful of users that was your internal champions that maybe when you were looking to roll a feature out, you would beta test it on them?
    Alistair Dinning:
    Absolutely. So the best example I can think of this is a university in Ontario where I was working with the business school. And that school we had Salesforce was being used by the professional services team, the student services team, the marketing team, the alumni group. I'm going to say there were two other groups there as well. I'm trying to think of all the different departments.
    Mike:
    Wow.
    Alistair Dinning:
    This business school had a COE, a Center of Excellence for Salesforce that was represented by business users from all of those individual departments and the IT group were there. They were there to answer the question that we were answering today, which was, "Hey, there's this brand new feature in Salesforce. Do you want it? This is what it could look like. This is what we've heard from your users, but does this make sense to you?" And this school had a, they met on a regular basis. I would say every two weeks the COE would meet. And again, it was driven by business users who demonstrated an interest in both learning Salesforce and expanding Salesforce and contributing to the overall picture that we had one record of a student that we could follow their life cycle through.
    So we had good transparency on what the motivation behind Salesforce was in this organization. And they had a forum where the business users could come with problems, the business users could come with ideas, and the IT group and myself as the consultant were there to say, "Yeah, Salesforce can support that and this is how we could look at it." Or, "Salesforce can support that. Give us a couple of weeks. Let's have some detailed conversations, then we'll come back and see how this fits into the big picture."
    So having in any organization that we had, I think 120 Salesforce users in this group, this school, having a team of business users that would come together in a well-structured discussion forum where people were learning the product and able to contribute was really, really valuable for the development part of that because it wasn't one executive who just determined that this is the way we're going. It was the business who said, "This is the way we're going." Because the business asked for it, the business adopted it, because the business adopted it, they got really deep into owning the solution and they had true ownership of what that environment was and where that product was going.
    Mike:
    Wow. I've ran into something similar where the contract group of an organization really, really had a defined vision on what they wanted. And I created the demo and pushed it to them. And once it went live, they were the biggest champions because they were so invested in that feature. And it made the old system they were moving from just light years worth of antiquated. And it was kind of cool because then they could be at the forefront to help push change for other parts of the organization that maybe were a little less innovative.
    Alistair Dinning:
    Well, it's not just less innovative. It's maybe scared in some respects or unsure. I mean, I think when you have multiple groups working in Salesforce and you've got somebody who can really demonstrate the value and say, "Right, we can move an application from potential students signing in to application submission and review process. And we can drop the timeline that was that process that was four months. We can drop it to two and a half months because we were able to take time out here and take time out here because we can make the process more rigorous and more efficient and more locked down."
    If one team can show the rest of the business that, that's far more valuable than myself as a consultant saying, "I can save you money. I can save you time." It's far more valuable than the admin even saying, "I can save you money and I can save you time." Because if the business will step up and say, "Hey, we did cut costs," or, "We did improve our opportunity close," or, "We did cut our service response time," then those are the wins that really matter that other business users hear and then get incentive to go, "Right, well tell me more. Tell me how did you achieve that efficiency? What did you do? Who did you partner with? What did they bring to the table?"
    Mike:
    Yep. I hear you. Thinking about timing of this podcast as it comes out, we're right on the heels of the newest winter release. For an admin listening to this that's reading the title very literally, How Do I Decide If a New Feature Belongs In My Org? Is there a thinking structure or I don't know, a plan at which you go through release notes that you could give them as a way to think about how they look at features they see in the newest releases?
    Alistair Dinning:
    So I think the first thing to do is to marry up, "Hey, that looks fabulous in the release notes," to where does that align to the business requirements that we're hearing or the business problems that I'm hearing from my users? So if we have something that looks cool and we know it's going to resonate, that's the place where we start. If we've got 10... and there are hundreds of features in every release. But if you've got 10 things that catch your eye, which of those 10 things resonate against what the business has been asking for or complaining about? Because we can deliver what they're asking for, you can fix a problem, that's a great place to be.
    Then we're going to look to see how do we pilot that? We're going to look at how do I get this in front of the business in a way that I can, for low investment, how can I build a proof of concept that the business can see and see whether it actually resonates and does this solve the problem? So whether this is building it out in the sandbox and turning on all its features, is this going to developer.salesforce.com/freetrials and grabbing a free trial that's pre-built with this feature enabled because the developer of free trials, you have two choices. You can get an empty org or you can get an org that's pre-populated with data. If you get an org that's pre-populated with data, you don't have to seed it, you don't have to make it look fancy. It's already done for you.
    So either do a sandbox or a free trial and prototype it. And then you can put that in front of the business and get the feedback from the business. And then if it looks right and the feedback is positive, does this fall into the life cycle of where the business is at? Is this a good time to launch new functionality? And then if all of those things align, look at the technical complexity of doing it. In my case as a consultant, I'm going to be like, "Right, how much do I need to then knowledge transfer to the admin team so that they can maintain it after I'm done? If I am the admin building it, does this make sense?" And from that point you can move forward with, "Hey, yeah, let's run with this new feature, or not."
    Mike:
    I think that makes sense. Alastair, thanks for coming on the podcast and helping us walk through what can be a myriad of constant decisions in not only just the number of features that Salesforce comes out with, but the number of ways that we can build and deploy those features.
    Alistair Dinning:
    Mike, it's been my pleasure.
    Mike:
    And I want to thank Alistair for taking time out of his day to join me on the podcast and really give me a practical way to think through what it can feel like with an endless stream of feature decisions. And here's something you can try for the next release. I want you to take the features that catch your attention and match each one against an actual business problem or a request that you've heard from your users. You can prototype the strongest candidate, put it in front of a few people and pay attention to what happens. Then ask whether the timing is right and whether your team can realistically own what you're about to introduce. A feature that earns its way into your org by solving something that matters and leaving you with a solution you can keep after you support for launch.
    Well, that's it for this week. Thanks for listening and until next time, we'll see you in the cloud.
Plus de podcasts Business
À propos de Salesforce Admins Podcast
The Salesforce Admins podcast features real-life Salesforce Admins, product managers, and community leaders who transform businesses, careers, and community with clicks, not code. This 20min (sometimes a bit more) weekly podcast hosted by Mike Gerholdt feature episodes to empower Salesforce Admins who are implementing Enterprise CRM solutions. There may be some (digital) confetti. For more than our most recent episodes, go to https://admin.salesforce.com/salesforce-admin-podcast.
Site web du podcast

Écoutez Salesforce Admins Podcast, La Martingale ou d'autres podcasts du monde entier - avec l'app de radio.fr

Obtenez l’app radio.fr
 gratuite

  • Ajout de radios et podcasts en favoris
  • Diffusion via Wi-Fi ou Bluetooth
  • Carplay & Android Auto compatibles
  • Et encore plus de fonctionnalités