Episode 33

full
Published on:

20th May 2024

Lessons from Leading a Unified RevOps Function - Julia Kim

I'm a really big believer in the idea of a unified RevOps function supporting all the go-to-market teams.

But I'll be honest, sometimes it's a little discouraging when I look at how RevOps is done in practice, because outside of a few examples, I usually see essentially a sales ops function with a new name.

So I wanted to find people who are actually leading a unified RevOps team in the real world and to understand how they're doing it and how it's working out for them.

Today's guest is leading a very mature RevOps function at Electric and has a ton of practical insight to share.

Thanks to Our Sponsor

Many thanks to the sponsor of this episode - Knak.

If you don't know them (you should), Knak is an amazing email and landing page builder that integrates directly with your marketing automation platform.

You set the brand guidelines and then give your users a building experience that’s slick, modern and beautiful. When they’re done, everything goes to your MAP at the push of a button.

What's more, it supports global teams, approval workflows, and it’s got your integrations. Click the link below to get a special offer just for my listeners.

Try Knak

About Today's Guest

Julia Kim is VP of Revenue Operations for Electric and an Adjunct Instructor at Columbia University. She has over 10 years experience as an operations executive and has launched award-winning consumer and SaaS products mentioned in the Wall Street Journal, Forbes, Forrester, and TechCrunch.

Before Electric, she led GTM operations for 4 profitable acquisitions. In addition to her RevOps experience, she has a technical background with a recent focus in artificial intelligence and predictive data modelling.

https://www.linkedin.com/in/juliajuleskim/

Key Topics

  • [00:00] - Introduction
  • [01:50] - Definition of Revenue Operations
  • [03:40] - RevOps at different stages of maturity
  • [09:09] - Deep dive on Julia’s team structure
  • [14:00] - Collaboration within the RevOps team
  • [21:52] - Addressing concerns about unifying the ops functions
  • [28:07] - Identifying biggest opportunities for impact
  • [37:19] - Relationship with data team
  • [40:11] - Change management and enablement
  • [47:37] - RevOps and AI
  • [55:11] - What’s a current challenge?

Thanks to Our Sponsor

Big thanks goes out UserGems for sponsoring today’s episode. 

We all know that outbound is really tough. Now imagine a world where you’re reaching people who know your product, love your product, and are actually happy to hear from you. 

UserGems makes that a reality. They identify your customers and champions who change jobs and automatically push new contacts to your CRM so your team can follow up. 

If you’re not reaching out to customer job changers, you’re missing opportunities. Click the link below for a special offer just for my listeners.

Try UserGems

Learn More

Visit the RevOps FM Substack for our weekly newsletter:

Newsletter

Transcript
Justin Norris:

I'm a really big believer in the idea of RebOps as a function,

Justin Norris:

supporting all the go to market teams, marketing, sales, customer success.

Justin Norris:

Quite often partner ops or data ops to this belief is one of the

Justin Norris:

reasons for the name of this show.

Justin Norris:

And it's really why I try to take a broad view across the entire go

Justin Norris:

to market function in terms of the episodes and the guests that we have.

Justin Norris:

But I'll be honest, sometimes it's a little discouraging when I look

Justin Norris:

at how Rev Ops is done in practice.

Justin Norris:

And when I look at job descriptions for Rev Ops leaders, because outside

Justin Norris:

of a few examples, I usually see essentially a sales ops function with.

Justin Norris:

So I posted on LinkedIn a few weeks ago, thinking out loud and asking who's

Justin Norris:

actually leading a unified rev ops team in the real world, where are all

Justin Norris:

these people and how are they doing it and how's it working out for them?

Justin Norris:

And lo and behold, I got connected with a bunch of really smart

Justin Norris:

folks who you'll be hearing from in the weeks and months ahead.

Justin Norris:

And first on that list is Julia Kim, VP of revenue operations at electric,

Justin Norris:

where she leads a unified rev ops team.

Justin Norris:

Julie has been an operations executive for over 10 years now, and is also an

Justin Norris:

adjunct professor at Columbia university.

Justin Norris:

So she's got a ton of good stuff to share with us.

Justin Norris:

Very excited to chat with you today, Julia.

Julia Kim:

I'm absolutely thrilled to be here because I absolutely

Julia Kim:

know what you're talking about.

Julia Kim:

It is a challenge.

Julia Kim:

I think a lot of people think of RevOps as a sales ops function, but

Julia Kim:

you're missing out on so many of the benefits of revenue operations

Julia Kim:

if you think in sort of that silo.

Julia Kim:

And so I'm really glad we're going to be able to talk about

Julia Kim:

that today.

Justin Norris:

Amazing.

Justin Norris:

So maybe let's start there with revenue operations.

Justin Norris:

How do you think of it?

Justin Norris:

If you had to put it in a nutshell, what's the scope and

Justin Norris:

what is the mandate of RevOps?

Julia Kim:

So here at electric, it really is very cross functional

Julia Kim:

and very much focused on the go to market teams and motion.

Julia Kim:

So, if you think about what teams typically are included in a go to market

Julia Kim:

team, You know, kind of scope, it would be sales, marketing, customer success,

Julia Kim:

partnerships or business development a little bit of finance thrown in but lots

Julia Kim:

of different opportunities to collaborate when it comes to generating revenue,

Julia Kim:

whether it's through new business net new.

Julia Kim:

or retention through existing customers and then utilizing your relationship

Julia Kim:

with those customers to grow revenue.

Julia Kim:

And so when I think about revenue operations, I really think about it

Julia Kim:

in the context of all of those teams.

Julia Kim:

And then also thinking about it from the perspective of data.

Julia Kim:

What data do we have?

Julia Kim:

How are we collecting that data?

Julia Kim:

How are we storing that data?

Julia Kim:

How are we reporting on that data?

Julia Kim:

The process.

Julia Kim:

in terms of what's different between a marketing process that may be

Julia Kim:

top of funnel versus a customer success workflow in, retention.

Julia Kim:

And then also thinking about it from a tech stack perspective, because one of

Julia Kim:

the biggest drivers and one of the things I leverage all the time is technology

Julia Kim:

because that is a multiplier for you.

Julia Kim:

A lot of times RevOps teams don't get a ton of support internally.

Julia Kim:

Fortunately for me here at Electric, there's a ton of support for RevOps,

Julia Kim:

but in many organizations you don't get a lot of the support that you need

Julia Kim:

in the form of resources or people.

Julia Kim:

And so what do you do?

Julia Kim:

You can absolutely use technology to help multiply all of those benefits that you

Julia Kim:

would get from a unified RevOps team.

Justin Norris:

/one of the things that I think about a lot.

Justin Norris:

Is where does the responsibility of the function itself and,

Justin Norris:

where does rev ops begin?

Justin Norris:

I mean, there's certain things like technology is a, is an area where

Justin Norris:

it's usually quite unambiguous.

Justin Norris:

And then I find that there are sometimes gray areas where it's a partnership.

Justin Norris:

There's some push and pull.

Justin Norris:

how do you think about that?

Justin Norris:

like, where do people say, like, we need to bring ops in for

Justin Norris:

this sort of problem in your

Julia Kim:

it really depends on where you are in the spectrum of

Julia Kim:

maturity for your organization.

Julia Kim:

And I think this is a piece that is sometimes missed because I think a lot of

Julia Kim:

times people just kind of have a blanket approach to how they balance that ratio of

Julia Kim:

operational tactical things and strategy.

Julia Kim:

And so When I first came to Electric, I was actually actively recruited

Julia Kim:

to join two fixed rev ops there.

Julia Kim:

There was a lot that was going on.

Julia Kim:

were more on the immature side when it came to the

Julia Kim:

operations and tactical pieces.

Julia Kim:

And so when you think about an organization that's in that state, you

Julia Kim:

really have to think about What is going to benefit the organization the most?

Julia Kim:

And it's usually the more operational processes, less on the strategy.

Julia Kim:

It's the doing and getting things done and kind of cleaning things

Julia Kim:

up and right sizing things.

Julia Kim:

And so if you're in an organization where you're sort of on that immature

Julia Kim:

side of that spectrum, you're spending a lot more time doing Less time

Julia Kim:

on the responsibility of coming up with the strategy and the direction.

Julia Kim:

However, as the organization matures, and this is where electric is today,

Julia Kim:

we're fairly mature on the operational And that's where RevOps has come in

Julia Kim:

more recently to be much more strategic.

Julia Kim:

So one of the things that I try to align at every stage of RevOps

Julia Kim:

organization is your org design.

Julia Kim:

