Prioritization is probably the biggest challenge for ops teams. Say yes to everything - you pretty quickly become a service department. Set your own priorities without input from the business - you can quickly find yourself irrelevant, even out of a job. The best model that I've seen for tackling this problem is what we could call the product management approach to managing MarTech. This is where you effectively treat your stack as an internal product and ops as a product management team working on delivering features for internal customers. Today's guest has practiced this approach at enterprise scale, with an ops team dozens strong. Josh Hill shares his insights and lessons learned, as well as his journey as one of the earliest and well-recognized experts in the Marketo community. 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 Josh Hill is a GTM operations and systems executive who builds revenue accelerating GTM platforms, global teams, and processes in partnership with Product, Sales, and Marketing. He has a strong track record of turning business strategies into live enterprise capabilities and impactful customer experiences. https://www.linkedin.com/in/jhill2/ Key Topics [00:00] - Introduction [01:37] - Josh’s professional journey [04:19] - Development of automation pro as a professional identity [06:48] - Scope and scale of the teams Josh led [08:54] - Definition of a product management approach to martech [15:45] - Should marketing ops be oriented around business impact? [21:03] - Reasons why ops teams need to say “no” sometimes [27:38] - Solving for the internal vs. external customer [30:39] - Asking tough questions about adoption and ROI [33:53] - Building your roadmap [35:53] - Communicating your roadmap internally [40:10] - Cultivating resolve around prioritization and triaging requests [42:43] - How to transition to a product management approach Resource Links Learn More Visit the RevOps FM Substack for our weekly newsletter: Newsletter
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Justin Norris: If I had to name the single biggest challenge for ops teams, it would have to be prioritization. We all have limited resources and we all have way more requests than we can ever handle, even if we worked a 24 hour day. So how do you deal with this problem? If you say yes to everything, you pretty quickly become a service department. You have no strategic input. You just do what you're told and life gets. Kind of miserable. At the same time, if you just set your own priorities and you don't have enough input from the business, you can quickly find yourself irrelevant and you can
potentially find yourself out of a job. So there's a conflict here that needs to be resolved. And the best model that I've seen for tackling this problem is what some people would call the product management approach to managing MarTech or to managing your ops team. And this is where you effectively treat your stack as an internal product and ops as a product management team working on delivering. Features for internal customers today. We're joined by a marketing ops legend, Josh Hill, who has put this into practice in an enterprise setting. And he's going to tell us about how you implement this approach, what it means for
prioritization, how you build the right team to support it and a whole lot more, Josh, it's awesome to have you here today. Josh Hill: I'm glad to be here. Just it's a really interesting early topic for marketing operations pros. And I think I'm still exploring it. So I appreciate that. You think I'm an expert at it. Justin Norris: I want to start with a quick overview of your journey and before I throw that to you to give that to us, I just want to give credit where credit is due and acknowledge kind of a big impact. I think that you've had on my career, like in the very early days
of marketing automation and the nascent era of marketing operations. You were, I think, one of the first people to recognize the opportunity of this discipline and establishing. Yourself as a thought leader, as an expert with your early blog marketing rockstar guides and in particular just diving into the Marketo community, when and it had a leaderboard. I think yours was the face at the top of that leaderboard every day. You could see the investment you were putting into just almost becoming. like the representation of that community and it motivated me to dive
in and to, reply more and to build up my professional identity there. So, maybe you can talk a little bit or touch on, what led you to do that, but I would just love to understand how you got into this field and what you've done. Josh Hill: A lot of people say something similar, and I'm glad that I had an impact on you and others with answering lots and lots of questions. I think that helped me think through the problems I was facing as well. Dive into the technology and how it could actually be used to build experiences. How did I get into this? Well, you know, today, right?
I build scalable GTM platforms and I support the full customer lifecycle working with product marketing and sales. But that's not how it started, right? I was actually in sales working on. Selling information products, which I thought about frequently. And then I moved into demand gen and I ran events and ads and all sorts of things. And because I was process oriented and technical, I took on this implementation of Marketo, right? I chose Marketo and went in pretty deep and then became a consultant as
you know, and answered lots and lots of questions and took on larger and larger projects to the point where. I was working on RingCentral's team, designing systems and teams to support their scale up from 300 million to 2 billion in revenue, working on next generation omnichannel capabilities, radical improvements to speed to lead, and campaign operations um, and a lot more, but I was able to do that because I built up a team. That work, I'm working on little projects at a time, answering questions people had on the community and kind of thinking through, well, how would I solve
that and realizing that many respects a lot of these marketing automation platforms and even Salesforce is a workflow tool and you can make it do. Just about anything you want. So knowing what it is you want to do, building that as a product, right, is important. You know, having an actual curiosity about these things is also important as well. Justin Norris: Do you remember like when you had this recognition that this was a field that you could build a career around? Cause it seemed to me in the beginning that.
you had a lot of like demand gen people buying Marketo and figuring out how to use it and kind of being like amateurs. And I don't mean that in a negative way, but they were not Martech professionals. They were people in an adjacent discipline who are using this tool to do a particular job. And you again, in my mind, were the first person who was like, wait a second, like No, this is a professional discipline. I can establish myself in this way and treat it that way. Where did that recognition come from for you? Or, where did that light bulb go off?
Josh Hill: Yeah, I would say it was A couple months after my first implementation, and it was a funny, I have a funny story about that, which I actually don't share very often is I was doing the project I was maybe, it was live, maybe a couple weeks into seeing auto responders go out right we never had auto responders and I can manage them and it was saving a huge amount of time. And I was seeing that other people were getting traditional marketing projects that I wasn't. And I said, well, gee, you know, I feel like maybe I'm in a backwater now, like I got sidelined because I was working on this technology.
And I feel like, oh, now I'm in this marketing operations backwater. And that seems weird to say now, right? no one had coined marketing operations, or at least I hadn't come across it at the time. And after a couple of months departing the company, I was like, huh. You know, I really like doing that, right? Maybe I should make that my job, right? And I've seen more and more jobs kind of coming up about, like, people needing DemandGen and Marketo because a lot of those, like you said, people were, DemandGen was buying Marketo, it was buying Eloqua, and There were no
professional marketing operations folks, at least for most of the B2B companies. And because I had that technology experience in my past, like where I was a tech support, I ran sysadmin for Linux boxes and all sorts of things. I like that and I'm like, Oh, I can take that approach and apply it to this technology. So it's. more secure, more managed effectively. What we might call marketing operations, DevOps, or something like that today and put some discipline around it because no one else has that kind of unique set of experiences.
Turned out some people did, which is great. But that's how it took it to the next level. but I want people to make sure they understand, like. IT style management of these technologies is important. I think you should master that. But that's not the same as product management. Justin Norris: And so that's where we want to go. And just before we do, you touched a little bit on the sort of scope and scale of some of the teams that you led. And I have a little bit of an inside. View here is we actually collaborated with myself as a consultant. you were my client. So I had a bit of a window into what you were doing.
and it was a big operation that you ran, particularly at ring central, which is where we work together. A big team, lots of people, lots of complexity. it was huge. Can you just give a sense of like the operation that you had there? Josh Hill: So my team grew into more than 30 people around the world, four or five teams, depending on the quarter we were talking about where I did follow, you know, Aidan Thanks approach sort of naturally, but I became a little more aware of it later, right? And architecture system analysts.
Not really programmers per se, but people who knew enough to do low to mid code kind of integration work and would ask the important questions about scale and ensure that there was a lot of cross functional and cross system. Work they would do things like BRDs. I mean everybody could but that's that was more of their focus There was demand gen systems and campaigns there's a front end development team and it was important to separate those because At least at RingCentral, the motion
and the systems are very different for customers versus prospectors. How the campaigns were thought of were different. So you really had to understand each technology, each kind of data flow that was going on, and they were different. and that was only half of the marketing operations team. We had marketing data, we had DevOps, and that had a whole other set of things going on. We had project management and production management, which was also very important. And, people talk about those things as pillars, but I actually got the chance to practice it in real life and build those things with the team
to support a large scale system. And that led me to thinking about, how do you do this at a very large scale? you know, you were the person introduced us to a lot of other tools as well, so thank you for that. Justin Norris: Oh glad to have done it. So thinking then about this product management approach, maybe just a definition, like how do you definitionally think about it? what does it mean? And was it something that you applied? Back then, or is it something kind of just retrospectively looking back? You're like this is the way that I would do it if I was to build That work again.
Josh Hill: I did. And I did. Right. You know, when I think about products, you know, I've been working with software building software or ecosystems for a long time, and I would always think about, okay, well, how does this product work? How is it thinking about the world? And every product does have a point of view, forget who talked about it. Maybe it was Scott Brinker. And, Marketo had a point of view about how you handle B2B lead management, And how much of that influences your choice as a process. But getting back to your question, right?
I love thinking about how customer service, how sales, how features, how other things work to integrate into a product experience. I wanted to be a product manager at one point. And, you know, on an amateur level, as you put it, right? Like, I think about these things daily, right? I would talk with Marketo. I think the product should work this way, right? It's not solving my actual problem. How do I solve my actual problem in the hope that they would put that on the roadmap? And sometimes they did, And what's interesting is that when I started
diving into understanding what a product manager does, as it's defined, you know, in the software world, pMs think about the same things that marketing ops pros think about. They're at this intersection of business, customer experience approval processes, feature development, BRDs, product requirement documents. So it's all of these things. The only other discipline that really works on that is marketing operations or rev ops, or even to some degree sales operations where all of these threads come together to build something So with marketing operations, we're
building typically products around like an event experience or a lead flow. Experience or internal sales product experience, right? So it can be a little bit different because it's more internal typically, but we're always thinking about the outside world and asking marketers. Hey, are you sure you want that form that way and building frameworks to help? Get those requirements and those experiences built, And this really didn't come up as a crystallized thought until a VP brought it up from a very large
organization, like super large and comes by and he says, I want to bring in a product manager for marketing technology. We need strategy and. That was a little surprising because I thought we had strategy. But it did get me thinking about, okay, well, why is he saying this? Right? What is a product management approach doing that's different than what I'm doing? there are some differences, but there are a lot of similarities. So over the last couple of years, I've been researching that and kind of understanding, how are they different? How are they not? Do they just talk differently?
But it's doing the same thing? And largely, yes. If you ask ChatGPT or the internet, you know, what does a product manager do? It's going to give you something mild, like, well, it's responsible for developing and managing products. Okay. Marketing operations focuses on executing marketing strategies and optimizing marketing processes. not very helpful, and it's kind of incomplete, but it's also true. in many ways. It's a messaging question. So when I think about marketing operations, we're often at the bleeding edge of a business of marketing, making an experience come to life for
a marketer for a customer, Whether it's in campaign operations or architecture, you're kind of trying to figure out How does the rubber meet the road? And guess what? Product managers do the same thing, but they don't talk about it exactly the same way. Justin Norris: So is it about in some cases just adopting a product management lexicon, like instead of saying like, Hey, I have a request, say, all right, well, this is a feature and I'm going to put it in my roadmap and we'll develop it in sprints. And, you know, just adopting that terminology, or is there something more fundamental?
At the root of how you think about what you're doing that comes with the product management approach. Josh Hill: You can do that. I suspect a lot of us already are doing that. So what does a PM do, right? it's probably familiar to people who are particularly marketing technology architects or more experienced pros You're aligning experiences to the mission or the customer experience you're enforcing product boundaries or against a strategy Are we going to do something or not do something? Right? How do we treat? Our customers, whether it's internally or externally.
And sometimes you have to think about both in marketing operations, right? I'm building a privacy product to capture opt ins and help speak in compliance. How does that whole end to end process work from the branded page and interaction that an actual customer or non customer has down to how do we use it? Inside our internal systems, you know, how do we get all the approvals for that? And we build products with customers with engineers, We manage all the stakeholders involved from, you know, vps your day to day stakeholders Whoever's
asking for a feature, Someone comes to me and says hey, I want To send gifts to our prospects or our customers for some reason Yeah, we can bring in a vendor do that, but that workflow that goes around it, that's a product, How we use that vendor is a product. And like you said, we do build features, right? And that ideally is managed through a process with business requirements doc, or if you're going to be a product manager, it's a product requirement doc, They're not different, They all have user stories. They have jobs to be done.
And some of us have borrowed from Agile and product management. Terminology to in our data to pay work. So you're probably already doing that. And I think it's really important to do that. If you're going to do an RFP, if you're creating a new workflow, which a workflow can be a product, you know, if you're delivering specifications to engineers. You're creating wireframes and experience workloads. You're doing UX and creative on your team, right? I have a front end development team. What did we talk about a lot? The user experience, We had to build wireframes for certain situations.
You know, how do we create capabilities for a marketer or for our customers or our users to do something, Did we get the requirements right for that? Did we build a minimum viable product, which a lot of us use that terminology? We do testing, UAT, launch decision points, feedback loops. So you're already doing all these things. Now, there is a difference though. Product managers, marketing operations folks, we are interdisciplinary. We're at this intersection of business, marketing, demand gen, sales, user experience, UI, front end development.
We have to know the back end pretty well or back end enough. maybe we know some SQL and some Python, DNS, and email marketing. And that all goes into being a product manager, right? Understanding the customer life cycle. Now where I'd say there are some differences, not just in terminology, is Product managers sometimes say that they're the CEO of a product. Sometimes they don't like that, and that's a debate. But they are closer to understanding the business impact. They're trying to build a business, And they'll have core metrics, like
a North Star metric or aha moments. And they're going to leverage product data and telemetry and build that in. And understand how people interact with the product and whether that feature is working delivering whatever it is they want, Like more and more usage typically, right? Slack users inviting more people from their organization or outside their organization? Marketing Ops doesn't really do that typically. Now you might, if you're saying like implementing You know, sales automation platform, right? Do people send out emails from it?
Are they adopting it? And I've used that to help manage the martech stack, right? If someone's not adopting a product or something I built, maybe we should just continue it or change it. But we don't typically think of it in that way. And that, to me, that's the real difference. The monetization is the real difference between the two functions. Justin Norris: Well, you just said to me, it goes to the heart of the matter in terms of the role, the function, the orientation that marketing ops should have. And I agree with you that we typically don't do it as a discipline.
Quite often we're getting these requests. And even when we're delivering them we're thinking about. what's the best way to deliver this architecturally? Is it going to be robust? Is it going to be scalable? What role do you think marketing ops should have? This is the big question for me in assessing the potential impact of that request, like, Hey, I know you want to. do chat bots that, you know, send AI enabled text messages and, gift baskets whenever somebody does X, Y, Z, but like, is this going to be a good idea?
Is this going to be revenue impacting? In other words, should. Marketing ops, take some of that product oriented mindset of like really looking at the revenue impact of what they're working on and push back more against other teams. Josh Hill: so when we think about pushing back It can be done in different ways in different situations. I would think more about that in first thought, which is the ROI or the impact of the product you're going to build, so we're whether someone's asking you to build something or has a good idea or an idea about something, right?
The first thing I want to do is understand that business requirement and Understand the complete workflow and experience they're trying to give either the internal person or the internal person and the customer, whether the customers pay it or not. And elicit that out and get it into workflow or wireframe, something that we can kind of be more tangible and reactive then understand, okay, well, if we did these things, what's The goal here, right? Do we want someone to fill out a form? Okay. What does that mean for us? Exactly.
They're going to register for an event. And that's, you know, an obvious pipeline generation. Is it going to reduce costs greatly because we automated something for us or our customers? Are we going to enable growth that could not be done before, like with a click to calendar solution, right? Where supposedly will reduce friction in the meeting process. Increase our number of meetings that we get per day, and therefore that should be to an expected revenue. That's a lot higher, And that's the kind of question you need to really ask, especially when you're prioritizing work is I need an ROI metric in order to have
a conversation and to show you where this project is going to live in the queue. I always love working on win back products because there was a clear connection between what I did and the revenue. If you're going to create a chatbot, which is another one of my favorites is that typically doesn't have a connection between building the product and delivering revenue because you're getting someone to sales or getting someone to customer service. And increase an MPS score or getting an upsell opportunity, whatever that is. And I built those products, And in many ways, it was managed like a product,
even if we didn't talk about it that way. But there are other things like, oh, you know, building a CDP or, you know, we're going to create a process that's going to reduce costs or something. You have to really think through the implication of that build to the business, right? So theoretically, a CDP could create some self service opportunities, although that I think is overblown. It could unify enough of our data and identifiers to better personalize the product experience or the website so that Theoretically, at
least that will increase the number of conversions through the funnel. And that has an impact on revenue. So you can definitely tie it back, but you need to think through that. And like you said, that hasn't always been an obvious thing for marketing operations to do. But as I talked about in a couple of presentations, I did on building a business case, you do have to do that. And that's where the pushback happens is you have to ensure that your stakeholders are helping you build that business case. typically Moss is not the business owner, We might be the technical owner, but if you don't have a business partner who is on the hook for
delivering dollars from something you build, then you're just building stuff. Maybe it gets used. Maybe it works. Maybe it doesn't. You should never have tools that don't have a business owner Justin Norris: And about that relationship between, mops and the teams we support in my little intro I kind of presented a straw man vision of, you know, a few different ways that relationship could be structured. They were based on reality though. I think a lot of the teams. Do find themselves in a position where they're getting handed a list of priorities and like, here's the things we need you to do.
Here's the tools we want you to implement. that's not a great place to be, not just for ops, but it's not good for the business because there isn't any of that pushback and I think on the flip side, and I've seen this more in an enterprise setting, maybe you have two where you have a team that's built such a huge kind of a moat around themselves. But everything is just like, no, or, Oh, it'll be on the roadmap in a year. And they just seem completely unresponsive to needs of the business. I think I, I've seen this probably more with CRM teams than with
marketing ops teams, but sorry to say that CRM teams and at that point you end up with like shadow it or people hiring their own, external consultants ,how do you think about the types of approaches that are out there and how to move from one polarity or the other towards this, what I would think of as a more balanced approach, you know, where it's more of a true partnership delivering on business outcomes versus a power struggle. Josh Hill: Well, ideally, that's, the leadership. Saying the right thing, And I've seen this too, in many organizations, right?
Where you get the hippo or what I call the VP stomp, where you got to do something. no explanation, no discussion, no, review of, best options to achieve that goal. Maybe not even a discussion of what that goal really is, in some case. there was someone who posted Something with that thought the other day on LinkedIn where they were very much like, Mops is the saying no to me and they were very upset about this And I really wanted to push back on that person because I it felt like every conversation with someone who hasn't taken the time to explain what
they want to achieve It's like, I didn't say no, I'm thinking about your problem. And that often gets interpreted as no, because I didn't do it in the last five minutes. these things don't happen in five minutes, usually. Or even 30 minutes, and it really depends what it is you're trying to achieve. And that's what, you know, I built the journey doc process for the business requirements doc process. It feels slow to people who just want it now. And the reason that process exists is to ensure we're actually delivering what you want and what you really want and understanding that so that we don't
show up with a product or a hack that actually didn't deliver anything because that has definitely happened before, or everyone misunderstands each other. It's a way to. Avoid misunderstandings and any product manager will have the same problem, Where they get ideas from customers, or they're trying to solve a customer problem. They build a purity and they're trying to explain it to the engineers who are already working on their road map, or they have their own ideas. And that's fine, or they might have a better way of solving it, but is it
actually solving the customer problem? Or is it how they think about the customer problem? And then you get conflicts in the prioritization. And that's really what, one of the things I actually kind of learned very clearly from product management interview videos is you always have to connect back what you're doing to the strategy of the company and the product, you know, it feels a little business Casey. Which is fine, but it makes a good point, right? Like, if we're loading a product at, let's just say, Emails 10 million people
a day to try to get them to respond. But our whole strategy and customer branding is about being nice to people and treating people well, for whatever reason, right? I'm just kind of making up a business strategy. And we have that branding, but we don't treat people that way, right? We're going to have a big mismatch in how people. Perceive us, and we're probably going to hurt our brand and product manager, marketing ops professional with some experience is going to
often say like, Hey, this doesn't feel brand aligned, Are you sure you want to treat people this way? Are you sure that image you're giving us is not brand aligned? Because we see everything that comes through the queue, and we're going to push it back to creative or ask you to get a different approval. And those processes exist to protect us in the company from making it. A big mistake. But, we could build anything you want. It's just, is that really the best thing to do for us for the customer? when I think about product management, when I think about the CRM team, when
I think about marketing ops does the CRM team, the enterprise applications teams They get into difficult situations because if they pull out the Jenga piece, it can break critical processes. And especially if you're a public company, you have SOX compliance, you have impact to street numbers, you cannot do that, You do not break things like that. I mean, I've seen people ask for a field where, for whatever reason, the CRM team just does it and 10, 000 ops get deleted or get closed
out without proper procedures. And then everything blows up in the emergency slack channels. And I'm not saying that happened to any particular company, but I've seen and heard things, right? Well, that's because a process got bypassed, So when I built an SMS product, and my architect did the hard work, so I give her credit for that one. We designed everything out. How do we treat people? When should this happen in the process? How do we do an MVP so we don't just spam everybody who could get an SMS? How do we even know if this person has a cell phone, if
this is a cell phone number? Did we run this by the privacy team who actually had a lot of good advice about that? And then we could launch it and test it. And, oh, by the way, we came up against regulatory issues and maybe we can't do the SMS product for a while because we have to get certain other approvals. Right. And the environment changed product teams, product managers come against the same problem all the time. So I don't like it when people say, Oh, that team is saying no, it's they're trying to protect themselves because they got burned or the
company is going to get burned. So it's up to escalation process to prioritization should be and try to, as some people would say, breakthrough. But I would say it's more about. If you need to escalate something, to me that tells us that there are conflicting priorities, again, across the silos, but they're also not a clear understanding of the strategy that could help us build a rubric or an ROI metric around should we be doing this Justin Norris: when you think about that difficult conversation that you're describing, you know, the stakeholder that feels you're saying no, you're trying
to understand, you know, the job of the product manager, broadly speaking, is to solve for the needs of the customer, you could say, in this context, who is your customer, is it the end customer that you're trying to sell to and serve? And so you're looking at it through is what we're trying to do here. Serving that person or is the customer, the internal stakeholder who you're saying, you know, as long as I deliver the needs for them and they get what they want, whether it ultimately serves the needs of that
end customer, you know, is up to them. And I, I've heard arguments and I can see pros and cons of both points of view. I'm curious where you land on that question. Josh Hill: Well it depends right? Like, what are we building, right? So if I'm building self-service segmentation tool. That's typically an internal product I don't have to worry or think through a lot of the customer impacts other than maybe like ensuring that we have certain privacy rules around it or communication limits. For example, I have to worry about did I understand the goal and is
it actually going to deliver that? And is it easy to use? Is that one of the requirements? Or do you need a sequel? I would assume in a self service situation you would want to have right As little code as possible in order for a natural understanding of how someone would think about a segmentation and how to enable them to do it. And you might have an MVP and you might build out additional things. And I've done that. And the more difficult conversations tend to be someone wants it now and didn't talk to you ahead of time and think through their entire process and you try
to bring them through the requirements process just to really understand what are we trying to achieve, right? Get them to explain themselves. And they don't always love that. But sometimes people. Warm up to the process, especially if you deliver and other times it's been okay. This is an internal and an external impact, I always think of events or privacy in that sense, because they often have internal processes and procedures. That we need to build out for and there's customer experience impacts. So we don't have certain privacy operationalized that could impact
the customer in negative ways, or as well as the company in negative ways. And people don't love it when you bring up potential hurdles, but these are all things we can just make decisions on. These aren't inherently hurdles unless you want to do something that's just illegal. okay, you want to build a CDP. Here's what it's going to take. We can either stop doing these things, or we can hire an agency or hire a team to get it started or launched. Do we have the right business case for that? And working with them. And I've had great partnerships with many stakeholders about building that business case to be effective and either making a decision like, yeah, That's
probably not going to have an ROI. Maybe we should forget about that. Or yeah, this does have a great ROI and it's going to pass all of our IT procurement and financial teams with flying colors. Justin Norris: That ROI question, can be troubling because I think CDP or self service segmentation project that you described is a good example. You could have a model project in the sense that you work with your stakeholder, you define their requirements, you deliver it, it works well, it's scalable.
And then the other question is, as a result of having that capability, were they actually able to send better communications that produced more revenue? So it's like the project was successful on one side, but then did it ultimately meet its goal? The goal that the marketer had. Do you need to care about that? Or is there a certain size at scale of company at which point the separation of powers is such that you just can't really. Have that conversation effectively anymore. Josh Hill: yes. So one of the things I had in my presentation I talked about is I
can make a growth estimate, right? Having a meeting tool is going to likely get us 25 percent more meetings and that'll justify the cost of this tool and implementation. And ideally, you've built in a process and a set of metrics and you've captured that data so that in a month, two months, six months from now, you can actually compare before and after and say, yep, we achieved that or Nope, we didn't. And ideally, you can make a harder call and say, okay, well, we didn't achieve the goal, but it's still paying for itself. Okay, let's investigate how we can increase it.
Or it's completely not doing anything. Do we cancel it? The sales squeal about it. Can we just keep it there? That's a little squishier goal. I tend to be a little harsher and say like, well, I didn't achieve the goal. Maybe we should stop spending money on it. And I've done that. we had a potentially great idea. It's been a lot of time building it out with the vendor and they use 15 percent of it. And I asked the stakeholders, did this change anything? Did you achieve your adoption goal because of this product? And they said, nope, which is great.
Sometimes they don't admit those things, right? They don't want to say that they were wrong. But data doesn't lie, which is nice, usually. So I said, okay, well, we're going to cancel it. And you know what happened? It turned out we could have built the same thing with VelocityScript if we had just Thought about it a little harder instead of rushing into it, that's where, You do have to kind of push back a little bit and think like what options do I really have? And could I have built an MVP for free rather than putting, you know, huge amount of effort and direct dollars into this I've also had other products where we did the segmentation thing and It wasn't really for hyper segmentation.
Oh, that's a favorite topic of mine. It was just to try to speed the marketer to be at the keyboard and say, okay, how many people can I get for this invitation? For example instead of waiting for three or four days for a SQL expert data engineer to do this because of the various complexities and it didn't really get adopted and probably had two or three versions of that built because of poor adoption. we could debate what that was, but at some point, we kind of just stopped maintaining the product, and that's why we have the RDs and ROI analysis
to try to figure out, is this really worth the effort and following up on that process to understand, did we actually achieve that goal? And sometimes you do, I mean, which is great, Justin Norris: hopefully more often than not. Josh Hill: Ideally. Yeah. Justin Norris: so you're constantly making these sorts of decisions, but they don't happen in a vacuum. Ideally with a product, you have a roadmap, a longer term plan, how long that can be, typically depending on the size of the company and how fast or slow it moves. How do you think about that process of building a roadmap?
I know sometimes when I sit down with a blank page, you can be overwhelmed by the different possibilities and all the different things you could be doing. So how do you. bring structure to that Josh Hill: Well, roadmapping is also a product management technique as well as an IT technique. And it's very much the same former of mops. It's very much the same for a product or an enterprise apps team, right? What's the strategy of the org? And that should determine your priorities and generally your methodology. if that's not communicated effectively, then that's going to create a lot more conflicts across the organization because you don't have a rubric, you don't have an ROI base to make comparisons without escalation, And
you want to have ROI prioritization so you minimize the impact of a HIPPO. And, of course, your feelings, Interview stakeholders and certainly bring your own opinions Look at the marketplace. Look at the strategy of the larger company and the other and your competitors. Ideally, right? What are they doing? Are they seeing success? And do that gap analysis of your capabilities versus where you think you want to go and where the marketers and sales team thinks they want to go, And map that back to your goals, your timing. And then, of course, always outcomes, right?
Are we getting an ROI? And when are those milestones? And when should we actually achieve that ROI? And of course, you know, is that cost reduction? Is that a revenue gain? What's that total cost of ownership? Really kind of think through all those pieces, right? If we're going to build a CVP, do we have all of our other data ducks in a row? And what would that cost us? And what would that help us achieve? so if your overall strategy is we're going to have omni channel personalization. You're going to make different decisions in your roadmap to achieve that. If you're doing a PLG motion, you're going to have different decisions and milestones.
If you're doing PLG plus SLG, you'll have different tools and different needs and different capabilities. Justin Norris: very tactically. How do you communicate what the roadmap is? Do you have, Google slide deck? Do you have a wiki page? Cause I find that's a big area of either concern or stress or frustration for stakeholders when they want something, but you're saying not right now, but then they're like, well, where does it sit in there? Like they kind of want. This visibility. How do you provide that? Josh Hill: It's about knowing your audience, You know, the technical schematic is generally for you and the IT team.
I wouldn't show that to anyone typically outside. You know, your roadmap could also be missing something they asked for, and you could show them the roadmap and say, if you want this in the next six months, which is usually how long XYZ would take, we have to change the roadmap. And this is how we're gonna, how we could do that. I think educating marketers and salespeople about those capabilities is really important. If you're not doing that every quarter, they tend to forget and then they go off and buy something. And you're like, well, I could have done that for you in 10 minutes. Why did you go off and buy something? Oh, we didn't know.
Too late. But you did know because it's on the wiki page. Well, they don't know that. They're not going to go look at that. Right? That's why, you know, procurement processes are important to try to catch them before they go too far. Yeah, I mean, a wiki page can help, a spreadsheet can help. Ideally, it's some sort of slider visual that explains capabilities possibly against the funnel or customer lifecycle. I've tried different versions of that. I don't think there's any one solution that works for every company in all situations.
There was a really great set of slides and I don't think I downloaded it, but someone posted on LinkedIn and one of those little click things that slide through that you can't really download. And they were explaining how the PLGmotion can work. And it was kind of a very simple set of steps and it was in a multi slide version, which I thought was actually kind of helpful. I'm a little bit curious. The motion. And then here are increasingly detailed views of the kind of tool you would need to enable that part of the motion and that messaging, adding a sales motion to it.
You know, where does your product fit into it? It doesn't have to describe your every database and our data flow, but it kind of generally described the motion. And I thought that was actually pretty helpful and was probably digestible by most. Senior leaders, but any sort of capability guy. I had a lot of different views as well as a giant deck it was part of our marketing enablement effort. And it you know, we had a wiki and we had an image, but I also had, you know, 200 slides explaining every tool we had and who used it, who owned it,
who, why it was being used, what it could do Theoretically you could search that, did anybody really do that? I don't know. But it was a more helpful guide for my team because it showed everything and not just my team, but all the other teams that we worked with, you could see the whole ecosystem and capabilities. So I don't have a good answer for you. That's going to be the silver bullet. Justin Norris: No, I don't think it's universal. But it's yeah, having that something with the right level of detail that is accessible that gives people what they want, but that doesn't become you know, a
homework assignment in and of itself that Sucks a lot of oxygen out of the room. Josh Hill: You know, if we're gonna bring it back to product management for a moment, like these things are always living documents, right? And you can reprioritize depending on your stakeholders, your customers, the changes in the marketplace, right? Like if AI wasn't on your roadmap a year ago, it probably is now, right? And, you know, engineers are also going to push back on aspects of it or offer their own advice that might impact how you want to think through the order in which things get done. Or might make it simpler for you to achieve certain things if you kind
of walk through the specifications and they can give you feedback on the best way to achieve that. And you might. Keep that as a living document, but it's really up to you as the product manager of your, go to market platform to keep that in front of engineers and your team, stakeholders, as well as executives. And I know that's hard because I've done that. And it's hard because you're doing all these other things they asked me to do. You're trying to actually execute on the roadmap. So do you have time to flash it up every now and then? Say, hey, this is what we achieved.
This is where we're going. This is what has changed. But you do have to do it as a senior MOPS leader Justin Norris: I saw a scenario recently where something broke, you know, that you would consider to be pretty vital to the business and it had a product impact or product input was required to fix it. And yet even. With that happening you know, it wasn't like the product team just jumped on that and said, yeah, we're going to drop everything and fix that. It said we need to review this against all our priorities and then we need to arbitrate what's going to take precedence.
And I thought that was an impressive display of cool headedness and rationality because yep, I know that there's a fire there, but actually there's already three fires over here or there's a water leak here. And like, We still need to always have that assessment and they had, obviously, through long experience, the courage of their convictions and the sort of fortitude to stick to that process, even though something really significant had gone wrong. I don't often see mobs teams have that same kind of fortitude and courage of their convictions, I guess, in those situations, like, okay, great, like that you want to do this, or this is broken, like, here's all the other things
how do you think we cultivate that? Is it just sort of rewiring? Our brains, or how else can we do that? Josh Hill: Yeah, right. ultimately you can only control your own actions and reactions. So you're right. Whoever said that was very much in control of themselves and very confident in Their position and process and that does need to be cultivated and having a good coach, a good executive leader on your side can help that having clear incident processes and documentation can help build that motion. Just because you know, you're following the triage process
or the prioritization process. And that's why it's also again important to have a ROI based approach to prioritization that matches your company strategy because you can always point and say, well, you guys agreed that we're going to do this. Rankly is based on ROI, and your ROI is here, and these other projects are up here, so I'm going to do those first, that takes discipline on your part, But it also takes discipline on the part of the executives. they need to be clear about the ROI, about the priorities of the business. They need to have that discussion together and not in silos.
And that takes discipline on their part. And if that's not happening, for some reason, and they're stomping their feet you know, that's where you escalate, right? Or You know, get everybody on a phone call and say, Hey, look, we've got this conflict about priorities. X, Y, Z. So they wanted this. This is where it falls into the process. These other things are a lower priority right now. if you want to change that's fine. Let's figure it out now before we get too far, whether that's a fire or it's a project. And I Again, that's a personal thing that somebody has to really build into their leadership team.
Justin Norris: so maybe just final thoughts, wrapping up this topic. Let's say somebody is not in this product management mode right now. Their team has a sort of different posture in relation to their stakeholders, but they want to make this transition. What are like kind of the simple first, second and third things they can do to start to make this evolution a reality? Josh Hill: think first recognition is to think that, especially if you've been doing mops for a while. You're probably doing half of the thing as a product manager does, but you're just not thinking that you're doing product management.
So that's 1 thing. You can just say, hey, I'm a product manager now. And then that will get you into a learning mode to say, okay, well, what else does a product manager do? And, you know, there's a couple of things. That you're doing today, So you're doing things like pain points and requirement gathering, you're building features, whether that's a event in a box program template or entire chat workflow or whatever, right? You might have some goals and metrics. You might have some feedback loops already with your stakeholders, Are they adopting this product?
Is a customer using it? Is it generating revenue? Is it tied to revenue? So you're doing maybe like three or four out of the eight. Core thing to add as you grow is to say, okay, well, you might want to look at using a framework to validate and prioritize, Whether it's an ROI framework or a larger view of the business, And what's that strategy the business is taking? What business are you actually in? Do you understand the business owners metrics? Do you understand the potential market scope of your opportunity in the larger scale business, right?
Whatever that is, right? Do you fully understand the target market, the buying teams, the ICPs, and does your database validate those? Are you close to monetization? And you don't have to be necessarily, but you know, if you own a chat product or you're building out certain things that impact revenue in some way, like certain kinds of campaigns or workflows make sure you know that number. Talk about that number, Going back was easy for me to prioritize it. I love that example because I could call up The person requested it. And I said, what's your revenue change from the time before and after?
And they would tell me and we love building for them because they always told us how well we were doing. But don't just make it depend on them. Right? Build that into your process. Understand the goal of the product itself. What is the aha moment? That the product manager of your product is building and do you have it in your database? Are you working on projects related to it? Should you be maybe you should be can you have that conversation with the customer lifecycle team? Or the product manager of the business that you're in and that will help you Obviously better align with the business and your business stakeholders a lot of
people talk about this on linkedin But The product management discipline is typically closer to a business, and the more you can talk about the business, as they always say, right, the more executives will be aligned with you, or you'll be aligned with the executives, and the more they'll view you not an operations function that's there to serve them. They'll view you as that partner, and you won't get flamed on LinkedIn by people who claim you're not paying attention to their needs. Because you actually are. Because you understand the business that they're actually in and you're supporting it. Justin Norris: That's a great note to end on Josh.
I want to thank you for joining me today and, the knowledge and support you've shared kind of with the community at large and with me personally over the years, I'm really grateful for Josh Hill: Always glad to do it, Justin. Thank you for having me.
Every time you explain your business to an AI from scratch, you’re repeating work. The opportunity with context engineering is to make your company’s expertise, processes, and past learning available whenever an agent...
Justin and Lily reflect on their parallel journeys diving deep into AI throughout 2025. They discuss why most AI content misses the mark for operators and system builders working within corporate constraints, share...
SEO used to be the ultimate growth lever - offering massive “free” traffic to marketers who could outsmart the algorithm. But in 2025, it's a different game. In this episode, I’m joined by Gaetano DiNardi - an SEO...
AI agents are everywhere in conversation right now - but what actually makes them work? It’s not just slapping a large language model into a workflow and calling it a day. Under the hood, real agentic systems operate...
Not many people make it to VP of Marketing Operations - Kimi Corrigan has done it twice. In this episode, she shares her journey from marketing coordinator to leading marketing ops at companies like Duo Security, Cisco,...