1 00:00:14,093 --> 00:00:16,983 Justin Norris: If I had to name the single biggest challenge for ops teams, 2 00:00:16,993 --> 00:00:18,963 it would have to be prioritization. 3 00:00:19,423 --> 00:00:23,503 We all have limited resources and we all have way more requests than we can ever 4 00:00:23,503 --> 00:00:26,053 handle, even if we worked a 24 hour day. 5 00:00:26,153 --> 00:00:28,563 So how do you deal with this problem? 6 00:00:29,193 --> 00:00:33,033 If you say yes to everything, you pretty quickly become a service department. 7 00:00:33,043 --> 00:00:34,283 You have no strategic input. 8 00:00:34,283 --> 00:00:36,373 You just do what you're told and life gets. 9 00:00:36,713 --> 00:00:37,443 Kind of miserable. 10 00:00:37,973 --> 00:00:40,963 At the same time, if you just set your own priorities and you don't have enough 11 00:00:41,023 --> 00:00:45,433 input from the business, you can quickly find yourself irrelevant and you can 12 00:00:45,433 --> 00:00:47,143 potentially find yourself out of a job. 13 00:00:47,283 --> 00:00:50,013 So there's a conflict here that needs to be resolved. 14 00:00:50,013 --> 00:00:53,253 And the best model that I've seen for tackling this problem is what 15 00:00:53,263 --> 00:00:56,343 some people would call the product management approach to managing 16 00:00:56,763 --> 00:00:58,873 MarTech or to managing your ops team. 17 00:00:59,263 --> 00:01:01,743 And this is where you effectively treat your stack as an internal 18 00:01:01,743 --> 00:01:05,893 product and ops as a product management team working on delivering. 19 00:01:06,183 --> 00:01:09,493 Features for internal customers today. 20 00:01:09,493 --> 00:01:13,433 We're joined by a marketing ops legend, Josh Hill, who has put this into 21 00:01:13,433 --> 00:01:14,783 practice in an enterprise setting. 22 00:01:14,783 --> 00:01:18,553 And he's going to tell us about how you implement this approach, what it means for 23 00:01:18,553 --> 00:01:22,973 prioritization, how you build the right team to support it and a whole lot more, 24 00:01:23,533 --> 00:01:25,473 Josh, it's awesome to have you here today. 25 00:01:26,234 --> 00:01:27,033 Josh Hill: I'm glad to be here. 26 00:01:27,033 --> 00:01:32,374 Just it's a really interesting early topic for marketing operations pros. 27 00:01:32,454 --> 00:01:34,824 And I think I'm still exploring it. 28 00:01:34,824 --> 00:01:35,614 So I appreciate that. 29 00:01:35,614 --> 00:01:37,144 You think I'm an expert at it. 30 00:01:37,465 --> 00:01:41,505 Justin Norris: I want to start with a quick overview of your journey and before 31 00:01:41,505 --> 00:01:44,884 I throw that to you to give that to us, I just want to give credit where credit is 32 00:01:44,884 --> 00:01:47,455 due and acknowledge kind of a big impact. 33 00:01:47,465 --> 00:01:50,455 I think that you've had on my career, like in the very early days 34 00:01:50,985 --> 00:01:55,384 of marketing automation and the nascent era of marketing operations. 35 00:01:55,384 --> 00:01:59,775 You were, I think, one of the first people to recognize the opportunity 36 00:01:59,815 --> 00:02:01,698 of this discipline and establishing. 37 00:02:01,805 --> 00:02:05,131 Yourself as a thought leader, as an expert with your early blog marketing 38 00:02:05,131 --> 00:02:09,532 rockstar guides and in particular just diving into the Marketo community, 39 00:02:09,532 --> 00:02:10,721 when and it had a leaderboard. 40 00:02:10,761 --> 00:02:15,221 I think yours was the face at the top of that leaderboard every day. 41 00:02:15,221 --> 00:02:18,001 You could see the investment you were putting into just almost becoming. 42 00:02:18,401 --> 00:02:21,655 like the representation of that community and it motivated me to dive 43 00:02:21,655 --> 00:02:26,232 in and to, reply more and to build up my professional identity there. 44 00:02:26,232 --> 00:02:29,907 So, maybe you can talk a little bit or touch on, what led you to do that, but I 45 00:02:29,907 --> 00:02:33,100 would just love to understand how you got into this field and what you've done. 46 00:02:33,824 --> 00:02:36,284 Josh Hill: A lot of people say something similar, and I'm glad that 47 00:02:36,634 --> 00:02:40,724 I had an impact on you and others with answering lots and lots of questions. 48 00:02:40,724 --> 00:02:45,017 I think that helped me think through the problems I was facing as well. 49 00:02:45,797 --> 00:02:49,971 Dive into the technology and how it could actually be used to build experiences. 50 00:02:50,031 --> 00:02:51,322 How did I get into this? 51 00:02:51,382 --> 00:02:53,347 Well, you know, today, right? 52 00:02:53,347 --> 00:02:57,237 I build scalable GTM platforms and I support the full customer lifecycle 53 00:02:57,247 --> 00:02:59,147 working with product marketing and sales. 54 00:02:59,177 --> 00:03:01,187 But that's not how it started, right? 55 00:03:01,217 --> 00:03:03,817 I was actually in sales working on. 56 00:03:03,903 --> 00:03:07,772 Selling information products, which I thought about frequently. 57 00:03:08,172 --> 00:03:13,412 And then I moved into demand gen and I ran events and ads and all sorts of things. 58 00:03:13,932 --> 00:03:17,052 And because I was process oriented and technical, I took on this 59 00:03:17,062 --> 00:03:18,822 implementation of Marketo, right? 60 00:03:18,852 --> 00:03:24,002 I chose Marketo and went in pretty deep and then became a consultant as 61 00:03:24,002 --> 00:03:26,960 you know, and answered lots and lots of questions and took on larger and 62 00:03:26,960 --> 00:03:29,397 larger projects to the point where. 63 00:03:30,107 --> 00:03:34,697 I was working on RingCentral's team, designing systems and teams to support 64 00:03:34,697 --> 00:03:38,728 their scale up from 300 million to 2 billion in revenue, working on next 65 00:03:38,728 --> 00:03:42,089 generation omnichannel capabilities, radical improvements to speed to 66 00:03:42,089 --> 00:03:47,594 lead, and campaign operations um, and a lot more, but I was able to 67 00:03:47,594 --> 00:03:49,219 do that because I built up a team. 68 00:03:49,459 --> 00:03:53,089 That work, I'm working on little projects at a time, answering questions 69 00:03:53,659 --> 00:03:57,029 people had on the community and kind of thinking through, well, how would I solve 70 00:03:57,029 --> 00:04:00,884 that and realizing that many respects a lot of these marketing automation 71 00:04:00,884 --> 00:04:05,444 platforms and even Salesforce is a workflow tool and you can make it do. 72 00:04:05,754 --> 00:04:07,034 Just about anything you want. 73 00:04:07,784 --> 00:04:11,201 So knowing what it is you want to do, building that as a 74 00:04:11,221 --> 00:04:14,543 product, right, is important. 75 00:04:15,174 --> 00:04:18,844 You know, having an actual curiosity about these things is also important as well. 76 00:04:19,434 --> 00:04:22,294 Justin Norris: Do you remember like when you had this recognition 77 00:04:22,294 --> 00:04:26,314 that this was a field that you could build a career around? 78 00:04:26,314 --> 00:04:28,074 Cause it seemed to me in the beginning that. 79 00:04:28,364 --> 00:04:32,044 you had a lot of like demand gen people buying Marketo and figuring out how to 80 00:04:32,044 --> 00:04:35,114 use it and kind of being like amateurs. 81 00:04:35,114 --> 00:04:38,924 And I don't mean that in a negative way, but they were not Martech professionals. 82 00:04:38,924 --> 00:04:41,384 They were people in an adjacent discipline who are using this 83 00:04:41,394 --> 00:04:43,194 tool to do a particular job. 84 00:04:43,754 --> 00:04:48,183 And you again, in my mind, were the first person who was like, wait a second, like 85 00:04:48,198 --> 00:04:49,738 No, this is a professional discipline. 86 00:04:49,738 --> 00:04:53,148 I can establish myself in this way and treat it that way. 87 00:04:53,678 --> 00:04:55,361 Where did that recognition come from for you? 88 00:04:55,371 --> 00:04:57,741 Or, where did that light bulb go off? 89 00:04:58,846 --> 00:05:03,036 Josh Hill: Yeah, I would say it was A couple months after my first 90 00:05:03,036 --> 00:05:06,166 implementation, and it was a funny, I have a funny story about that, which I 91 00:05:06,406 --> 00:05:11,928 actually don't share very often is I was doing the project I was maybe, it was 92 00:05:11,938 --> 00:05:15,818 live, maybe a couple weeks into seeing auto responders go out right we never 93 00:05:15,818 --> 00:05:19,351 had auto responders and I can manage them and it was saving a huge amount of time. 94 00:05:20,011 --> 00:05:23,367 And I was seeing that other people were getting traditional 95 00:05:23,377 --> 00:05:25,087 marketing projects that I wasn't. 96 00:05:25,503 --> 00:05:28,446 And I said, well, gee, you know, I feel like maybe I'm in a backwater 97 00:05:28,446 --> 00:05:31,646 now, like I got sidelined because I was working on this technology. 98 00:05:32,216 --> 00:05:35,796 And I feel like, oh, now I'm in this marketing operations backwater. 99 00:05:36,326 --> 00:05:38,536 And that seems weird to say now, right? 100 00:05:38,976 --> 00:05:41,566 no one had coined marketing operations, or at least I hadn't 101 00:05:41,616 --> 00:05:42,886 come across it at the time. 102 00:05:42,886 --> 00:05:45,902 And after a couple of months departing the company, I was like, huh. 103 00:05:46,537 --> 00:05:48,747 You know, I really like doing that, right? 104 00:05:49,617 --> 00:05:51,847 Maybe I should make that my job, right? 105 00:05:52,387 --> 00:05:55,117 And I've seen more and more jobs kind of coming up about, like, people 106 00:05:55,117 --> 00:05:58,727 needing DemandGen and Marketo because a lot of those, like you said, people 107 00:05:58,727 --> 00:06:03,982 were, DemandGen was buying Marketo, it was buying Eloqua, and There were no 108 00:06:04,282 --> 00:06:08,872 professional marketing operations folks, at least for most of the B2B companies. 109 00:06:09,542 --> 00:06:13,822 And because I had that technology experience in my past, like where I 110 00:06:13,822 --> 00:06:18,512 was a tech support, I ran sysadmin for Linux boxes and all sorts of things. 111 00:06:18,512 --> 00:06:21,952 I like that and I'm like, Oh, I can take that approach and 112 00:06:21,952 --> 00:06:23,332 apply it to this technology. 113 00:06:23,332 --> 00:06:23,552 So it's. 114 00:06:23,855 --> 00:06:26,254 more secure, more managed effectively. 115 00:06:26,369 --> 00:06:29,309 What we might call marketing operations, DevOps, or something like 116 00:06:29,309 --> 00:06:32,690 that today and put some discipline around it because no one else has that 117 00:06:32,690 --> 00:06:34,470 kind of unique set of experiences. 118 00:06:34,732 --> 00:06:36,232 Turned out some people did, which is great. 119 00:06:36,332 --> 00:06:38,195 But that's how it took it to the next level. 120 00:06:38,454 --> 00:06:40,794 but I want people to make sure they understand, like. 121 00:06:41,478 --> 00:06:44,148 IT style management of these technologies is important. 122 00:06:44,248 --> 00:06:45,358 I think you should master that. 123 00:06:46,008 --> 00:06:48,018 But that's not the same as product management. 124 00:06:48,291 --> 00:06:49,911 Justin Norris: And so that's where we want to go. 125 00:06:49,911 --> 00:06:54,352 And just before we do, you touched a little bit on the sort of scope and 126 00:06:54,352 --> 00:06:56,762 scale of some of the teams that you led. 127 00:06:56,912 --> 00:06:58,462 And I have a little bit of an inside. 128 00:06:58,782 --> 00:07:00,382 View here is we actually collaborated 129 00:07:00,792 --> 00:07:02,155 with myself as a consultant. 130 00:07:02,165 --> 00:07:02,965 you were my client. 131 00:07:02,965 --> 00:07:05,545 So I had a bit of a window into what you were doing. 132 00:07:05,574 --> 00:07:09,054 and it was a big operation that you ran, particularly at ring central, 133 00:07:09,054 --> 00:07:10,124 which is where we work together. 134 00:07:10,544 --> 00:07:13,494 A big team, lots of people, lots of complexity. 135 00:07:13,964 --> 00:07:14,464 it was huge. 136 00:07:14,474 --> 00:07:17,234 Can you just give a sense of like the operation that you had there? 137 00:07:17,687 --> 00:07:24,021 Josh Hill: So my team grew into more than 30 people around the world, four 138 00:07:24,021 --> 00:07:28,291 or five teams, depending on the quarter we were talking about where I did 139 00:07:28,291 --> 00:07:32,926 follow, you know, Aidan Thanks approach sort of naturally, but I became a 140 00:07:32,926 --> 00:07:34,236 little more aware of it later, right? 141 00:07:34,586 --> 00:07:36,366 And architecture system analysts. 142 00:07:36,911 --> 00:07:41,141 Not really programmers per se, but people who knew enough to do low to 143 00:07:41,141 --> 00:07:45,813 mid code kind of integration work and would ask the important questions about 144 00:07:45,813 --> 00:07:50,331 scale and ensure that there was a lot of cross functional and cross system. 145 00:07:50,876 --> 00:07:53,526 Work they would do things like BRDs. 146 00:07:53,686 --> 00:07:58,076 I mean everybody could but that's that was more of their focus There was demand 147 00:07:58,076 --> 00:08:02,639 gen systems and campaigns there's a front end development team and it was 148 00:08:02,639 --> 00:08:07,484 important to separate those because At least at RingCentral, the motion 149 00:08:07,684 --> 00:08:10,524 and the systems are very different for customers versus prospectors. 150 00:08:10,852 --> 00:08:12,992 How the campaigns were thought of were different. 151 00:08:13,451 --> 00:08:17,781 So you really had to understand each technology, each kind of data flow that 152 00:08:17,781 --> 00:08:19,751 was going on, and they were different. 153 00:08:20,159 --> 00:08:22,599 and that was only half of the marketing operations team. 154 00:08:23,164 --> 00:08:26,654 We had marketing data, we had DevOps, and that had a whole 155 00:08:26,654 --> 00:08:27,994 other set of things going on. 156 00:08:28,804 --> 00:08:33,426 We had project management and production management, which was also very important. 157 00:08:34,015 --> 00:08:37,279 And, people talk about those things as pillars, but I actually got the 158 00:08:37,279 --> 00:08:40,899 chance to practice it in real life and build those things with the team 159 00:08:40,899 --> 00:08:42,709 to support a large scale system. 160 00:08:43,299 --> 00:08:47,773 And that led me to thinking about, how do you do this at a very large scale? 161 00:08:48,016 --> 00:08:50,286 you know, you were the person introduced us to a lot of other 162 00:08:50,286 --> 00:08:52,604 tools as well, so thank you for that. 163 00:08:53,109 --> 00:08:54,259 Justin Norris: Oh glad to have done it. 164 00:08:54,339 --> 00:08:58,908 So thinking then about this product management approach, maybe just 165 00:08:58,908 --> 00:09:02,148 a definition, like how do you definitionally think about it? 166 00:09:02,170 --> 00:09:02,963 what does it mean? 167 00:09:02,973 --> 00:09:04,967 And was it something that you applied? 168 00:09:05,402 --> 00:09:08,372 Back then, or is it something kind of just retrospectively looking back? 169 00:09:08,432 --> 00:09:11,610 You're like this is the way that I would do it if I was to build That work again. 170 00:09:12,255 --> 00:09:12,605 Josh Hill: I did. 171 00:09:12,605 --> 00:09:13,145 And I did. 172 00:09:13,465 --> 00:09:13,805 Right. 173 00:09:14,065 --> 00:09:18,575 You know, when I think about products, you know, I've been working with software 174 00:09:18,585 --> 00:09:24,405 building software or ecosystems for a long time, and I would always think about, 175 00:09:24,955 --> 00:09:26,525 okay, well, how does this product work? 176 00:09:26,535 --> 00:09:28,265 How is it thinking about the world? 177 00:09:28,335 --> 00:09:31,235 And every product does have a point of view, forget who talked about it. 178 00:09:31,235 --> 00:09:32,535 Maybe it was Scott Brinker. 179 00:09:33,126 --> 00:09:36,554 And, Marketo had a point of view about how you handle B2B lead 180 00:09:36,554 --> 00:09:40,016 management, And how much of that influences your choice as a process. 181 00:09:40,096 --> 00:09:42,116 But getting back to your question, right? 182 00:09:42,536 --> 00:09:46,326 I love thinking about how customer service, how sales, how features, 183 00:09:47,015 --> 00:09:49,955 how other things work to integrate into a product experience. 184 00:09:50,215 --> 00:09:51,955 I wanted to be a product manager at one point. 185 00:09:52,555 --> 00:09:55,865 And, you know, on an amateur level, as you put it, right? 186 00:09:55,955 --> 00:09:58,005 Like, I think about these things daily, right? 187 00:09:58,005 --> 00:09:58,725 I would talk with Marketo. 188 00:10:02,445 --> 00:10:04,785 I think the product should work this way, right? 189 00:10:05,085 --> 00:10:06,665 It's not solving my actual problem. 190 00:10:06,685 --> 00:10:09,845 How do I solve my actual problem in the hope that they 191 00:10:09,845 --> 00:10:10,805 would put that on the roadmap? 192 00:10:10,845 --> 00:10:14,576 And sometimes they did, And what's interesting is that when I started 193 00:10:14,586 --> 00:10:18,596 diving into understanding what a product manager does, as it's defined, 194 00:10:18,596 --> 00:10:21,706 you know, in the software world, pMs think about the same things 195 00:10:21,706 --> 00:10:23,116 that marketing ops pros think about. 196 00:10:23,116 --> 00:10:27,663 They're at this intersection of business, customer experience approval 197 00:10:27,663 --> 00:10:32,243 processes, feature development, BRDs, product requirement documents. 198 00:10:32,903 --> 00:10:34,523 So it's all of these things. 199 00:10:35,268 --> 00:10:38,418 The only other discipline that really works on that is marketing operations 200 00:10:38,588 --> 00:10:42,788 or rev ops, or even to some degree sales operations where all of these 201 00:10:43,288 --> 00:10:48,231 threads come together to build something So with marketing operations, we're 202 00:10:48,231 --> 00:10:52,471 building typically products around like an event experience or a lead flow. 203 00:10:52,566 --> 00:10:57,076 Experience or internal sales product experience, right? 204 00:10:57,623 --> 00:11:00,103 So it can be a little bit different because it's more internal typically, 205 00:11:00,103 --> 00:11:03,963 but we're always thinking about the outside world and asking marketers. 206 00:11:03,963 --> 00:11:09,973 Hey, are you sure you want that form that way and building frameworks to help? 207 00:11:10,357 --> 00:11:14,992 Get those requirements and those experiences built, And this really didn't 208 00:11:14,992 --> 00:11:19,857 come up as a crystallized thought until a VP brought it up from a very large 209 00:11:19,857 --> 00:11:25,017 organization, like super large and comes by and he says, I want to bring in a 210 00:11:25,017 --> 00:11:26,767 product manager for marketing technology. 211 00:11:27,187 --> 00:11:29,350 We need strategy and. 212 00:11:29,836 --> 00:11:32,076 That was a little surprising because I thought we had strategy. 213 00:11:32,536 --> 00:11:36,906 But it did get me thinking about, okay, well, why is he saying this? 214 00:11:36,906 --> 00:11:37,106 Right? 215 00:11:37,106 --> 00:11:39,276 What is a product management approach doing that's 216 00:11:39,386 --> 00:11:40,456 different than what I'm doing? 217 00:11:41,281 --> 00:11:44,251 there are some differences, but there are a lot of similarities. 218 00:11:44,871 --> 00:11:47,351 So over the last couple of years, I've been researching that and kind of 219 00:11:47,351 --> 00:11:49,212 understanding, how are they different? 220 00:11:49,212 --> 00:11:49,772 How are they not? 221 00:11:49,792 --> 00:11:51,032 Do they just talk differently? 222 00:11:51,452 --> 00:11:52,572 But it's doing the same thing? 223 00:11:52,632 --> 00:11:54,042 And largely, yes. 224 00:11:54,702 --> 00:11:59,295 If you ask ChatGPT or the internet, you know, what does a product manager do? 225 00:11:59,295 --> 00:12:02,050 It's going to give you something mild, like, well, it's responsible 226 00:12:02,050 --> 00:12:03,650 for developing and managing products. 227 00:12:04,210 --> 00:12:04,700 Okay. 228 00:12:05,080 --> 00:12:08,010 Marketing operations focuses on executing marketing strategies and 229 00:12:08,010 --> 00:12:09,630 optimizing marketing processes. 230 00:12:10,185 --> 00:12:12,975 not very helpful, and it's kind of incomplete, but it's also true. 231 00:12:13,386 --> 00:12:14,136 in many ways. 232 00:12:14,136 --> 00:12:15,536 It's a messaging question. 233 00:12:15,976 --> 00:12:18,779 So when I think about marketing operations, we're often at the bleeding 234 00:12:18,779 --> 00:12:24,809 edge of a business of marketing, making an experience come to life for 235 00:12:24,809 --> 00:12:28,819 a marketer for a customer, Whether it's in campaign operations or architecture, 236 00:12:28,819 --> 00:12:31,239 you're kind of trying to figure out How does the rubber meet the road? 237 00:12:32,019 --> 00:12:33,659 And guess what? 238 00:12:33,669 --> 00:12:37,049 Product managers do the same thing, but they don't talk 239 00:12:37,059 --> 00:12:38,289 about it exactly the same way. 240 00:12:39,267 --> 00:12:43,107 Justin Norris: So is it about in some cases just adopting a product 241 00:12:43,107 --> 00:12:46,127 management lexicon, like instead of saying like, Hey, I have a request, 242 00:12:46,127 --> 00:12:49,107 say, all right, well, this is a feature and I'm going to put it in my roadmap 243 00:12:49,167 --> 00:12:50,707 and we'll develop it in sprints. 244 00:12:50,707 --> 00:12:53,529 And, you know, just adopting that terminology, or is there 245 00:12:53,549 --> 00:12:54,839 something more fundamental? 246 00:12:55,479 --> 00:12:59,299 At the root of how you think about what you're doing that comes with 247 00:12:59,359 --> 00:13:00,649 the product management approach. 248 00:13:01,537 --> 00:13:02,267 Josh Hill: You can do that. 249 00:13:02,307 --> 00:13:05,078 I suspect a lot of us already are doing that. 250 00:13:05,369 --> 00:13:07,419 So what does a PM do, right? 251 00:13:08,598 --> 00:13:12,208 it's probably familiar to people who are particularly marketing technology 252 00:13:12,228 --> 00:13:16,614 architects or more experienced pros You're aligning experiences to the 253 00:13:16,614 --> 00:13:20,504 mission or the customer experience you're enforcing product boundaries 254 00:13:20,504 --> 00:13:23,904 or against a strategy Are we going to do something or not do something? 255 00:13:23,904 --> 00:13:24,044 Right? 256 00:13:24,044 --> 00:13:24,754 How do we treat? 257 00:13:25,029 --> 00:13:27,559 Our customers, whether it's internally or externally. 258 00:13:28,079 --> 00:13:31,509 And sometimes you have to think about both in marketing operations, right? 259 00:13:31,569 --> 00:13:37,629 I'm building a privacy product to capture opt ins and help speak in compliance. 260 00:13:37,639 --> 00:13:41,579 How does that whole end to end process work from the branded page and 261 00:13:41,579 --> 00:13:46,874 interaction that an actual customer or non customer has down to how do we use it? 262 00:13:47,164 --> 00:13:50,984 Inside our internal systems, you know, how do we get all the approvals for that? 263 00:13:51,248 --> 00:13:55,318 And we build products with customers with engineers, We manage all the 264 00:13:55,318 --> 00:13:59,508 stakeholders involved from, you know, vps your day to day stakeholders Whoever's 265 00:13:59,538 --> 00:14:03,281 asking for a feature, Someone comes to me and says hey, I want To send 266 00:14:03,281 --> 00:14:07,699 gifts to our prospects or our customers for some reason Yeah, we can bring in 267 00:14:07,699 --> 00:14:12,062 a vendor do that, but that workflow that goes around it, that's a product, 268 00:14:12,526 --> 00:14:14,806 How we use that vendor is a product. 269 00:14:15,570 --> 00:14:17,590 And like you said, we do build features, right? 270 00:14:17,620 --> 00:14:22,330 And that ideally is managed through a process with business requirements doc, or 271 00:14:22,920 --> 00:14:26,581 if you're going to be a product manager, it's a product requirement doc, They're 272 00:14:26,681 --> 00:14:28,741 not different, They all have user stories. 273 00:14:28,741 --> 00:14:29,841 They have jobs to be done. 274 00:14:29,981 --> 00:14:32,621 And some of us have borrowed from Agile and product management. 275 00:14:32,961 --> 00:14:35,621 Terminology to in our data to pay work. 276 00:14:35,661 --> 00:14:37,071 So you're probably already doing that. 277 00:14:38,011 --> 00:14:40,201 And I think it's really important to do that. 278 00:14:40,561 --> 00:14:44,858 If you're going to do an RFP, if you're creating a new workflow, which a workflow 279 00:14:44,878 --> 00:14:48,228 can be a product, you know, if you're delivering specifications to engineers. 280 00:14:48,853 --> 00:14:51,393 You're creating wireframes and experience workloads. 281 00:14:51,403 --> 00:14:53,673 You're doing UX and creative on your team, right? 282 00:14:53,723 --> 00:14:54,923 I have a front end development team. 283 00:14:55,593 --> 00:14:56,693 What did we talk about a lot? 284 00:14:56,837 --> 00:15:00,648 The user experience, We had to build wireframes for certain situations. 285 00:15:01,158 --> 00:15:05,148 You know, how do we create capabilities for a marketer or for our customers 286 00:15:05,188 --> 00:15:08,873 or our users to do something, Did we get the requirements right for that? 287 00:15:09,343 --> 00:15:13,083 Did we build a minimum viable product, which a lot of us use that terminology? 288 00:15:13,890 --> 00:15:17,530 We do testing, UAT, launch decision points, feedback loops. 289 00:15:17,540 --> 00:15:19,290 So you're already doing all these things. 290 00:15:19,850 --> 00:15:21,210 Now, there is a difference though. 291 00:15:21,874 --> 00:15:25,134 Product managers, marketing operations folks, we are interdisciplinary. 292 00:15:25,326 --> 00:15:29,456 We're at this intersection of business, marketing, demand gen, sales, user 293 00:15:29,456 --> 00:15:32,265 experience, UI, front end development. 294 00:15:32,315 --> 00:15:35,085 We have to know the back end pretty well or back end enough. 295 00:15:35,485 --> 00:15:39,215 maybe we know some SQL and some Python, DNS, and email marketing. 296 00:15:39,745 --> 00:15:42,415 And that all goes into being a product manager, right? 297 00:15:42,435 --> 00:15:44,225 Understanding the customer life cycle. 298 00:15:44,922 --> 00:15:48,082 Now where I'd say there are some differences, not just in terminology, 299 00:15:48,082 --> 00:15:52,940 is Product managers sometimes say that they're the CEO of a product. 300 00:15:53,548 --> 00:15:55,468 Sometimes they don't like that, and that's a debate. 301 00:15:55,888 --> 00:16:00,528 But they are closer to understanding the business impact. 302 00:16:00,528 --> 00:16:04,578 They're trying to build a business, And they'll have core metrics, like 303 00:16:04,638 --> 00:16:07,458 a North Star metric or aha moments. 304 00:16:07,798 --> 00:16:10,918 And they're going to leverage product data and telemetry and build that in. 305 00:16:10,998 --> 00:16:15,570 And understand how people interact with the product and whether that 306 00:16:15,570 --> 00:16:19,498 feature is working delivering whatever it is they want, Like more 307 00:16:19,498 --> 00:16:20,888 and more usage typically, right? 308 00:16:21,144 --> 00:16:24,971 Slack users inviting more people from their organization 309 00:16:24,981 --> 00:16:26,191 or outside their organization? 310 00:16:26,856 --> 00:16:28,606 Marketing Ops doesn't really do that typically. 311 00:16:29,226 --> 00:16:32,606 Now you might, if you're saying like implementing You know, 312 00:16:32,606 --> 00:16:33,966 sales automation platform, right? 313 00:16:33,966 --> 00:16:35,676 Do people send out emails from it? 314 00:16:35,796 --> 00:16:36,756 Are they adopting it? 315 00:16:36,816 --> 00:16:40,736 And I've used that to help manage the martech stack, right? 316 00:16:40,736 --> 00:16:44,606 If someone's not adopting a product or something I built, maybe we 317 00:16:44,606 --> 00:16:46,476 should just continue it or change it. 318 00:16:47,016 --> 00:16:48,796 But we don't typically think of it in that way. 319 00:16:48,806 --> 00:16:50,341 And that, to me, that's the real difference. 320 00:16:50,381 --> 00:16:53,381 The monetization is the real difference between the two functions. 321 00:16:54,211 --> 00:16:56,021 Justin Norris: Well, you just said to me, it goes to the heart of 322 00:16:56,021 --> 00:17:02,361 the matter in terms of the role, the function, the orientation 323 00:17:02,601 --> 00:17:04,151 that marketing ops should have. 324 00:17:04,221 --> 00:17:09,580 And I agree with you that we typically don't do it as a discipline. 325 00:17:09,621 --> 00:17:12,261 Quite often we're getting these requests. 326 00:17:12,261 --> 00:17:14,171 And even when we're delivering them we're thinking about. 327 00:17:14,705 --> 00:17:17,047 what's the best way to deliver this architecturally? 328 00:17:17,057 --> 00:17:18,097 Is it going to be robust? 329 00:17:18,097 --> 00:17:19,207 Is it going to be scalable? 330 00:17:20,037 --> 00:17:22,577 What role do you think marketing ops should have? 331 00:17:22,676 --> 00:17:28,367 This is the big question for me in assessing the potential impact of that 332 00:17:28,367 --> 00:17:30,207 request, like, Hey, I know you want to. 333 00:17:30,887 --> 00:17:37,554 do chat bots that, you know, send AI enabled text messages and, gift baskets 334 00:17:37,584 --> 00:17:41,254 whenever somebody does X, Y, Z, but like, is this going to be a good idea? 335 00:17:41,254 --> 00:17:42,780 Is this going to be revenue impacting? 336 00:17:42,780 --> 00:17:43,610 In other words, should. 337 00:17:44,060 --> 00:17:48,280 Marketing ops, take some of that product oriented mindset of like really looking at 338 00:17:48,280 --> 00:17:53,440 the revenue impact of what they're working on and push back more against other teams. 339 00:17:53,879 --> 00:17:56,100 Josh Hill: so when we think about pushing back It can be done in 340 00:17:56,100 --> 00:17:57,800 different ways in different situations. 341 00:17:58,010 --> 00:18:03,547 I would think more about that in first thought, which is the ROI or the impact 342 00:18:03,617 --> 00:18:07,504 of the product you're going to build, so we're whether someone's asking you 343 00:18:07,504 --> 00:18:11,924 to build something or has a good idea or an idea about something, right? 344 00:18:12,404 --> 00:18:15,014 The first thing I want to do is understand that business requirement 345 00:18:15,494 --> 00:18:19,154 and Understand the complete workflow and experience they're trying to give 346 00:18:19,284 --> 00:18:22,994 either the internal person or the internal person and the customer, 347 00:18:23,794 --> 00:18:25,224 whether the customers pay it or not. 348 00:18:25,224 --> 00:18:31,738 And elicit that out and get it into workflow or wireframe, something that we 349 00:18:31,738 --> 00:18:36,393 can kind of be more tangible and reactive then understand, okay, well, if we did 350 00:18:36,393 --> 00:18:38,684 these things, what's The goal here, right? 351 00:18:38,684 --> 00:18:40,194 Do we want someone to fill out a form? 352 00:18:40,624 --> 00:18:40,994 Okay. 353 00:18:41,094 --> 00:18:42,084 What does that mean for us? 354 00:18:42,164 --> 00:18:42,664 Exactly. 355 00:18:42,834 --> 00:18:44,064 They're going to register for an event. 356 00:18:44,514 --> 00:18:47,294 And that's, you know, an obvious pipeline generation. 357 00:18:47,814 --> 00:18:50,584 Is it going to reduce costs greatly because we automated 358 00:18:50,584 --> 00:18:53,054 something for us or our customers? 359 00:18:53,634 --> 00:18:57,284 Are we going to enable growth that could not be done before, like with 360 00:18:57,324 --> 00:18:59,604 a click to calendar solution, right? 361 00:18:59,604 --> 00:19:02,864 Where supposedly will reduce friction in the meeting process. 362 00:19:03,035 --> 00:19:06,883 Increase our number of meetings that we get per day, and therefore that 363 00:19:06,883 --> 00:19:08,803 should be to an expected revenue. 364 00:19:08,813 --> 00:19:12,273 That's a lot higher, And that's the kind of question you need to really ask, 365 00:19:12,411 --> 00:19:17,119 especially when you're prioritizing work is I need an ROI metric in order to have 366 00:19:17,189 --> 00:19:22,069 a conversation and to show you where this project is going to live in the queue. 367 00:19:22,750 --> 00:19:26,650 I always love working on win back products because there was a clear connection 368 00:19:26,650 --> 00:19:28,160 between what I did and the revenue. 369 00:19:28,476 --> 00:19:30,996 If you're going to create a chatbot, which is another one of my favorites 370 00:19:31,006 --> 00:19:34,910 is that typically doesn't have a connection between building the 371 00:19:34,910 --> 00:19:37,740 product and delivering revenue because you're getting someone to sales or 372 00:19:37,770 --> 00:19:39,320 getting someone to customer service. 373 00:19:39,780 --> 00:19:43,260 And increase an MPS score or getting an upsell opportunity, whatever that is. 374 00:19:43,980 --> 00:19:47,670 And I built those products, And in many ways, it was managed like a product, 375 00:19:47,780 --> 00:19:49,520 even if we didn't talk about it that way. 376 00:19:50,219 --> 00:19:54,959 But there are other things like, oh, you know, building a CDP or, you know, 377 00:19:54,959 --> 00:19:57,809 we're going to create a process that's going to reduce costs or something. 378 00:19:57,849 --> 00:20:00,899 You have to really think through the implication of that 379 00:20:00,909 --> 00:20:03,129 build to the business, right? 380 00:20:03,199 --> 00:20:07,040 So theoretically, a CDP could create some self service opportunities, 381 00:20:07,040 --> 00:20:09,540 although that I think is overblown. 382 00:20:10,142 --> 00:20:15,382 It could unify enough of our data and identifiers to better personalize 383 00:20:15,412 --> 00:20:19,874 the product experience or the website so that Theoretically, at 384 00:20:19,904 --> 00:20:22,604 least that will increase the number of conversions through the funnel. 385 00:20:23,092 --> 00:20:24,362 And that has an impact on revenue. 386 00:20:24,502 --> 00:20:27,362 So you can definitely tie it back, but you need to think through that. 387 00:20:27,372 --> 00:20:31,602 And like you said, that hasn't always been an obvious thing 388 00:20:31,602 --> 00:20:32,902 for marketing operations to do. 389 00:20:33,732 --> 00:20:36,690 But as I talked about in a couple of presentations, I did on building a 390 00:20:36,690 --> 00:20:39,150 business case, you do have to do that. 391 00:20:39,210 --> 00:20:44,400 And that's where the pushback happens is you have to ensure that your stakeholders 392 00:20:44,400 --> 00:20:45,810 are helping you build that business case. 393 00:20:45,984 --> 00:20:49,282 typically Moss is not the business owner, We might be the technical 394 00:20:49,282 --> 00:20:53,502 owner, but if you don't have a business partner who is on the hook for 395 00:20:53,844 --> 00:20:58,174 delivering dollars from something you build, then you're just building stuff. 396 00:20:58,450 --> 00:20:59,190 Maybe it gets used. 397 00:20:59,200 --> 00:20:59,790 Maybe it works. 398 00:20:59,790 --> 00:21:00,360 Maybe it doesn't. 399 00:21:00,960 --> 00:21:03,010 You should never have tools that don't have a business owner 400 00:21:03,480 --> 00:21:03,572 Justin Norris: And 401 00:21:03,572 --> 00:21:09,095 about that relationship between, mops and the teams we support in my little 402 00:21:09,095 --> 00:21:13,835 intro I kind of presented a straw man vision of, you know, a few different ways 403 00:21:13,835 --> 00:21:15,575 that relationship could be structured. 404 00:21:15,605 --> 00:21:17,005 They were based on reality though. 405 00:21:17,005 --> 00:21:18,135 I think a lot of the teams. 406 00:21:18,680 --> 00:21:21,030 Do find themselves in a position where they're getting handed a 407 00:21:21,030 --> 00:21:23,550 list of priorities and like, here's the things we need you to do. 408 00:21:23,890 --> 00:21:25,460 Here's the tools we want you to implement. 409 00:21:25,850 --> 00:21:28,850 that's not a great place to be, not just for ops, but it's not good for 410 00:21:28,850 --> 00:21:32,060 the business because there isn't any of that pushback and I think on the flip 411 00:21:32,060 --> 00:21:35,300 side, and I've seen this more in an enterprise setting, maybe you have two 412 00:21:35,710 --> 00:21:42,460 where you have a team that's built such a huge kind of a moat around themselves. 413 00:21:42,870 --> 00:21:46,730 But everything is just like, no, or, Oh, it'll be on the roadmap in a year. 414 00:21:47,210 --> 00:21:51,330 And they just seem completely unresponsive to needs of the business. 415 00:21:51,330 --> 00:21:54,000 I think I, I've seen this probably more with CRM teams than with 416 00:21:54,000 --> 00:21:55,630 marketing ops teams, but sorry to 417 00:21:55,630 --> 00:21:59,499 say that CRM teams and at that point you end up with like shadow it or 418 00:21:59,499 --> 00:22:03,321 people hiring their own, external consultants ,how do you think about 419 00:22:03,371 --> 00:22:08,387 the types of approaches that are out there and how to move from one polarity 420 00:22:08,417 --> 00:22:12,447 or the other towards this, what I would think of as a more balanced approach, 421 00:22:12,447 --> 00:22:15,712 you know, where it's more of a true partnership delivering on business 422 00:22:15,717 --> 00:22:17,567 outcomes versus a power struggle. 423 00:22:18,145 --> 00:22:20,455 Josh Hill: Well, ideally, that's, the leadership. 424 00:22:21,520 --> 00:22:25,191 Saying the right thing, And I've seen this too, in many organizations, right? 425 00:22:25,191 --> 00:22:31,877 Where you get the hippo or what I call the VP stomp, where you got to do something. 426 00:22:32,563 --> 00:22:38,614 no explanation, no discussion, no, review of, best options to achieve that goal. 427 00:22:38,784 --> 00:22:42,384 Maybe not even a discussion of what that goal really is, in some case. 428 00:22:43,024 --> 00:22:45,897 there was someone who posted Something with that thought the other day on 429 00:22:45,897 --> 00:22:49,825 LinkedIn where they were very much like, Mops is the saying no to me and they were 430 00:22:49,825 --> 00:22:54,790 very upset about this And I really wanted to push back on that person because I it 431 00:22:54,810 --> 00:23:00,554 felt like every conversation with someone who hasn't taken the time to explain what 432 00:23:00,554 --> 00:23:04,165 they want to achieve It's like, I didn't say no, I'm thinking about your problem. 433 00:23:04,479 --> 00:23:07,319 And that often gets interpreted as no, because I didn't do 434 00:23:07,319 --> 00:23:08,299 it in the last five minutes. 435 00:23:10,729 --> 00:23:13,399 these things don't happen in five minutes, usually. 436 00:23:13,930 --> 00:23:17,110 Or even 30 minutes, and it really depends what it is you're trying to achieve. 437 00:23:17,110 --> 00:23:19,820 And that's what, you know, I built the journey doc process for the 438 00:23:19,970 --> 00:23:21,570 business requirements doc process. 439 00:23:21,570 --> 00:23:24,810 It feels slow to people who just want it now. 440 00:23:25,690 --> 00:23:29,180 And the reason that process exists is to ensure we're actually delivering 441 00:23:29,190 --> 00:23:33,920 what you want and what you really want and understanding that so that we don't 442 00:23:33,940 --> 00:23:38,382 show up with a product or a hack that actually didn't deliver anything because 443 00:23:38,412 --> 00:23:42,373 that has definitely happened before, or everyone misunderstands each other. 444 00:23:42,373 --> 00:23:43,163 It's a way to. 445 00:23:43,239 --> 00:23:48,669 Avoid misunderstandings and any product manager will have the same problem, Where 446 00:23:48,669 --> 00:23:51,969 they get ideas from customers, or they're trying to solve a customer problem. 447 00:23:51,969 --> 00:23:58,040 They build a purity and they're trying to explain it to the engineers who 448 00:23:58,050 --> 00:24:00,460 are already working on their road map, or they have their own ideas. 449 00:24:00,990 --> 00:24:05,160 And that's fine, or they might have a better way of solving it, but is it 450 00:24:05,190 --> 00:24:07,420 actually solving the customer problem? 451 00:24:07,420 --> 00:24:09,160 Or is it how they think about the customer problem? 452 00:24:10,130 --> 00:24:12,120 And then you get conflicts in the prioritization. 453 00:24:12,950 --> 00:24:15,390 And that's really what, one of the things I actually kind of learned very 454 00:24:15,490 --> 00:24:21,902 clearly from product management interview videos is you always have to connect 455 00:24:21,902 --> 00:24:25,738 back what you're doing to the strategy of the company and the product, you 456 00:24:25,738 --> 00:24:27,328 know, it feels a little business Casey. 457 00:24:28,203 --> 00:24:30,323 Which is fine, but it makes a good point, right? 458 00:24:30,353 --> 00:24:36,418 Like, if we're loading a product at, let's just say, Emails 10 million people 459 00:24:36,418 --> 00:24:38,568 a day to try to get them to respond. 460 00:24:39,348 --> 00:24:44,238 But our whole strategy and customer branding is about being nice 461 00:24:44,238 --> 00:24:47,860 to people and treating people well, for whatever reason, right? 462 00:24:47,860 --> 00:24:50,090 I'm just kind of making up a business strategy. 463 00:24:50,680 --> 00:24:53,620 And we have that branding, but we don't treat people that way, right? 464 00:24:53,620 --> 00:24:56,790 We're going to have a big mismatch in how people. 465 00:24:57,145 --> 00:25:01,965 Perceive us, and we're probably going to hurt our brand and product 466 00:25:01,965 --> 00:25:06,405 manager, marketing ops professional with some experience is going to 467 00:25:06,425 --> 00:25:09,921 often say like, Hey, this doesn't feel brand aligned, Are you sure 468 00:25:09,921 --> 00:25:11,121 you want to treat people this way? 469 00:25:11,701 --> 00:25:14,891 Are you sure that image you're giving us is not brand aligned? 470 00:25:15,311 --> 00:25:17,971 Because we see everything that comes through the queue, and we're going 471 00:25:17,971 --> 00:25:21,421 to push it back to creative or ask you to get a different approval. 472 00:25:21,491 --> 00:25:25,211 And those processes exist to protect us in the company from making it. 473 00:25:25,551 --> 00:25:26,471 A big mistake. 474 00:25:27,011 --> 00:25:28,721 But, we could build anything you want. 475 00:25:28,781 --> 00:25:33,051 It's just, is that really the best thing to do for us for the customer? 476 00:25:33,723 --> 00:25:37,873 when I think about product management, when I think about the CRM team, when 477 00:25:37,873 --> 00:25:42,178 I think about marketing ops does the CRM team, the enterprise applications 478 00:25:42,178 --> 00:25:45,998 teams They get into difficult situations because if they pull out the Jenga 479 00:25:45,998 --> 00:25:48,738 piece, it can break critical processes. 480 00:25:48,998 --> 00:25:54,468 And especially if you're a public company, you have SOX compliance, you have impact 481 00:25:54,508 --> 00:25:59,375 to street numbers, you cannot do that, You do not break things like that. 482 00:25:59,847 --> 00:26:03,978 I mean, I've seen people ask for a field where, for whatever reason, 483 00:26:04,132 --> 00:26:09,187 the CRM team just does it and 10, 000 ops get deleted or get closed 484 00:26:09,187 --> 00:26:10,867 out without proper procedures. 485 00:26:10,907 --> 00:26:14,377 And then everything blows up in the emergency slack channels. 486 00:26:14,853 --> 00:26:16,843 And I'm not saying that happened to any particular company, but 487 00:26:16,843 --> 00:26:18,253 I've seen and heard things, right? 488 00:26:18,793 --> 00:26:24,133 Well, that's because a process got bypassed, So when I built an SMS product, 489 00:26:24,503 --> 00:26:27,813 and my architect did the hard work, so I give her credit for that one. 490 00:26:28,292 --> 00:26:29,462 We designed everything out. 491 00:26:29,643 --> 00:26:30,683 How do we treat people? 492 00:26:30,771 --> 00:26:32,511 When should this happen in the process? 493 00:26:32,521 --> 00:26:37,200 How do we do an MVP so we don't just spam everybody who could get an SMS? 494 00:26:37,230 --> 00:26:40,230 How do we even know if this person has a cell phone, if 495 00:26:40,230 --> 00:26:41,370 this is a cell phone number? 496 00:26:41,880 --> 00:26:45,440 Did we run this by the privacy team who actually had a lot 497 00:26:45,440 --> 00:26:46,600 of good advice about that? 498 00:26:47,266 --> 00:26:48,796 And then we could launch it and test it. 499 00:26:48,866 --> 00:26:54,421 And, oh, by the way, we came up against regulatory issues and maybe we can't 500 00:26:54,421 --> 00:26:58,190 do the SMS product for a while because we have to get certain other approvals. 501 00:26:58,190 --> 00:26:58,410 Right. 502 00:26:58,410 --> 00:27:01,930 And the environment changed product teams, product managers come against 503 00:27:01,930 --> 00:27:03,020 the same problem all the time. 504 00:27:03,578 --> 00:27:08,148 So I don't like it when people say, Oh, that team is saying no, it's 505 00:27:08,508 --> 00:27:11,578 they're trying to protect themselves because they got burned or the 506 00:27:11,578 --> 00:27:12,648 company is going to get burned. 507 00:27:12,988 --> 00:27:19,038 So it's up to escalation process to prioritization should be and try to, 508 00:27:19,268 --> 00:27:21,398 as some people would say, breakthrough. 509 00:27:21,428 --> 00:27:23,198 But I would say it's more about. 510 00:27:23,364 --> 00:27:27,043 If you need to escalate something, to me that tells us that there are 511 00:27:27,043 --> 00:27:31,683 conflicting priorities, again, across the silos, but they're also not a clear 512 00:27:31,683 --> 00:27:36,063 understanding of the strategy that could help us build a rubric or an ROI 513 00:27:36,063 --> 00:27:37,653 metric around should we be doing this 514 00:27:38,388 --> 00:27:40,922 Justin Norris: when you think about that difficult conversation that you're 515 00:27:40,922 --> 00:27:43,878 describing, you know, the stakeholder that feels you're saying no, you're trying 516 00:27:43,878 --> 00:27:48,278 to understand, you know, the job of the product manager, broadly speaking, is 517 00:27:48,318 --> 00:27:54,428 to solve for the needs of the customer, you could say, in this context, who is 518 00:27:54,678 --> 00:28:00,718 your customer, is it the end customer that you're trying to sell to and serve? 519 00:28:00,788 --> 00:28:03,758 And so you're looking at it through is what we're trying to do here. 520 00:28:04,118 --> 00:28:08,808 Serving that person or is the customer, the internal stakeholder 521 00:28:09,128 --> 00:28:12,478 who you're saying, you know, as long as I deliver the needs for them and 522 00:28:12,478 --> 00:28:16,118 they get what they want, whether it ultimately serves the needs of that 523 00:28:16,118 --> 00:28:17,758 end customer, you know, is up to them. 524 00:28:17,768 --> 00:28:21,248 And I, I've heard arguments and I can see pros and cons of both points of view. 525 00:28:21,288 --> 00:28:23,558 I'm curious where you land on that question. 526 00:28:24,238 --> 00:28:26,128 Josh Hill: Well it depends right? 527 00:28:26,788 --> 00:28:28,228 Like, what are we building, right? 528 00:28:28,228 --> 00:28:31,428 So if I'm building self-service segmentation tool. 529 00:28:32,213 --> 00:28:36,548 That's typically an internal product I don't have to worry or think through a lot 530 00:28:36,548 --> 00:28:40,668 of the customer impacts other than maybe like ensuring that we have certain privacy 531 00:28:40,668 --> 00:28:43,570 rules around it or communication limits. 532 00:28:43,620 --> 00:28:48,133 For example, I have to worry about did I understand the goal and is 533 00:28:48,133 --> 00:28:49,253 it actually going to deliver that? 534 00:28:49,283 --> 00:28:51,903 And is it easy to use? 535 00:28:51,903 --> 00:28:53,063 Is that one of the requirements? 536 00:28:53,093 --> 00:28:54,083 Or do you need a sequel? 537 00:28:54,306 --> 00:28:57,546 I would assume in a self service situation you would want to have right 538 00:28:58,781 --> 00:29:02,091 As little code as possible in order for a natural understanding of how 539 00:29:02,091 --> 00:29:06,581 someone would think about a segmentation and how to enable them to do it. 540 00:29:06,611 --> 00:29:09,581 And you might have an MVP and you might build out additional things. 541 00:29:09,621 --> 00:29:10,421 And I've done that. 542 00:29:11,338 --> 00:29:16,748 And the more difficult conversations tend to be someone wants it now and didn't 543 00:29:16,748 --> 00:29:20,768 talk to you ahead of time and think through their entire process and you try 544 00:29:20,768 --> 00:29:23,668 to bring them through the requirements process just to really understand 545 00:29:23,668 --> 00:29:25,018 what are we trying to achieve, right? 546 00:29:25,118 --> 00:29:26,428 Get them to explain themselves. 547 00:29:26,726 --> 00:29:28,404 And they don't always love that. 548 00:29:28,434 --> 00:29:29,324 But sometimes people. 549 00:29:29,829 --> 00:29:35,116 Warm up to the process, especially if you deliver and other times it's been okay. 550 00:29:35,346 --> 00:29:39,672 This is an internal and an external impact, I always think of events or 551 00:29:39,672 --> 00:29:43,942 privacy in that sense, because they often have internal processes and procedures. 552 00:29:44,627 --> 00:29:47,557 That we need to build out for and there's customer experience impacts. 553 00:29:48,177 --> 00:29:52,557 So we don't have certain privacy operationalized that could impact 554 00:29:52,557 --> 00:29:56,487 the customer in negative ways, or as well as the company in negative ways. 555 00:29:56,487 --> 00:30:01,546 And people don't love it when you bring up potential hurdles, but these are all 556 00:30:01,596 --> 00:30:03,176 things we can just make decisions on. 557 00:30:03,186 --> 00:30:07,436 These aren't inherently hurdles unless you want to do something that's just illegal. 558 00:30:08,028 --> 00:30:09,618 okay, you want to build a CDP. 559 00:30:09,648 --> 00:30:10,818 Here's what it's going to take. 560 00:30:11,037 --> 00:30:14,147 We can either stop doing these things, or we can hire an agency or hire a 561 00:30:14,147 --> 00:30:16,455 team to get it started or launched. 562 00:30:16,646 --> 00:30:18,006 Do we have the right business case for that? 563 00:30:18,126 --> 00:30:19,136 And working with them. 564 00:30:19,136 --> 00:30:22,236 And I've had great partnerships with many stakeholders about building that 565 00:30:22,236 --> 00:30:26,046 business case to be effective and either making a decision like, yeah, That's 566 00:30:26,066 --> 00:30:27,406 probably not going to have an ROI. 567 00:30:27,446 --> 00:30:28,736 Maybe we should forget about that. 568 00:30:29,406 --> 00:30:33,056 Or yeah, this does have a great ROI and it's going to pass all of 569 00:30:33,056 --> 00:30:37,676 our IT procurement and financial teams with flying colors. 570 00:30:38,899 --> 00:30:43,148 Justin Norris: That ROI question, can be troubling because I think CDP 571 00:30:43,148 --> 00:30:47,678 or self service segmentation project that you described is a good example. 572 00:30:48,068 --> 00:30:51,778 You could have a model project in the sense that you work with your stakeholder, 573 00:30:51,868 --> 00:30:56,808 you define their requirements, you deliver it, it works well, it's scalable. 574 00:30:57,648 --> 00:31:00,885 And then the other question is, as a result of having that capability, 575 00:31:00,885 --> 00:31:04,965 were they actually able to send better communications that produced more revenue? 576 00:31:05,035 --> 00:31:07,265 So it's like the project was successful on one side, but then 577 00:31:07,315 --> 00:31:09,145 did it ultimately meet its goal? 578 00:31:09,145 --> 00:31:10,495 The goal that the marketer had. 579 00:31:11,205 --> 00:31:12,555 Do you need to care about that? 580 00:31:12,565 --> 00:31:16,695 Or is there a certain size at scale of company at which point the separation of 581 00:31:16,695 --> 00:31:19,045 powers is such that you just can't really. 582 00:31:19,930 --> 00:31:22,000 Have that conversation effectively anymore. 583 00:31:23,153 --> 00:31:23,513 Josh Hill: yes. 584 00:31:24,743 --> 00:31:29,251 So one of the things I had in my presentation I talked about is I 585 00:31:29,251 --> 00:31:31,071 can make a growth estimate, right? 586 00:31:31,199 --> 00:31:34,620 Having a meeting tool is going to likely get us 25 percent more 587 00:31:34,620 --> 00:31:37,520 meetings and that'll justify the cost of this tool and implementation. 588 00:31:38,193 --> 00:31:43,086 And ideally, you've built in a process and a set of metrics and you've captured 589 00:31:43,086 --> 00:31:47,236 that data so that in a month, two months, six months from now, you can actually 590 00:31:47,236 --> 00:31:51,627 compare before and after and say, yep, we achieved that or Nope, we didn't. 591 00:31:51,899 --> 00:31:56,012 And ideally, you can make a harder call and say, okay, well, we didn't achieve the 592 00:31:56,012 --> 00:31:58,322 goal, but it's still paying for itself. 593 00:31:58,602 --> 00:32:01,082 Okay, let's investigate how we can increase it. 594 00:32:01,582 --> 00:32:03,562 Or it's completely not doing anything. 595 00:32:03,975 --> 00:32:04,805 Do we cancel it? 596 00:32:05,435 --> 00:32:06,735 The sales squeal about it. 597 00:32:07,155 --> 00:32:08,195 Can we just keep it there? 598 00:32:08,935 --> 00:32:10,385 That's a little squishier goal. 599 00:32:10,385 --> 00:32:13,715 I tend to be a little harsher and say like, well, I didn't achieve the goal. 600 00:32:13,715 --> 00:32:15,085 Maybe we should stop spending money on it. 601 00:32:16,285 --> 00:32:16,975 And I've done that. 602 00:32:16,975 --> 00:32:19,086 we had a potentially great idea. 603 00:32:19,378 --> 00:32:22,559 It's been a lot of time building it out with the vendor and 604 00:32:22,619 --> 00:32:24,039 they use 15 percent of it. 605 00:32:24,389 --> 00:32:28,215 And I asked the stakeholders, did this change anything? 606 00:32:28,455 --> 00:32:31,205 Did you achieve your adoption goal because of this product? 607 00:32:31,536 --> 00:32:32,906 And they said, nope, which is great. 608 00:32:33,116 --> 00:32:34,836 Sometimes they don't admit those things, right? 609 00:32:34,876 --> 00:32:36,274 They don't want to say that they were wrong. 610 00:32:36,834 --> 00:32:39,514 But data doesn't lie, which is nice, usually. 611 00:32:40,022 --> 00:32:41,502 So I said, okay, well, we're going to cancel it. 612 00:32:41,552 --> 00:32:42,282 And you know what happened? 613 00:32:42,282 --> 00:32:45,342 It turned out we could have built the same thing with VelocityScript if we had just 614 00:32:45,644 --> 00:32:50,084 Thought about it a little harder instead of rushing into it, that's where, You do 615 00:32:50,084 --> 00:32:53,994 have to kind of push back a little bit and think like what options do I really have? 616 00:32:54,255 --> 00:32:57,987 And could I have built an MVP for free rather than putting, you know, huge 617 00:32:57,987 --> 00:33:02,087 amount of effort and direct dollars into this I've also had other products where 618 00:33:02,777 --> 00:33:07,402 we did the segmentation thing and It wasn't really for hyper segmentation. 619 00:33:07,402 --> 00:33:08,972 Oh, that's a favorite topic of mine. 620 00:33:09,472 --> 00:33:15,362 It was just to try to speed the marketer to be at the keyboard and say, okay, how 621 00:33:15,362 --> 00:33:17,252 many people can I get for this invitation? 622 00:33:17,252 --> 00:33:21,982 For example instead of waiting for three or four days for a SQL expert 623 00:33:21,992 --> 00:33:26,082 data engineer to do this because of the various complexities and 624 00:33:26,601 --> 00:33:29,442 it didn't really get adopted and probably had two or three versions of 625 00:33:29,442 --> 00:33:32,552 that built because of poor adoption. 626 00:33:33,697 --> 00:33:36,257 we could debate what that was, but at some point, we kind of just stopped 627 00:33:36,257 --> 00:33:40,087 maintaining the product, and that's why we have the RDs and ROI analysis 628 00:33:40,087 --> 00:33:44,717 to try to figure out, is this really worth the effort and following 629 00:33:44,717 --> 00:33:47,817 up on that process to understand, did we actually achieve that goal? 630 00:33:48,517 --> 00:33:50,007 And sometimes you do, I mean, which is great, 631 00:33:50,563 --> 00:33:51,663 Justin Norris: hopefully more often than not. 632 00:33:51,826 --> 00:33:52,316 Josh Hill: Ideally. 633 00:33:52,336 --> 00:33:52,546 Yeah. 634 00:33:52,944 --> 00:33:55,564 Justin Norris: so you're constantly making these sorts of decisions, 635 00:33:55,794 --> 00:33:57,054 but they don't happen in a vacuum. 636 00:33:57,054 --> 00:34:02,255 Ideally with a product, you have a roadmap, a longer term plan, how long that 637 00:34:02,255 --> 00:34:07,375 can be, typically depending on the size of the company and how fast or slow it moves. 638 00:34:08,105 --> 00:34:11,114 How do you think about that process of building a roadmap? 639 00:34:11,165 --> 00:34:14,837 I know sometimes when I sit down with a blank page, you can be overwhelmed by 640 00:34:14,837 --> 00:34:18,237 the different possibilities and all the different things you could be doing. 641 00:34:18,237 --> 00:34:18,657 So how do you. 642 00:34:19,212 --> 00:34:20,081 bring structure to that 643 00:34:20,472 --> 00:34:23,931 Josh Hill: Well, roadmapping is also a product management technique 644 00:34:24,250 --> 00:34:25,630 as well as an IT technique. 645 00:34:25,659 --> 00:34:27,409 And it's very much the same former of mops. 646 00:34:27,420 --> 00:34:30,110 It's very much the same for a product or an enterprise apps team, right? 647 00:34:30,110 --> 00:34:31,159 What's the strategy of the org? 648 00:34:31,382 --> 00:34:34,123 And that should determine your priorities and generally your methodology. 649 00:34:34,206 --> 00:34:37,184 if that's not communicated effectively, then that's going to create a lot 650 00:34:37,184 --> 00:34:40,014 more conflicts across the organization because you don't have a rubric, 651 00:34:40,083 --> 00:34:45,110 you don't have an ROI base to make comparisons without escalation, And 652 00:34:45,110 --> 00:34:50,070 you want to have ROI prioritization so you minimize the impact of a HIPPO. 653 00:34:50,620 --> 00:34:54,328 And, of course, your feelings, Interview stakeholders and certainly bring your 654 00:34:54,328 --> 00:34:55,915 own opinions Look at the marketplace. 655 00:34:55,915 --> 00:34:59,825 Look at the strategy of the larger company and the other and your competitors. 656 00:34:59,895 --> 00:35:00,655 Ideally, right? 657 00:35:00,655 --> 00:35:01,265 What are they doing? 658 00:35:01,325 --> 00:35:02,425 Are they seeing success? 659 00:35:03,111 --> 00:35:06,131 And do that gap analysis of your capabilities versus where you think you 660 00:35:06,131 --> 00:35:09,840 want to go and where the marketers and sales team thinks they want to go, And 661 00:35:09,850 --> 00:35:12,020 map that back to your goals, your timing. 662 00:35:12,682 --> 00:35:15,252 And then, of course, always outcomes, right? 663 00:35:15,302 --> 00:35:16,452 Are we getting an ROI? 664 00:35:16,452 --> 00:35:17,932 And when are those milestones? 665 00:35:17,982 --> 00:35:19,912 And when should we actually achieve that ROI? 666 00:35:20,297 --> 00:35:22,357 And of course, you know, is that cost reduction? 667 00:35:22,357 --> 00:35:23,337 Is that a revenue gain? 668 00:35:23,337 --> 00:35:24,637 What's that total cost of ownership? 669 00:35:24,647 --> 00:35:27,289 Really kind of think through all those pieces, right? 670 00:35:27,289 --> 00:35:31,389 If we're going to build a CVP, do we have all of our other data ducks in a row? 671 00:35:31,489 --> 00:35:32,529 And what would that cost us? 672 00:35:33,309 --> 00:35:34,429 And what would that help us achieve? 673 00:35:34,761 --> 00:35:38,057 so if your overall strategy is we're going to have omni channel personalization. 674 00:35:38,987 --> 00:35:41,327 You're going to make different decisions in your roadmap to achieve that. 675 00:35:41,897 --> 00:35:44,327 If you're doing a PLG motion, you're going to have different 676 00:35:44,337 --> 00:35:45,737 decisions and milestones. 677 00:35:45,947 --> 00:35:50,377 If you're doing PLG plus SLG, you'll have different tools and different 678 00:35:50,377 --> 00:35:51,717 needs and different capabilities. 679 00:35:53,024 --> 00:35:54,234 Justin Norris: very tactically. 680 00:35:54,734 --> 00:35:57,414 How do you communicate what the roadmap is? 681 00:35:57,414 --> 00:35:59,871 Do you have, Google slide deck? 682 00:35:59,911 --> 00:36:02,259 Do you have a wiki page? 683 00:36:02,382 --> 00:36:06,009 Cause I find that's a big area of either concern or stress or frustration 684 00:36:06,009 --> 00:36:08,259 for stakeholders when they want something, but you're saying not 685 00:36:08,259 --> 00:36:10,269 right now, but then they're like, well, where does it sit in there? 686 00:36:10,279 --> 00:36:11,169 Like they kind of want. 687 00:36:11,544 --> 00:36:12,454 This visibility. 688 00:36:12,464 --> 00:36:13,454 How do you provide that? 689 00:36:14,352 --> 00:36:15,612 Josh Hill: It's about knowing your audience, You know, the 690 00:36:15,612 --> 00:36:18,632 technical schematic is generally for you and the IT team. 691 00:36:19,993 --> 00:36:22,233 I wouldn't show that to anyone typically outside. 692 00:36:22,783 --> 00:36:26,743 You know, your roadmap could also be missing something they asked for, and 693 00:36:26,743 --> 00:36:30,277 you could show them the roadmap and say, if you want this in the next six months, 694 00:36:30,337 --> 00:36:33,487 which is usually how long XYZ would take, we have to change the roadmap. 695 00:36:34,089 --> 00:36:36,199 And this is how we're gonna, how we could do that. 696 00:36:36,443 --> 00:36:40,043 I think educating marketers and salespeople about those 697 00:36:40,043 --> 00:36:41,573 capabilities is really important. 698 00:36:41,933 --> 00:36:44,513 If you're not doing that every quarter, they tend to forget and 699 00:36:44,513 --> 00:36:45,563 then they go off and buy something. 700 00:36:45,835 --> 00:36:47,865 And you're like, well, I could have done that for you in 10 minutes. 701 00:36:47,935 --> 00:36:48,985 Why did you go off and buy something? 702 00:36:49,825 --> 00:36:51,045 Oh, we didn't know. 703 00:36:51,315 --> 00:36:51,745 Too late. 704 00:36:52,448 --> 00:36:54,708 But you did know because it's on the wiki page. 705 00:36:55,228 --> 00:36:56,058 Well, they don't know that. 706 00:36:56,058 --> 00:36:57,263 They're not going to go look at that. 707 00:36:57,723 --> 00:36:57,953 Right? 708 00:36:57,993 --> 00:37:01,123 That's why, you know, procurement processes are important to try to 709 00:37:01,613 --> 00:37:03,603 catch them before they go too far. 710 00:37:04,183 --> 00:37:06,733 Yeah, I mean, a wiki page can help, a spreadsheet can help. 711 00:37:07,434 --> 00:37:12,624 Ideally, it's some sort of slider visual that explains capabilities possibly 712 00:37:12,624 --> 00:37:14,754 against the funnel or customer lifecycle. 713 00:37:15,914 --> 00:37:17,544 I've tried different versions of that. 714 00:37:18,269 --> 00:37:20,869 I don't think there's any one solution that works for every 715 00:37:20,869 --> 00:37:22,779 company in all situations. 716 00:37:23,379 --> 00:37:28,039 There was a really great set of slides and I don't think I downloaded it, but 717 00:37:28,099 --> 00:37:31,919 someone posted on LinkedIn and one of those little click things that slide 718 00:37:31,919 --> 00:37:33,689 through that you can't really download. 719 00:37:34,209 --> 00:37:37,269 And they were explaining how the PLGmotion can work. 720 00:37:37,899 --> 00:37:42,534 And it was kind of a very simple set of steps and it was in a multi 721 00:37:42,554 --> 00:37:44,694 slide version, which I thought was actually kind of helpful. 722 00:37:44,704 --> 00:37:45,409 I'm a little bit curious. 723 00:37:45,909 --> 00:37:46,559 The motion. 724 00:37:47,689 --> 00:37:52,876 And then here are increasingly detailed views of the kind of tool you would need 725 00:37:52,876 --> 00:37:58,258 to enable that part of the motion and that messaging, adding a sales motion to it. 726 00:37:58,537 --> 00:38:00,077 You know, where does your product fit into it? 727 00:38:00,097 --> 00:38:03,357 It doesn't have to describe your every database and our data flow, but it 728 00:38:03,357 --> 00:38:04,667 kind of generally described the motion. 729 00:38:05,347 --> 00:38:07,967 And I thought that was actually pretty helpful and was 730 00:38:07,977 --> 00:38:09,787 probably digestible by most. 731 00:38:10,382 --> 00:38:13,451 Senior leaders, but any sort of capability guy. 732 00:38:14,263 --> 00:38:19,171 I had a lot of different views as well as a giant deck it was part 733 00:38:19,171 --> 00:38:21,781 of our marketing enablement effort. 734 00:38:21,781 --> 00:38:25,134 And it you know, we had a wiki and we had an image, but I also had, you 735 00:38:25,134 --> 00:38:29,954 know, 200 slides explaining every tool we had and who used it, who owned it, 736 00:38:29,964 --> 00:38:32,814 who, why it was being used, what it could do Theoretically you could search 737 00:38:32,814 --> 00:38:34,564 that, did anybody really do that? 738 00:38:34,654 --> 00:38:35,144 I don't know. 739 00:38:35,669 --> 00:38:39,929 But it was a more helpful guide for my team because it showed everything and 740 00:38:39,939 --> 00:38:43,689 not just my team, but all the other teams that we worked with, you could see 741 00:38:43,689 --> 00:38:45,539 the whole ecosystem and capabilities. 742 00:38:46,661 --> 00:38:47,931 So I don't have a good answer for you. 743 00:38:47,961 --> 00:38:49,841 That's going to be the silver bullet. 744 00:38:51,176 --> 00:38:52,946 Justin Norris: No, I don't think it's universal. 745 00:38:52,986 --> 00:38:57,506 But it's yeah, having that something with the right level of detail that is 746 00:38:57,516 --> 00:39:01,916 accessible that gives people what they want, but that doesn't become you know, a 747 00:39:01,916 --> 00:39:05,851 homework assignment in and of itself that Sucks a lot of oxygen out of the room. 748 00:39:06,413 --> 00:39:07,793 Josh Hill: You know, if we're gonna bring it back to product management 749 00:39:07,833 --> 00:39:11,303 for a moment, like these things are always living documents, right? 750 00:39:11,303 --> 00:39:14,613 And you can reprioritize depending on your stakeholders, your customers, 751 00:39:14,823 --> 00:39:16,343 the changes in the marketplace, right? 752 00:39:16,343 --> 00:39:20,473 Like if AI wasn't on your roadmap a year ago, it probably is now, right? 753 00:39:21,023 --> 00:39:24,883 And, you know, engineers are also going to push back on aspects of it 754 00:39:25,053 --> 00:39:28,203 or offer their own advice that might impact how you want to think through 755 00:39:28,253 --> 00:39:29,613 the order in which things get done. 756 00:39:30,061 --> 00:39:33,581 Or might make it simpler for you to achieve certain things if you kind 757 00:39:33,581 --> 00:39:36,331 of walk through the specifications and they can give you feedback 758 00:39:36,381 --> 00:39:38,501 on the best way to achieve that. 759 00:39:39,184 --> 00:39:39,684 And you might. 760 00:39:40,104 --> 00:39:44,194 Keep that as a living document, but it's really up to you as the product manager 761 00:39:44,794 --> 00:39:50,641 of your, go to market platform to keep that in front of engineers and your team, 762 00:39:50,681 --> 00:39:52,451 stakeholders, as well as executives. 763 00:39:53,091 --> 00:39:55,101 And I know that's hard because I've done that. 764 00:39:55,101 --> 00:39:58,181 And it's hard because you're doing all these other things they asked me to do. 765 00:39:58,191 --> 00:39:59,901 You're trying to actually execute on the roadmap. 766 00:39:59,921 --> 00:40:02,671 So do you have time to flash it up every now and then? 767 00:40:03,024 --> 00:40:04,604 Say, hey, this is what we achieved. 768 00:40:04,604 --> 00:40:05,424 This is where we're going. 769 00:40:05,424 --> 00:40:06,654 This is what has changed. 770 00:40:07,214 --> 00:40:09,334 But you do have to do it as a senior MOPS leader 771 00:40:10,107 --> 00:40:13,347 Justin Norris: I saw a scenario recently where something broke, you know, that 772 00:40:13,347 --> 00:40:19,787 you would consider to be pretty vital to the business and it had a product impact 773 00:40:19,787 --> 00:40:22,097 or product input was required to fix it. 774 00:40:22,717 --> 00:40:23,497 And yet even. 775 00:40:24,047 --> 00:40:28,287 With that happening you know, it wasn't like the product team just 776 00:40:28,297 --> 00:40:30,637 jumped on that and said, yeah, we're going to drop everything and fix that. 777 00:40:30,637 --> 00:40:34,137 It said we need to review this against all our priorities and then we need to 778 00:40:34,155 --> 00:40:36,546 arbitrate what's going to take precedence. 779 00:40:36,815 --> 00:40:40,067 And I thought that was an impressive display of cool headedness and 780 00:40:40,067 --> 00:40:43,729 rationality because yep, I know that there's a fire there, but actually 781 00:40:43,729 --> 00:40:46,059 there's already three fires over here or there's a water leak here. 782 00:40:46,059 --> 00:40:49,073 And like, We still need to always have that assessment and they had, 783 00:40:49,199 --> 00:40:51,819 obviously, through long experience, the courage of their convictions 784 00:40:51,869 --> 00:40:55,319 and the sort of fortitude to stick to that process, even though something 785 00:40:55,319 --> 00:40:56,767 really significant had gone wrong. 786 00:40:56,854 --> 00:41:01,118 I don't often see mobs teams have that same kind of fortitude and courage of 787 00:41:01,118 --> 00:41:03,958 their convictions, I guess, in those situations, like, okay, great, like 788 00:41:04,178 --> 00:41:07,378 that you want to do this, or this is broken, like, here's all the other things 789 00:41:07,708 --> 00:41:09,090 how do you think we cultivate that? 790 00:41:09,090 --> 00:41:10,330 Is it just sort of rewiring? 791 00:41:10,607 --> 00:41:12,791 Our brains, or how else can we do that? 792 00:41:13,101 --> 00:41:13,571 Josh Hill: Yeah, right. 793 00:41:13,745 --> 00:41:16,665 ultimately you can only control your own actions and reactions. 794 00:41:17,207 --> 00:41:17,757 So you're right. 795 00:41:17,787 --> 00:41:21,457 Whoever said that was very much in control of themselves and very confident 796 00:41:21,717 --> 00:41:26,912 in Their position and process and that does need to be cultivated and 797 00:41:26,912 --> 00:41:31,392 having a good coach, a good executive leader on your side can help that 798 00:41:31,469 --> 00:41:34,980 having clear incident processes and documentation can help build that motion. 799 00:41:34,980 --> 00:41:37,480 Just because you know, you're following the triage process 800 00:41:38,086 --> 00:41:39,646 or the prioritization process. 801 00:41:39,766 --> 00:41:43,006 And that's why it's also again important to have a ROI based approach 802 00:41:43,006 --> 00:41:46,146 to prioritization that matches your company strategy because you can 803 00:41:46,146 --> 00:41:49,436 always point and say, well, you guys agreed that we're going to do this. 804 00:41:49,856 --> 00:41:54,676 Rankly is based on ROI, and your ROI is here, and these other projects 805 00:41:54,676 --> 00:41:59,107 are up here, so I'm going to do those first, that takes discipline on your 806 00:41:59,107 --> 00:42:01,867 part, But it also takes discipline on the part of the executives. 807 00:42:02,042 --> 00:42:06,721 they need to be clear about the ROI, about the priorities of the business. 808 00:42:06,761 --> 00:42:10,931 They need to have that discussion together and not in silos. 809 00:42:11,031 --> 00:42:12,551 And that takes discipline on their part. 810 00:42:12,776 --> 00:42:14,716 And if that's not happening, for some reason, and they're 811 00:42:14,977 --> 00:42:17,427 stomping their feet you know, that's where you escalate, right? 812 00:42:17,437 --> 00:42:20,863 Or You know, get everybody on a phone call and say, Hey, look, we've 813 00:42:20,873 --> 00:42:22,483 got this conflict about priorities. 814 00:42:22,733 --> 00:42:23,383 X, Y, Z. 815 00:42:23,383 --> 00:42:24,133 So they wanted this. 816 00:42:24,153 --> 00:42:25,643 This is where it falls into the process. 817 00:42:26,278 --> 00:42:28,818 These other things are a lower priority right now. 818 00:42:29,230 --> 00:42:30,380 if you want to change that's fine. 819 00:42:30,800 --> 00:42:33,710 Let's figure it out now before we get too far, whether that's 820 00:42:33,710 --> 00:42:35,680 a fire or it's a project. 821 00:42:36,231 --> 00:42:40,249 And I Again, that's a personal thing that somebody has to really 822 00:42:40,460 --> 00:42:42,600 build into their leadership team. 823 00:42:43,391 --> 00:42:46,886 Justin Norris: so maybe just final thoughts, wrapping up this topic. 824 00:42:46,956 --> 00:42:50,546 Let's say somebody is not in this product management mode right now. 825 00:42:50,596 --> 00:42:53,636 Their team has a sort of different posture in relation to their stakeholders, 826 00:42:53,636 --> 00:42:55,936 but they want to make this transition. 827 00:42:56,396 --> 00:43:00,166 What are like kind of the simple first, second and third things they can do to 828 00:43:00,166 --> 00:43:02,576 start to make this evolution a reality? 829 00:43:03,307 --> 00:43:06,007 Josh Hill: think first recognition is to think that, especially if 830 00:43:06,007 --> 00:43:07,257 you've been doing mops for a while. 831 00:43:07,734 --> 00:43:10,872 You're probably doing half of the thing as a product manager does, 832 00:43:11,392 --> 00:43:14,091 but you're just not thinking that you're doing product management. 833 00:43:14,321 --> 00:43:15,131 So that's 1 thing. 834 00:43:15,131 --> 00:43:16,811 You can just say, hey, I'm a product manager now. 835 00:43:17,671 --> 00:43:20,001 And then that will get you into a learning mode to say, okay, well, 836 00:43:20,001 --> 00:43:21,531 what else does a product manager do? 837 00:43:22,211 --> 00:43:24,761 And, you know, there's a couple of things. 838 00:43:25,035 --> 00:43:28,095 That you're doing today, So you're doing things like pain points and 839 00:43:28,095 --> 00:43:33,275 requirement gathering, you're building features, whether that's a event 840 00:43:33,275 --> 00:43:38,405 in a box program template or entire chat workflow or whatever, right? 841 00:43:38,925 --> 00:43:40,265 You might have some goals and metrics. 842 00:43:40,265 --> 00:43:43,095 You might have some feedback loops already with your stakeholders, 843 00:43:43,095 --> 00:43:44,445 Are they adopting this product? 844 00:43:44,445 --> 00:43:45,935 Is a customer using it? 845 00:43:45,945 --> 00:43:47,125 Is it generating revenue? 846 00:43:47,135 --> 00:43:48,065 Is it tied to revenue? 847 00:43:48,725 --> 00:43:51,079 So you're doing maybe like three or four out of the eight. 848 00:43:51,710 --> 00:43:56,659 Core thing to add as you grow is to say, okay, well, you might want 849 00:43:56,659 --> 00:44:00,780 to look at using a framework to validate and prioritize, Whether 850 00:44:00,780 --> 00:44:04,570 it's an ROI framework or a larger view of the business, And what's 851 00:44:04,570 --> 00:44:06,050 that strategy the business is taking? 852 00:44:06,050 --> 00:44:07,850 What business are you actually in? 853 00:44:08,320 --> 00:44:10,630 Do you understand the business owners metrics? 854 00:44:11,310 --> 00:44:14,010 Do you understand the potential market scope of your opportunity in 855 00:44:14,300 --> 00:44:15,270 the larger scale business, right? 856 00:44:15,721 --> 00:44:16,631 Whatever that is, right? 857 00:44:16,631 --> 00:44:21,351 Do you fully understand the target market, the buying teams, the ICPs, 858 00:44:21,701 --> 00:44:23,981 and does your database validate those? 859 00:44:24,831 --> 00:44:26,321 Are you close to monetization? 860 00:44:26,711 --> 00:44:29,711 And you don't have to be necessarily, but you know, if you own a chat product 861 00:44:29,889 --> 00:44:33,495 or you're building out certain things that impact revenue in some way, like 862 00:44:33,695 --> 00:44:36,833 certain kinds of campaigns or workflows make sure you know that number. 863 00:44:37,149 --> 00:44:40,015 Talk about that number, Going back was easy for me to prioritize it. 864 00:44:40,065 --> 00:44:43,540 I love that example because I could call up The person requested it. 865 00:44:43,620 --> 00:44:47,840 And I said, what's your revenue change from the time before and after? 866 00:44:47,890 --> 00:44:51,870 And they would tell me and we love building for them because they always 867 00:44:51,870 --> 00:44:53,170 told us how well we were doing. 868 00:44:53,414 --> 00:44:55,334 But don't just make it depend on them. 869 00:44:55,334 --> 00:44:55,624 Right? 870 00:44:55,922 --> 00:44:56,862 Build that into your process. 871 00:44:57,135 --> 00:44:58,885 Understand the goal of the product itself. 872 00:44:58,915 --> 00:44:59,915 What is the aha moment? 873 00:45:00,311 --> 00:45:03,917 That the product manager of your product is building and do 874 00:45:03,917 --> 00:45:05,317 you have it in your database? 875 00:45:05,347 --> 00:45:07,527 Are you working on projects related to it? 876 00:45:07,957 --> 00:45:11,077 Should you be maybe you should be can you have that conversation 877 00:45:11,077 --> 00:45:12,377 with the customer lifecycle team? 878 00:45:12,427 --> 00:45:16,222 Or the product manager of the business that you're in and that will help you 879 00:45:16,792 --> 00:45:20,359 Obviously better align with the business and your business stakeholders a lot of 880 00:45:20,369 --> 00:45:24,806 people talk about this on linkedin But The product management discipline is typically 881 00:45:24,866 --> 00:45:29,278 closer to a business, and the more you can talk about the business, as they 882 00:45:29,278 --> 00:45:32,858 always say, right, the more executives will be aligned with you, or you'll be 883 00:45:32,858 --> 00:45:35,744 aligned with the executives, and the more they'll view you not an operations 884 00:45:35,744 --> 00:45:37,084 function that's there to serve them. 885 00:45:37,270 --> 00:45:40,590 They'll view you as that partner, and you won't get flamed on LinkedIn 886 00:45:42,170 --> 00:45:44,500 by people who claim you're not paying attention to their needs. 887 00:45:45,036 --> 00:45:46,006 Because you actually are. 888 00:45:46,286 --> 00:45:47,956 Because you understand the business that they're actually 889 00:45:47,956 --> 00:45:48,786 in and you're supporting it. 890 00:45:49,869 --> 00:45:51,869 Justin Norris: That's a great note to end on Josh. 891 00:45:51,869 --> 00:45:56,953 I want to thank you for joining me today and, the knowledge and support 892 00:45:56,953 --> 00:46:00,483 you've shared kind of with the community at large and with me personally over 893 00:46:00,483 --> 00:46:01,573 the years, I'm really grateful for 894 00:46:01,989 --> 00:46:03,169 Josh Hill: Always glad to do it, Justin. 895 00:46:03,239 --> 00:46:03,989 Thank you for having me.