So if you think about your org design, it's who are the people

Julia Kim:

that are on your RevOps team.

Julia Kim:

In Electric, it's a stand alone team.

Julia Kim:

some organizations, RevOps as a function is embedded within the

Julia Kim:

different go to market teams.

Julia Kim:

So there might be an ops person on marketing, an ops person on sales,

Julia Kim:

but at Electric, everything is centralized into a central team.

Julia Kim:

And that's actually worked out really well.

Julia Kim:

And when I first started, It was more focus on the operational aspects.

Julia Kim:

So we could get all the things done, build those processes, get the data in

Julia Kim:

the systems be able to report on how we're doing and what's happening in the

Julia Kim:

systems and the processes that we have.

Julia Kim:

But as we became more mature.

Julia Kim:

The strategy piece became a larger and larger component of what RevOps is.

Julia Kim:

And so as part of that, I actually added a new team within

Julia Kim:

RevOps called Revenue Programs.

Julia Kim:

And essentially what Revenue Programs does is it is very much forward thinking.

Julia Kim:

They are thinking about piloting testing out those operational processes

Julia Kim:

at a very small scale, sometimes manually, sometimes with light.

Julia Kim:

Technology or light automation just to make sure that one, we're seeing the

Julia Kim:

outcomes that we want, that we kind of work out all those kinks that, you

Julia Kim:

know, can exist in any process because, anyone can come up with the process,

Julia Kim:

but does it actually work right?

Julia Kim:

you don't know sometimes until you actually roll it out and the

Julia Kim:

mistake and, you know, For a lot of organizations, I think, is when you

Julia Kim:

roll something out with expectation that it's just going to work perfectly

Julia Kim:

on day one, and that's not the case.

Julia Kim:

I think if you are an organization like Electric, where you're a

Julia Kim:

startup, you need to move quickly.

Julia Kim:

Things are shifting constantly.

Julia Kim:

You really do need to take a more iterative and agile approach.

Julia Kim:

And so, Revenue Programs is actually a new what I call a pod.

Julia Kim:

So, we have a Sales Ops pod.

Julia Kim:

A marketing ops pod, a CX pod partnerships and business development

Julia Kim:

actually falls under the sales ops pod.

Julia Kim:

We also have a tech ops pod that supports all of the tech stack that we

Julia Kim:

have, but we now also have a revenue programs pod because that is where we

Julia Kim:

do a lot of our experimentation and say, Does it make sense to you know,

Julia Kim:

roll out this type of payment plan?

Julia Kim:

Does it make sense for us to have the CSMs own this part of, you know, the process?

Julia Kim:

And it's been really great because as we shift and continue to grow, I

Julia Kim:

think strategy is going to be a larger and larger part of what Rev Ops does.

Julia Kim:

But for many organizations where you're sort of in the earlier

Julia Kim:

stages, it's probably not feasible to be as strategic or.

Julia Kim:

Own a lot of that directionality you're talking about because

Julia Kim:

there's just too many things on

Julia Kim:

fire.

Justin Norris:

It's kind of a hierarchy of needs, almost, if we think about it that

Julia Kim:

Absolutely.

Julia Kim:

Absolutely.

Justin Norris:

run an email campaign, then you're not necessarily going to

Justin Norris:

be thinking deeply about strategy until you have those fundamentals in place.

Julia Kim:

Yes.

Julia Kim:

people are like, well, what's the value of revenue operations if they

Julia Kim:

can't even get in your example, right?

Julia Kim:

An email campaign, you know, standardized and have it deliver in terms of, click

Julia Kim:

through rates or things like that.

Julia Kim:

And so again, it's really focusing on where can you provide the most value?

Julia Kim:

And once you hit those.

Julia Kim:

points, that's when you have to really think about, okay, well, how

Julia Kim:

can I shift more of to that strategy?

Julia Kim:

So we're not in a place where we're being reactive because I think a lot

Julia Kim:

of rev ops teams are very reactive.

Julia Kim:

And so how do you shift from being very reactive to being more proactive?

Julia Kim:

It's also part of that maturity, right?

Julia Kim:

Because when you're strategic, you can almost put those processes in

Julia Kim:

place to help you be more strategic.

Julia Kim:

But you can't get there without kind of cleaning house and making

Julia Kim:

sure your own house is in order.

Justin Norris:

I'm fascinated by the structure of your team.

Justin Norris:

And so I want to just pull those different pods apart a bit that you described.

Justin Norris:

Maybe we'll just start with the tech podcast, perhaps it's the easiest

Justin Norris:

for everyone to understand, but it sounds to me like kind of almost like

Justin Norris:

a business systems function embedded within your team runs the technology.

Justin Norris:

Is that an accurate way of thinking about it?

Julia Kim:

Yes, absolutely.

Julia Kim:

they are responsible for primarily for our CRM system.

Julia Kim:

We use Salesforce at electric.

Julia Kim:

And a lot of what they do is.

Julia Kim:

day to day in terms of ticket management, because obviously there

Julia Kim:

are many issues that might come up or, you know, people want different

Julia Kim:

fields or different functions.

Julia Kim:

They're also responsible for things like tech debt.

Julia Kim:

You know, with any systems you often have things that you really need

Julia Kim:

to think about cleaning up in order to kind of maintain the system.

Julia Kim:

And then also strategy in terms of how can we expand the use of our

Julia Kim:

systems in order to make it better?

Julia Kim:

So one great example is we use Salesforce primarily for

Julia Kim:

sales cloud and service cloud.

Julia Kim:

We also have Salesforce CPQ and billing, but is what we have in

Julia Kim:

place good enough or supporting the partnerships and business

Julia Kim:

development we're trying to accomplish?

Julia Kim:

Right now we're okay, but I think we'll soon get to a point Because of the

Julia Kim:

partnerships that we have, because of the partner ecosystem, we have that we

Julia Kim:

will likely need to think about, you know, are there more ways that we can

Julia Kim:

leverage salesforce or some other tool that maybe integrates with salesforce

Julia Kim:

to better enable both internal folks.

Julia Kim:

And also external partners, right?

Julia Kim:

And so really thinking about that and starting to do discovery around

Julia Kim:

that and really having a milestone in place that says when partnerships

Julia Kim:

looks like this might be a good time for us to kind of pull the trigger and

Julia Kim:

start really being serious about this.

Julia Kim:

But that's where tech ops has been, you know, an amazing partner

Julia Kim:

for many of these go to market teams, because it's not just about.

Julia Kim:

Making sure that the systems are running, but it's also thinking strategically

Julia Kim:

about what are their needs in the future,

Justin Norris:

And are they running all the technology that

Justin Norris:

the go to market teams use?

Justin Norris:

Or are there like, let's say your marketing automation system, or

Justin Norris:

maybe even smaller, tools with a, with a narrower scope, are those run

Justin Norris:

by some of the other pods directly?

Julia Kim:

So it used to be that a lot of those tools were actually centralized

Julia Kim:

and tech ops, but again, part of this maturity model that I'm talking about.

Julia Kim:

You sometimes get to a point where you need to really dig deeper

Julia Kim:

into the tools that you have.

Julia Kim:

And at that point, you need someone who's almost a subject

Julia Kim:

matter expert in that tool.

Julia Kim:

So it's not just about administering the tool, like adding users or

Julia Kim:

removing users or turning on features.

Julia Kim:

It's almost thinking about what are we not using or what are we

Julia Kim:

using that we could use better?

Julia Kim:

And so now the shift has actually been.

Julia Kim:

Exactly what you're saying.

Julia Kim:

We are now moving a lot of these core systems, for example, like our marketing

Julia Kim:

automation platform, which is Marketo, or our customer engagement platform,

Julia Kim:

which is Gainsight, we're moving them now into the Ops Manager's domain, because

Julia Kim:

they're likely to have much better insight and how we can leverage those tools.

Julia Kim:

They can build those relationships with our vendors.

Julia Kim:

And so it's really about figuring out how can we dig even deeper,

Julia Kim:

and I think this also aligns with what a lot of companies are doing.

Julia Kim:

the economy is not that great.

Julia Kim:

And so a lot of RevOps teams are being asked to, you know, be strategic, do

Julia Kim:

some tech consolidation seeing how they can reduce expenses, right, And

Julia Kim:

so part of that for us at electric has been how can I have my team, Almost

Julia Kim:

say, is this really a tool or is there another tool that we're using that

Julia Kim:

has the same exact features, but we can incorporate a lower costs or maybe

Julia Kim:

it's already included in our contract.

Julia Kim:

A great example is a chat feature.

Julia Kim:

