Thu, 23 March 2023
Today on the Salesforce Admins Podcast, we talk to Stuart Werner, Principle Instructor at Salesforce, and Feroz Abdul Rehman, Senior Manager of Technical Curriculum Development at MuleSoft.
Join us as we talk about two new Trailhead Academy courses that can help you harness the power of automation and transform your business.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Stuart Werner and Feroz Abdul Rehman.
Enroll in Trailhead Academy
Trailhead Academy is a collection of certified instructors who offer specific trainings you can take, as an individual or as a member of a company, to come up to speed on various Salesforce products. We brought Stuart and Feroz on the pod to share details about their new classes, both of which are focused on automation.
ADX301: Automate No-Code Solutions Using Flow
Admins are getting more and more interested in Flow, and there have been a lot of folks who cross-register for the class aimed at developers. However, one piece of feedback Stuart has heard a lot as an instructor is, “I know how to click but I just don’t understand why to click.” And so he got together with some other instructors to come up with a class to help admins learn how to think like a developer and use Flow.
The class starts with the basics of development: variables, control statements, algorithms, “all the fun stuff that might not be in a Salesforce Admin’s toolbox,” Stuart says. From there, they move on to look at specific use cases and learn how to analyze requirements and whiteboard a solution. By the end, you’ll be making powerful, automated solutions in a snap with Flow.
ADX350: Build Salesforce Hyperautomation Solutions with MuleSoft
“Hyperautomation is the new frontier,” Feroz says, “[it’s] all about the maximum amount of automation you can build into your daily processes that helps people focus on what’s really important.” It’s not just about saving 5 minutes here or there, it’s about finding all of the places where there’s potential for automation across your organization.
In the class, you’ll learn how to use all the automation tools Salesforce has to offer, from Flow to MuleSoft to Einstein Bots, and how to connect them together. The goal is to give you the skills you need to deliver business transformation through end-to-end automation solutions that improve the employee experience, deliver value, and drive innovation.
If you’re already familiar with some automation tools but you’re trying to figure out what’s next, this class is perfect for you.
Be sure to listen to the full episode to learn about how Feroz and Stuart approach teaching and why classes are a great opportunity to put yourself out there. And head on over to Trailhead Academy to get started.
Direct download: New_Admin_Classes_from_Trailhead_Academy_with_Stuart_and_Feroz.mp3
Category:general -- posted at: 3:00am PDT
Thu, 16 March 2023
Today on the Salesforce Admins Podcast, we talk to LeeAnne Rimel, Senior Director of Admin Evangelism at Salesforce.
Join us as we talk about the biggest mistakes admins make and what to do to avoid them.
You should subscribe for the full episode, but here are a few takeaways from our conversation with LeeAnne Rimel.
What’s the biggest mistake new admins make?
About once a year, LeeAnne gets asked the same question: what are the biggest mistakes she sees new admins make? And LeeAnne is a great person to answer this question. She’s worked at Salesforce for a long time, including a spell as a tier-three support engineer. She’s seen literally thousands of implementations and, you’ll be glad to know, she has an answer.
“The biggest mistake that I see Salesforce Admins make is not asking why,” LeeAnne says. That means putting on your business analyst hat and understanding what’s behind what you’re trying to build. Not just how you’re going to implement it, but why you’re being asked for it in the first place.
Measure twice and cut once
Let’s take a common request: you’re asked to add a new field. LeeAnne points out that the bulk of your work is actually going to be done in the discovery process, where you’re interviewing stakeholders, talking with users, and understanding how it fits into the business process already in place in your organization. Is this something other business units will use? What will be the reporting requirements for this field?
That’s why business analyst skills are such a point of emphasis in the Salesforce Admin Skills Kit. When you ask why you’re building something, you’re trying to understand how it affects the user, how it affects the business units, how it affects the organization, and how it affects other dependencies. Only after you’ve got a firm grasp on all that and written your plan down on paper do you start to actually build something. In short, LeeAnne is a big proponent of “measure twice and cut once.”
Your time to shine
You might feel hesitant to push back on requests because it makes you feel like you’re saying no. But just building whatever’s been requested and not taking the extra time to understand the context means you’re missing out on opportunities to shine. It could be that several business units need to track something similar, and you can actually make a solution that works for everyone across your organization, or give them reporting they didn’t know they needed.
If you need help brushing up on your business analyst skills and getting a comprehensive understanding of what makes a solid discovery process, we’ve got you covered. Check out the links below and remember: always ask why.
Gillian Bruce: Welcome to the Salesforce Admins podcast, where we talk about product, community, and careers to help you be an awesome admin. I'm your host today, Gillian Bruce, and we are going to be joined by podcast frequenter, LeeAnne Rimel, my amazing teammate who had a really interesting thought for an episode, and I agreed that it was an important topic. So, I said, "Come on on the podcast, LeeAnne, let's talk about it." It's all about the biggest mistakes that admins make. So, without further ado, let's get LeeAnne on the podcast. LeeAnne, welcome to the podcast.
LeeAnne Rimel: Hey, Gillian, thanks for having me.
Gillian Bruce: Good to have you back. Now, I wanted to dig into something that you and I had a quick chat about the other day and I thought, "Hey, we should probably bring this to our listeners." This came up for you because you had just done a presentation to a group of students learning about technology in Salesforce, and it's all about the biggest mistakes that admins make. Now, I'm sure everyone's wondering what are the biggest mistakes. So, LeeAnne, can you give us a little more context about this conversation and this idea in general?
LeeAnne Rimel: Yeah. It's one of my favorite questions to get asked. I feel like at least once a year, usually more, someone asks me this question, whether it's on a panel, it's often when working with students who might be entering the Salesforce ecosystem in the next year or so. The question is always what's the biggest mistake you see Salesforce admins make, or what's the worst thing you can do as a new Salesforce admin. Understandable question, right? People want to avoid possible missteps, and totally makes sense.
Gillian Bruce: What's the biggest mistake, LeeAnne? I want to know. This is buildup.
LeeAnne Rimel: We've got the buildup. Well, okay. The great thing is that it's something that you can do or you can avoid this mistake whether you're a brand new admin or you're a really tenured admin. The biggest mistake that I see Salesforce admins make is not asking why, is not diving into their business analyst skills, is not evaluating why a solution needs to be built before they build it. And so, the great news is that no matter where you are in your Salesforce admin journey, you can ask why. As we grow our business analyst skills, as we grow our admin skills, we grow our language and our methodology and our toolkit of how we ask why and how we build out those solutions. But on your first day as an admin, if someone asks you to add a checkbox, you can ask why, and I really strongly recommend you all do that.
Gillian Bruce: Yes. So, I a hundred thousand percent agree with this and I think it's really interesting because a lot of times when you think about, "Oh, I'm scared about making a mistake when I build something or I'm scared about making a mistake in this implementation," that is actually, that's fine. Those are good mistakes to make because you learn something. It's like this idea of experimenting and continuing to iterate. But before you even get there, before you build anything, really understanding what it is you're trying to accomplish and what's the problem you're trying to solve.
LeeAnne Rimel: Yeah, absolutely. I don't know if anyone else's parents ever used to tell them the rule about measure twice, cut once, right? It's a good attitude to bring to building solutions as well. A huge amount of your work, let's say you're going to build an automation, business automation for one of your business units. The bulk of your work is not going to be the clicking around in Salesforce. The most meaningful and valuable part of your work is going to be conducting those stakeholder interviews, creating your process map, asking good questions about what needs is this serving, creating your user stories, really understanding the solution that you want to build and asking good questions about often as admins were approached by maybe heads of business units, "Hey, we need to track this. We need to add a field for this." That's a very common request. We need to add a field for this.
Gillian Bruce: So, actually on that, LeeAnne, so let's say I have been in an organization in a Salesforce admin role and I've been just kind of taking orders and just adding fields when people ask me to add fields or building the thing because they tell me that's what they want to have built, and I haven't done a lot of asking why. How would you go about trying to change that and shift that in my current role? Because it's a little weird to all of a sudden just change and be like, "Well, why do you need that?" And then people be like, "Well, why are you asking me why I need it? You just do what I tell you to do." How do you combat that?
LeeAnne Rimel: Yeah, I think that's a really great question, right? I think we approach this with a lot of empathy for our end users. I think that's always a great way. Writing user stories is kind of an act of empathy because you are imagining that you are that user working through a system and trying to accomplish a task, right? And so, I think approaching it in that way, it's not about, "Hey, you have to give me the right answer or else I'm not going to build you this thing you're asking for." It's, "Hey, I want to better understand. I'm interested in better understanding how you need this to perform. What's the problem that this is solving?" because there might be other groups you can interview as well. There might be a chance if you've got one sales group is requesting a field, is that a field that has a similar need in other business units and other sales processes, and maybe it should be a different... Instead of having multiple fields for each sales unit, maybe it's one field or maybe it's a custom object.
Gillian Bruce: It's why on all of the levels, all of the whys.
LeeAnne Rimel: But it's like if I'm going to ask you why, it's fair to provide some additional background on why, what I'm going to do with that information to make you my partner in it because that makes you my partner. If I'm like, "Hey, can we collaborate on this for a minute? Can we have a little interview?" We talk about stakeholder interviews. A stakeholder interview doesn't have to be like, "Oh, we scheduled an hour on the calendar that's titled stakeholder interview, and we're following this template." A stakeholder interview can be, "Hey, sales user that I work with, can I sit down with you for 15 minutes and ask you some key questions about what's difficult for you?" Or, it can be putting a user story together and then gut checking in with one of your stakeholders. Those are all business analysis. A lot of the interpersonal skills that many admins are so strong in, those are all business analysis skills.
Gillian Bruce: Yeah, and it's all before you start solutioning at all. I think one of the things that I heard you say, especially focusing on the empathy, like you said, it establishes the relationship with your users, but it also establishes with your leadership, it shows that you're thinking more big picture about where the business is going and how Salesforce can fit within the context of that. I think we've talked about this a fair amount on our team to various groups of admins, but really as a Salesforce admin, especially given the current environment that we're all in, we're asked to do more with less. This is a moment and this is an opportunity to really demonstrate that you do understand the business goals, you can connect the business goals with the skills you have and the technology skills that you have to deliver really impactful results pretty quickly. And so, I think especially tapping into this idea of don't make the mistake of not asking why you go into this, this is a really important thing to think about right now.
LeeAnne Rimel: Absolutely. I think it's an opportunity to uncover some gold mines really as an admin for where you can add value to your organization. Earlier I mentioned thinking about the user, thinking about the business unit, thinking about the enterprise, when you ask why and when you dive in and when you conduct stakeholder interviews and when you understand the context of these requests, it helps you understand the business and the things that are pains for the business and how you can potentially create solutions for those. That's an incredibly valuable place for a Salesforce admin to be, and it's a really smart place, career-wise, to be, to be positioning yourself to understand, okay, I see that we're wanting to dive into analytics more across these parts of the business, because not only does asking why help you build a better solution, you're the Salesforce expert, probably not your leadership structure, probably not your business unit leaders.
Gillian Bruce: Well, and I mean understanding what different parts of the businesses need and understanding what Salesforce can do or what you can do with Salesforce as an admin. I've heard stories before where an admin says, "Oh, well this business unit was using this specific app for this process. They didn't realize we could do that in Salesforce which we already pay for. So, I'm going to just save us a bunch of money and say, 'You don't have to use that anymore and it's all going to be in Salesforce.'" You talk about a business understanding the value you can bring as an admin, that is huge.
LeeAnne Rimel: Absolutely.
Gillian Bruce: Yeah.
LeeAnne Rimel: Yeah, I think what you're talking about is kind of doing an audit of systems, right?, And so if you're looking for projects as an admin or trying to understand where you can add value, that is an incredible place to look for value ads, because if you are on, say, Sales Cloud or Service Cloud, you can create custom objects. You have platform access, right? I remember working with a customer and they were using I think Sales Cloud, and it was when they realized we were working together and they were showing me the different systems they used and the different places that they tracked things, and they were using, I think Evernote or something to track customer stories and it was how they were tracking, and they had this whole kind of complex template and they were adding Salesforce record IDs and it was a whole thing.
Gillian Bruce: Mm-hmm. I love that. That's a fantastic story, and yeah, again, it really demonstrates, hey, you use those business analysis skills as an admin. You never know what kind of things you're going to discover. I mean, talk about a leader who would not appreciate that, right? Oh, I'm already paying for a thing so I don't have to pay for this extra thing. We can get rid of that and just continue to pay for what we're already paying for. Yeah, especially given the world as it is now, that's the huge kind of impact that we can have as admins using those business analysis skills.
LeeAnne Rimel: Discovery is such an important, when I say ask why, really if you're Googling for and looking on Trailhead for content, asking why is really all about discovery. It's a huge part of it is discovery, and we'll share in the show notes some great Trailhead resources and admin resources to dive into that further. But doing that customer discovery, because your users and your business unit leaders are your customers, it's so illuminating because we assume that we know what people... Sorry, there's my dog. We assume that we know what people are doing as they're working with Salesforce all day, but we don't. That's why Mike Gerholdt, our colleague, coined the term SABWA, Salesforce administration by walking around, and that's another form of discovery. It's doing those interviews and research into how are people using Salesforce and how can we make their life a little better.
Gillian Bruce: Well, I know Riley's very passionate about this. I can hear that she cares a lot about asking why it's good. So, I just, I love everything you shared, LeeAnne. I think that this is a really valuable aspect for all of us to think about no matter where we are in our careers, especially as Salesforce admins. If you're brand new, your first day on your job as a Salesforce admin, what are the top few questions that you would ask?
LeeAnne Rimel: Well, if you're brand new as a Salesforce admin and you're dealing with an existing implementation, I think some of the most important questions you can ask is help me understand why was this built, help me understand why you're using this, or who's using this, and making sure you're asking the right people, right? That's a huge part of identifying your stakeholders and identifying who would ask. Make sure you're asking the right people. Make sure you're interviewing your power users as well as people who have admin rights and things like that. Sometimes power users are using things in a way that wasn't originally architected, but it's providing value for them, so you want to make sure you figure out how they're using a text field or something like that.
Gillian Bruce: Yeah, it's your job as the admin to connect the business goals and the overall goals of your leadership with what you and Salesforce can do together. I think that's a really important point. Well, LeeAnne, it's been so fun to have this excuse to talk about this very important topic with you on the podcast. Any final thoughts you want to leave with us before we end, we wrap up today?
LeeAnne Rimel: Every admin is a business analyst and has the power to be a strong business analyst and to continue to build those business analyst skills. One of the most important elements of being a business analyst is curiosity with that customer discovery. I think admins, it was curiosity that likely led you to learning this new skillset and learning how to be a Salesforce admin and exploring all these different tools and features. So, lean into that curiosity. You already have everything it takes to be a business analyst. Lean into that curiosity.
Gillian Bruce: I love that. Great note to end on. Thanks again so much for joining us today, LeeAnne. I appreciate it.
LeeAnne Rimel: Thank you, Gillian.
Gillian Bruce: Huge thanks to LeeAnne for taking the time to join me on the podcast today. Now, if you want to learn anything that we mentioned on the podcast, including resources about how to do discovery and how to ask why, please check out the show notes. We've got some great Trailhead content there, some great content in general to help you understand how to kind of hone those business analysis skills. We've also got links to our Salesforce admin skills kit, which has a whole section on business analysis. As always, if you want to learn anything more about being an awesome admin, you can go to my favorite website, admin.salesforce.com, where you'll find the skills kit and all kinds of great blogs and videos and more podcasts actually very closely related to some of the topics we talked about today. So, check it out.
Direct download: Biggest_Mistakes_Admins_Make_with_LeeAnne_Rimel.mp3
Category:general -- posted at: 3:00am PDT
Thu, 9 March 2023
Today on the Salesforce Admins Podcast, we talk to Rakesh Gupta Senior Solution Solution Architect at IBM, a six-time Salesforce MVP, evangelist, Salesforce coach, and the creator of Automation Champion.
Join us as we talk about how to fit blogging into a busy schedule and what to think about when you’re writing about a solution.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Rakesh Gupta.
The birth of Automation Champion
We’re big fans of Rakesh’s blog, Automation Champion, so we brought him on the pod to find out more about the man, the myth, the legend. When he first got started, he would answer questions from the community to see if he could find solutions with automations that didn’t require code.
Rakesh started saving these answers in a gigantic Google Doc which he would share over and over again, but he started thinking that maybe there was a better way. The same questions would come up, time after time, and it would be really handy to put all the answers in one place. That’s when he took his first steps into the blogosphere.
Why you should start blogging
Mike is doing a little blogging of his own about, well…blogging and why admins should start doing it. So we wanted to get some tips from Rakesh about how he fits writing into his busy schedule.
The first thing Rakesh does is block out a couple of hours each weekend to plan his content schedule and research new topics. “I try to write [a post] four or five times before I publish it,” he says, “if I understand it well then anyone can, too.” He goes to the Trailblazer Community to look for new questions and, believe it or not, he still has material he has gotten to in that Google Doc.
It’s important to have confidence in the fact that your perspective matters. No matter where you are on your Salesforce journey, you’re going to have a unique perspective and a unique way of solving problems. As Rakesh says, you need to realize that there’s an audience out there that will resonate with the way you, specifically, explain things.
How Rakesh writes a new post
When Rakesh is writing a new blog post, the first thing he does is jump into his Developer Sandbox to see if he can get a solution working. He especially wants to make sure that he’s testing with enough records to tell if it will be useable at scale.
Most importantly, Rakesh tries to frame his solutions in terms of tangible business problems that anyone can understand. He’s always thinking about the perspective of someone who is new to Salesforce: will they be able to understand and implement this solution? If not, he’ll go back and make some edits.
Finally, Rakesh does a regular session on Saturdays called Salesforce Flow Office Hours. “Trying to build a Flow is the last step,” he says, “the first step is to spend time thinking it through, you have to create a Process Flow Diagram or write something down on paper so you understand how it works in real life.” If you want help with your Flows, hop in a session on Saturdays at 10 am (US Central Time).
Mike: Welcome to the Salesforce Admins Podcast, where we talk about product community and career to help you become an awesome admin.
Rakesh Gupta: Thank you for inviting me, Mike.
Mike: It's been a long time coming. I feel like I've read a lot of your stuff. But for those people, the less than 1%, I would say, of the community that may not know everything that you do, can you just give us a brief history of how you got into the Salesforce ecosystem?
Rakesh Gupta: Sure. My name is Rakesh and I'm a Senior Solution Architect working at IBM. I started my career as soon as I got out of college in India as a [inaudible] developer. Then I was fortunate enough to join couple of Salesforce community events that happened around that time, lead by Kalender Patel and other Salesforce evangelist in India, and I learned about Salesforce. Right after that, I found the recruiting application work and I started learning Salesforce and working on Salesforce platform and I involved in community. That's how I learn and get most of the knowledge and use cases that I put on my blog on automationchampion.com and how then later I started user group in Navi Mumbai, which called as Navi Mumbai Developer User Group. And in 2016, I started Automation Hour with Jennifer Lee and David Litton to help community to learn Salesforce automation process builder/Salesforce flow by using Salesforce use case that everyone implement in their org.
Mike: So you do a few things. I feel like you hit on some really good parts. According to your site, you're six times Salesforce MVP. Holy cow. That's nothing to shake a stick at.
Rakesh Gupta:I started this blog post when I was in India and I was posting page three Bollywood parties' picture initially. It was started as [inaudible] and then as soon I just started my Salesforce career, I come to know about, there are lots of community people, they are looking for solutions like for example, initially we have success.com, success.salesforce.com or developer.salesforce.com and I hunt those website to find use case, help people to solve their problem using automations without writing code. Some of them, you can able to do the code, but there are lots of possibilities and Salesforce introduce workload. Then ability to launch a flow from workflow and then later process builder. Now Salesforce flows. So there are possibilities that the solution and use cases one has can we solve without writing code. So what I initially did is I started writing those into a Word document 10 or 20 pages what document step by steps and posting into the Trailblazer community.
Mike: No, it's cool. I love it. And some of these are rhetorical, but I would love to know some of the questions that I get asked. Because I feel like as a fellow blogger, these are things that we know but you talked about you also did automation hour with Jennifer Lee and Jennifer Lee's on our admin relations team. And she writes a ton of automation stuff too. What was the unique value that you were like, you know what, I got to put this out in the world even though there's other people doing stuff like it?
Rakesh Gupta:Well that's a very hard question.
Mike: I know.
Rakesh Gupta:So initially, see I'm from the background that coming from, I don't have lots of technical background in my family. My father is a retired teacher and my mom is housewife. So I see that people is struggling to getting into ecosystems and getting the use case that they are trying to solve by going through some articles. Because one thing that I believe is there is a user for every use cases, there are person that require the same intensity that you solve a challenge. For example, there are products, there are laptop, there are different kind of laptops and there are audience for each of them, there are movies then audience for each of them, those categories. So likewise, that's what I believe. If there are different people, how I can make myself unique in that front is when I get a requirement or use case from the community.
Mike: I think you nailed it. There's so many use cases out there and there's so many reasons to share what you do that I'm surprised your Google Drive last as long as it did before you started the blog.
Rakesh Gupta:I still have lots of scenarios in my Google Drive that I have in my Twitter list to put into the blog post in a blog post format and there are lots of community people who is helping me to put this into the block right now.
Mike: Well so let's talk about that because I think one of the things that if you're creating content for the community and running, you go to automation champion, you look at it and you're like, man, that must take him millions of hours a week to do. What does that look like? How do you categorize that time in your life to get that content out the door? Because you're busy, you're doing stuff, you're flying around the world, you've got a day job.
Rakesh Gupta:I spend my weekends to plan for at least next two weekends so that I am ahead in the content planning. So usually on every Sunday, four to five or four to six central, I spend two hours just to going through my content knowledge base that I have in my to-do list. So what else I can take this week or next week and try to implement for the community. And there are lots of other things like I write the blog post on Salesforce Flow, Salesforce religious and mainly part of related things. So I categorize them and there are some architect things as well. I started writing, so I categorize them and see what is most valuable thing that one can learn from me and my experience and I take one and start researching it, breaking it down, writing it, and trying to read four or five times before I publish so that if I understand then anyone can understand this,
Mike: That's real similar to what I used to do too. I remember I used to do it on Saturday mornings because Sunday evenings usually my brain is mush. So I took advantage of that Saturday morning wake up brain, let's plan some content stuff. That was always fun.
Rakesh Gupta:Saturday morning I run Salesforce office hours for community 10 to 10:30. So I spend.
Mike: So you just do more because you're not busy enough?
Rakesh Gupta:So every Saturday, 10 to 10:30 central, I spend 30 minutes to people if they have any questions come and try to solve online at the same time. And sometime I teach them how to think through this scenarios use case and how they can utilize their knowledge and they can learn something new. Some of the people when I talk to them, the problem, the major challenges that I see is they don't understand the data model and then there is something that I help them to learn. You can go to the Salesforce is schema builder that you can use to understand how the objects are connected, how this wheels are connected so that when you go and do the query it is very easy for anyone.
Mike: You know this as well as I do for every problem or every challenge that you're trying to solve for in a business, there's probably three or 400 different ways to solve it in Salesforce. Are you ever concerned that you're not putting out a piece of content that's right?
Rakesh Gupta:Yes. If I agree, yes. Sometime when I saw some scenario that Jen or David or someone else put on this website, I feel like, this is good. And I think that is the opportunity for everyone to learn because no one is perfect. So that's where I see community and my friends like, this is the other way that you can think to solve some problem that I never think and this is good for me to learn and think about. There are different approaches as well that can solve and maybe that is more efficient way. And it did happen many times. So I make a note of it and next time I try to see if I can do solution differently or this is the best solution.
Mike: I found myself at least, and there's different years depending on the iteration of the Salesforce release where depending on what the product or feature is that you're writing about, it could really change and it could really dramatically impact the solution that you wrote about maybe two years ago or even a year ago. And I think you're probably running into that a lot with flow and orchestrator and especially with some process builder. What part of working in automation do you find the part that you really want to write about the most?
Rakesh Gupta:You nailed it and you said very right. So Salesforce now move into the process builder to Salesforce flows. And last year Francis and Monira, we wrote at least 150 blocks, convert 150 blocks a process builder to Salesforce flows. And nowadays, I try to update all those blocks whenever you see there are new UI here and there in Salesforce, new variables. So I try to update those every day.
Mike: Not because anything's changing or different, I say that tongue in cheek.
Rakesh Gupta:It is part lots of people following it and I feel like if I provide an hour a day to update those so it'll help for at least one people that would be I think sufficient.
Mike: Absolutely. I noticed you mentioned your bio, you've been working on the Salesforce platform for over 10 years. In looking back, so let's see, it's 2023 that put you back to 2013, can you remember a point in time where maybe it was a feature or something that you learned that really felt like it was a turning point for you where you looked at that and was like, wow, this is a thing and it just changed my career?
Rakesh Gupta:It is. In 2013 when I was initial involved in community and I found lots of use cases that can automate, but again everyone providing the solutions using APEX code and that time I started learning about Salesforce Visual flow is what's calling us cloud flow designer/visual flow. So I started investing my time and you cannot imagine, some time I spend eight to nine hour a day or maybe whole night just to thinking about the solution that how one can solve because there was very less blocks and information available in the market and that was one of the game changing point for me in my career that helped me to think through what can be possible without writing code and that give me lots of knowledge, even information about the platform, knowledge about the platforms and help me to grow in my career. And that's how I started writing my blocks as well as books in Salesforce Process Builder and Salesforce flows.
Mike: So you mentioned you used to write and probably still do maybe, I don't know, we'll find out a lot of what would turn into blogs on Google Docs. What is your process for creating content from the moment that Rakesh has the idea to the moment that Mike sees it as a post on automation champion?
Rakesh Gupta:So the first thing is I have lots of ideas. So I write it down and if the idea is I feel like could it be a business use case? And this is a very business use case. So I started first implementing in my Dev Sandbox where I can just try to see if it can be possible and test with at least 10 or 100 record to see if that is working and if that is working, that is again the success for a blog. If not, and it happened many times. So then that's the first thing that I do. And then next step is to start writing a blog post, which is basically now I have a format to think about how I can put in a format, like what business scenario that I convert this use case to, and then create a process flow diagram and think through and person who just joined Salesforce how he can see this use case and if I write in this week and he able to read this and try to implement.
Mike: Quite extensive. You mentioned Salesforce flow office hours, so on top of just everything that you're doing and you're super busy writing content, you decided to take, is it 30 minutes? 30 minutes?
Rakesh Gupta:30 minutes.
Mike: On Saturday and do that. What are some of the things that you're accomplishing in office hours?
Rakesh Gupta:One, the couple of things that I accomplished is helping people and there are so many people that reach out, they were not able to build. There was one person from South Africa, he is working for a nonprofit and he just joined Salesforce a week ago and he was trying to build the flows and I built that flow for him on live-
Rakesh Gupta:... In the same sessions. And he was very happy because he said that it's going to help for his nonprofit tremendously. And then I helped couple of people, lots of people on the call to help them to understand and I feel I got happy when I see that people understand how to implement a flow, it's not writing, just go and try to build the flow. That is the last step. The first step is you have to spend timing in thinking it, you have to create a process flow diagram or you have to write down your thinking into a piece of paper so that you understand how this actually implement in real life and then implementing is the last step.
Mike: I think sometimes people jump ahead, I'm sure you see that, right? They want to jump into a solution already and you need to back up and think about everything that you're trying to do. Especially now with some of the capabilities of flow, the amount of what you can achieve in a single flow compared to what Process Builder was and even backing up into the days of Workflow builder is just in incredible.
Rakesh Gupta:Yes. For one example a couple of months ago, you cannot able to query the get element by saying that, "Hey, can you give me all opportunity where account ID in the list?" Now Salesforce has that feature in flows where you can say, give me all opportunity where ID in the list. So these are the lots of things that one has to understand and think that this can be also possible with the flows like sorting and there are few other new features. So one has to keep up to date and think how they can implement this while thinking or designing a solution yielding flows.
Mike: I think back to the days of when I was excited just to build a workflow and somehow Daisy chain all of them together with a checkbox and now that's very simple flow. So as we wrap things up, we talked about your blog, you're super busy. And I'm being selfish here because I'm also writing this Build to blog series that I'll plug again, for somebody thinking about starting a blog and not necessarily on automation, maybe they're going to write something on page design. There's so many features, there's so many topics to write on. If you were to give them piece of advice, what would that be?
Rakesh Gupta:First, remember there is a audience for each content, even though that content has written 200 times or 2000 times does not matter. There is a audience for everything and there is a person who match with your frequency. It is possible that if I explain to you something you can able to understand, but not every people, maybe it is possible that the way that you explain he can or she can able to understand. So that is very first thing one has to understand before writing content. And then second is write the genuine content. Don't copy paste from here and there.
Mike: Nailed it. I have nothing more to say. There is a piece of content for everybody and I could not agree more. I think that's great. Rakesh, we love reading your site and I'm so appreciative that you have the passion behind doing what you do on the site and hosting office hours and writing books and creating trainings like it. It's really fun to find that level of passion in what you do and then be able to translate that into fun bit of work to do outside of your day job, which I know probably doesn't feel like work. So thank you so much for coming on the pod, sharing your information. I appreciate that and I will be sure to link to your site in the show notes.
Rakesh Gupta:No, thank you so much Mike. Thanks for inviting me. This is my dream comes true. I listen your podcast from when you started as a button click admin. And from that day, I am a big fan of you, so thank you so much for inviting me and it is a pleasure.
Mike: That was a fun conversation with Rakesh. It was good to catch up with him. Awfully busy person running a blog and doing office hours and I even saw an sight the written a few books, so holy cow, that's a lot of contributions. But if you'd like to learn more about all things Salesforce admin, go to admin.salesforce.com to find more resources, including all the links, which I will include the special link to that build a blog series that I've got going, which I will definitely pull some snippets for this. And that goes all summer long that we mentioned. Be in the show notes. And of course there's also a full transcript for you to read in case you missed part of it. You can stay up to date with us on social. We are at Salesforce. Admins, no I on Twitter, my co-host Gillian is on Twitter. She is at Gillian K Bruce and I am at Mike Gert. So with that, stay safe, stay awesome, and stay tuned for the next episode. We'll see you in the cloud.
Direct download: Automation_Champion_with_Rakesh_Gupta.mp3
Category:general -- posted at: 3:00am PDT
Thu, 2 March 2023
Today on the Salesforce Admins Podcast, we talk to Muralidhar Krishnaprasad, EVP of Engineering, Next Gen Customer 360 Data Services at Salesforce.
Join us as we talk about Data Cloud and all of the exciting innovations coming to help admins own all the data in their org.
You should subscribe for the full episode, but here are a few takeaways from our conversation with Muralidhar Krishnaprasad.
What is Data Cloud?
Muralidhar is in charge of Data, AI, and analytics platforms at Salesforce, and we wanted to bring him on the pod to share the awesomeness that is Data Cloud.
Right now, we tend to keep our data in many different pools. Between Sales Cloud, Marketing Cloud, Service Cloud, and outside sources, we don’t necessarily have one single source of truth for what’s going on between a customer and your organization. Currently, getting something even close to that requires a bunch of legwork to migrate data back and forth. It’s expensive, complicated, and presents extra layers of security challenges for your business.
Data Cloud looks to make all of this a lot easier. You can bring all your data to the same place, with Salesforce at the center of it all. It’s simply a game-changer for everything from analytics to building applications to decisions and everything in between.
How Data Cloud empowers admins
While all of this sounds amazing, what does this mean for admins? With everything in one place in Salesforce, you’re finally able to manage all your org’s data and not just what’s already on the platform.
However, that means you get up to speed on the Data Cloud concepts:
“As an admin, knowing that lifecycle of the data and how you can control and administer it will be the big work to be done,” Muralidhar says. But getting a handle on that will make it easier to protect your data and help your org use it in new ways.
How to get ready for Data Cloud
If this conversation has gotten you excited about Data Cloud, there are a few things you can do to get your org ready. Muralidhar outlines three steps you can take:
Muralidhar recommends starting small and limiting the scope at first, and then expanding as you make things that work for you. He goes over some use cases, including how one bank saw a 35x (!) ROI on their marketing and the insights Mike’s favorite pizza chain, Casey’s, were able to uncover by looking at their data in new ways.
If you’re as psyched about Data Cloud as we are, there’s already a Trailmix to help you get started and even more resources on the way.
Gillian Bruce: Welcome to the Salesforce Admins Podcast, where we talk about product, community, and careers to help you be an awesome admin. I'm your host today, Gillian Bruce, and we have a very special guest, I'm sure all of you have been hearing about Data Cloud and all of the exciting innovations coming in that space from Salesforce. Guess what? We have the leader at Salesforce, our EVP of Engineering, NextGen Customer 360 data services at Salesforce.
MK: Thank you, Gillian. How are you?
Gillian Bruce: Oh, I'm wonderful. I am very, very happy to have you on the podcast today, and Mike is with us today as well.
Mike: Yes, hello. It's going to be an awesome podcast. Can't wait.
Gillian Bruce: We're going to have a data party on the podcast today.
Mike: It's always a data party.
Gillian Bruce: Okay, so MK, let's, before we get into it, can you just introduce yourself to our listeners and a little bit about what you do at Salesforce?
MK: Absolutely. Hi, my full name is Muralidhar Krishnaprasad. I also go by Murali or MK for short. I'm the executive vice President for engineering. My team, we deliver the data cloud that we are going to be talking about. Einstein that you guys might already know, the whole AI platform and then the analytics efforts with regard to Datorama and many others in Tableau and many others as well. So overall, think of it as data AI and analytics platforms being delivered here, and I've been here in Salesforce about four plus years. Prior to that, I worked at Microsoft building most of the Azure infrastructure dynamics and many others. And then I started my career before that at Oracle, building databases.
Gillian Bruce: Okay, so you're a busy person these days because all those products you just mentioned that you're working on at Salesforce, there's a lot going on there.
MK: Absolutely. Really, yes. There's a lot of news you would've heard as well as we are also doing a lot of integrations across Salesforce and across the industry as well.
Gillian Bruce: That's great. Okay, so let's dig into it. MK, can you explain to us what is Data Cloud?
MK: Yeah, in simple terms. So think of it as an admin. You're going to have various clouds today, sales cloud, marketing, commerce and so on. Problem that we often run into is businesses want to be able to really know what their customer is doing because a customer is not dealing with sales, cloud service, cloud marketing, they're dealing with your business. And so that means you really need to know what they have done. Have they ever opened an email you have sent them? Do they have service cases? Did salesperson make a call and try to sell them something or have they been on your website trying to browse something and purchase something? And this is common across all industries. It's not related to just finance or health. It's literally like every industry that you can think of goes through this motion.
Mike: Wow. Coming back from vacation, I find it funny that we can sit and have a data conversation and talk about lakes and lake houses, and you could totally do a podcast that people would think we're talking about vacation homes, don't you?Help my vacation brain boil this down for admins, what should admins know about cloud besides the Lakehouse?
MK: Great point. So I think as an admin, you need to be thrilled that data is not leaving your ambit because before, if you think about it as a Salesforce admin, you are only administering your cloud, but most of the businesses ended up taking all the data outside. And so your security layer was gone right there, and all the business semantics you created is also gone because they're going to get recreated somewhere else on some other platform.
Gillian Bruce: Okay. So get a little bit of work to do to get our arms around what data Cloud means for admins, but I like how you set it up there about how understanding, hey, it does give you... you're in control. I mean, all admins are control freaks, so that's a really good way of putting it. But in some ways, the idea of Data Cloud, MK kind of shifts the idea of what Salesforce can do.
MK: Yeah, great point. I think what you're looking at is certainly today your sales and service is in the same place. If you install in the same org, that is your sales and service can see all that data and you can put the right security, et cetera. But more often than not in any enterprise setting, there's a lot more data out there. We cannot bring that into Salesforce today because either it's a scale problem or it could be other issues related to their backend systems.
Mike: I was kind of excited when you said that because one of my vehicles, I get a monthly email on it's health, it's not electric, but I think it's from Salesforce. So I'm going to go with that because that would be really cool. So it sounds like, it's not like lightning flip a switch and here we are, but I think there's some stuff that admins need to do to help their organizations and just organizations in general, prepare. Could you MK could kind of touch on some of that?
MK: Yeah, I think it's a great point. I think what as an admin you need to do first, like I said, understand what Data Cloud is, but second is really understand what sources you want to bring data from into this data cloud, which org you want to obviously install the data cloud in first and then you may have business unit considerations, geo considerations and so on. And so we are introducing new concepts that you should be aware of. There's a new concept called Data Space, which allows you to have a data cloud and then still split the data within that via business units. It's a security concept and also you need to understand what are the layers that Data Cloud needs to go interface with. For example, it could be I have a marketing cloud here, I have a commerce here, I have these two sales cloud or two service Cloud.
Gillian Bruce: So I mean what I'm hearing here in terms of preparing is thinking about the flows of data, which data, I mean, would you go into setting up Data Cloud already with knowing the questions you want to answer, like say, Hey, I want to be able to get more people to buy this product by implementing Data Cloud, I'm going to be able to know when to target them. Or I mean, can you give us a little bit more of an example of what use cases might spur someone to want to implement and set up data
MK: Cloud? Yeah, great question. I think what we have seen success come is what you mentioned, Gillian, which is steel threads. If you have a clear steel thread the business wants to make happen and starting there, starting small and then building on it is better than a gigantic project where I'm going to bring in 50 different sources and not know how to use them. So I think what we have seen, great success. Obviously last year, data Cloud started off building our sort of go to business market in the marketing area, and now we are expanding beyond marketing. And so a lot of success we have seen is threads where people say, I have all this data. I want to bring in my marketing data, my sales service or external data. By the way, data Cloud today we have hundreds and hundreds of customers live on it.
Gillian Bruce: Wow.
MK: Instead of their scattershot, like send email to everybody thing, they sent much less emails to targeted people, and they saw huge returns on investment. And so they allow this now. And so that's a great example of one steel thread end-to-end that people have done. And we have seen similar things in various other customers as well.
Mike: I just have to pause for a second because everybody probably knows I live in the Midwest and the fact that Casey's uses this is now just above and beyond for me. Also, Casey's pizza is phenomenal. So MK, I don't know where you're based, but you need to come visit me in Iowa and we need to have some Casey's pizza because it's probably the best pizza you're ever going to have, and it's from a gas station. And it's a topic of conversation in the Midwest when people pass through. But yeah, I've also used the Casey's app and gotten very specific coupon things that I was like interesting. I have no idea how they would guess this, but if they're looking at my purchase history and every time I buy their breakfast pizza or so, holy cow, you just changed my life knowing that Casey's uses this.
MK: Yeah, and that's coming from Data Cloud, all the processing, all the things you buy, everything is going through Data Cloud.
Mike: That's so cool. That's so cool. I mean, I'm a huge Casey's fan anyway.
MK: That's awesome. Yes. See if I'm coming to the Midwest-
Mike: Gillian also knows that just about every podcast food gets mentioned on it. I wasn't even the first one to mention it, Gillian.
Gillian Bruce: I know. Well, I could hear your wheels turning as soon as MK talked about Casey's Pizza. I feel like you've even talked about it on the podcast before.
Mike: You have no idea how good their pizza is.
MK: And there is a press release also that we did late last year that you can reference to your customers to go look at it.
Gillian Bruce: We'll put it in the show notes.
Mike: Speaking of things to put in the show notes, MK, could you provide some admins with tips or resources on where they can get started learning about Data Cloud perhaps maybe while they eat Casey's Pizza?
MK: Yes. I think if you go to salesforce.com data cloud, we have a lot of materials there. We are also preparing New Trailheads as well. There's already a Trailhead that you can take and there are more coming along the way. And of course we have the standard documentation that can help them as well for them to use Data Cloud. The main thing to realize in Data Cloud is it is a Salesforce cloud that can really change your business. And so learn how to bring data, how to harmonize, and then how to create the insights of it and then push it back into all your systems.
Gillian Bruce: Oh, that's great. MK, I so appreciate you taking the time to chat with us today and demystify Data Cloud for admins, and I have a feeling there's going to be a lot more in this space.
Mike: Seriously, and I'm going to use Data Cloud today when I order pizza or maybe tomorrow.
MK: Right. Whenever you eat Casey's Pizza, think of-
Mike: Oh my God, I am going to start racking up some data in Data Cloud for guys.
Gillian Bruce: You got to show us what insights you're getting or is that like too going to expose your habits too much? I don't know.
Mike: I will willingly give anybody that wants to visit me a demo of the Casey's app in my backyard if we can order pizza.
Gillian Bruce: I love it. MK, thank you so much for joining us and I really appreciate all the work that you're doing in this really important space. And we didn't even talk about anything AI or Einstein related, so we'll have to do that on another podcast. But thank you to you and your team for all the great work that you do, and we look forward to hearing from you again very soon.
MK: Sounds great. Thank you both. This was a great conversation. Again, we you'll see more of Data Cloud and more of Einstein Automation, Tableau and all of that coming through the next few months and years.
Gillian Bruce: Huge thanks to MK for taking time out of his very, very busy schedule to chat with Mike and I. It was also fun to do a podcast with Mike. It's been a while since we've done one of those. I hope that you got some good ideas and thoughts and questions from some of the things that MK shared with us about Data Cloud. I mean, it is one of the most exciting areas right now in Salesforce ecosystem of innovation, and it really opens up some exciting possibilities of what we can do as admins with our declarative capabilities to really bring in the power of data and have those truly connected customer experiences.
Direct download: Data_Cloud_for_Admins_with_Muralidhar_Krishnaprasad.mp3
Category:general -- posted at: 3:00am PDT