1 00:00:14,462 --> 00:00:17,982 Justin Norris: I'm a really big believer in the idea of RebOps as a function, 2 00:00:17,982 --> 00:00:22,202 supporting all the go to market teams, marketing, sales, customer success. 3 00:00:22,537 --> 00:00:27,017 Quite often partner ops or data ops to this belief is one of the 4 00:00:27,017 --> 00:00:28,217 reasons for the name of this show. 5 00:00:28,217 --> 00:00:32,077 And it's really why I try to take a broad view across the entire go 6 00:00:32,077 --> 00:00:36,137 to market function in terms of the episodes and the guests that we have. 7 00:00:36,567 --> 00:00:38,997 But I'll be honest, sometimes it's a little discouraging when I look 8 00:00:38,997 --> 00:00:41,057 at how Rev Ops is done in practice. 9 00:00:41,057 --> 00:00:44,617 And when I look at job descriptions for Rev Ops leaders, because outside 10 00:00:44,627 --> 00:00:49,027 of a few examples, I usually see essentially a sales ops function with. 11 00:00:49,347 --> 00:00:54,697 So I posted on LinkedIn a few weeks ago, thinking out loud and asking who's 12 00:00:54,697 --> 00:00:59,247 actually leading a unified rev ops team in the real world, where are all 13 00:00:59,257 --> 00:01:02,467 these people and how are they doing it and how's it working out for them? 14 00:01:03,007 --> 00:01:05,577 And lo and behold, I got connected with a bunch of really smart 15 00:01:05,577 --> 00:01:08,567 folks who you'll be hearing from in the weeks and months ahead. 16 00:01:08,967 --> 00:01:14,197 And first on that list is Julia Kim, VP of revenue operations at electric, 17 00:01:14,457 --> 00:01:16,527 where she leads a unified rev ops team. 18 00:01:17,017 --> 00:01:20,967 Julie has been an operations executive for over 10 years now, and is also an 19 00:01:20,987 --> 00:01:23,207 adjunct professor at Columbia university. 20 00:01:23,612 --> 00:01:25,892 So she's got a ton of good stuff to share with us. 21 00:01:26,382 --> 00:01:28,312 Very excited to chat with you today, Julia. 22 00:01:28,765 --> 00:01:32,185 Julia Kim: I'm absolutely thrilled to be here because I absolutely 23 00:01:32,185 --> 00:01:33,425 know what you're talking about. 24 00:01:33,755 --> 00:01:34,795 It is a challenge. 25 00:01:34,795 --> 00:01:39,125 I think a lot of people think of RevOps as a sales ops function, but 26 00:01:39,325 --> 00:01:44,175 you're missing out on so many of the benefits of revenue operations 27 00:01:44,185 --> 00:01:46,435 if you think in sort of that silo. 28 00:01:46,705 --> 00:01:48,965 And so I'm really glad we're going to be able to talk about 29 00:01:48,995 --> 00:01:49,495 that today. 30 00:01:50,002 --> 00:01:50,562 Justin Norris: Amazing. 31 00:01:50,592 --> 00:01:54,602 So maybe let's start there with revenue operations. 32 00:01:54,652 --> 00:01:55,722 How do you think of it? 33 00:01:55,722 --> 00:01:57,922 If you had to put it in a nutshell, what's the scope and 34 00:01:57,922 --> 00:01:59,372 what is the mandate of RevOps? 35 00:02:00,063 --> 00:02:03,763 Julia Kim: So here at electric, it really is very cross functional 36 00:02:03,793 --> 00:02:07,093 and very much focused on the go to market teams and motion. 37 00:02:07,643 --> 00:02:12,783 So, if you think about what teams typically are included in a go to market 38 00:02:12,783 --> 00:02:17,918 team, You know, kind of scope, it would be sales, marketing, customer success, 39 00:02:17,958 --> 00:02:23,628 partnerships or business development a little bit of finance thrown in but lots 40 00:02:23,629 --> 00:02:27,728 of different opportunities to collaborate when it comes to generating revenue, 41 00:02:27,739 --> 00:02:29,998 whether it's through new business net new. 42 00:02:30,309 --> 00:02:35,029 or retention through existing customers and then utilizing your relationship 43 00:02:35,039 --> 00:02:36,989 with those customers to grow revenue. 44 00:02:37,469 --> 00:02:41,229 And so when I think about revenue operations, I really think about it 45 00:02:41,229 --> 00:02:43,349 in the context of all of those teams. 46 00:02:43,859 --> 00:02:47,308 And then also thinking about it from the perspective of data. 47 00:02:47,628 --> 00:02:48,949 What data do we have? 48 00:02:49,149 --> 00:02:50,508 How are we collecting that data? 49 00:02:50,528 --> 00:02:51,778 How are we storing that data? 50 00:02:51,778 --> 00:02:53,408 How are we reporting on that data? 51 00:02:53,978 --> 00:02:54,978 The process. 52 00:02:55,529 --> 00:02:58,809 in terms of what's different between a marketing process that may be 53 00:02:58,809 --> 00:03:03,489 top of funnel versus a customer success workflow in, retention. 54 00:03:04,259 --> 00:03:08,629 And then also thinking about it from a tech stack perspective, because one of 55 00:03:08,629 --> 00:03:13,368 the biggest drivers and one of the things I leverage all the time is technology 56 00:03:13,389 --> 00:03:15,719 because that is a multiplier for you. 57 00:03:16,039 --> 00:03:19,829 A lot of times RevOps teams don't get a ton of support internally. 58 00:03:19,929 --> 00:03:23,969 Fortunately for me here at Electric, there's a ton of support for RevOps, 59 00:03:24,239 --> 00:03:27,629 but in many organizations you don't get a lot of the support that you need 60 00:03:28,099 --> 00:03:30,298 in the form of resources or people. 61 00:03:30,559 --> 00:03:31,639 And so what do you do? 62 00:03:31,738 --> 00:03:36,869 You can absolutely use technology to help multiply all of those benefits that you 63 00:03:36,869 --> 00:03:39,069 would get from a unified RevOps team. 64 00:03:39,449 --> 00:03:42,039 Justin Norris: /one of the things that I think about a lot. 65 00:03:42,579 --> 00:03:47,264 Is where does the responsibility of the function itself and, 66 00:03:47,264 --> 00:03:48,787 where does rev ops begin? 67 00:03:48,807 --> 00:03:51,147 I mean, there's certain things like technology is a, is an area where 68 00:03:51,147 --> 00:03:53,307 it's usually quite unambiguous. 69 00:03:53,627 --> 00:03:57,360 And then I find that there are sometimes gray areas where it's a partnership. 70 00:03:57,370 --> 00:03:58,620 There's some push and pull. 71 00:03:59,186 --> 00:04:00,216 how do you think about that? 72 00:04:00,216 --> 00:04:02,546 like, where do people say, like, we need to bring ops in for 73 00:04:02,546 --> 00:04:03,966 this sort of problem in your 74 00:04:04,531 --> 00:04:08,661 Julia Kim: it really depends on where you are in the spectrum of 75 00:04:08,681 --> 00:04:11,181 maturity for your organization. 76 00:04:11,211 --> 00:04:15,151 And I think this is a piece that is sometimes missed because I think a lot of 77 00:04:15,151 --> 00:04:20,493 times people just kind of have a blanket approach to how they balance that ratio of 78 00:04:20,593 --> 00:04:23,693 operational tactical things and strategy. 79 00:04:24,043 --> 00:04:27,803 And so When I first came to Electric, I was actually actively recruited 80 00:04:27,803 --> 00:04:29,563 to join two fixed rev ops there. 81 00:04:30,583 --> 00:04:32,583 There was a lot that was going on. 82 00:04:32,583 --> 00:04:35,466 were more on the immature side when it came to the 83 00:04:35,466 --> 00:04:37,356 operations and tactical pieces. 84 00:04:37,676 --> 00:04:41,426 And so when you think about an organization that's in that state, you 85 00:04:41,426 --> 00:04:46,051 really have to think about What is going to benefit the organization the most? 86 00:04:46,091 --> 00:04:50,101 And it's usually the more operational processes, less on the strategy. 87 00:04:50,101 --> 00:04:53,701 It's the doing and getting things done and kind of cleaning things 88 00:04:53,701 --> 00:04:55,811 up and right sizing things. 89 00:04:55,841 --> 00:05:00,991 And so if you're in an organization where you're sort of on that immature 90 00:05:00,991 --> 00:05:05,780 side of that spectrum, you're spending a lot more time doing Less time 91 00:05:05,800 --> 00:05:09,230 on the responsibility of coming up with the strategy and the direction. 92 00:05:09,740 --> 00:05:14,770 However, as the organization matures, and this is where electric is today, 93 00:05:15,180 --> 00:05:19,890 we're fairly mature on the operational And that's where RevOps has come in 94 00:05:19,900 --> 00:05:22,290 more recently to be much more strategic. 95 00:05:22,320 --> 00:05:28,250 So one of the things that I try to align at every stage of RevOps 96 00:05:28,260 --> 00:05:30,780 organization is your org design. 97 00:05:31,430 --> 00:05:34,700 So if you think about your org design, it's who are the people 98 00:05:34,740 --> 00:05:36,200 that are on your RevOps team. 99 00:05:36,320 --> 00:05:38,470 In Electric, it's a stand alone team. 100 00:05:38,470 --> 00:05:42,254 some organizations, RevOps as a function is embedded within the 101 00:05:42,254 --> 00:05:43,344 different go to market teams. 102 00:05:43,354 --> 00:05:46,504 So there might be an ops person on marketing, an ops person on sales, 103 00:05:46,724 --> 00:05:49,714 but at Electric, everything is centralized into a central team. 104 00:05:49,844 --> 00:05:51,384 And that's actually worked out really well. 105 00:05:51,864 --> 00:05:57,409 And when I first started, It was more focus on the operational aspects. 106 00:05:57,409 --> 00:06:01,869 So we could get all the things done, build those processes, get the data in 107 00:06:01,879 --> 00:06:05,719 the systems be able to report on how we're doing and what's happening in the 108 00:06:05,719 --> 00:06:07,959 systems and the processes that we have. 109 00:06:08,409 --> 00:06:10,169 But as we became more mature. 110 00:06:11,104 --> 00:06:15,994 The strategy piece became a larger and larger component of what RevOps is. 111 00:06:16,324 --> 00:06:20,944 And so as part of that, I actually added a new team within 112 00:06:20,974 --> 00:06:23,024 RevOps called Revenue Programs. 113 00:06:23,394 --> 00:06:27,834 And essentially what Revenue Programs does is it is very much forward thinking. 114 00:06:28,224 --> 00:06:32,401 They are thinking about piloting testing out those operational processes 115 00:06:32,671 --> 00:06:36,681 at a very small scale, sometimes manually, sometimes with light. 116 00:06:37,131 --> 00:06:41,181 Technology or light automation just to make sure that one, we're seeing the 117 00:06:41,181 --> 00:06:44,781 outcomes that we want, that we kind of work out all those kinks that, you 118 00:06:44,781 --> 00:06:48,081 know, can exist in any process because, anyone can come up with the process, 119 00:06:48,081 --> 00:06:49,511 but does it actually work right? 120 00:06:49,761 --> 00:06:52,891 you don't know sometimes until you actually roll it out and the 121 00:06:52,891 --> 00:06:57,801 mistake and, you know, For a lot of organizations, I think, is when you 122 00:06:57,801 --> 00:07:00,911 roll something out with expectation that it's just going to work perfectly 123 00:07:00,911 --> 00:07:02,651 on day one, and that's not the case. 124 00:07:02,691 --> 00:07:05,961 I think if you are an organization like Electric, where you're a 125 00:07:05,961 --> 00:07:08,261 startup, you need to move quickly. 126 00:07:08,261 --> 00:07:10,031 Things are shifting constantly. 127 00:07:10,271 --> 00:07:13,201 You really do need to take a more iterative and agile approach. 128 00:07:13,201 --> 00:07:17,161 And so, Revenue Programs is actually a new what I call a pod. 129 00:07:17,161 --> 00:07:18,801 So, we have a Sales Ops pod. 130 00:07:19,111 --> 00:07:24,491 A marketing ops pod, a CX pod partnerships and business development 131 00:07:24,491 --> 00:07:26,171 actually falls under the sales ops pod. 132 00:07:26,171 --> 00:07:29,911 We also have a tech ops pod that supports all of the tech stack that we 133 00:07:29,911 --> 00:07:34,931 have, but we now also have a revenue programs pod because that is where we 134 00:07:34,931 --> 00:07:39,276 do a lot of our experimentation and say, Does it make sense to you know, 135 00:07:39,276 --> 00:07:40,916 roll out this type of payment plan? 136 00:07:40,926 --> 00:07:45,526 Does it make sense for us to have the CSMs own this part of, you know, the process? 137 00:07:45,526 --> 00:07:50,666 And it's been really great because as we shift and continue to grow, I 138 00:07:50,686 --> 00:07:54,676 think strategy is going to be a larger and larger part of what Rev Ops does. 139 00:07:55,056 --> 00:07:58,166 But for many organizations where you're sort of in the earlier 140 00:07:58,166 --> 00:08:02,726 stages, it's probably not feasible to be as strategic or. 141 00:08:02,961 --> 00:08:06,421 Own a lot of that directionality you're talking about because 142 00:08:06,421 --> 00:08:07,621 there's just too many things on 143 00:08:07,621 --> 00:08:08,021 fire. 144 00:08:08,763 --> 00:08:11,736 Justin Norris: It's kind of a hierarchy of needs, almost, if we think about it that 145 00:08:11,771 --> 00:08:12,721 Julia Kim: Absolutely. 146 00:08:12,881 --> 00:08:13,611 Absolutely. 147 00:08:14,293 --> 00:08:16,743 Justin Norris: run an email campaign, then you're not necessarily going to 148 00:08:16,753 --> 00:08:20,423 be thinking deeply about strategy until you have those fundamentals in place. 149 00:08:21,211 --> 00:08:21,521 Julia Kim: Yes. 150 00:08:21,521 --> 00:08:24,821 people are like, well, what's the value of revenue operations if they 151 00:08:24,821 --> 00:08:26,911 can't even get in your example, right? 152 00:08:26,911 --> 00:08:32,631 An email campaign, you know, standardized and have it deliver in terms of, click 153 00:08:32,631 --> 00:08:34,141 through rates or things like that. 154 00:08:34,461 --> 00:08:39,031 And so again, it's really focusing on where can you provide the most value? 155 00:08:39,181 --> 00:08:40,721 And once you hit those. 156 00:08:41,186 --> 00:08:43,926 points, that's when you have to really think about, okay, well, how 157 00:08:43,926 --> 00:08:46,566 can I shift more of to that strategy? 158 00:08:46,566 --> 00:08:49,916 So we're not in a place where we're being reactive because I think a lot 159 00:08:49,916 --> 00:08:52,126 of rev ops teams are very reactive. 160 00:08:52,436 --> 00:08:56,866 And so how do you shift from being very reactive to being more proactive? 161 00:08:57,466 --> 00:08:59,286 It's also part of that maturity, right? 162 00:08:59,286 --> 00:09:02,086 Because when you're strategic, you can almost put those processes in 163 00:09:02,086 --> 00:09:04,006 place to help you be more strategic. 164 00:09:04,421 --> 00:09:07,461 But you can't get there without kind of cleaning house and making 165 00:09:07,461 --> 00:09:08,791 sure your own house is in order. 166 00:09:09,358 --> 00:09:11,078 Justin Norris: I'm fascinated by the structure of your team. 167 00:09:11,078 --> 00:09:15,048 And so I want to just pull those different pods apart a bit that you described. 168 00:09:15,408 --> 00:09:18,818 Maybe we'll just start with the tech podcast, perhaps it's the easiest 169 00:09:19,008 --> 00:09:21,848 for everyone to understand, but it sounds to me like kind of almost like 170 00:09:21,848 --> 00:09:25,488 a business systems function embedded within your team runs the technology. 171 00:09:25,768 --> 00:09:27,338 Is that an accurate way of thinking about it? 172 00:09:27,906 --> 00:09:29,246 Julia Kim: Yes, absolutely. 173 00:09:29,246 --> 00:09:32,556 they are responsible for primarily for our CRM system. 174 00:09:32,556 --> 00:09:34,266 We use Salesforce at electric. 175 00:09:34,316 --> 00:09:38,001 And a lot of what they do is. 176 00:09:38,077 --> 00:09:41,354 day to day in terms of ticket management, because obviously there 177 00:09:41,354 --> 00:09:45,324 are many issues that might come up or, you know, people want different 178 00:09:45,324 --> 00:09:47,124 fields or different functions. 179 00:09:47,774 --> 00:09:50,584 They're also responsible for things like tech debt. 180 00:09:50,684 --> 00:09:53,684 You know, with any systems you often have things that you really need 181 00:09:53,684 --> 00:09:57,794 to think about cleaning up in order to kind of maintain the system. 182 00:09:58,064 --> 00:10:02,514 And then also strategy in terms of how can we expand the use of our 183 00:10:02,514 --> 00:10:04,514 systems in order to make it better? 184 00:10:04,764 --> 00:10:10,274 So one great example is we use Salesforce primarily for 185 00:10:10,344 --> 00:10:12,464 sales cloud and service cloud. 186 00:10:12,494 --> 00:10:18,654 We also have Salesforce CPQ and billing, but is what we have in 187 00:10:18,654 --> 00:10:23,544 place good enough or supporting the partnerships and business 188 00:10:23,544 --> 00:10:25,364 development we're trying to accomplish? 189 00:10:25,834 --> 00:10:30,944 Right now we're okay, but I think we'll soon get to a point Because of the 190 00:10:30,944 --> 00:10:35,374 partnerships that we have, because of the partner ecosystem, we have that we 191 00:10:35,374 --> 00:10:40,794 will likely need to think about, you know, are there more ways that we can 192 00:10:40,794 --> 00:10:45,113 leverage salesforce or some other tool that maybe integrates with salesforce 193 00:10:45,153 --> 00:10:48,023 to better enable both internal folks. 194 00:10:48,358 --> 00:10:51,058 And also external partners, right? 195 00:10:51,408 --> 00:10:56,558 And so really thinking about that and starting to do discovery around 196 00:10:56,558 --> 00:11:01,398 that and really having a milestone in place that says when partnerships 197 00:11:01,448 --> 00:11:04,708 looks like this might be a good time for us to kind of pull the trigger and 198 00:11:04,708 --> 00:11:06,578 start really being serious about this. 199 00:11:07,078 --> 00:11:10,658 But that's where tech ops has been, you know, an amazing partner 200 00:11:10,658 --> 00:11:14,618 for many of these go to market teams, because it's not just about. 201 00:11:15,098 --> 00:11:18,558 Making sure that the systems are running, but it's also thinking strategically 202 00:11:18,558 --> 00:11:20,408 about what are their needs in the future, 203 00:11:20,850 --> 00:11:23,860 Justin Norris: And are they running all the technology that 204 00:11:23,860 --> 00:11:24,970 the go to market teams use? 205 00:11:24,970 --> 00:11:27,370 Or are there like, let's say your marketing automation system, or 206 00:11:27,370 --> 00:11:31,470 maybe even smaller, tools with a, with a narrower scope, are those run 207 00:11:31,470 --> 00:11:33,010 by some of the other pods directly? 208 00:11:33,988 --> 00:11:37,928 Julia Kim: So it used to be that a lot of those tools were actually centralized 209 00:11:37,928 --> 00:11:42,195 and tech ops, but again, part of this maturity model that I'm talking about. 210 00:11:42,795 --> 00:11:46,555 You sometimes get to a point where you need to really dig deeper 211 00:11:46,555 --> 00:11:47,965 into the tools that you have. 212 00:11:48,375 --> 00:11:51,135 And at that point, you need someone who's almost a subject 213 00:11:51,135 --> 00:11:52,755 matter expert in that tool. 214 00:11:52,765 --> 00:11:56,275 So it's not just about administering the tool, like adding users or 215 00:11:56,275 --> 00:11:58,425 removing users or turning on features. 216 00:11:58,765 --> 00:12:03,135 It's almost thinking about what are we not using or what are we 217 00:12:03,135 --> 00:12:04,815 using that we could use better? 218 00:12:05,025 --> 00:12:08,175 And so now the shift has actually been. 219 00:12:08,595 --> 00:12:09,815 Exactly what you're saying. 220 00:12:10,045 --> 00:12:15,125 We are now moving a lot of these core systems, for example, like our marketing 221 00:12:15,125 --> 00:12:19,535 automation platform, which is Marketo, or our customer engagement platform, 222 00:12:19,535 --> 00:12:24,665 which is Gainsight, we're moving them now into the Ops Manager's domain, because 223 00:12:24,665 --> 00:12:29,315 they're likely to have much better insight and how we can leverage those tools. 224 00:12:29,575 --> 00:12:32,445 They can build those relationships with our vendors. 225 00:12:32,865 --> 00:12:39,133 And so it's really about figuring out how can we dig even deeper, 226 00:12:39,143 --> 00:12:42,353 and I think this also aligns with what a lot of companies are doing. 227 00:12:42,718 --> 00:12:44,428 the economy is not that great. 228 00:12:44,473 --> 00:12:48,783 And so a lot of RevOps teams are being asked to, you know, be strategic, do 229 00:12:48,783 --> 00:12:53,415 some tech consolidation seeing how they can reduce expenses, right, And 230 00:12:53,415 --> 00:12:59,771 so part of that for us at electric has been how can I have my team, Almost 231 00:12:59,771 --> 00:13:04,111 say, is this really a tool or is there another tool that we're using that 232 00:13:04,111 --> 00:13:08,271 has the same exact features, but we can incorporate a lower costs or maybe 233 00:13:08,271 --> 00:13:10,051 it's already included in our contract. 234 00:13:10,461 --> 00:13:12,571 A great example is a chat feature. 235 00:13:12,571 --> 00:13:17,651 We had actually three different tools that had chat, and one of the nice things 236 00:13:17,651 --> 00:13:23,681 about Marketo was that they talked about this AI driven dynamic chat feature that 237 00:13:23,681 --> 00:13:27,841 they rolled out last year, and we were clearly not leveraging because we were 238 00:13:27,841 --> 00:13:30,041 using two other chat, you know, platforms. 239 00:13:30,451 --> 00:13:34,311 And so that's a great opportunity for us to say, okay, well, let's 240 00:13:34,311 --> 00:13:36,021 not pay for these other two tools. 241 00:13:36,331 --> 00:13:38,741 Let's consolidate in a tool we have, Marketo. 242 00:13:39,071 --> 00:13:44,951 Leverage the AI features that they're saying are fantastic and really make 243 00:13:44,951 --> 00:13:48,171 that experience for our prospects even better than they were before. 244 00:13:48,571 --> 00:13:53,321 And so I think that's a strategy that anyone can take, especially at a 245 00:13:53,321 --> 00:13:56,731 time like this, when a lot of finance teams are saying, Hey, you know, 246 00:13:56,841 --> 00:13:58,331 we're spending a lot on these tools. 247 00:13:58,351 --> 00:13:59,161 What can we do? 248 00:13:59,850 --> 00:14:03,120 Justin Norris: And what you just described in a way, to me, it highlights 249 00:14:03,120 --> 00:14:07,813 some of the benefits ostensibly that we should gain from RevOps and 250 00:14:07,813 --> 00:14:10,653 that we, we don't have these silos where like, you know, sales ops has 251 00:14:10,653 --> 00:14:12,150 a tool and marketing ops has a tool. 252 00:14:12,180 --> 00:14:15,500 Um, The team's actually can look at things holistically together. 253 00:14:16,190 --> 00:14:19,220 And I'm curious, how do those different, like, you've got your marketing ops 254 00:14:19,240 --> 00:14:22,380 pod, your sales ops pod, and your CFs pod, aside from the fact that they all 255 00:14:22,390 --> 00:14:25,810 roll up to you, how do they collaborate together on like a day to day basis 256 00:14:25,810 --> 00:14:27,200 to make these sorts of decisions? 257 00:14:28,123 --> 00:14:31,173 Julia Kim: Yeah, there's a few different ways that I've built 258 00:14:31,233 --> 00:14:34,043 collaboration into our team. 259 00:14:34,658 --> 00:14:38,528 It really starts with just us being humans and getting to know each 260 00:14:38,528 --> 00:14:42,062 other and enjoying, the day to day and working with each other. 261 00:14:42,372 --> 00:14:46,922 So, I do a lot with my team to really build up our personal relationship, 262 00:14:46,932 --> 00:14:49,542 because if you don't enjoy working with them, and we're at work for 263 00:14:49,542 --> 00:14:51,664 many hours a day, that's a problem. 264 00:14:51,664 --> 00:14:55,924 And so we've built 1, a really strong team of high performers. 265 00:14:55,944 --> 00:14:59,334 And then 2, we have a lot of activities where we're. 266 00:14:59,674 --> 00:15:02,624 maybe not talking about RevOps, but we're getting to know each 267 00:15:02,624 --> 00:15:05,594 other, we're solving problems together, we're having fun together. 268 00:15:05,854 --> 00:15:09,034 We have a weekly meeting on Friday afternoons called Weekly Wins. 269 00:15:09,254 --> 00:15:14,075 It started out with a whole was a win that I had from a professional perspective 270 00:15:14,075 --> 00:15:16,845 to what did I have as a personal win? 271 00:15:17,105 --> 00:15:20,905 But What we found was, we knew so much about what was happening week over 272 00:15:20,905 --> 00:15:23,115 week that wasn't really that engaging. 273 00:15:23,125 --> 00:15:27,085 And so we actually now have it essentially a half hour game time together. 274 00:15:27,355 --> 00:15:30,275 And so we break up into teams, we have different formations, we are 275 00:15:30,275 --> 00:15:31,825 competitive, we solve problems. 276 00:15:32,115 --> 00:15:36,685 And so all of those things are ways that aren't focused on our day to 277 00:15:36,685 --> 00:15:40,035 day, but we're still getting to know each other, build culture, and then 278 00:15:40,035 --> 00:15:41,495 learn to solve problems together. 279 00:15:42,360 --> 00:15:47,140 On the flip side, when it comes to projects and visibility, we have a 280 00:15:47,150 --> 00:15:50,780 weekly team stand on Tuesday mornings where we go through high priority 281 00:15:50,810 --> 00:15:54,230 projects, people kind of flag different things that they're talking about. 282 00:15:54,690 --> 00:15:58,260 We also have systems in place to help us because as much as we all 283 00:15:58,260 --> 00:15:59,580 want to be creatures of habits. 284 00:16:00,040 --> 00:16:04,280 There's a lot of things that are often being thrown at RevOps teams, so having 285 00:16:04,280 --> 00:16:08,020 systems in place to help collaborate, so we're very active on Slack. 286 00:16:08,370 --> 00:16:12,166 We have dedicated, internal Slack channels for different things. 287 00:16:13,056 --> 00:16:14,746 we use the Atlassian suite. 288 00:16:14,746 --> 00:16:16,996 So we use Confluence for documentation. 289 00:16:17,006 --> 00:16:18,636 That is so important to us. 290 00:16:19,036 --> 00:16:21,796 I was looking at just the sheer number of documents that we 291 00:16:21,796 --> 00:16:23,206 created in the last six months. 292 00:16:23,206 --> 00:16:27,736 And it's, over 150 pages that we created, which is incredible the more 293 00:16:27,756 --> 00:16:31,036 information that you're sharing, the better, not just for us internally, 294 00:16:31,036 --> 00:16:32,786 but for the entire organization. 295 00:16:33,096 --> 00:16:35,416 And then we use JIRA as another tool. 296 00:16:35,571 --> 00:16:37,108 Again, to help with collaboration. 297 00:16:37,328 --> 00:16:40,408 So the way that every day starts is that we actually have a 9 a. 298 00:16:40,408 --> 00:16:40,728 m. 299 00:16:40,824 --> 00:16:43,484 JIRA stand, where we go through all the tickets that came 300 00:16:43,484 --> 00:16:44,774 through together as a team. 301 00:16:44,794 --> 00:16:45,784 It's really quick. 302 00:16:46,404 --> 00:16:49,814 On average, it's about 7, 10 minutes, but we allocate about 303 00:16:49,814 --> 00:16:51,064 15 minutes every morning. 304 00:16:51,264 --> 00:16:53,802 So we're, going through things that are high priority, any 305 00:16:53,812 --> 00:16:55,172 incidents that come through. 306 00:16:55,532 --> 00:16:59,980 And then we're leaving most of the day to work on different projects. 307 00:16:59,980 --> 00:17:06,100 And between the weekly team stand touch point, and then just the constant 308 00:17:06,100 --> 00:17:13,390 communication that happens on Slack and usage of JIRA, we are in pretty 309 00:17:13,390 --> 00:17:19,190 good communication and fairly aware of what's happening from marketing 310 00:17:19,240 --> 00:17:22,598 all the way to, customer success. 311 00:17:22,698 --> 00:17:23,698 The one thing that. 312 00:17:24,043 --> 00:17:29,063 I have been consciously doing from an internal perspective to even broaden 313 00:17:29,063 --> 00:17:32,723 our understanding because 1 of the things that electric has been doing 314 00:17:32,973 --> 00:17:36,593 in the last 6 months is shifting from a sales led organization to a 315 00:17:36,593 --> 00:17:38,533 much more product led organization. 316 00:17:38,753 --> 00:17:43,283 So the emphasis is much more on the product is really educating everyone 317 00:17:43,283 --> 00:17:49,733 on what that means and bringing in engineering, bringing in product into 318 00:17:49,733 --> 00:17:55,103 those conversations and really trying to, break down those silos that has been one 319 00:17:55,213 --> 00:18:00,133 of the things that we've been actively working with all of the teams around. 320 00:18:00,463 --> 00:18:04,233 And I think we've been able to make this transition into a 321 00:18:04,233 --> 00:18:05,873 more product led organization. 322 00:18:05,873 --> 00:18:09,218 We have a ways to go because our product, we revamped our product 323 00:18:09,218 --> 00:18:10,818 in November and relaunched it. 324 00:18:11,038 --> 00:18:12,038 And that's newer. 325 00:18:12,268 --> 00:18:16,888 And so there's still a lot of growth there, but there's a ton of collaboration, 326 00:18:16,888 --> 00:18:22,258 a ton of communication, not just within RevOps, but outside of RevOps that is 327 00:18:22,268 --> 00:18:24,828 also feeding back within the team itself. 328 00:18:24,838 --> 00:18:30,238 So it's really about building all of that communication and collaboration 329 00:18:30,238 --> 00:18:34,596 at many different levels so that there isn't one thing that's solving the 330 00:18:34,596 --> 00:18:37,596 problem, but it's all these little things that are contributing to a 331 00:18:37,596 --> 00:18:43,226 much more smooth and standardized and I would say even consistent process. 332 00:18:44,368 --> 00:18:46,594 Justin Norris: My friend Paul Wilson has a phrase that's really stuck with 333 00:18:46,594 --> 00:18:49,961 me about teams that run the business and then other teams that change the 334 00:18:49,961 --> 00:18:51,271 business and how you kind of need both. 335 00:18:51,721 --> 00:18:53,151 Is that how you think about it as well? 336 00:18:53,161 --> 00:18:56,433 Like the programs team is really there to come in and like disrupt 337 00:18:56,433 --> 00:18:58,473 business as usual and figure out better ways of doing things? 338 00:18:58,974 --> 00:18:59,804 Julia Kim: Absolutely. 339 00:18:59,854 --> 00:19:04,104 A great example is that with our new product, you can 340 00:19:04,104 --> 00:19:06,024 actually buy Result software. 341 00:19:06,024 --> 00:19:07,454 You can buy services from us. 342 00:19:08,194 --> 00:19:12,264 You can buy hardware like a new computer and bundle it with a 343 00:19:12,264 --> 00:19:14,544 monitor and all kinds of things. 344 00:19:14,564 --> 00:19:21,794 And so the question was, where does it live in terms of, Hey, we want to 345 00:19:21,794 --> 00:19:24,074 experiment with a flexible payment plan. 346 00:19:24,084 --> 00:19:24,934 Where does that live? 347 00:19:24,964 --> 00:19:25,914 Does that live in product? 348 00:19:25,954 --> 00:19:27,044 Does that live in engineering? 349 00:19:27,044 --> 00:19:28,154 Does that live in finance? 350 00:19:28,154 --> 00:19:28,824 Does that live? 351 00:19:28,824 --> 00:19:31,844 with the customer success team, like where does that live? 352 00:19:32,284 --> 00:19:35,374 And I think a lot of companies struggle with that question. 353 00:19:35,634 --> 00:19:39,574 And so you end up wasting a lot of time trying to find the right home 354 00:19:39,584 --> 00:19:41,194 or someone says, Hey, you know what? 355 00:19:41,194 --> 00:19:44,614 I think I'm going to lead this project, but they don't have the right support. 356 00:19:44,614 --> 00:19:46,004 They don't have the right resources. 357 00:19:46,004 --> 00:19:47,404 They don't have the right access. 358 00:19:47,694 --> 00:19:51,255 And so the project just stalls for a period of time. 359 00:19:51,255 --> 00:19:53,285 And then people are like, what happened to that project? 360 00:19:53,455 --> 00:19:55,435 thought we were going to do, flexible payments. 361 00:19:56,170 --> 00:20:01,710 And so that revenue programs pod essentially answers that question, it's 362 00:20:01,710 --> 00:20:06,580 not that they have full ownership of all the aspects of flexible payments 363 00:20:06,580 --> 00:20:08,260 in this example I'm sharing with you. 364 00:20:08,920 --> 00:20:13,850 But they have the ability to bring in the right people at the right time. 365 00:20:14,390 --> 00:20:18,530 They have the ability to project manage that project and essentially put some 366 00:20:18,530 --> 00:20:22,310 stakes in the ground saying, hey, let's do discovery and see what comes out of this. 367 00:20:22,390 --> 00:20:27,297 Let's see, what we can, Push out as an initial product offering, does 368 00:20:27,297 --> 00:20:28,977 it mean from a legal perspective? 369 00:20:29,087 --> 00:20:34,077 Let me go back to sales ops and see how that looks within that process, or 370 00:20:34,187 --> 00:20:37,707 let me go to the procurement team and let me understand what that looks like. 371 00:20:37,717 --> 00:20:43,807 So it provides those really important initiatives a home, but maybe not 372 00:20:43,847 --> 00:20:47,257 ownership, because at the end of the day, there's probably a different 373 00:20:47,257 --> 00:20:48,607 team that needs to own that. 374 00:20:48,607 --> 00:20:49,707 Maybe it's finance. 375 00:20:49,727 --> 00:20:50,237 Maybe it's. 376 00:20:50,333 --> 00:20:56,253 product, I'm not sure, but it allows us to still move forward and maybe get to 377 00:20:56,253 --> 00:20:58,482 the point where end owner is obvious. 378 00:20:58,492 --> 00:21:02,579 And not only that, but we have some real data about what happened, we put 379 00:21:02,579 --> 00:21:06,109 a social post up and people actually click the button and raise their 380 00:21:06,109 --> 00:21:07,899 hand and saying, I'm interested. 381 00:21:07,939 --> 00:21:12,959 But I think it provides us an ability to move forward without all the pieces in 382 00:21:12,959 --> 00:21:16,459 place, because I think that's the biggest killer for a lot of startups, right? 383 00:21:16,899 --> 00:21:19,459 Do you have this assumption you need every single thing in place 384 00:21:19,479 --> 00:21:20,989 in order for us to be successful? 385 00:21:20,989 --> 00:21:21,679 And that's not true. 386 00:21:22,499 --> 00:21:22,969 You can. 387 00:21:23,915 --> 00:21:28,855 Essentially build the train as you're running down the track and so that's 388 00:21:28,865 --> 00:21:34,585 really the value that I see in a pod or structure like revenue programs. 389 00:21:35,197 --> 00:21:37,467 Justin Norris: I think it's a pillar that a lot of teams are missing or 390 00:21:37,467 --> 00:21:41,147 haven't identified or other people do it ad hoc and it creates some tension 391 00:21:41,157 --> 00:21:46,317 because I've got to focus on, you know, all these businesses, usual things and 392 00:21:46,317 --> 00:21:47,777 keeping the trains running on time. 393 00:21:47,777 --> 00:21:49,847 And then when do I have time to focus on those other things? 394 00:21:49,847 --> 00:21:52,377 So I find it really interesting that you split that out. 395 00:21:52,422 --> 00:21:57,652 There are a lot of folks out there who have concerns about bringing the 396 00:21:57,652 --> 00:22:01,522 teams together, whether it's that, you know, a unified function won't be as 397 00:22:01,522 --> 00:22:06,162 responsive to the needs of the functions they serve as they would be if they 398 00:22:06,162 --> 00:22:10,462 were embedded within it, or that, you know, there can be power disparities. 399 00:22:10,462 --> 00:22:13,242 Like I know a lot of marketing ops functions, frankly, are afraid of just 400 00:22:13,252 --> 00:22:17,432 being like swallowed up by a bigger sales ops fish and being run by a sales ops 401 00:22:17,432 --> 00:22:18,862 leader that doesn't understand marketing. 402 00:22:19,262 --> 00:22:22,812 I spoke to a CS ops leader who said that there are similar concerns there. 403 00:22:22,812 --> 00:22:24,622 So have you seen those challenges? 404 00:22:24,622 --> 00:22:26,042 I guess would be the first question. 405 00:22:26,092 --> 00:22:27,692 And how did you address them if so? 406 00:22:28,289 --> 00:22:32,865 Julia Kim: Yes they exist, but I work really hard to 407 00:22:32,865 --> 00:22:35,943 try to reduce those impacts. 408 00:22:35,943 --> 00:22:40,867 And it's really at again, many different levels. 409 00:22:40,867 --> 00:22:42,714 Uh, Number 1. 410 00:22:43,164 --> 00:22:47,414 is that the, again, the org structure makes a lot of difference. 411 00:22:48,074 --> 00:22:53,324 And so having a similar structure between the different operational 412 00:22:53,324 --> 00:22:55,134 pods is very important. 413 00:22:55,144 --> 00:23:01,644 So for example the sales ops pod has a ops manager and an analyst, 414 00:23:02,044 --> 00:23:03,634 and there's an enablement person. 415 00:23:03,644 --> 00:23:07,474 CX ops has ops manager, analyst enablement. 416 00:23:07,924 --> 00:23:11,554 You know, they essentially have a dedicated tech ops person that they 417 00:23:11,554 --> 00:23:14,904 can go to someone who's stronger on the sales cloud side, someone who's 418 00:23:14,904 --> 00:23:16,444 stronger on the service cloud side. 419 00:23:16,714 --> 00:23:21,810 so there's a sort of a mirroring of the org structure that provides 420 00:23:21,810 --> 00:23:28,438 just a organizational harmony or equality in those teams. 421 00:23:28,833 --> 00:23:31,463 But of course, you have teams like marketing, which 422 00:23:31,483 --> 00:23:32,733 tends to be smaller, right? 423 00:23:32,773 --> 00:23:37,953 Marketing tends to be smaller than a sales team or a CX team or CS team. 424 00:23:38,463 --> 00:23:41,503 And so that's the case here at electric. 425 00:23:41,553 --> 00:23:43,653 The marketing pod is quite small. 426 00:23:43,663 --> 00:23:48,493 It's one individual right now we have a marketing ops manager, but they can 427 00:23:48,503 --> 00:23:53,284 leverage time and work and resources from. 428 00:23:53,824 --> 00:23:58,305 Either the sales ops or CX ops pods. 429 00:23:58,625 --> 00:24:03,885 So there's ability to leverage resources from different pods. 430 00:24:04,295 --> 00:24:10,513 And not only that, but again, thinking about to make that fear go away. 431 00:24:12,230 --> 00:24:17,308 there isn't a clear answer for this, but I think the biggest thing is just try it 432 00:24:17,308 --> 00:24:23,108 and see if it works because at electric, they actually had the ops teams embedded 433 00:24:23,108 --> 00:24:24,938 within the different go to market teams. 434 00:24:25,248 --> 00:24:26,928 It didn't work at all. 435 00:24:26,958 --> 00:24:28,308 It failed miserably. 436 00:24:28,718 --> 00:24:32,418 And so they were very open to a different type of structure. 437 00:24:33,068 --> 00:24:34,888 There is really nothing to lose. 438 00:24:35,188 --> 00:24:40,508 And the benefit there was that we actually were able to get a ton more productivity. 439 00:24:40,918 --> 00:24:46,238 And then you got things like collaboration between Marketing Ops and Sales Ops. 440 00:24:46,238 --> 00:24:49,648 I think traditionally, Marketing and Sales and Marketing Ops and 441 00:24:49,648 --> 00:24:53,008 Sales Ops, as you were saying, can be a little bit of a conflict. 442 00:24:53,288 --> 00:24:57,868 But because we're under one single umbrella, because we're doing the work 443 00:24:57,868 --> 00:25:03,868 to, work together, be humans, know that we are all trying to get to that 444 00:25:04,138 --> 00:25:08,398 end goal of generating revenue and retaining revenue for our company. 445 00:25:09,058 --> 00:25:10,828 We work really well together. 446 00:25:10,828 --> 00:25:16,342 And I think it does take the right type of organizational structure and leader, 447 00:25:16,622 --> 00:25:20,612 just because you bring everyone together, doesn't mean that it's going to work. 448 00:25:21,032 --> 00:25:26,212 And again, I've been very thoughtful in hiring for the team because We 449 00:25:26,212 --> 00:25:30,932 want to make sure that everyone is able to have those hard conversations. 450 00:25:30,932 --> 00:25:35,232 Sometimes there are problems and it's not that you're the problem or they're the 451 00:25:35,232 --> 00:25:38,362 problem or someone caused that problem. 452 00:25:38,502 --> 00:25:39,762 There is a problem. 453 00:25:40,132 --> 00:25:44,753 And so some wild investigation to figure out what happened. 454 00:25:45,438 --> 00:25:50,848 Really, our time is better spent on solving that problem and figuring out 455 00:25:50,858 --> 00:25:55,938 how do we move on from here and so having those individuals on the team that have 456 00:25:55,938 --> 00:26:02,108 that type of mentality is so important I specifically have been trying to make sure 457 00:26:02,108 --> 00:26:06,448 that our culture supports an environment where things are going to not work. 458 00:26:06,448 --> 00:26:07,548 Things are going to fail. 459 00:26:07,707 --> 00:26:13,057 People may get upset, but the most important thing is how do we identify 460 00:26:13,117 --> 00:26:15,407 a solution and how do we move forward? 461 00:26:15,717 --> 00:26:18,687 Because if we can, then we're all winning, right? 462 00:26:19,204 --> 00:26:22,044 . Justin Norris: I think that is 100 percent the most healthy attitude. 463 00:26:22,134 --> 00:26:24,074 And last quick org structure question. 464 00:26:24,074 --> 00:26:26,034 I'm just curious, who do you report into? 465 00:26:26,295 --> 00:26:26,625 Julia Kim: Yeah. 466 00:26:26,715 --> 00:26:28,735 I currently report into our CRO. 467 00:26:29,089 --> 00:26:32,529 when I first started, we had a senior VP of sales and I reported 468 00:26:32,529 --> 00:26:34,829 into that senior VP of sales. 469 00:26:34,829 --> 00:26:40,019 And at some point I had reported into finance, but I think this particular 470 00:26:40,019 --> 00:26:42,959 structure, and I was actually talking about this with someone over the weekend. 471 00:26:43,459 --> 00:26:48,829 Is most optimal because we've actually renamed our go to market teams from 472 00:26:48,829 --> 00:26:50,829 go to market teams to revenue teams. 473 00:26:51,199 --> 00:26:55,619 Partnerships actually wasn't originally underneath revenue it 474 00:26:55,619 --> 00:26:56,979 was actually underneath product. 475 00:26:57,009 --> 00:27:03,579 And so that shift and thinking about go to market and thinking about it 476 00:27:03,579 --> 00:27:06,599 from a revenue perspective, made us. 477 00:27:07,274 --> 00:27:11,224 Very quickly realized that, you know, what partnerships actually belongs 478 00:27:11,224 --> 00:27:13,514 under revenue, it is generating revenue. 479 00:27:13,944 --> 00:27:18,114 And so, more recently partnerships in the last few months has moved 480 00:27:18,134 --> 00:27:21,114 underneath the revenue teams and. 481 00:27:21,984 --> 00:27:27,654 Everything kind of revolves around this idea of, are we doing the best 482 00:27:27,654 --> 00:27:29,694 we can from a revenue perspective? 483 00:27:30,274 --> 00:27:35,004 And not to lose sight of the customer. 484 00:27:35,974 --> 00:27:37,554 How do you generate revenue? 485 00:27:38,249 --> 00:27:39,539 It's through your customer. 486 00:27:39,819 --> 00:27:42,779 So at the end of the day, if you actually drill down and drill down, 487 00:27:43,059 --> 00:27:44,839 it always ends up the customer. 488 00:27:45,179 --> 00:27:49,989 And so, having RevOps report into our CRO has been fantastic because we have 489 00:27:49,989 --> 00:27:56,269 been able to one really bring together all the revenue teams, have revenue as 490 00:27:56,269 --> 00:28:01,722 a clear line of sight, build our OKRs around that, but then also again, how do 491 00:28:01,722 --> 00:28:04,056 we generate revenue through our customers? 492 00:28:04,076 --> 00:28:06,266 And so not lose sight of our customers. 493 00:28:07,223 --> 00:28:10,513 Justin Norris: It's a good launching off point for the next thing I wanted to ask 494 00:28:10,513 --> 00:28:16,193 about, which is, how do you identify where you're going to have the most impact? 495 00:28:16,273 --> 00:28:20,209 And it seems like a simple question in a lot of ways, but a hundred percent, 496 00:28:20,219 --> 00:28:23,429 let's say revenue operations teams have way more on their plate than they 497 00:28:23,429 --> 00:28:25,899 could handle besieged by requests. 498 00:28:26,739 --> 00:28:31,389 And so it's a really important capability to have that discernment, to have 499 00:28:31,389 --> 00:28:33,059 good judgment about what you take on. 500 00:28:33,689 --> 00:28:36,639 So how do you think about that problem about like where your 501 00:28:36,639 --> 00:28:38,029 team can make the biggest impact? 502 00:28:39,263 --> 00:28:41,873 Julia Kim: it is a little easier because we use OKRs. 503 00:28:43,963 --> 00:28:50,623 And so what that means is that right now for 2024, our top three are one 504 00:28:50,703 --> 00:28:56,293 called fund the future second called efficient funnel and third is MVP 505 00:28:56,333 --> 00:28:58,073 is basically most valuable partner. 506 00:28:59,223 --> 00:29:01,863 So short of those things and. 507 00:29:02,658 --> 00:29:07,098 allocating some time for important things like dealing with tech debt 508 00:29:07,118 --> 00:29:14,438 or, just system critical things that essentially very much aligns our priority. 509 00:29:15,038 --> 00:29:21,388 Because there is a distribution in the work that we do for each of these OKRs. 510 00:29:22,068 --> 00:29:25,408 So the majority of it being on the efficient funnel side, 511 00:29:25,428 --> 00:29:34,463 obviously, but not neglecting The MVP OKR or fund the future OKR. 512 00:29:34,903 --> 00:29:38,483 So we are constantly looking at it from that lens. 513 00:29:39,053 --> 00:29:45,103 And not only that, but also having the right tools in place to be able to capture 514 00:29:45,103 --> 00:29:49,813 information that you can then leverage to make that case back to the business. 515 00:29:50,393 --> 00:29:54,243 And the reason why I say this is because when I first came to electric there 516 00:29:54,243 --> 00:29:56,363 wasn't really a ticket tracking system. 517 00:29:56,803 --> 00:30:00,893 There was a little bit of a sauna here and there, some Excel, but 518 00:30:00,893 --> 00:30:02,443 it really was a free for all. 519 00:30:02,443 --> 00:30:05,443 I think people were just like, Hey, this thing needs to be done. 520 00:30:05,443 --> 00:30:07,293 And people are like, okay, yes, I'll do it. 521 00:30:08,083 --> 00:30:10,123 And that's a terrible way to function. 522 00:30:10,513 --> 00:30:12,233 And so you're absolutely right. 523 00:30:12,233 --> 00:30:13,303 People get frustrated. 524 00:30:13,303 --> 00:30:14,433 Like, why did you do this? 525 00:30:14,433 --> 00:30:15,503 And why didn't you do this? 526 00:30:15,513 --> 00:30:16,493 Or I need this. 527 00:30:16,493 --> 00:30:17,123 And what do you mean? 528 00:30:17,123 --> 00:30:18,263 It's going to take you three weeks. 529 00:30:18,663 --> 00:30:21,073 The first priority was we it doesn't seem like you're doing anything right? 530 00:30:22,833 --> 00:30:27,603 Number one priority was one, put some sort of system in place where we can actually 531 00:30:27,623 --> 00:30:33,153 track what requests we're getting, have them documented and sort of use that 532 00:30:33,153 --> 00:30:35,093 as a framework for us to evolve from. 533 00:30:35,133 --> 00:30:36,993 And so that's how we ended up with JIRA. 534 00:30:37,203 --> 00:30:41,223 It wasn't perfect, but it was like, let's start with a sprint. 535 00:30:46,958 --> 00:30:50,408 I think sprint 45 right now, which is fantastic. 536 00:30:50,848 --> 00:30:57,288 And we have been able to measure as part of this process, how many tickets 537 00:30:57,598 --> 00:30:59,038 get submitted every single day. 538 00:30:59,278 --> 00:31:00,898 How many of them are high priority? 539 00:31:01,000 --> 00:31:05,281 many of them are low priority or middle, and see how long does 540 00:31:05,281 --> 00:31:09,381 it take for us to close tickets, which ones, generate other tickets 541 00:31:09,381 --> 00:31:11,181 because there's a little too broad. 542 00:31:11,181 --> 00:31:11,201 Yeah. 543 00:31:11,891 --> 00:31:15,971 But it's provided us with so much data and it's been able to provide 544 00:31:15,971 --> 00:31:20,011 us with information that says we need more resourcing on this side because 545 00:31:20,011 --> 00:31:24,201 there's a lot of things happening on this side or oh my gosh it looks like 546 00:31:24,231 --> 00:31:27,811 we have a serious enablement issue because all of the tickets that have 547 00:31:27,811 --> 00:31:31,481 been coming in for the last two weeks have all been questions that you know 548 00:31:31,531 --> 00:31:36,101 could be solved by enablement rather than a you know technical change or 549 00:31:36,361 --> 00:31:39,971 you know a process change it's just people just weren't sure what they were 550 00:31:39,971 --> 00:31:47,736 doing and so That, that system was such a valuable piece and having the OKRs 551 00:31:47,766 --> 00:31:50,006 align with the things that we're doing. 552 00:31:50,556 --> 00:31:53,789 We've since evolved because it has been, instrumental to 553 00:31:53,799 --> 00:31:55,189 being able to manage priorities. 554 00:31:55,189 --> 00:31:58,919 But we've since evolved since day one when I said, Hey we're 555 00:31:58,919 --> 00:32:00,009 going to start using JIRA. 556 00:32:00,309 --> 00:32:01,849 and there was honestly some pushback. 557 00:32:01,869 --> 00:32:02,229 There was. 558 00:32:02,804 --> 00:32:05,984 Concern about how do we maintain something like this? 559 00:32:05,984 --> 00:32:07,714 And it's like, okay, well, let's just try it. 560 00:32:08,244 --> 00:32:11,334 But we're now at the point where we actually have bi weekly 561 00:32:11,344 --> 00:32:15,364 sprint planning meetings where we can actually fill out things. 562 00:32:15,594 --> 00:32:19,064 We have regular meetings with different stakeholders saying, Hey, 563 00:32:19,074 --> 00:32:20,974 what do you want in our next sprint? 564 00:32:21,664 --> 00:32:24,114 Which gives people so much joy and excitement. 565 00:32:24,114 --> 00:32:28,579 Cause they're like Oh, That thing I asked for, can you do it in Sprint 46? 566 00:32:28,719 --> 00:32:30,249 You know, yes, absolutely. 567 00:32:30,249 --> 00:32:32,279 Or, you know, actually that's going to have to wait until 568 00:32:32,279 --> 00:32:35,899 47 because that's dependent on something that's being done in 46. 569 00:32:36,189 --> 00:32:39,449 So having that framework has been so important in being able 570 00:32:39,449 --> 00:32:40,949 to balance those priorities. 571 00:32:41,439 --> 00:32:47,919 And I think one of the challenges RevOps org and dealing with the 572 00:32:47,919 --> 00:32:51,929 sort of prioritization issues and how, to manage that process. 573 00:32:53,094 --> 00:32:57,374 Having a tool, even though there's overhead in having that tool is so 574 00:32:57,404 --> 00:33:03,444 valuable because it gives you actual data and actual, leverage to say, 575 00:33:03,754 --> 00:33:07,864 it's not reasonable for you to expect an email to go out after you just 576 00:33:07,864 --> 00:33:10,044 sent it to me 30 minutes ago, right? 577 00:33:10,044 --> 00:33:11,414 poor marketing ops manager. 578 00:33:11,414 --> 00:33:11,734 Right. 579 00:33:12,553 --> 00:33:17,213 Justin Norris: you've mentioned tickets and working with your stakeholders, and 580 00:33:17,213 --> 00:33:20,191 then we've also talked about strategy you know, a team that is sort of 581 00:33:20,191 --> 00:33:25,731 proactively identifying opportunities to evolve strategy and make impact. 582 00:33:26,351 --> 00:33:27,961 This is something that I think about a lot. 583 00:33:28,081 --> 00:33:29,851 How do you think about. 584 00:33:30,941 --> 00:33:35,101 balance or how to wait, taking requests and working with teams 585 00:33:35,101 --> 00:33:36,701 to fulfill those requests. 586 00:33:37,171 --> 00:33:41,211 In other words, giving GTM teams what they asked for versus proactively 587 00:33:41,741 --> 00:33:45,641 looking yourself at data or process and saying, I actually think 588 00:33:45,641 --> 00:33:48,076 we need to go in this direction there's these two different motions. 589 00:33:48,076 --> 00:33:49,036 They're both important. 590 00:33:49,556 --> 00:33:51,636 How do you split your effort between them? 591 00:33:52,168 --> 00:33:56,381 Julia Kim: I would say it's probably 60% managing requests at this point 592 00:33:56,381 --> 00:34:00,091 and 40 percent driving a lot of that. 593 00:34:00,631 --> 00:34:03,221 Like, Hey, did you notice this? 594 00:34:03,291 --> 00:34:04,181 What do you think about? 595 00:34:05,201 --> 00:34:08,591 and I think it's going to shift more in the coming year. 596 00:34:09,216 --> 00:34:11,246 it's because of where we are but. 597 00:34:12,376 --> 00:34:17,586 want to be clear that for that first 60%, we aren't just taking 598 00:34:17,586 --> 00:34:22,796 any ticket and saying, okay, sprint 44, sprint 45, you know, done check. 599 00:34:22,966 --> 00:34:25,986 No, we do really think about. 600 00:34:26,351 --> 00:34:30,711 One, how does it impact data that we have existing in the system? 601 00:34:31,031 --> 00:34:33,511 How does it impact other systems? 602 00:34:33,541 --> 00:34:38,711 Because our go to market or RevOps tech stack is highly integrated. 603 00:34:38,981 --> 00:34:42,051 We have a ton of integrations, not just to. 604 00:34:42,446 --> 00:34:47,486 Existing vendors, but to our product and our legacy product and many different 605 00:34:47,496 --> 00:34:51,606 services that we have to provide from a service delivery perspective. 606 00:34:51,626 --> 00:34:55,496 And so really important for us to ask those questions and be sort 607 00:34:55,496 --> 00:34:59,246 of the gatekeepers around that, but then also really think about. 608 00:34:59,770 --> 00:35:01,830 what is the true problem, right? 609 00:35:01,830 --> 00:35:03,740 Because we get a lot of requests where they're like, 610 00:35:04,100 --> 00:35:05,610 I'm trying to build a report. 611 00:35:06,595 --> 00:35:08,715 But I can't get Salesforce to give me this data. 612 00:35:08,715 --> 00:35:09,575 Can you add this field? 613 00:35:09,945 --> 00:35:13,155 I just need you to add this field so I could build my report so 614 00:35:13,155 --> 00:35:14,995 I could send it to X, Y, and Z. 615 00:35:14,995 --> 00:35:21,918 And one of the things that I have been really pushing this year with support 616 00:35:21,918 --> 00:35:27,298 from our data we have a dedicated engineering data team is really thinking 617 00:35:27,298 --> 00:35:31,318 about our CRM as a transactional system. 618 00:35:32,213 --> 00:35:35,923 And our snowflake data warehouse as a reporting system. 619 00:35:36,923 --> 00:35:40,373 And I think people tend to conflate the two because a lot of times, I mean, 620 00:35:40,393 --> 00:35:44,113 Salesforce does have some really great reports and dashboards, but we have 621 00:35:44,223 --> 00:35:48,443 become more mature as an organization where we want to integrate product data. 622 00:35:48,483 --> 00:35:53,173 We want to integrate other sources of data that don't originate Salesforce. 623 00:35:53,203 --> 00:35:56,623 And yes, we can absolutely put that stuff in Salesforce, but. 624 00:35:57,088 --> 00:35:58,978 What is the purpose behind that? 625 00:35:59,208 --> 00:36:01,148 how is that going to serve us better? 626 00:36:01,428 --> 00:36:05,578 And is that really the true purpose of Salesforce? 627 00:36:05,628 --> 00:36:10,748 As much as we call it our system of truth, and that is absolutely true, it 628 00:36:10,748 --> 00:36:15,048 can still be our system of truth if it's pushing data into our data warehouse 629 00:36:15,068 --> 00:36:16,438 and we're reporting there, right? 630 00:36:16,848 --> 00:36:22,223 And so, Tools like Looker, Tableau, any BI tool that you have, or 631 00:36:22,223 --> 00:36:24,057 even any, data management tools. 632 00:36:24,237 --> 00:36:27,497 They're going to do a much better job of slicing and dicing and visualizing 633 00:36:27,497 --> 00:36:29,277 the data that you want than Salesforce. 634 00:36:29,317 --> 00:36:31,847 As much as Salesforce tries, I mean, they really do try. 635 00:36:32,387 --> 00:36:37,356 But, the thing that I think we've come to that point in our 636 00:36:37,356 --> 00:36:42,446 maturity level is Salesforce needs to be a transactional database. 637 00:36:42,466 --> 00:36:44,666 Anything that has to do with transactions lives there. 638 00:36:44,846 --> 00:36:47,766 Anything that has to do with data lives in our data warehouse. 639 00:36:48,086 --> 00:36:53,666 And so we can do this ticket, but that's not actually what we need to do here. 640 00:36:53,686 --> 00:36:58,156 What really needs to happen is, are you able to generate that report in Loker 641 00:36:58,166 --> 00:37:00,636 or Tableau or whatever the system is? 642 00:37:00,936 --> 00:37:05,256 And if you're not, Can I help you communicate with our data team? 643 00:37:05,256 --> 00:37:07,216 So you can get that information that you need. 644 00:37:07,466 --> 00:37:11,226 So it's really kind of thinking about it from that perspective, because as much 645 00:37:11,226 --> 00:37:15,826 as it is like it is ticket resolution, it's also thinking about things as in 646 00:37:15,826 --> 00:37:17,236 terms of like, what is the true problem? 647 00:37:17,236 --> 00:37:18,206 What are we trying to solve? 648 00:37:18,588 --> 00:37:19,948 Justin Norris: you've touched on data. 649 00:37:20,118 --> 00:37:23,428 What's the relationship between your data team and your team? 650 00:37:23,458 --> 00:37:26,158 Because obviously there's a lot of codependency there. 651 00:37:27,216 --> 00:37:27,546 Julia Kim: Yeah. 652 00:37:27,576 --> 00:37:32,866 So Salesforce related, Marketo related. 653 00:37:33,406 --> 00:37:36,466 And then the data team is fully responsible for our 654 00:37:36,466 --> 00:37:38,066 Snowflake data warehouse. 655 00:37:38,869 --> 00:37:42,767 Justin Norris: One of the challenges I've found with reporting, out of a 656 00:37:42,767 --> 00:37:45,887 data warehouse or using that entirely as the system of reporting, and I 657 00:37:45,897 --> 00:37:50,117 think a reason why a lot of people just relapse into Salesforce is Even though 658 00:37:50,117 --> 00:37:53,797 it's more powerful and ultimately more flexible, there can also be a rigidity. 659 00:37:53,847 --> 00:37:55,917 It's like, Oh, actually this table doesn't have this. 660 00:37:55,917 --> 00:37:57,887 I'm going to have to do a request and there's friction. 661 00:37:57,887 --> 00:38:01,057 So I'm just going to create a quick Salesforce report because it's not right, 662 00:38:01,092 --> 00:38:03,083 but it's, the path of least resistance. 663 00:38:03,492 --> 00:38:06,312 how have you thought about that in terms of your relationship with that team and 664 00:38:06,312 --> 00:38:09,792 making sure that the reporting environment is going to serve those needs so that 665 00:38:09,792 --> 00:38:12,072 you can push people towards that place? 666 00:38:12,343 --> 00:38:14,503 Julia Kim: Yeah, so, that's a really great question. 667 00:38:14,513 --> 00:38:17,823 We actually have a data council specifically for that purpose. 668 00:38:18,283 --> 00:38:22,423 And the data council is comprised of people from the data team, obviously 669 00:38:22,463 --> 00:38:26,943 people from RevOps, there's someone from finance, there's someone from product. 670 00:38:27,163 --> 00:38:30,803 There's a lot of different people who are part of that council 671 00:38:31,093 --> 00:38:32,703 specifically to talk about. 672 00:38:33,073 --> 00:38:35,913 Those questions and almost get ahead of those things. 673 00:38:35,913 --> 00:38:39,263 Because a lot of times you have a project that's coming up and it's 674 00:38:39,263 --> 00:38:42,493 like, there's probably going to be a data component to this project. 675 00:38:42,743 --> 00:38:47,693 So let's make sure that you're aware of it and that we're really thinking about it. 676 00:38:47,723 --> 00:38:51,473 The other piece too, is that as we've become more rigorous or a little bit 677 00:38:51,533 --> 00:38:56,373 more structured from a rev ops internal process perspective, we have been. 678 00:38:57,278 --> 00:39:02,098 Doing more around incorporating UAT or user acceptance testing in our process. 679 00:39:02,368 --> 00:39:07,182 And really, it's been an evolution of incorporating the Agile methodology and 680 00:39:07,192 --> 00:39:12,102 having sprints and do sprint planning, using JIRA to help manage that. 681 00:39:12,472 --> 00:39:16,642 for what we consider medium projects, that might be quick user acceptance 682 00:39:16,662 --> 00:39:21,782 testing and, you know, pulling in the data team to help with that user acceptance 683 00:39:21,792 --> 00:39:27,212 testing by the ops managers before it gets rolled out, or maybe the enablement 684 00:39:27,212 --> 00:39:31,562 manager, and then it gets rolled out for larger projects that are maybe 685 00:39:31,572 --> 00:39:37,052 three months in duration or longer, We actually have dedicated testers, either 686 00:39:37,062 --> 00:39:41,502 end users from the business or different people that are a part of that process. 687 00:39:42,452 --> 00:39:46,092 And we build enablement as part of that testing process too. 688 00:39:46,822 --> 00:39:48,737 And the data team is involved there. 689 00:39:48,737 --> 00:39:53,207 So we're trying to build multiple touch points so that any data 690 00:39:53,207 --> 00:39:58,087 discrepancies or issues and integrating data are caught early. 691 00:39:58,467 --> 00:40:01,477 Because we are trying to integrate more of that. 692 00:40:01,832 --> 00:40:07,682 Testing and collaboration and knowledge and understanding of what is coming out 693 00:40:07,712 --> 00:40:10,602 of this project earlier in the process. 694 00:40:11,110 --> 00:40:11,230 Justin Norris: I 695 00:40:11,230 --> 00:40:12,410 think that's really important. 696 00:40:12,440 --> 00:40:14,850 And you touched on user acceptance testing. 697 00:40:14,850 --> 00:40:19,600 You've also mentioned enablement and all that to me speaks to, you know, 698 00:40:19,600 --> 00:40:21,053 the importance of change management. 699 00:40:21,573 --> 00:40:25,903 it's something that RevOps teams in general, maybe don't give as much 700 00:40:25,923 --> 00:40:28,403 emphasis as they should in all cases. 701 00:40:28,955 --> 00:40:31,255 And honestly, I think it's one of things like they can can make or 702 00:40:31,255 --> 00:40:35,255 break, particularly with functions like sales ops or CS ops, where 703 00:40:35,255 --> 00:40:37,185 you have to change the behavior. 704 00:40:37,500 --> 00:40:40,520 Sometimes have a large number of users, you know, for your project 705 00:40:40,540 --> 00:40:43,830 to be successful users who may not necessarily be very interested. 706 00:40:43,870 --> 00:40:45,180 Like they want to hit their quota. 707 00:40:45,190 --> 00:40:47,840 They're not necessarily care about the success or failure 708 00:40:47,850 --> 00:40:50,619 of your project, intrinsically, unless you can make them care. 709 00:40:51,219 --> 00:40:54,335 And so I guess the question is, how do you make them care? 710 00:40:54,335 --> 00:40:56,515 You know, when you have a project that you're rolling out to those 711 00:40:56,515 --> 00:40:59,615 teams, how do you get their buy in so that you can succeed? 712 00:41:00,527 --> 00:41:06,717 I am really fortunate that at electric the messaging is consistent 713 00:41:06,727 --> 00:41:09,197 from the very top levels down. 714 00:41:09,977 --> 00:41:14,897 And so when we have all hands meetings every month, it's pretty 715 00:41:14,897 --> 00:41:16,497 clear, like what we care about. 716 00:41:17,287 --> 00:41:19,257 You know, Hey, we have a new partnership. 717 00:41:19,257 --> 00:41:23,247 This is a focus for us, or Hey, this is a channel that's important for us. 718 00:41:23,257 --> 00:41:25,817 This is a process that we're excited about. 719 00:41:26,417 --> 00:41:31,529 And so it's that messaging makes it easier to then break that down to 720 00:41:31,679 --> 00:41:36,129 what is that specific thing as you were talking about that and cares 721 00:41:36,129 --> 00:41:37,749 about that might motivate them. 722 00:41:38,219 --> 00:41:40,159 And it could be a financial component, right? 723 00:41:40,159 --> 00:41:42,609 It could be a specific could be maybe the way that their comp 724 00:41:42,619 --> 00:41:44,159 plan is structured or whatever. 725 00:41:44,659 --> 00:41:49,209 Or, you know, for the CSM, maybe it's, you know, Ooh, I don't want my 726 00:41:49,209 --> 00:41:56,034 customer to submit a negative NPS, survey or whatnot, but it really is 727 00:41:56,034 --> 00:42:01,434 leveraging the clarity that starts in the transparency that starts at the top. 728 00:42:01,464 --> 00:42:06,484 And then just then customizing it, and just really understanding who 729 00:42:06,494 --> 00:42:09,594 your true end users are internally. 730 00:42:10,394 --> 00:42:13,484 But I think it's also a strength of enablement. 731 00:42:14,034 --> 00:42:18,414 I think people think of enablement as just training. 732 00:42:19,054 --> 00:42:24,374 And I think that's where, again, I have made a conscious effort to differentiate 733 00:42:24,384 --> 00:42:26,064 what I think of as enablement. 734 00:42:26,964 --> 00:42:32,199 And it actually answers one of the earlier questions you had around You know how do 735 00:42:32,199 --> 00:42:34,809 you, how proactive are you about things? 736 00:42:35,199 --> 00:42:37,599 And that's a great area for enablement. 737 00:42:37,639 --> 00:42:40,529 When they're past the sort of traditional things you think about 738 00:42:40,529 --> 00:42:44,399 from an enablement perspective, like training or putting materials 739 00:42:44,399 --> 00:42:46,599 together, that's great and everything. 740 00:42:46,619 --> 00:42:51,059 And I'm having my enablement manager leverage or analysts more 741 00:42:51,059 --> 00:42:53,049 to kind of get some of that done. 742 00:42:53,929 --> 00:42:59,429 The real value of enablement is saying, what, where are the gaps in productivity? 743 00:42:59,999 --> 00:43:01,729 Because it's not just about learning. 744 00:43:01,749 --> 00:43:06,009 It's also about productivity from their perspective from their roles perspective. 745 00:43:06,029 --> 00:43:10,739 And so one of the things that my enablement manager and I are actively 746 00:43:10,739 --> 00:43:16,549 working on is leveraging her expertise and how people learn, how people 747 00:43:16,549 --> 00:43:21,249 ingest information, how people, the different ways that people have to 748 00:43:21,249 --> 00:43:24,699 like see or feel or engage with things. 749 00:43:25,529 --> 00:43:27,919 And knowledge within the tool. 750 00:43:27,919 --> 00:43:31,739 So for example we were just looking at Gong and saying, Hey, you know, maybe 751 00:43:31,739 --> 00:43:35,959 there's a better way we can expose some of these dashboard widgets and stuff 752 00:43:35,969 --> 00:43:39,249 for people that are in there, or is there a way we can actually kind of 753 00:43:39,249 --> 00:43:42,999 pull out some of this information and have it in Salesforce in a better way? 754 00:43:42,999 --> 00:43:45,199 We, we actually have an integration, but in a better way. 755 00:43:45,889 --> 00:43:46,569 And so. 756 00:43:47,209 --> 00:43:51,219 Enablement then becomes not just about training, not just about teaching 757 00:43:51,219 --> 00:43:52,899 them about like a sales process. 758 00:43:53,179 --> 00:43:56,899 It's almost like, yes, okay, that is the basics of what you need to do. 759 00:43:56,909 --> 00:44:01,669 But the real value in enablement is for an AE that now understands 760 00:44:01,669 --> 00:44:02,829 what the sales process is. 761 00:44:03,039 --> 00:44:04,889 How much time are they spending on emails? 762 00:44:04,899 --> 00:44:06,719 How much time are they spending on calls? 763 00:44:06,979 --> 00:44:08,849 And is that distribution look okay? 764 00:44:09,209 --> 00:44:12,479 So if there's someone who's being much more successful in close winning, 765 00:44:12,479 --> 00:44:18,879 how opportunities and they happen to have maybe a 40 60 ratio of like, you 766 00:44:18,879 --> 00:44:20,829 know, emails to calls being greater. 767 00:44:21,929 --> 00:44:24,759 Maybe that's a tactic that other people on the team can do. 768 00:44:24,779 --> 00:44:28,199 And how great is it that enablement can say, Hey, I've been looking at the 769 00:44:28,199 --> 00:44:32,319 data, you know, sales director or sales manager, and we've noticed that these 770 00:44:32,349 --> 00:44:35,069 2 people or these 3 people are not. 771 00:44:35,469 --> 00:44:39,539 quite performing as well, but they're also not doing these other things as well. 772 00:44:39,609 --> 00:44:43,439 I know, I think there are some AEs, especially some high performing 773 00:44:43,719 --> 00:44:46,639 AEs that have their own kind of method, and it works for them. 774 00:44:46,949 --> 00:44:50,459 But I think for the most part, many people maybe just aren't doing 775 00:44:50,459 --> 00:44:51,759 the things that they need to do. 776 00:44:52,079 --> 00:44:54,329 And it's not just this one time, hey, let's train them 777 00:44:54,329 --> 00:44:55,219 and get them knowledgeable. 778 00:44:55,219 --> 00:44:56,969 It's a lifelong learning process. 779 00:44:57,349 --> 00:45:03,679 And so I think that's where an enablement can be because they can almost, you 780 00:45:03,679 --> 00:45:08,134 know, Be a productivity coach, and that can be applied across the board. 781 00:45:08,564 --> 00:45:09,694 It's not just eight years. 782 00:45:09,714 --> 00:45:10,474 It's not just S. 783 00:45:10,474 --> 00:45:10,634 D. 784 00:45:10,634 --> 00:45:10,834 R. 785 00:45:10,904 --> 00:45:10,924 S. 786 00:45:10,924 --> 00:45:12,074 It's not just C. 787 00:45:12,084 --> 00:45:12,184 S. 788 00:45:12,184 --> 00:45:12,464 M. 789 00:45:12,474 --> 00:45:12,554 S. 790 00:45:12,554 --> 00:45:12,874 Or A. 791 00:45:12,874 --> 00:45:13,044 M. 792 00:45:13,054 --> 00:45:13,124 S. 793 00:45:13,444 --> 00:45:16,504 You could almost think about this from a project perspective. 794 00:45:16,504 --> 00:45:21,717 Like, are we doing projects in a way that are conducive to collaboration, right? 795 00:45:22,187 --> 00:45:24,397 and so that's what we're trying to do with enablement and take 796 00:45:24,397 --> 00:45:25,927 it to the next level beyond just 797 00:45:26,087 --> 00:45:26,457 training. 798 00:45:26,979 --> 00:45:33,592 I love that example, as A case of how ops can really drive impact, beyond 799 00:45:33,922 --> 00:45:38,745 just, yes, we have a request, we have to partner on those things, but also kind of 800 00:45:38,745 --> 00:45:41,955 challenging the business, being somebody who's there, like having a second set of 801 00:45:41,955 --> 00:45:44,075 eyes, are we doing this in the best way? 802 00:45:44,085 --> 00:45:45,505 Is this what great looks like? 803 00:45:46,015 --> 00:45:47,505 How can we move this forward? 804 00:45:47,955 --> 00:45:50,035 That's such an important part that often gets missed. 805 00:45:50,035 --> 00:45:53,485 I think his teams often don't have time to do it and in full fairness, 806 00:45:53,895 --> 00:45:56,225 but having those folks that have that as part of their scope. 807 00:45:56,290 --> 00:45:58,110 I think it's just so important 808 00:45:58,738 --> 00:45:59,498 Julia Kim: Absolutely. 809 00:45:59,508 --> 00:46:05,368 And I think one of the best examples I can think of how enablement helped 810 00:46:05,578 --> 00:46:12,138 me really again, consolidate our tech stack and therefore save money is I 811 00:46:12,138 --> 00:46:18,018 asked our enablement manager to do an analysis and look at our sales stages in 812 00:46:18,018 --> 00:46:23,458 the pipeline and see what was the level of usage across all of those stages. 813 00:46:24,073 --> 00:46:25,853 And of course, some of it makes sense, right? 814 00:46:25,853 --> 00:46:29,223 Like in the beginning, you know, they're having a lot of calls with people. 815 00:46:29,223 --> 00:46:30,993 So gong is like high usage, right? 816 00:46:31,213 --> 00:46:34,893 And then you can kind of see Salesforce is maybe consistently used maybe a little 817 00:46:34,893 --> 00:46:40,669 bit more when you're negotiating but that sort of heat map of how different 818 00:46:40,679 --> 00:46:45,619 tools were being utilized, the level of usage, the duration of usage. 819 00:46:45,954 --> 00:46:50,894 And the sales stages made it so obvious which tools provided the most value 820 00:46:50,894 --> 00:46:56,150 consistently across all the sales stages and then also which ones had sort of like 821 00:46:56,150 --> 00:47:02,920 the most impact when and that's a great example of how if you don't think of 822 00:47:02,940 --> 00:47:05,710 enablement as just that training function. 823 00:47:06,285 --> 00:47:10,745 That is a huge piece of value because you want to make sure that if AEs 824 00:47:10,765 --> 00:47:14,315 are spending a ton of time in Gong in the beginning, that they really are 825 00:47:14,355 --> 00:47:19,205 leveraging the tools within Gong that are going to help them really move 826 00:47:19,205 --> 00:47:21,055 those stages to that next stage, right? 827 00:47:21,295 --> 00:47:29,245 And so it's really another efficiency approach in aligning your tech 828 00:47:29,245 --> 00:47:33,385 stack, the data you have, the people you have, the process you have. 829 00:47:34,295 --> 00:47:36,285 Using a team like RevOps. 830 00:47:36,891 --> 00:47:41,551 Justin Norris: when we think about technology and go to market, obviously 831 00:47:41,551 --> 00:47:44,472 the thing that looms over over us all, uh, right now and for the past 832 00:47:44,472 --> 00:47:47,422 year or so has been AI and all the changes that have happened there. 833 00:47:47,792 --> 00:47:51,162 No, this is something that you have thought a lot about and 834 00:47:51,172 --> 00:47:52,282 have been doing some work there. 835 00:47:52,697 --> 00:47:56,878 What are the main use cases that you see, where you think there's an opportunity 836 00:47:56,878 --> 00:47:59,698 to drive real value with AI and rev ops? 837 00:48:00,480 --> 00:48:05,700 Julia Kim: may be alone in this, but I feel so strongly that AI is 838 00:48:05,700 --> 00:48:10,790 one of those things that a RevOps team can absolutely leverage and 839 00:48:10,790 --> 00:48:12,360 it doesn't have to be homegrown. 840 00:48:12,895 --> 00:48:16,345 I was just at a, the Stripe conference last week in San Francisco 841 00:48:16,675 --> 00:48:21,895 and Jensen Wong, who is the CEO of Nvidia, was a speaker on one 842 00:48:21,895 --> 00:48:23,215 of the days of the conference. 843 00:48:23,220 --> 00:48:28,345 And he had this really great quote where he talks about, first you as an 844 00:48:28,345 --> 00:48:32,506 individual, so, people are always afraid that they're gonna lose their job to ai. 845 00:48:32,716 --> 00:48:35,416 And he said, you're not gonna lose your job to ai, you're gonna lose 846 00:48:35,421 --> 00:48:38,146 your job to someone who is using ai. 847 00:48:38,696 --> 00:48:42,326 so don't worry about the AI, worry about the person who's leveraging AI. 848 00:48:42,796 --> 00:48:48,326 But I think the most impactful statement he said was the second one, which is that 849 00:48:48,336 --> 00:48:50,346 your company isn't competing with AI. 850 00:48:50,356 --> 00:48:55,626 It's not like your company versus AI, open AI or any of these other, you know, 851 00:48:55,626 --> 00:48:58,496 like Microsoft or Google or whatnot, meta. 852 00:48:59,006 --> 00:49:05,236 It's competing with another company that is using AI strategically, right? 853 00:49:05,336 --> 00:49:07,526 Because you can do all the operational. 854 00:49:08,076 --> 00:49:12,886 excellence, tactics, all of that, even strategy, but if you don't have 855 00:49:12,886 --> 00:49:19,226 that special sauce of AI you're not going to win against all the others. 856 00:49:19,636 --> 00:49:23,146 And so I thought that was so interesting And I think this is where, 857 00:49:23,196 --> 00:49:27,116 because there's such a technical component to revenue operations. 858 00:49:27,456 --> 00:49:32,366 And because there are so many great tools that are spending millions of dollars 859 00:49:32,396 --> 00:49:37,486 within the RevOps tech stack, that you can leverage all of those benefits. 860 00:49:37,726 --> 00:49:40,576 Oftentimes these things are already included in your contract. 861 00:49:40,576 --> 00:49:44,046 You just don't know about them, or maybe you're not sure. 862 00:49:44,046 --> 00:49:47,656 And, you know, you can kind of talk to your rep and say, Hey, I don't want to 863 00:49:47,666 --> 00:49:52,396 pay an extra, you know, God knows what for this AI feature, but I would love to 864 00:49:52,396 --> 00:49:55,816 pilot it out to see what the ROI might be. 865 00:49:56,716 --> 00:50:01,736 But such a great opportunity to leverage all the things that are happening. 866 00:50:02,606 --> 00:50:06,106 And really understand what are your true needs around AI. 867 00:50:06,406 --> 00:50:09,206 And then if it is something that you need to customize, you 868 00:50:09,206 --> 00:50:10,766 can work with your data team. 869 00:50:10,886 --> 00:50:15,996 You can work with your engineering team to build out those very custom models or 870 00:50:16,006 --> 00:50:21,396 custom machine learning algorithms that might be specific to your industry, but. 871 00:50:22,111 --> 00:50:26,161 today, literally today, you could say, Hey, I have gong. 872 00:50:26,191 --> 00:50:30,491 How can I leverage those AI features and get started and be competitive? 873 00:50:30,801 --> 00:50:35,971 But the areas that, you know, I really think that AI is going to benefit. 874 00:50:35,971 --> 00:50:38,641 Rev ops is one around predictive ai. 875 00:50:38,911 --> 00:50:42,561 You know, a lot of rev ops teams, I am, you know, one of them 876 00:50:42,621 --> 00:50:44,331 have to think about forecasting. 877 00:50:44,331 --> 00:50:45,711 What are sales gonna look like? 878 00:50:46,436 --> 00:50:51,136 What is spend going to look like, you know, is this customer going to churn? 879 00:50:51,516 --> 00:50:55,986 And there are some really great built in features across again, all of those 880 00:50:56,176 --> 00:51:00,396 tools in our RevOps tech stack that can help you leverage those use cases. 881 00:51:00,706 --> 00:51:06,386 But I think again, predictive AI is such an important area where we can utilize 882 00:51:06,386 --> 00:51:10,306 it today and make some contribution to the bottom line for our companies. 883 00:51:10,896 --> 00:51:14,126 The other area that's so important is generative AI. 884 00:51:14,156 --> 00:51:18,586 And I always think of generative AI, not just about content creation, but 885 00:51:18,586 --> 00:51:20,616 really around productivity, right? 886 00:51:20,846 --> 00:51:25,596 So it's, you know, if you have outreach, use those gen AI tools in order to, 887 00:51:25,796 --> 00:51:30,946 you know, generate those email follow ups you know, use those call summaries 888 00:51:31,026 --> 00:51:34,576 and other action item features that are built into, again, the tools 889 00:51:34,586 --> 00:51:35,736 that you have in your tech stack. 890 00:51:36,236 --> 00:51:39,726 For the most part, those are things that, you know, it's just time consuming 891 00:51:39,726 --> 00:51:45,022 for an AE or a CSM they just had a call to do, and great, you know, now they 892 00:51:45,022 --> 00:51:46,672 don't have to worry about it anymore. 893 00:51:47,162 --> 00:51:50,152 And then one of the other areas that I just think is so 894 00:51:50,152 --> 00:51:51,822 great is conversational AI. 895 00:51:52,042 --> 00:51:58,068 So you think about how a lot of times AEs spend time trying to 896 00:51:58,068 --> 00:52:01,318 explain what the product is doing, what services you're providing. 897 00:52:01,578 --> 00:52:06,298 But if you have an inbound prospect that's interested and they can have a 898 00:52:06,308 --> 00:52:10,188 very short and meaningful conversation that seems very human like, almost 899 00:52:10,188 --> 00:52:14,468 like there's a person behind it and learn and kind of get assets and then 900 00:52:14,538 --> 00:52:16,068 talk to an AE when they're ready. 901 00:52:16,363 --> 00:52:18,023 That saves time and energy, right? 902 00:52:18,023 --> 00:52:21,073 And it increases the likelihood that they're going to ask 903 00:52:21,073 --> 00:52:21,913 you the right question. 904 00:52:21,913 --> 00:52:25,013 So you can identify the pain points that they truly have 905 00:52:25,013 --> 00:52:26,563 that your product can solve for. 906 00:52:26,897 --> 00:52:29,427 And I would say the 3rd area that's important is what 907 00:52:29,437 --> 00:52:30,867 they call descriptive AI. 908 00:52:31,562 --> 00:52:35,022 It's really about, you know, taking unstructured data and 909 00:52:35,022 --> 00:52:38,682 finding visibility or insights through that unstructured data. 910 00:52:38,682 --> 00:52:41,432 So, Gong is a classic example of that, right? 911 00:52:41,432 --> 00:52:44,672 You can't go through every single call recording you have, but it does a 912 00:52:44,672 --> 00:52:48,762 really great job of sentiment analysis and just kind of flagging different 913 00:52:48,772 --> 00:52:51,442 things within a call at scale, right? 914 00:52:51,732 --> 00:52:56,422 And so when you're thinking about, how do I know if our AEs 915 00:52:56,442 --> 00:52:58,032 are mentioning our new product? 916 00:52:58,777 --> 00:53:01,657 Well, set up a trigger in Gong and see if, you know, if 917 00:53:01,657 --> 00:53:02,697 it's actually being discussed. 918 00:53:03,387 --> 00:53:08,757 Those are very low lift ways that you can incorporate AI into your day to day 919 00:53:08,757 --> 00:53:14,087 RevOps processes and tech stack so that you can actually raise your hand when exec 920 00:53:14,087 --> 00:53:15,717 is like, what are you doing for me today? 921 00:53:16,057 --> 00:53:17,767 You're like, we've got AI covered. 922 00:53:17,987 --> 00:53:20,687 That is such an easy thing to start with now. 923 00:53:20,857 --> 00:53:24,405 going back to what Jensen Wang said, at the conference last week. 924 00:53:24,491 --> 00:53:25,565 A. 925 00:53:25,565 --> 00:53:26,645 There is a lot of hype. 926 00:53:26,655 --> 00:53:28,035 There is a hype cycle around A. 927 00:53:28,035 --> 00:53:28,265 I. 928 00:53:28,325 --> 00:53:29,835 But it's not going away. 929 00:53:29,855 --> 00:53:35,095 It is a fundamental technology, a fundamental way of doing business that is 930 00:53:35,095 --> 00:53:37,265 going to change many different industries. 931 00:53:37,655 --> 00:53:38,205 And. 932 00:53:38,830 --> 00:53:42,920 How great, you know, from a rev ops perspective, would it be if you could 933 00:53:42,920 --> 00:53:47,650 kind of lead and control how that's used rather than being sort of told? 934 00:53:47,690 --> 00:53:49,990 Oh, my gosh, why are we not doing AI? 935 00:53:50,160 --> 00:53:54,380 And almost being sort of forced into being in that reactive mode. 936 00:53:54,760 --> 00:53:58,524 Whereas you can be very proactive and a lot of, the reps for these 937 00:53:58,524 --> 00:54:02,114 vendors are going to be so happy to talk to you and say, Hey, 938 00:54:02,124 --> 00:54:03,574 here's some, you know, suggestions. 939 00:54:03,644 --> 00:54:07,984 In fact, if you haven't had a QBR recently, or maybe, you know, an 940 00:54:07,984 --> 00:54:10,624 executive review recently, schedule one. 941 00:54:10,764 --> 00:54:14,294 I'm always interested in learning about what's happening in the roadmap. 942 00:54:14,944 --> 00:54:19,050 Maybe you're, hearing about other tools that are being used in the industry. 943 00:54:19,410 --> 00:54:20,960 But this is something where. 944 00:54:21,645 --> 00:54:25,665 Such a powerful lever, especially if RevOps can kind of say, Hey, 945 00:54:25,715 --> 00:54:29,525 I have ownership of this and I can fundamentally change how our 946 00:54:29,535 --> 00:54:33,165 business works using this tool. 947 00:54:33,425 --> 00:54:34,045 so amazing. 948 00:54:34,045 --> 00:54:36,165 So I'm, very much excited about AI. 949 00:54:36,565 --> 00:54:37,735 If you cannot tell, 950 00:54:38,078 --> 00:54:42,238 Justin Norris: Yeah, I mean, I think there is huge opportunity, and I think there is 951 00:54:42,238 --> 00:54:44,288 a lot of learning, that needs to be done. 952 00:54:44,608 --> 00:54:47,638 That's one of the things that has impressed itself upon me. 953 00:54:47,648 --> 00:54:51,278 It's one thing to have AI, but it's another thing to know how to prompt it 954 00:54:51,278 --> 00:54:56,388 very well, to understand how to leverage the outputs, how to debug things if 955 00:54:56,388 --> 00:54:59,238 you're not getting the results that you want, which, none of which I claim 956 00:54:59,238 --> 00:55:03,141 to be expert in, but just speaking to people like yourself, It is a new skill. 957 00:55:03,161 --> 00:55:06,791 So to your point about, you know, losing your job to the person who knows how 958 00:55:06,791 --> 00:55:10,631 to use AI, there's a real thing there and it is something to keep in mind. 959 00:55:10,981 --> 00:55:14,261 Maybe we'll just to end on, uh, you know, a slightly introspective note. 960 00:55:14,261 --> 00:55:15,551 You have a very mature team. 961 00:55:16,078 --> 00:55:17,528 It seems very high performing. 962 00:55:17,578 --> 00:55:19,328 You've told us about all the great things you do. 963 00:55:19,743 --> 00:55:22,713 It's interesting also to note the, like we all have challenges. 964 00:55:23,620 --> 00:55:27,010 No matter where we are in our career, what are some of the things that you are 965 00:55:27,010 --> 00:55:30,830 finding difficult today or that you just don't have totally figured out just yet? 966 00:55:31,683 --> 00:55:36,163 Julia Kim: working in a startup environment, things shift so 967 00:55:36,163 --> 00:55:40,338 quickly and I guess a really big thing. 968 00:55:40,338 --> 00:55:42,028 And then a sort of small, big thing. 969 00:55:42,338 --> 00:55:50,618 The biggest thing is how can you consistently support the changes that 970 00:55:50,618 --> 00:55:57,078 happen day to day, week over week, month over month as a startup and keep 971 00:55:57,078 --> 00:56:02,198 your team feeling motivated and driven? 972 00:56:02,288 --> 00:56:04,178 Because sometimes. 973 00:56:04,993 --> 00:56:08,153 It seems like there's a change in priority, but there isn't. 974 00:56:08,193 --> 00:56:12,653 It's just maybe the slight focus, but at the end of the day, the things 975 00:56:12,653 --> 00:56:16,403 that you need to accomplish are the same, but people get distracted by 976 00:56:16,403 --> 00:56:22,153 maybe the messaging or what's being said, but it's balancing sort of 977 00:56:22,153 --> 00:56:27,923 the chaos of being in a startup, the instability of doing new things, right? 978 00:56:27,923 --> 00:56:31,133 If you're a startup, that's trying to make a difference in the world. 979 00:56:31,748 --> 00:56:34,808 You're doing something that other people have not been doing, And how 980 00:56:34,808 --> 00:56:39,188 do you balance that with stability for a team that needs some stability, 981 00:56:39,198 --> 00:56:44,068 some structure, some consistency in order to work effectively, right? 982 00:56:44,068 --> 00:56:46,878 Because when you think about operations, or you think about 983 00:56:46,878 --> 00:56:51,338 things like forecasting or reporting, you can't report if everything's 984 00:56:51,338 --> 00:56:52,838 constantly changing every second. 985 00:56:52,848 --> 00:56:52,888 Right. 986 00:56:53,358 --> 00:56:55,955 And so by the nature of operations, by the nature of 987 00:56:55,955 --> 00:56:58,515 process, you need some stability. 988 00:56:58,525 --> 00:57:02,915 And so that is the biggest and hardest thing to manage or balance 989 00:57:03,015 --> 00:57:04,815 when you're in a startup environment. 990 00:57:05,625 --> 00:57:11,395 And I think the second piece for me is, how do you keep people inspired? 991 00:57:11,475 --> 00:57:15,334 Because a lot of times, Your day to day is not that sexy, right? 992 00:57:16,964 --> 00:57:18,264 You know, it's troubleshooting. 993 00:57:18,394 --> 00:57:20,284 Why is Marketo not syncing with 994 00:57:20,284 --> 00:57:20,934 Salesforce 995 00:57:20,964 --> 00:57:23,134 and I think as humans, as people. 996 00:57:23,514 --> 00:57:26,504 As much as we, you know, we're like, yeah, we can do this day in, 997 00:57:26,544 --> 00:57:30,264 day out we're curious, we want to learn, we want to grow, we want 998 00:57:30,284 --> 00:57:32,424 to have pride in what we're doing. 999 00:57:32,434 --> 00:57:38,974 And so, the second hardest thing for me is how do you create that environment 1000 00:57:38,984 --> 00:57:40,774 where people feel like they're growing? 1001 00:57:41,269 --> 00:57:46,259 Even when they're running a, you know, at 110%, because all of that 110 1002 00:57:46,259 --> 00:57:47,639 percent is for the business, right? 1003 00:57:47,639 --> 00:57:50,599 Because they're doing all these things to optimize revenue. 1004 00:57:50,669 --> 00:57:54,609 And we may or may not see that some people get comped, you know, maybe because 1005 00:57:54,609 --> 00:57:57,849 they have a bonus structure that, you know, benefits them when the company's 1006 00:57:57,899 --> 00:57:59,339 doing well, some people aren't right. 1007 00:57:59,779 --> 00:58:02,029 And so how do you make people feel like they're growing? 1008 00:58:02,029 --> 00:58:05,959 How do you make them feel like, wait, here's a way that I can. 1009 00:58:06,329 --> 00:58:07,589 Make my team better. 1010 00:58:07,659 --> 00:58:12,309 I mean, I had a really great one on one with one of my analysts earlier today 1011 00:58:12,309 --> 00:58:16,359 where she said, I know that we talked about like me working on these projects 1012 00:58:16,359 --> 00:58:19,919 and I'm working on them and hear my status updates, but you know, I was thinking 1013 00:58:19,919 --> 00:58:23,599 about something you said, where you said, you know, it's really important for us 1014 00:58:23,609 --> 00:58:29,378 to alignment and service our internal end users as much as our external, end users. 1015 00:58:29,708 --> 00:58:34,028 And then I think one way I could do that, would be to help clean up page 1016 00:58:34,038 --> 00:58:36,758 layouts and Salesforce, which everyone in the world totally understands. 1017 00:58:36,758 --> 00:58:37,748 Cause it's always a nightmare. 1018 00:58:37,860 --> 00:58:40,470 she was like, but I, you know, I think our sales ops manager is doing it. 1019 00:58:41,110 --> 00:58:44,803 But, the second thing I thought of is like, maybe I can make it easier for 1020 00:58:44,833 --> 00:58:46,683 people to submit juror tickets with us. 1021 00:58:46,713 --> 00:58:49,363 Cause I think we've gotten so many different form fields that 1022 00:58:49,363 --> 00:58:50,343 now it's a little confusing. 1023 00:58:51,113 --> 00:58:52,023 Amazing. 1024 00:58:52,313 --> 00:58:55,123 And I think she had the bandwidth to think about that because 1025 00:58:55,123 --> 00:58:56,583 we gave her space for growth. 1026 00:58:56,793 --> 00:59:01,183 So one really important thing that I do for my team, and this is so important, 1027 00:59:01,183 --> 00:59:06,823 I think as a RevOps team is that there is some kind of growth from a technology 1028 00:59:06,823 --> 00:59:09,353 perspective, from a skillset perspective. 1029 00:59:10,113 --> 00:59:13,893 We have a monthly certification accountability group that we do. 1030 00:59:14,723 --> 00:59:15,953 It's just 30 minutes. 1031 00:59:16,673 --> 00:59:20,427 Half the time we're like, yeah, we meant to, get through modules X, Y, and Z. 1032 00:59:20,427 --> 00:59:22,107 And we didn't cause it was a crazy month. 1033 00:59:22,567 --> 00:59:27,699 But I think making that space for people on your team, so you can not 1034 00:59:27,699 --> 00:59:35,129 just grow the business, but grow them as individual so that they can take the, 1035 00:59:35,159 --> 00:59:40,582 that knowledge and take that investment in them as a person and then bring that 1036 00:59:40,582 --> 00:59:42,072 back because it does come back tenfold. 1037 00:59:42,072 --> 00:59:45,312 I mean, I just gave you that example of again, this analyst who was like. 1038 00:59:46,202 --> 00:59:49,612 I want to make things better and here's an example of how I can tangibly do that. 1039 00:59:49,942 --> 00:59:52,312 But I think she was able to do that because we have been 1040 00:59:52,312 --> 00:59:53,832 investing in her career growth. 1041 00:59:54,307 --> 00:59:58,687 We've been investing in her ability to upskill, getting her exposed to different 1042 00:59:58,697 --> 01:00:01,017 tools that she's never used before. 1043 01:00:01,457 --> 01:00:07,727 And so it's really not just thinking about how can RevOps help the business, but 1044 01:00:07,737 --> 01:00:09,757 you also have to feed yourself, right? 1045 01:00:09,757 --> 01:00:14,897 So how do you feed your internal RevOps team so that they can be even more 1046 01:00:14,897 --> 01:00:20,521 stronger, even more aligned with what's happening in the industry or technology 1047 01:00:20,521 --> 01:00:22,791 wise so that they can be very effective. 1048 01:00:22,801 --> 01:00:25,567 And so that's the second thing that keeps me up at night. 1049 01:00:26,678 --> 01:00:33,177 how do I keep my team interested, growing without disrupting day to day operations. 1050 01:00:33,406 --> 01:00:33,956 Justin Norris: I love it. 1051 01:00:33,966 --> 01:00:34,556 So important. 1052 01:00:35,556 --> 01:00:37,846 Julia, really glad you could join us today. 1053 01:00:37,846 --> 01:00:40,236 It was super inspiring hearing about what you're doing. 1054 01:00:40,236 --> 01:00:42,852 And, lots of folks out there are going to find it interesting too. 1055 01:00:42,902 --> 01:00:44,422 So thank you so much for sharing with us. 1056 01:00:45,035 --> 01:00:46,555 Julia Kim: Well, thank you so much for having me.