We had actually three different tools that had chat, and one of the nice things

Julia Kim:

about Marketo was that they talked about this AI driven dynamic chat feature that

Julia Kim:

they rolled out last year, and we were clearly not leveraging because we were

Julia Kim:

using two other chat, you know, platforms.

Julia Kim:

And so that's a great opportunity for us to say, okay, well, let's

Julia Kim:

not pay for these other two tools.

Julia Kim:

Let's consolidate in a tool we have, Marketo.

Julia Kim:

Leverage the AI features that they're saying are fantastic and really make

Julia Kim:

that experience for our prospects even better than they were before.

Julia Kim:

And so I think that's a strategy that anyone can take, especially at a

Julia Kim:

time like this, when a lot of finance teams are saying, Hey, you know,

Julia Kim:

we're spending a lot on these tools.

Julia Kim:

What can we do?

Justin Norris:

And what you just described in a way, to me, it highlights

Justin Norris:

some of the benefits ostensibly that we should gain from RevOps and

Justin Norris:

that we, we don't have these silos where like, you know, sales ops has

Justin Norris:

a tool and marketing ops has a tool.

Justin Norris:

Um, The team's actually can look at things holistically together.

Justin Norris:

And I'm curious, how do those different, like, you've got your marketing ops

Justin Norris:

pod, your sales ops pod, and your CFs pod, aside from the fact that they all

Justin Norris:

roll up to you, how do they collaborate together on like a day to day basis

Justin Norris:

to make these sorts of decisions?

Julia Kim:

Yeah, there's a few different ways that I've built

Julia Kim:

collaboration into our team.

Julia Kim:

It really starts with just us being humans and getting to know each

Julia Kim:

other and enjoying, the day to day and working with each other.

Julia Kim:

So, I do a lot with my team to really build up our personal relationship,

Julia Kim:

because if you don't enjoy working with them, and we're at work for

Julia Kim:

many hours a day, that's a problem.

Julia Kim:

And so we've built 1, a really strong team of high performers.

Julia Kim:

And then 2, we have a lot of activities where we're.

Julia Kim:

maybe not talking about RevOps, but we're getting to know each

Julia Kim:

other, we're solving problems together, we're having fun together.

Julia Kim:

We have a weekly meeting on Friday afternoons called Weekly Wins.

Julia Kim:

It started out with a whole was a win that I had from a professional perspective

Julia Kim:

to what did I have as a personal win?

Julia Kim:

But What we found was, we knew so much about what was happening week over

Julia Kim:

week that wasn't really that engaging.

Julia Kim:

And so we actually now have it essentially a half hour game time together.

Julia Kim:

And so we break up into teams, we have different formations, we are

Julia Kim:

competitive, we solve problems.

Julia Kim:

And so all of those things are ways that aren't focused on our day to

Julia Kim:

day, but we're still getting to know each other, build culture, and then

Julia Kim:

learn to solve problems together.

Julia Kim:

On the flip side, when it comes to projects and visibility, we have a

Julia Kim:

weekly team stand on Tuesday mornings where we go through high priority

Julia Kim:

projects, people kind of flag different things that they're talking about.

Julia Kim:

We also have systems in place to help us because as much as we all

Julia Kim:

want to be creatures of habits.

Julia Kim:

There's a lot of things that are often being thrown at RevOps teams, so having

Julia Kim:

systems in place to help collaborate, so we're very active on Slack.

Julia Kim:

We have dedicated, internal Slack channels for different things.

Julia Kim:

we use the Atlassian suite.

Julia Kim:

So we use Confluence for documentation.

Julia Kim:

That is so important to us.

Julia Kim:

I was looking at just the sheer number of documents that we

Julia Kim:

created in the last six months.

Julia Kim:

And it's, over 150 pages that we created, which is incredible the more

Julia Kim:

information that you're sharing, the better, not just for us internally,

Julia Kim:

but for the entire organization.

Julia Kim:

And then we use JIRA as another tool.

Julia Kim:

Again, to help with collaboration.

Julia Kim:

So the way that every day starts is that we actually have a 9 a.

Julia Kim:

m.

Julia Kim:

JIRA stand, where we go through all the tickets that came

Julia Kim:

through together as a team.

Julia Kim:

It's really quick.

Julia Kim:

On average, it's about 7, 10 minutes, but we allocate about

Julia Kim:

15 minutes every morning.

Julia Kim:

So we're, going through things that are high priority, any

Julia Kim:

incidents that come through.

Julia Kim:

And then we're leaving most of the day to work on different projects.

Julia Kim:

And between the weekly team stand touch point, and then just the constant

Julia Kim:

communication that happens on Slack and usage of JIRA, we are in pretty

Julia Kim:

good communication and fairly aware of what's happening from marketing

Julia Kim:

all the way to, customer success.

Julia Kim:

The one thing that.

Julia Kim:

I have been consciously doing from an internal perspective to even broaden

Julia Kim:

our understanding because 1 of the things that electric has been doing

Julia Kim:

in the last 6 months is shifting from a sales led organization to a

Julia Kim:

much more product led organization.

Julia Kim:

So the emphasis is much more on the product is really educating everyone

Julia Kim:

on what that means and bringing in engineering, bringing in product into

Julia Kim:

those conversations and really trying to, break down those silos that has been one

Julia Kim:

of the things that we've been actively working with all of the teams around.

Julia Kim:

And I think we've been able to make this transition into a

Julia Kim:

more product led organization.

Julia Kim:

We have a ways to go because our product, we revamped our product

Julia Kim:

in November and relaunched it.

Julia Kim:

And that's newer.

Julia Kim:

And so there's still a lot of growth there, but there's a ton of collaboration,

Julia Kim:

a ton of communication, not just within RevOps, but outside of RevOps that is

Julia Kim:

also feeding back within the team itself.

Julia Kim:

So it's really about building all of that communication and collaboration

Julia Kim:

at many different levels so that there isn't one thing that's solving the

Julia Kim:

problem, but it's all these little things that are contributing to a

Julia Kim:

much more smooth and standardized and I would say even consistent process.

Justin Norris:

My friend Paul Wilson has a phrase that's really stuck with

Justin Norris:

me about teams that run the business and then other teams that change the

Justin Norris:

business and how you kind of need both.

Justin Norris:

Is that how you think about it as well?

Justin Norris:

Like the programs team is really there to come in and like disrupt

Justin Norris:

business as usual and figure out better ways of doing things?

Julia Kim:

Absolutely.

Julia Kim:

A great example is that with our new product, you can

Julia Kim:

actually buy Result software.

Julia Kim:

You can buy services from us.

Julia Kim:

You can buy hardware like a new computer and bundle it with a

Julia Kim:

monitor and all kinds of things.

Julia Kim:

And so the question was, where does it live in terms of, Hey, we want to

Julia Kim:

experiment with a flexible payment plan.

Julia Kim:

Where does that live?

Julia Kim:

Does that live in product?

Julia Kim:

Does that live in engineering?

Julia Kim:

Does that live in finance?

Julia Kim:

Does that live?

Julia Kim:

with the customer success team, like where does that live?

Julia Kim:

And I think a lot of companies struggle with that question.

Julia Kim:

And so you end up wasting a lot of time trying to find the right home

Julia Kim:

or someone says, Hey, you know what?

Julia Kim:

I think I'm going to lead this project, but they don't have the right support.

Julia Kim:

They don't have the right resources.

Julia Kim:

They don't have the right access.

Julia Kim:

And so the project just stalls for a period of time.

Julia Kim:

And then people are like, what happened to that project?

Julia Kim:

thought we were going to do, flexible payments.

Julia Kim:

And so that revenue programs pod essentially answers that question, it's

Julia Kim:

not that they have full ownership of all the aspects of flexible payments

Julia Kim:

in this example I'm sharing with you.

Julia Kim:

But they have the ability to bring in the right people at the right time.

Julia Kim:

They have the ability to project manage that project and essentially put some

Julia Kim:

stakes in the ground saying, hey, let's do discovery and see what comes out of this.

Julia Kim:

Let's see, what we can, Push out as an initial product offering, does

Julia Kim:

it mean from a legal perspective?

Julia Kim:

Let me go back to sales ops and see how that looks within that process, or

Julia Kim:

let me go to the procurement team and let me understand what that looks like.

Julia Kim:

So it provides those really important initiatives a home, but maybe not

Julia Kim:

ownership, because at the end of the day, there's probably a different

Julia Kim:

team that needs to own that.

Julia Kim:

Maybe it's finance.

Julia Kim:

Maybe it's.

