『How Do I Decide If a New Salesforce Feature Belongs in My Org?』のカバーアート

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

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

無料で聴く

ポッドキャストの詳細を見る
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...
adbl_web_anon_alc_button_suppression_t1
まだレビューはありません