Julia Kim:

product, I'm not sure, but it allows us to still move forward and maybe get to

Julia Kim:

the point where end owner is obvious.

Julia Kim:

And not only that, but we have some real data about what happened, we put

Julia Kim:

a social post up and people actually click the button and raise their

Julia Kim:

hand and saying, I'm interested.

Julia Kim:

But I think it provides us an ability to move forward without all the pieces in

Julia Kim:

place, because I think that's the biggest killer for a lot of startups, right?

Julia Kim:

Do you have this assumption you need every single thing in place

Julia Kim:

in order for us to be successful?

Julia Kim:

And that's not true.

Julia Kim:

You can.

Julia Kim:

Essentially build the train as you're running down the track and so that's

Julia Kim:

really the value that I see in a pod or structure like revenue programs.

Justin Norris:

I think it's a pillar that a lot of teams are missing or

Justin Norris:

haven't identified or other people do it ad hoc and it creates some tension

Justin Norris:

because I've got to focus on, you know, all these businesses, usual things and

Justin Norris:

keeping the trains running on time.

Justin Norris:

And then when do I have time to focus on those other things?

Justin Norris:

So I find it really interesting that you split that out.

Justin Norris:

There are a lot of folks out there who have concerns about bringing the

Justin Norris:

teams together, whether it's that, you know, a unified function won't be as

Justin Norris:

responsive to the needs of the functions they serve as they would be if they

Justin Norris:

were embedded within it, or that, you know, there can be power disparities.

Justin Norris:

Like I know a lot of marketing ops functions, frankly, are afraid of just

Justin Norris:

being like swallowed up by a bigger sales ops fish and being run by a sales ops

Justin Norris:

leader that doesn't understand marketing.

Justin Norris:

I spoke to a CS ops leader who said that there are similar concerns there.

Justin Norris:

So have you seen those challenges?

Justin Norris:

I guess would be the first question.

Justin Norris:

And how did you address them if so?

Julia Kim:

Yes they exist, but I work really hard to

Julia Kim:

try to reduce those impacts.

Julia Kim:

And it's really at again, many different levels.

Julia Kim:

Uh, Number 1.

Julia Kim:

is that the, again, the org structure makes a lot of difference.

Julia Kim:

And so having a similar structure between the different operational

Julia Kim:

pods is very important.

Julia Kim:

So for example the sales ops pod has a ops manager and an analyst,

Julia Kim:

and there's an enablement person.

Julia Kim:

CX ops has ops manager, analyst enablement.

Julia Kim:

You know, they essentially have a dedicated tech ops person that they

Julia Kim:

can go to someone who's stronger on the sales cloud side, someone who's

Julia Kim:

stronger on the service cloud side.

Julia Kim:

so there's a sort of a mirroring of the org structure that provides

Julia Kim:

just a organizational harmony or equality in those teams.

Julia Kim:

But of course, you have teams like marketing, which

Julia Kim:

tends to be smaller, right?

Julia Kim:

Marketing tends to be smaller than a sales team or a CX team or CS team.

Julia Kim:

And so that's the case here at electric.

Julia Kim:

The marketing pod is quite small.

Julia Kim:

It's one individual right now we have a marketing ops manager, but they can

Julia Kim:

leverage time and work and resources from.

Julia Kim:

Either the sales ops or CX ops pods.

Julia Kim:

So there's ability to leverage resources from different pods.

Julia Kim:

And not only that, but again, thinking about to make that fear go away.

Julia Kim:

there isn't a clear answer for this, but I think the biggest thing is just try it

Julia Kim:

and see if it works because at electric, they actually had the ops teams embedded

Julia Kim:

within the different go to market teams.

Julia Kim:

It didn't work at all.

Julia Kim:

It failed miserably.

Julia Kim:

And so they were very open to a different type of structure.

Julia Kim:

There is really nothing to lose.

Julia Kim:

And the benefit there was that we actually were able to get a ton more productivity.

Julia Kim:

And then you got things like collaboration between Marketing Ops and Sales Ops.

Julia Kim:

I think traditionally, Marketing and Sales and Marketing Ops and

Julia Kim:

Sales Ops, as you were saying, can be a little bit of a conflict.

Julia Kim:

But because we're under one single umbrella, because we're doing the work

Julia Kim:

to, work together, be humans, know that we are all trying to get to that

Julia Kim:

end goal of generating revenue and retaining revenue for our company.

Julia Kim:

We work really well together.

Julia Kim:

And I think it does take the right type of organizational structure and leader,

Julia Kim:

just because you bring everyone together, doesn't mean that it's going to work.

Julia Kim:

And again, I've been very thoughtful in hiring for the team because We

Julia Kim:

want to make sure that everyone is able to have those hard conversations.

Julia Kim:

Sometimes there are problems and it's not that you're the problem or they're the

Julia Kim:

problem or someone caused that problem.

Julia Kim:

There is a problem.

Julia Kim:

And so some wild investigation to figure out what happened.

Julia Kim:

Really, our time is better spent on solving that problem and figuring out

Julia Kim:

how do we move on from here and so having those individuals on the team that have

Julia Kim:

that type of mentality is so important I specifically have been trying to make sure

Julia Kim:

that our culture supports an environment where things are going to not work.

Julia Kim:

Things are going to fail.

Julia Kim:

People may get upset, but the most important thing is how do we identify

Julia Kim:

a solution and how do we move forward?

Julia Kim:

Because if we can, then we're all winning, right?

Julia Kim:

. Justin Norris: I think that is 100 percent the most healthy attitude.

Julia Kim:

And last quick org structure question.

Julia Kim:

I'm just curious, who do you report into?

Julia Kim:

Yeah.

Julia Kim:

I currently report into our CRO.

Julia Kim:

when I first started, we had a senior VP of sales and I reported

Julia Kim:

into that senior VP of sales.

Julia Kim:

And at some point I had reported into finance, but I think this particular

Julia Kim:

structure, and I was actually talking about this with someone over the weekend.

Julia Kim:

Is most optimal because we've actually renamed our go to market teams from

Julia Kim:

go to market teams to revenue teams.

Julia Kim:

Partnerships actually wasn't originally underneath revenue it

Julia Kim:

was actually underneath product.

Julia Kim:

And so that shift and thinking about go to market and thinking about it

Julia Kim:

from a revenue perspective, made us.

Julia Kim:

Very quickly realized that, you know, what partnerships actually belongs

Julia Kim:

under revenue, it is generating revenue.

Julia Kim:

And so, more recently partnerships in the last few months has moved

Julia Kim:

underneath the revenue teams and.

Julia Kim:

Everything kind of revolves around this idea of, are we doing the best

Julia Kim:

we can from a revenue perspective?

Julia Kim:

And not to lose sight of the customer.

Julia Kim:

How do you generate revenue?

Julia Kim:

It's through your customer.

Julia Kim:

So at the end of the day, if you actually drill down and drill down,

Julia Kim:

it always ends up the customer.

Julia Kim:

And so, having RevOps report into our CRO has been fantastic because we have

Julia Kim:

been able to one really bring together all the revenue teams, have revenue as

Julia Kim:

a clear line of sight, build our OKRs around that, but then also again, how do

Julia Kim:

we generate revenue through our customers?

Julia Kim:

And so not lose sight of our customers.

Justin Norris:

It's a good launching off point for the next thing I wanted to ask

Justin Norris:

about, which is, how do you identify where you're going to have the most impact?

Justin Norris:

And it seems like a simple question in a lot of ways, but a hundred percent,

Justin Norris:

let's say revenue operations teams have way more on their plate than they

Justin Norris:

could handle besieged by requests.

Justin Norris:

And so it's a really important capability to have that discernment, to have

Justin Norris:

good judgment about what you take on.

Justin Norris:

So how do you think about that problem about like where your

Justin Norris:

team can make the biggest impact?

Julia Kim:

it is a little easier because we use OKRs.

Julia Kim:

And so what that means is that right now for 2024, our top three are one

Julia Kim:

called fund the future second called efficient funnel and third is MVP

Julia Kim:

is basically most valuable partner.

Julia Kim:

So short of those things and.

Julia Kim:

allocating some time for important things like dealing with tech debt

Julia Kim:

or, just system critical things that essentially very much aligns our priority.

Julia Kim:

Because there is a distribution in the work that we do for each of these OKRs.

Julia Kim:

So the majority of it being on the efficient funnel side,

Julia Kim:

obviously, but not neglecting The MVP OKR or fund the future OKR.

Julia Kim:

So we are constantly looking at it from that lens.

Julia Kim:

And not only that, but also having the right tools in place to be able to capture

Julia Kim:

information that you can then leverage to make that case back to the business.

Julia Kim:

And the reason why I say this is because when I first came to electric there

Julia Kim:

wasn't really a ticket tracking system.

Julia Kim:

There was a little bit of a sauna here and there, some Excel, but

Julia Kim:

it really was a free for all.

Julia Kim:

I think people were just like, Hey, this thing needs to be done.

Julia Kim:

And people are like, okay, yes, I'll do it.

Julia Kim:

And that's a terrible way to function.

Julia Kim:

And so you're absolutely right.

Julia Kim:

People get frustrated.

Julia Kim:

Like, why did you do this?

Julia Kim:

And why didn't you do this?

Julia Kim:

Or I need this.

Julia Kim:

And what do you mean?

Julia Kim:

It's going to take you three weeks.

Julia Kim:

The first priority was we it doesn't seem like you're doing anything right?

Julia Kim:

Number one priority was one, put some sort of system in place where we can actually

Julia Kim:

track what requests we're getting, have them documented and sort of use that

Julia Kim:

as a framework for us to evolve from.

Julia Kim:

And so that's how we ended up with JIRA.

Julia Kim:

It wasn't perfect, but it was like, let's start with a sprint.

Julia Kim:

I think sprint 45 right now, which is fantastic.

Julia Kim:

And we have been able to measure as part of this process, how many tickets

Julia Kim:

get submitted every single day.

Julia Kim:

How many of them are high priority?

Julia Kim:

many of them are low priority or middle, and see how long does

Julia Kim:

it take for us to close tickets, which ones, generate other tickets

Julia Kim:

because there's a little too broad.

Julia Kim:

Yeah.

Julia Kim:

But it's provided us with so much data and it's been able to provide

Julia Kim:

us with information that says we need more resourcing on this side because

Julia Kim:

there's a lot of things happening on this side or oh my gosh it looks like

Julia Kim:

we have a serious enablement issue because all of the tickets that have

Julia Kim:

been coming in for the last two weeks have all been questions that you know

Julia Kim:

could be solved by enablement rather than a you know technical change or

Julia Kim:

you know a process change it's just people just weren't sure what they were

Julia Kim:

doing and so That, that system was such a valuable piece and having the OKRs

Julia Kim:

align with the things that we're doing.

Julia Kim:

We've since evolved because it has been, instrumental to

Julia Kim:

being able to manage priorities.

Julia Kim:

But we've since evolved since day one when I said, Hey we're

Julia Kim:

going to start using JIRA.

Julia Kim:

and there was honestly some pushback.

Julia Kim:

There was.

Julia Kim:

Concern about how do we maintain something like this?

Julia Kim:

And it's like, okay, well, let's just try it.

Julia Kim:

But we're now at the point where we actually have bi weekly

Julia Kim:

sprint planning meetings where we can actually fill out things.

Julia Kim:

We have regular meetings with different stakeholders saying, Hey,

Julia Kim:

what do you want in our next sprint?

Julia Kim:

Which gives people so much joy and excitement.

Julia Kim:

Cause they're like Oh, That thing I asked for, can you do it in Sprint 46?

Julia Kim:

You know, yes, absolutely.

Julia Kim:

Or, you know, actually that's going to have to wait until

Julia Kim:

47 because that's dependent on something that's being done in 46.

Julia Kim:

So having that framework has been so important in being able

Julia Kim:

to balance those priorities.

Julia Kim:

And I think one of the challenges RevOps org and dealing with the

Julia Kim:

sort of prioritization issues and how, to manage that process.

Julia Kim:

Having a tool, even though there's overhead in having that tool is so

Julia Kim:

valuable because it gives you actual data and actual, leverage to say,

Julia Kim:

it's not reasonable for you to expect an email to go out after you just

Julia Kim:

sent it to me 30 minutes ago, right?

Julia Kim:

poor marketing ops manager.

Julia Kim:

Right.

Justin Norris:

you've mentioned tickets and working with your stakeholders, and

Justin Norris:

then we've also talked about strategy you know, a team that is sort of

Justin Norris:

proactively identifying opportunities to evolve strategy and make impact.

Justin Norris:

This is something that I think about a lot.

Justin Norris:

How do you think about.

Justin Norris:

balance or how to wait, taking requests and working with teams

Justin Norris:

to fulfill those requests.

Justin Norris:

In other words, giving GTM teams what they asked for versus proactively

Justin Norris:

looking yourself at data or process and saying, I actually think

Justin Norris:

we need to go in this direction there's these two different motions.

Justin Norris:

They're both important.

Justin Norris:

How do you split your effort between them?

Julia Kim:

I would say it's probably 60% managing requests at this point

Julia Kim:

and 40 percent driving a lot of that.

Julia Kim:

Like, Hey, did you notice this?

Julia Kim:

What do you think about?

Julia Kim:

and I think it's going to shift more in the coming year.

Julia Kim:

it's because of where we are but.

Julia Kim:

want to be clear that for that first 60%, we aren't just taking

Julia Kim:

any ticket and saying, okay, sprint 44, sprint 45, you know, done check.

Julia Kim:

No, we do really think about.

Julia Kim:

One, how does it impact data that we have existing in the system?

Julia Kim:

How does it impact other systems?

Julia Kim:

Because our go to market or RevOps tech stack is highly integrated.

Julia Kim:

We have a ton of integrations, not just to.

Julia Kim:

Existing vendors, but to our product and our legacy product and many different

Julia Kim:

services that we have to provide from a service delivery perspective.

Julia Kim:

And so really important for us to ask those questions and be sort

Julia Kim:

of the gatekeepers around that, but then also really think about.

Julia Kim:

what is the true problem, right?

Julia Kim:

Because we get a lot of requests where they're like,

Julia Kim:

I'm trying to build a report.

Julia Kim:

But I can't get Salesforce to give me this data.

Julia Kim:

Can you add this field?

Julia Kim:

I just need you to add this field so I could build my report so

Julia Kim:

I could send it to X, Y, and Z.

Julia Kim:

And one of the things that I have been really pushing this year with support

Julia Kim:

from our data we have a dedicated engineering data team is really thinking

Julia Kim:

about our CRM as a transactional system.

Julia Kim:

And our snowflake data warehouse as a reporting system.

Julia Kim:

And I think people tend to conflate the two because a lot of times, I mean,

Julia Kim:

Salesforce does have some really great reports and dashboards, but we have

Julia Kim:

become more mature as an organization where we want to integrate product data.

Julia Kim:

We want to integrate other sources of data that don't originate Salesforce.

Julia Kim:

And yes, we can absolutely put that stuff in Salesforce, but.

Julia Kim:

What is the purpose behind that?

Julia Kim:

how is that going to serve us better?

Julia Kim:

And is that really the true purpose of Salesforce?

Julia Kim:

As much as we call it our system of truth, and that is absolutely true, it

Julia Kim:

can still be our system of truth if it's pushing data into our data warehouse

Julia Kim:

and we're reporting there, right?

Julia Kim:

And so, Tools like Looker, Tableau, any BI tool that you have, or

Julia Kim:

even any, data management tools.

Julia Kim:

They're going to do a much better job of slicing and dicing and visualizing

Julia Kim:

the data that you want than Salesforce.

Julia Kim:

As much as Salesforce tries, I mean, they really do try.

Julia Kim:

But, the thing that I think we've come to that point in our

Julia Kim:

maturity level is Salesforce needs to be a transactional database.

Julia Kim:

Anything that has to do with transactions lives there.

Julia Kim:

Anything that has to do with data lives in our data warehouse.

Julia Kim:

And so we can do this ticket, but that's not actually what we need to do here.

Julia Kim:

What really needs to happen is, are you able to generate that report in Loker

Julia Kim:

or Tableau or whatever the system is?

Julia Kim:

And if you're not, Can I help you communicate with our data team?

Julia Kim:

So you can get that information that you need.

Julia Kim:

So it's really kind of thinking about it from that perspective, because as much

Julia Kim:

as it is like it is ticket resolution, it's also thinking about things as in

Julia Kim:

terms of like, what is the true problem?

Julia Kim:

What are we trying to solve?

Justin Norris:

you've touched on data.

Justin Norris:

What's the relationship between your data team and your team?

Justin Norris:

Because obviously there's a lot of codependency there.

Julia Kim:

Yeah.

Julia Kim:

So Salesforce related, Marketo related.

Julia Kim:

And then the data team is fully responsible for our

Julia Kim:

Snowflake data warehouse.

Justin Norris:

One of the challenges I've found with reporting, out of a

Justin Norris:

data warehouse or using that entirely as the system of reporting, and I

Justin Norris:

think a reason why a lot of people just relapse into Salesforce is Even though

Justin Norris:

it's more powerful and ultimately more flexible, there can also be a rigidity.

Justin Norris:

It's like, Oh, actually this table doesn't have this.

Justin Norris:

I'm going to have to do a request and there's friction.

Justin Norris:

So I'm just going to create a quick Salesforce report because it's not right,

Justin Norris:

but it's, the path of least resistance.

Justin Norris:

how have you thought about that in terms of your relationship with that team and

Justin Norris:

making sure that the reporting environment is going to serve those needs so that

Justin Norris:

you can push people towards that place?

Julia Kim:

Yeah, so, that's a really great question.

Julia Kim:

We actually have a data council specifically for that purpose.

Julia Kim:

And the data council is comprised of people from the data team, obviously

Julia Kim:

people from RevOps, there's someone from finance, there's someone from product.

Julia Kim:

There's a lot of different people who are part of that council

Julia Kim:

specifically to talk about.

Julia Kim:

Those questions and almost get ahead of those things.

Julia Kim:

Because a lot of times you have a project that's coming up and it's

Julia Kim:

like, there's probably going to be a data component to this project.

Julia Kim:

So let's make sure that you're aware of it and that we're really thinking about it.

Julia Kim:

The other piece too, is that as we've become more rigorous or a little bit

Julia Kim:

more structured from a rev ops internal process perspective, we have been.

Julia Kim:

Doing more around incorporating UAT or user acceptance testing in our process.

Julia Kim:

And really, it's been an evolution of incorporating the Agile methodology and

Julia Kim:

having sprints and do sprint planning, using JIRA to help manage that.

Julia Kim:

for what we consider medium projects, that might be quick user acceptance

Julia Kim:

testing and, you know, pulling in the data team to help with that user acceptance

Julia Kim:

testing by the ops managers before it gets rolled out, or maybe the enablement

Julia Kim:

manager, and then it gets rolled out for larger projects that are maybe

Julia Kim:

three months in duration or longer, We actually have dedicated testers, either

Julia Kim:

end users from the business or different people that are a part of that process.

Julia Kim:

And we build enablement as part of that testing process too.

Julia Kim:

And the data team is involved there.

Julia Kim:

So we're trying to build multiple touch points so that any data

Julia Kim:

discrepancies or issues and integrating data are caught early.

Julia Kim:

Because we are trying to integrate more of that.

Julia Kim:

Testing and collaboration and knowledge and understanding of what is coming out

Julia Kim:

of this project earlier in the process.

Justin Norris:

I

Justin Norris:

think that's really important.

Justin Norris:

And you touched on user acceptance testing.

Justin Norris:

You've also mentioned enablement and all that to me speaks to, you know,

Justin Norris:

the importance of change management.

Justin Norris:

it's something that RevOps teams in general, maybe don't give as much

Justin Norris:

emphasis as they should in all cases.

Justin Norris:

And honestly, I think it's one of things like they can can make or

Justin Norris:

break, particularly with functions like sales ops or CS ops, where

Justin Norris:

you have to change the behavior.

Justin Norris:

Sometimes have a large number of users, you know, for your project

Justin Norris:

to be successful users who may not necessarily be very interested.

Justin Norris:

Like they want to hit their quota.

Justin Norris:

They're not necessarily care about the success or failure

Justin Norris:

of your project, intrinsically, unless you can make them care.

Justin Norris:

And so I guess the question is, how do you make them care?

Justin Norris:

You know, when you have a project that you're rolling out to those

Justin Norris:

teams, how do you get their buy in so that you can succeed?

Justin Norris:

I am really fortunate that at electric the messaging is consistent

Justin Norris:

from the very top levels down.

Justin Norris:

And so when we have all hands meetings every month, it's pretty

Justin Norris:

clear, like what we care about.

Justin Norris:

You know, Hey, we have a new partnership.

Justin Norris:

This is a focus for us, or Hey, this is a channel that's important for us.

Justin Norris:

This is a process that we're excited about.

Justin Norris:

And so it's that messaging makes it easier to then break that down to

Justin Norris:

what is that specific thing as you were talking about that and cares

Justin Norris:

about that might motivate them.

Justin Norris:

And it could be a financial component, right?

Justin Norris:

It could be a specific could be maybe the way that their comp

Justin Norris:

plan is structured or whatever.

Justin Norris:

Or, you know, for the CSM, maybe it's, you know, Ooh, I don't want my

Justin Norris:

customer to submit a negative NPS, survey or whatnot, but it really is

Justin Norris:

leveraging the clarity that starts in the transparency that starts at the top.

Justin Norris:

And then just then customizing it, and just really understanding who

Justin Norris:

your true end users are internally.

Justin Norris:

But I think it's also a strength of enablement.

Justin Norris:

I think people think of enablement as just training.

Justin Norris:

And I think that's where, again, I have made a conscious effort to differentiate

Justin Norris:

what I think of as enablement.

Justin Norris:

And it actually answers one of the earlier questions you had around You know how do

Justin Norris:

you, how proactive are you about things?

Justin Norris:

And that's a great area for enablement.

Justin Norris:

When they're past the sort of traditional things you think about

Justin Norris:

from an enablement perspective, like training or putting materials

Justin Norris:

together, that's great and everything.

Justin Norris:

And I'm having my enablement manager leverage or analysts more

Justin Norris:

to kind of get some of that done.

Justin Norris:

The real value of enablement is saying, what, where are the gaps in productivity?

Justin Norris:

Because it's not just about learning.

Justin Norris:

It's also about productivity from their perspective from their roles perspective.

Justin Norris:

And so one of the things that my enablement manager and I are actively

Justin Norris:

working on is leveraging her expertise and how people learn, how people

Justin Norris:

ingest information, how people, the different ways that people have to

Justin Norris:

like see or feel or engage with things.

Justin Norris:

And knowledge within the tool.

Justin Norris:

So for example we were just looking at Gong and saying, Hey, you know, maybe

Justin Norris:

there's a better way we can expose some of these dashboard widgets and stuff

Justin Norris:

for people that are in there, or is there a way we can actually kind of

Justin Norris:

pull out some of this information and have it in Salesforce in a better way?

Justin Norris:

We, we actually have an integration, but in a better way.

Justin Norris:

And so.

Justin Norris:

Enablement then becomes not just about training, not just about teaching

Justin Norris:

them about like a sales process.

Justin Norris:

It's almost like, yes, okay, that is the basics of what you need to do.

Justin Norris:

But the real value in enablement is for an AE that now understands

Justin Norris:

what the sales process is.

Justin Norris:

How much time are they spending on emails?

Justin Norris:

How much time are they spending on calls?

Justin Norris:

And is that distribution look okay?

Justin Norris:

So if there's someone who's being much more successful in close winning,

Justin Norris:

how opportunities and they happen to have maybe a 40 60 ratio of like, you

Justin Norris:

know, emails to calls being greater.

Justin Norris:

Maybe that's a tactic that other people on the team can do.

Justin Norris:

And how great is it that enablement can say, Hey, I've been looking at the

Justin Norris:

data, you know, sales director or sales manager, and we've noticed that these

Justin Norris:

2 people or these 3 people are not.

Justin Norris:

quite performing as well, but they're also not doing these other things as well.

Justin Norris:

I know, I think there are some AEs, especially some high performing

Justin Norris:

AEs that have their own kind of method, and it works for them.

Justin Norris:

But I think for the most part, many people maybe just aren't doing

Justin Norris:

the things that they need to do.

Justin Norris:

And it's not just this one time, hey, let's train them

Justin Norris:

and get them knowledgeable.

Justin Norris:

It's a lifelong learning process.

Justin Norris:

And so I think that's where an enablement can be because they can almost, you

Justin Norris:

know, Be a productivity coach, and that can be applied across the board.

Justin Norris:

It's not just eight years.

Justin Norris:

It's not just S.

Justin Norris:

D.

Justin Norris:

R.

Justin Norris:

S.

Justin Norris:

It's not just C.

Justin Norris:

S.

Justin Norris:

M.

Justin Norris:

S.

Justin Norris:

Or A.

Justin Norris:

M.

Justin Norris:

S.

Justin Norris:

You could almost think about this from a project perspective.

Justin Norris:

Like, are we doing projects in a way that are conducive to collaboration, right?

Justin Norris:

and so that's what we're trying to do with enablement and take

Justin Norris:

it to the next level beyond just

Justin Norris:

training.

Justin Norris:

I love that example, as A case of how ops can really drive impact, beyond

Justin Norris:

just, yes, we have a request, we have to partner on those things, but also kind of

Justin Norris:

challenging the business, being somebody who's there, like having a second set of

Justin Norris:

eyes, are we doing this in the best way?

Justin Norris:

Is this what great looks like?

Justin Norris:

How can we move this forward?

Justin Norris:

That's such an important part that often gets missed.

Justin Norris:

I think his teams often don't have time to do it and in full fairness,

Justin Norris:

but having those folks that have that as part of their scope.

Justin Norris:

I think it's just so important

Julia Kim:

Absolutely.

Julia Kim:

And I think one of the best examples I can think of how enablement helped

Julia Kim:

me really again, consolidate our tech stack and therefore save money is I

Julia Kim:

asked our enablement manager to do an analysis and look at our sales stages in

Julia Kim:

the pipeline and see what was the level of usage across all of those stages.

Julia Kim:

And of course, some of it makes sense, right?

Julia Kim:

Like in the beginning, you know, they're having a lot of calls with people.

Julia Kim:

So gong is like high usage, right?

Julia Kim:

And then you can kind of see Salesforce is maybe consistently used maybe a little

Julia Kim:

bit more when you're negotiating but that sort of heat map of how different

Julia Kim:

tools were being utilized, the level of usage, the duration of usage.

Julia Kim:

And the sales stages made it so obvious which tools provided the most value

Julia Kim:

consistently across all the sales stages and then also which ones had sort of like

Julia Kim:

the most impact when and that's a great example of how if you don't think of

Julia Kim:

enablement as just that training function.

Julia Kim:

That is a huge piece of value because you want to make sure that if AEs

Julia Kim:

are spending a ton of time in Gong in the beginning, that they really are

Julia Kim:

leveraging the tools within Gong that are going to help them really move

Julia Kim:

those stages to that next stage, right?

Julia Kim:

And so it's really another efficiency approach in aligning your tech

Julia Kim:

stack, the data you have, the people you have, the process you have.

Julia Kim:

Using a team like RevOps.

Justin Norris:

when we think about technology and go to market, obviously

Justin Norris:

the thing that looms over over us all, uh, right now and for the past

Justin Norris:

year or so has been AI and all the changes that have happened there.

Justin Norris:

No, this is something that you have thought a lot about and

Justin Norris:

have been doing some work there.

Justin Norris:

What are the main use cases that you see, where you think there's an opportunity

Justin Norris:

to drive real value with AI and rev ops?

Julia Kim:

may be alone in this, but I feel so strongly that AI is

Julia Kim:

one of those things that a RevOps team can absolutely leverage and

Julia Kim:

it doesn't have to be homegrown.

Julia Kim:

I was just at a, the Stripe conference last week in San Francisco

Julia Kim:

and Jensen Wong, who is the CEO of Nvidia, was a speaker on one

Julia Kim:

of the days of the conference.

Julia Kim:

And he had this really great quote where he talks about, first you as an

Julia Kim:

individual, so, people are always afraid that they're gonna lose their job to ai.

Julia Kim:

And he said, you're not gonna lose your job to ai, you're gonna lose

Julia Kim:

your job to someone who is using ai.

Julia Kim:

so don't worry about the AI, worry about the person who's leveraging AI.

Julia Kim:

But I think the most impactful statement he said was the second one, which is that

Julia Kim:

your company isn't competing with AI.

Julia Kim:

It's not like your company versus AI, open AI or any of these other, you know,

Julia Kim:

like Microsoft or Google or whatnot, meta.

Julia Kim:

It's competing with another company that is using AI strategically, right?

Julia Kim:

Because you can do all the operational.

Julia Kim:

excellence, tactics, all of that, even strategy, but if you don't have

Julia Kim:

that special sauce of AI you're not going to win against all the others.

Julia Kim:

And so I thought that was so interesting And I think this is where,

Julia Kim:

because there's such a technical component to revenue operations.

Julia Kim:

And because there are so many great tools that are spending millions of dollars

Julia Kim:

within the RevOps tech stack, that you can leverage all of those benefits.

Julia Kim:

Oftentimes these things are already included in your contract.

Julia Kim:

You just don't know about them, or maybe you're not sure.

Julia Kim:

And, you know, you can kind of talk to your rep and say, Hey, I don't want to

Julia Kim:

pay an extra, you know, God knows what for this AI feature, but I would love to

Julia Kim:

pilot it out to see what the ROI might be.

Julia Kim:

But such a great opportunity to leverage all the things that are happening.

Julia Kim:

And really understand what are your true needs around AI.

Julia Kim:

And then if it is something that you need to customize, you

Julia Kim:

can work with your data team.

Julia Kim:

You can work with your engineering team to build out those very custom models or

Julia Kim:

custom machine learning algorithms that might be specific to your industry, but.

Julia Kim:

today, literally today, you could say, Hey, I have gong.

Julia Kim:

How can I leverage those AI features and get started and be competitive?

Julia Kim:

But the areas that, you know, I really think that AI is going to benefit.

Julia Kim:

Rev ops is one around predictive ai.

Julia Kim:

You know, a lot of rev ops teams, I am, you know, one of them

Julia Kim:

have to think about forecasting.

Julia Kim:

What are sales gonna look like?

Julia Kim:

What is spend going to look like, you know, is this customer going to churn?

Julia Kim:

And there are some really great built in features across again, all of those

Julia Kim:

tools in our RevOps tech stack that can help you leverage those use cases.

Julia Kim:

But I think again, predictive AI is such an important area where we can utilize

Julia Kim:

it today and make some contribution to the bottom line for our companies.

Julia Kim:

The other area that's so important is generative AI.

Julia Kim:

And I always think of generative AI, not just about content creation, but

Julia Kim:

really around productivity, right?

Julia Kim:

So it's, you know, if you have outreach, use those gen AI tools in order to,

Julia Kim:

you know, generate those email follow ups you know, use those call summaries

Julia Kim:

and other action item features that are built into, again, the tools

Julia Kim:

that you have in your tech stack.

Julia Kim:

For the most part, those are things that, you know, it's just time consuming

Julia Kim:

for an AE or a CSM they just had a call to do, and great, you know, now they

Julia Kim:

don't have to worry about it anymore.

Julia Kim:

And then one of the other areas that I just think is so

Julia Kim:

great is conversational AI.

Julia Kim:

So you think about how a lot of times AEs spend time trying to

Julia Kim:

explain what the product is doing, what services you're providing.

Julia Kim:

But if you have an inbound prospect that's interested and they can have a

Julia Kim:

very short and meaningful conversation that seems very human like, almost

Julia Kim:

like there's a person behind it and learn and kind of get assets and then

Julia Kim:

talk to an AE when they're ready.

Julia Kim:

That saves time and energy, right?

Julia Kim:

And it increases the likelihood that they're going to ask

Julia Kim:

you the right question.

Julia Kim:

So you can identify the pain points that they truly have

Julia Kim:

that your product can solve for.

Julia Kim:

And I would say the 3rd area that's important is what

Julia Kim:

they call descriptive AI.

Julia Kim:

It's really about, you know, taking unstructured data and

Julia Kim:

finding visibility or insights through that unstructured data.

Julia Kim:

So, Gong is a classic example of that, right?

Julia Kim:

You can't go through every single call recording you have, but it does a

Julia Kim:

really great job of sentiment analysis and just kind of flagging different

Julia Kim:

things within a call at scale, right?

Julia Kim:

And so when you're thinking about, how do I know if our AEs

Julia Kim:

are mentioning our new product?

Julia Kim:

Well, set up a trigger in Gong and see if, you know, if

Julia Kim:

it's actually being discussed.

Julia Kim:

Those are very low lift ways that you can incorporate AI into your day to day

Julia Kim:

RevOps processes and tech stack so that you can actually raise your hand when exec

Julia Kim:

is like, what are you doing for me today?

Julia Kim:

You're like, we've got AI covered.

Julia Kim:

That is such an easy thing to start with now.

Julia Kim:

going back to what Jensen Wang said, at the conference last week.

Julia Kim:

A.

Julia Kim:

There is a lot of hype.

Julia Kim:

There is a hype cycle around A.

Julia Kim:

I.

Julia Kim:

But it's not going away.

Julia Kim:

It is a fundamental technology, a fundamental way of doing business that is

Julia Kim:

going to change many different industries.

Julia Kim:

And.

Julia Kim:

How great, you know, from a rev ops perspective, would it be if you could

Julia Kim:

kind of lead and control how that's used rather than being sort of told?

Julia Kim:

Oh, my gosh, why are we not doing AI?

Julia Kim:

And almost being sort of forced into being in that reactive mode.

Julia Kim:

Whereas you can be very proactive and a lot of, the reps for these

Julia Kim:

vendors are going to be so happy to talk to you and say, Hey,

Julia Kim:

here's some, you know, suggestions.

Julia Kim:

In fact, if you haven't had a QBR recently, or maybe, you know, an

Julia Kim:

executive review recently, schedule one.

Julia Kim:

I'm always interested in learning about what's happening in the roadmap.

Julia Kim:

Maybe you're, hearing about other tools that are being used in the industry.

Julia Kim:

But this is something where.

Julia Kim:

Such a powerful lever, especially if RevOps can kind of say, Hey,

Julia Kim:

I have ownership of this and I can fundamentally change how our

Julia Kim:

business works using this tool.

Julia Kim:

so amazing.

Julia Kim:

So I'm, very much excited about AI.

Julia Kim:

If you cannot tell,

Justin Norris:

Yeah, I mean, I think there is huge opportunity, and I think there is

Justin Norris:

a lot of learning, that needs to be done.

Justin Norris:

That's one of the things that has impressed itself upon me.

Justin Norris:

It's one thing to have AI, but it's another thing to know how to prompt it

Justin Norris:

very well, to understand how to leverage the outputs, how to debug things if

Justin Norris:

you're not getting the results that you want, which, none of which I claim

Justin Norris:

to be expert in, but just speaking to people like yourself, It is a new skill.

Justin Norris:

So to your point about, you know, losing your job to the person who knows how

Justin Norris:

to use AI, there's a real thing there and it is something to keep in mind.

Justin Norris:

Maybe we'll just to end on, uh, you know, a slightly introspective note.

Justin Norris:

You have a very mature team.

Justin Norris:

It seems very high performing.

Justin Norris:

You've told us about all the great things you do.

Justin Norris:

It's interesting also to note the, like we all have challenges.

Justin Norris:

No matter where we are in our career, what are some of the things that you are

Justin Norris:

finding difficult today or that you just don't have totally figured out just yet?

Julia Kim:

working in a startup environment, things shift so

Julia Kim:

quickly and I guess a really big thing.

Julia Kim:

And then a sort of small, big thing.

Julia Kim:

The biggest thing is how can you consistently support the changes that

Julia Kim:

happen day to day, week over week, month over month as a startup and keep

Julia Kim:

your team feeling motivated and driven?

Julia Kim:

Because sometimes.

Julia Kim:

It seems like there's a change in priority, but there isn't.

Julia Kim:

It's just maybe the slight focus, but at the end of the day, the things

Julia Kim:

that you need to accomplish are the same, but people get distracted by

Julia Kim:

maybe the messaging or what's being said, but it's balancing sort of

Julia Kim:

the chaos of being in a startup, the instability of doing new things, right?

Julia Kim:

If you're a startup, that's trying to make a difference in the world.

Julia Kim:

You're doing something that other people have not been doing, And how

Julia Kim:

do you balance that with stability for a team that needs some stability,

Julia Kim:

some structure, some consistency in order to work effectively, right?

Julia Kim:

Because when you think about operations, or you think about

Julia Kim:

things like forecasting or reporting, you can't report if everything's

Julia Kim:

constantly changing every second.

Julia Kim:

Right.

Julia Kim:

And so by the nature of operations, by the nature of

Julia Kim:

process, you need some stability.

Julia Kim:

And so that is the biggest and hardest thing to manage or balance

Julia Kim:

when you're in a startup environment.

Julia Kim:

And I think the second piece for me is, how do you keep people inspired?

Julia Kim:

Because a lot of times, Your day to day is not that sexy, right?

Julia Kim:

You know, it's troubleshooting.

Julia Kim:

Why is Marketo not syncing with

Julia Kim:

Salesforce

Julia Kim:

and I think as humans, as people.

Julia Kim:

As much as we, you know, we're like, yeah, we can do this day in,

Julia Kim:

day out we're curious, we want to learn, we want to grow, we want

Julia Kim:

to have pride in what we're doing.

Julia Kim:

And so, the second hardest thing for me is how do you create that environment

Julia Kim:

where people feel like they're growing?

Julia Kim:

Even when they're running a, you know, at 110%, because all of that 110

Julia Kim:

percent is for the business, right?

Julia Kim:

Because they're doing all these things to optimize revenue.

Julia Kim:

And we may or may not see that some people get comped, you know, maybe because

Julia Kim:

they have a bonus structure that, you know, benefits them when the company's

Julia Kim:

doing well, some people aren't right.

Julia Kim:

And so how do you make people feel like they're growing?

Julia Kim:

How do you make them feel like, wait, here's a way that I can.

Julia Kim:

Make my team better.

Julia Kim:

I mean, I had a really great one on one with one of my analysts earlier today

Julia Kim:

where she said, I know that we talked about like me working on these projects

Julia Kim:

and I'm working on them and hear my status updates, but you know, I was thinking

Julia Kim:

about something you said, where you said, you know, it's really important for us

Julia Kim:

to alignment and service our internal end users as much as our external, end users.

Julia Kim:

And then I think one way I could do that, would be to help clean up page

Julia Kim:

layouts and Salesforce, which everyone in the world totally understands.

Julia Kim:

Cause it's always a nightmare.

Julia Kim:

she was like, but I, you know, I think our sales ops manager is doing it.

Julia Kim:

But, the second thing I thought of is like, maybe I can make it easier for

Julia Kim:

people to submit juror tickets with us.

Julia Kim:

Cause I think we've gotten so many different form fields that

Julia Kim:

now it's a little confusing.

Julia Kim:

Amazing.

Julia Kim:

And I think she had the bandwidth to think about that because

Julia Kim:

we gave her space for growth.

Julia Kim:

So one really important thing that I do for my team, and this is so important,

Julia Kim:

I think as a RevOps team is that there is some kind of growth from a technology

Julia Kim:

perspective, from a skillset perspective.

Julia Kim:

We have a monthly certification accountability group that we do.

Julia Kim:

It's just 30 minutes.

Julia Kim:

Half the time we're like, yeah, we meant to, get through modules X, Y, and Z.

Julia Kim:

And we didn't cause it was a crazy month.

Julia Kim:

But I think making that space for people on your team, so you can not

Julia Kim:

just grow the business, but grow them as individual so that they can take the,

Julia Kim:

that knowledge and take that investment in them as a person and then bring that

Julia Kim:

back because it does come back tenfold.

Julia Kim:

I mean, I just gave you that example of again, this analyst who was like.

Julia Kim:

I want to make things better and here's an example of how I can tangibly do that.

Julia Kim:

But I think she was able to do that because we have been

Julia Kim:

investing in her career growth.

Julia Kim:

We've been investing in her ability to upskill, getting her exposed to different

Julia Kim:

tools that she's never used before.

Julia Kim:

And so it's really not just thinking about how can RevOps help the business, but

Julia Kim:

you also have to feed yourself, right?

Julia Kim:

So how do you feed your internal RevOps team so that they can be even more

Julia Kim:

stronger, even more aligned with what's happening in the industry or technology

Julia Kim:

wise so that they can be very effective.

Julia Kim:

And so that's the second thing that keeps me up at night.

Julia Kim:

how do I keep my team interested, growing without disrupting day to day operations.

Justin Norris:

I love it.

Justin Norris:

So important.

Justin Norris:

Julia, really glad you could join us today.

Justin Norris:

It was super inspiring hearing about what you're doing.

Justin Norris:

And, lots of folks out there are going to find it interesting too.

Justin Norris:

So thank you so much for sharing with us.

Julia Kim:

Well, thank you so much for having me.

Show artwork for RevOps FM

About the Podcast

RevOps FM
Thinking out loud about RevOps and go-to-market strategy.
This podcast is your weekly masterclass on becoming a better revenue operator. We challenge conventional wisdom and dig into what actually works for building predictable revenue at scale.

For show notes and extra resources, visit https://revops.fm/show

Key topics include: marketing technology, sales technology, marketing operations, sales operations, process optimization, team structure, planning, reporting, forecasting, workflow automation, and GTM strategy.

About your host

Profile picture for Justin Norris

Justin Norris

Justin has over 15 years as a marketing, operations, and GTM professional.

He's worked almost exclusively at startups, including a successful exit. As an operations consultant, he's been a trusted partner to numerous SaaS "unicorns" and Fortune 500s.