Latest / Ops Cast / Fix the System, Fix the Results: Mapping Marketing Ops for Real Performance with Joe Bockerstette
Transcript
- 0:24Michael Hartmann: Hello everyone, welcome to another episode of OpsCast brought to you by marketingops.com, powered by all the no pros out there.
- 0:31Michael Hartmann: I'm your host, Michael Hartman, flying solo today.
- 0:34Michael Hartmann: In today's conversation, we're going to be talking about something that almost every marketing ops leader has felt, but never ever not everyone has knows how to diagnose.
- 0:43Michael Hartmann: So why does it take so long to get anything out the door?
- 0:46Michael Hartmann: Why do approvals multiply every time something breaks?
- 0:50Michael Hartmann: Why do teams work harder and still not see better results?
- 0:54Michael Hartmann: So, all about process.
- 0:55Michael Hartmann: So joining me for that conversation today is my guest Joe Bacherstedt.
- 0:59Michael Hartmann: He's a partner at Business Enterprise Mapping.
- 1:01Michael Hartmann: Joe is a former PWC partner, has led CPG companies and has spent more than 30 years helping the mid-size and public companies untangle complex workflows and redesign how their organizations actually function.
- 1:14Michael Hartmann: His firm maps entire business systems, including marketing, to show companies exactly why they're getting the results they're getting and what needs to change.
- 1:21Michael Hartmann: So Joe, welcome to OpsGas.
- 1:24Joe Bockerstette: Thank you, Michael.
- 1:25Joe Bockerstette: I appreciate the opportunity to be with you today.
- 1:27Michael Hartmann: Yeah, this is gonna be a fun and I think I think we talked about this.
- 1:30Michael Hartmann: Uh I used to I I worked at Price Waterhouse and people go like, oh PWC.
- 1:35Michael Hartmann: It's like, no, Chris Water before this evening.
- 1:38Michael Hartmann: It was a difference, really.
- 1:39Michael Hartmann: Yes, yeah.
- 1:40Michael Hartmann: So uh bringing back old memories.
- 1:43Michael Hartmann: All right.
- 1:44Michael Hartmann: Well, let's what we start with um I when I introduced you, we use the term business system, right?
- 1:50Michael Hartmann: I think probably has a lot of different I like people probably have different ideas in their mind, like what does that mean to you?
- 1:56Joe Bockerstette: And maybe how is that different like from I guess documenting just some marketing processes in our business system is a collection of processes that fulfills one of the primary purposes of an enterprise, right?
- 2:15Joe Bockerstette: So at Business Enterprise Mapping, uh, we define 12 standard business systems uh in any enterprise, and that architecture allows us to uh compare work across industries and size and type, et cetera.
- 2:33Joe Bockerstette: So in some ways they're departments, but when you look at actual organizations, it doesn't always match up that way.
- 2:40Joe Bockerstette: For instance, marketing department, we would consider a marketing business system.
- 2:46Joe Bockerstette: For example, you would have a sales department would be a sales business system.
- 2:52Joe Bockerstette: And uh let's just take sales because I know we're gonna talk about marketing autodase.
- 2:56Joe Bockerstette: And so the purpose of a sales system is to deliver customers and orders, right?
- 3:03Joe Bockerstette: It exists in order to create orders that the operation system is gonna fulfill.
- 3:10Joe Bockerstette: And so when you look at an overall enterprise, a business system fulfills a key purpose that, when combined with other business systems, sort of fulfills the entire mission of the enterprise.
- 3:25Joe Bockerstette: And any given business system is comprised of a series of business processes that enable that business system to achieve its purpose.
- 3:34Michael Hartmann: Okay.
- 3:34Michael Hartmann: So this is like So I'm familiar with something called ELS.
- 3:40Michael Hartmann: You probably have heard of it.
- 3:41Michael Hartmann: Enterprise operating.
- 3:42Michael Hartmann: So is it is it something kind of like that where it feels like that one that I I I'm not an expert at, but it sounds like it's that one I feel like has a little more bent towards organizational structure as opposed to this.
- 3:53Joe Bockerstette: Yeah.
- 3:53Joe Bockerstette: This is more, it's just more business model design, if you will, right?
- 3:58Joe Bockerstette: Uh leadership has a responsibility to design the mid business model that fulfills the purpose of that system of that enterprise.
- 4:06Joe Bockerstette: Let's take marketing, right?
- 4:07Joe Bockerstette: We'll just dive into marketing.
- 4:09Joe Bockerstette: So uh we've done a tremendous amount of marketing, both agencies and in-house.
- 4:16Joe Bockerstette: And they're all a little different, but I'm gonna generalize, right?
- 4:19Joe Bockerstette: In general, the purpose of marketing is to do what?
- 4:23Joe Bockerstette: Provide qualified leads, right?
- 4:26Joe Bockerstette: And so all activity in marketing is bent towards uh handing over to sales a qualified lead that sales can turn into a customer in an order, right?
- 4:36Joe Bockerstette: So when you frame the marketing system, where does it begin?
- 4:40Joe Bockerstette: Well, marketing as a system begins with a target market, a target uh community of uh of individuals, entities, whatever that you desire to turn into a qualified lead that we're gonna pass off to sales, right?
- 4:57Michael Hartmann: What some people call the tan total addressable market kind of Yeah.
- 5:01Joe Bockerstette: Exactly.
- 5:01Joe Bockerstette: Exactly.
- 5:02Joe Bockerstette: So in a pragmatic manner, we go into a new state, we open up a new state, right?
- 5:08Joe Bockerstette: So that state and the uh profile of our target customer becomes the target market, and our mission is to turn more of those target customers into qualified leads, right?
- 5:22Joe Bockerstette: Now, what do we do in order to make that happen?
- 5:25Joe Bockerstette: We have a series of processes, and it can vary greatly, but it's uh, you know, lead generation, social media content development, content management, web management, uh email outreach, advertising, marketing campaigns, like all of those are examples of processes that would begin maybe with an annual plan.
- 5:51Joe Bockerstette: That annual plan would turn into a campaign calendar, that campaign calendar would turn into campaigns, we would execute those campaigns using the various elements of content that uh informs them, and then would ultimately close out those campaigns with a successful lead generation uh capability that we turns uh that those targets into qualified leads we can pass on to sales.
- 6:19Michael Hartmann: Okay.
- 6:19Michael Hartmann: So I want to ask a couple questions.
- 6:21Michael Hartmann: So if I and there's there's sort of a hierarchy for lack of a better term, of like you've got the marketing system, the market system, if you will, and then within that uh it's made up of processes and it's and then kind of the other thing you gave the example, then those processes get broken down, and then I guess you kind of overlay it in the organizational structure is becomes a part of how you you know enable that system to work.
- 6:49Joe Bockerstette: Precisely.
- 6:50Joe Bockerstette: So we would argue that you design the business model first, being the workflow, and then you lay the organization structure on top of that workflow model so that the organization is in sync with the business model itself.
- 7:06Joe Bockerstette: Most times when we start work with clients, the organization structure is out of sync with the workflow model, right?
- 7:15Joe Bockerstette: And that's one of the reasons you get delays and uh approvals and uh disconnects, waste, right?
- 7:25Joe Bockerstette: It comes out of the fact that the org structure is out of sync with the actual work itself.
- 7:30Michael Hartmann: Okay, so I want that's that's good.
- 7:33Michael Hartmann: That's why I'm glad I confirmed that.
- 7:35Michael Hartmann: Um the the other part, you mentioned marketing primary purpose to deliver leads to sales, especially in the B2B space industry.
- 7:44Michael Hartmann: Uh I think there I and I think other people listening might argue that there's other purposes, like um, I mean you could I guess you can link it to ultimately to demand, but like I'm I'm yeah I my view of this has changed a little bit.
- 8:02Michael Hartmann: Like the building brand awareness is part of that, right?
- 8:05Michael Hartmann: Is looking a little further out in the future depending on what you're right.
- 8:08Michael Hartmann: Like, so do you do you layer that in as well?
- 8:11Michael Hartmann: Like, is that a separate process or is that a subsystem of marketing in the way you think about?
- 8:17Michael Hartmann: How does that work?
- 8:18Joe Bockerstette: No, it's part of the marketing system.
- 8:20Joe Bockerstette: Remember, I just said we were going to generalize at the front.
- 8:22Joe Bockerstette: Yeah, I just said curious.
- 8:24Joe Bockerstette: Yeah, but but I've got no uh hesitation to adopt brand awareness as well, right?
- 8:31Joe Bockerstette: Brand strength, all of that can fall.
- 8:34Joe Bockerstette: When you think of the purpose of a marketing system, it can be, you know, a half a dozen primary purposes, right?
- 8:43Joe Bockerstette: Uh, you know, lead generation being one, brand awareness being another, right?
- 8:48Joe Bockerstette: Um, but all of the processes that would exist inside those boundaries would be part of that same uh contribution to purpose.
- 8:58Joe Bockerstette: Now, each of those processes is a primary deliverable.
- 9:02Joe Bockerstette: So when you think about achieving the purpose of the system, I've got a series of deliverables that need to contribute to that purpose, right?
- 9:10Joe Bockerstette: So when I'm designing the business model of marketing, I need to look at what's the primary purpose of marketing, what are the deliverables that we need to produce in order to fulfill that purpose, and then what are the processes that we're gonna need in order to create those deliverables, right?
- 9:28Joe Bockerstette: So it's very hierarchically systematically built.
- 9:32Joe Bockerstette: So all the pieces of the puzzle fall in the right place in order to generate the overall purpose of our intention.
- 9:39Michael Hartmann: Got it.
- 9:40Michael Hartmann: Okay.
- 9:40Michael Hartmann: So that again, glad I asked for that clarification.
- 9:43Michael Hartmann: Let me so you mentioned that you work with you've worked with both sort of in-house, keep it to marketing, marketing corporations as well as agencies.
- 9:53Michael Hartmann: Like what do you what are the similarities, the differences that you see between them from the standpoint?
- 9:58Joe Bockerstette: So from the content itself, this they're they're all pretty similar, right?
- 10:02Joe Bockerstette: We have graphics, we have content management, we have social media, we have web, we have outreach, right?
- 10:09Joe Bockerstette: The we have campaigns.
- 10:11Joe Bockerstette: The difference between an agency and in-house are generally two things.
- 10:16Joe Bockerstette: Agencies generally have an account management function, the uh playmaker, if you will, between the client and the shop itself.
- 10:26Joe Bockerstette: And so they're funneling communications between the internal production and capabilities and project campaign management to the external customer.
- 10:36Joe Bockerstette: They're managing that relationship and the communication energy, the point primary point of communications.
- 10:43Joe Bockerstette: You don't typically see that in-house, right?
- 10:46Joe Bockerstette: The second component that you generally see with agencies are much more cost budget focused.
- 10:54Joe Bockerstette: An agency creates a contract with a client and it strives to make profit on that contract by tracking basically the internal projects that are executed in order to fulfill that contract.
- 11:09Joe Bockerstette: Right?
- 11:10Joe Bockerstette: Uh in-house, again, not so much.
- 11:13Joe Bockerstette: We don't generally see in-house agencies so concerned about that project management, contract cost relationship that you see in the external agencies.
- 11:26Michael Hartmann: Okay.
- 11:26Michael Hartmann: It's kind of considered more of a have a fixed cost for the overall organization as opposed to project-based cost.
- 11:34Joe Bockerstette: That's right.
- 11:35Joe Bockerstette: Uh agencies are basically project management companies who execute contracts with clients, fulfill those contracts, and uh leave satisfied clients to uh create more contracts, we owe.
- 11:49Michael Hartmann: Right, right.
- 11:50Michael Hartmann: Yes, uh hopefully, yeah.
- 11:51Michael Hartmann: Right.
- 11:52Michael Hartmann: That's the goal.
- 11:53Michael Hartmann: Yeah.
- 11:54Michael Hartmann: I uh yeah, okay.
- 11:57Michael Hartmann: Yeah, it's it's interesting.
- 11:58Michael Hartmann: I hadn't thought about that difference that way in terms of the um you know the the al like the cost tracking piece, because I think in my experience mostly in-house, right, when I've been asked like can we allocate our costs to campaigns, for example, right?
- 12:14Michael Hartmann: Like we can, but I wouldn't recommend it because anything that's sort of in by cost is like really hard to allocate as you know the number of things you're allocating to changes, you know, uh or something gets stopped or canceled, or it's just really hard.
- 12:31Michael Hartmann: And like direct costly fine.
- 12:33Michael Hartmann: Yes.
- 12:34Michael Hartmann: Whereas agencies follow you to do that.
- 12:37Joe Bockerstette: Agencies really that's their business, right?
- 12:39Joe Bockerstette: That's their core value proposition.
- 12:40Joe Bockerstette: The other thing I'll mention that I think is different about agencies, in my experience, is they're much more focused on the metrics of client satisfaction, uh, internal waste, uh lead time cycle times, much more focused on the operating metrics of uh performing well against those contract requirements and uh and testing the temperature of client satisfaction on how they're doing.
- 13:08Michael Hartmann: Yeah.
- 13:08Michael Hartmann: Makes sense.
- 13:10Michael Hartmann: Um I remember when we talked before, you there's an idea that you see if I get it right, every organization is perfectly designed to get the results it gets.
- 13:20Michael Hartmann: Right.
- 13:20Michael Hartmann: So what does that mean?
- 13:23Michael Hartmann: Uh then in an especially maybe especially if we're a marketing team that's maybe for a market me ops team, and considering that's our main audience, frustrated with their own skier to performance.
- 13:34Joe Bockerstette: Yeah, so that quote goes back to a book called Designing Organizations for High Performance by David Hannah out of Proctor and Gamble back in the 80s or 90s.
- 13:44Joe Bockerstette: I worked a lot with Proctor and Gamble when I was with PWC.
- 13:48Joe Bockerstette: And uh the quote is uh all organizations are perfectly designed to get the results they get.
- 13:55Joe Bockerstette: And uh I I still use that quote, obviously, frequently today.
- 13:59Joe Bockerstette: And and here's the implications of it.
- 14:01Joe Bockerstette: Uh, as leaders, uh it tells us that we can understand the reasons we're getting the outcomes we get, right?
- 14:11Joe Bockerstette: Like the frustration is I don't understand why things don't work the way I want them to.
- 14:16Joe Bockerstette: I don't understand why it takes so long, I don't understand why it costs so much, I don't understand why it's not better, right?
- 14:23Joe Bockerstette: So, in understanding that organization design underpins performance, I can diagnose the cause and effect relationships between why things aren't working the way I want them to and what I need to do differently to make it better.
- 14:39Joe Bockerstette: So that's the one side.
- 14:41Joe Bockerstette: Concurrent with that, however, comes the responsibility for leadership to do something about it, right?
- 14:48Joe Bockerstette: By understanding that there are reasons behind it, and these reasons can be addressed.
- 14:55Joe Bockerstette: It's now my responsibility to address those reasons, create a different and better organization design that overcomes the problems I'm experiencing and gets the performance I desire to get.
- 15:10Michael Hartmann: Yeah, it's funny.
- 15:11Michael Hartmann: It reminded me of Bill Bill Parcells, the football coach, coached the Cowboys for like two seasons or whatever it was, and he I think he had something that was like um your your your um performance is you know in this case, right?
- 15:31Michael Hartmann: Your standings, right?
- 15:32Michael Hartmann: What your win-loss ratio was like is really who you are, right?
- 15:36Joe Bockerstette: Yeah, you are what your record says you are.
- 15:38Joe Bockerstette: Yeah, yeah, yeah.
- 15:38Michael Hartmann: I think that's it.
- 15:39Michael Hartmann: Um so it's it's it's as like a parallel to that, right?
- 15:42Michael Hartmann: I mean it's so what do you think about this?
- 15:46Michael Hartmann: So um because I've seen this before where it's kind of obvious that there's problems within an organization.
- 15:54Michael Hartmann: And I often I can coach some people personally you know who are struggling with how do I deal with this situation, and it becomes one where I go like either the leadership doesn't see the problem or they see it, but they either are uh they're afraid to address it, they don't know how to address it, they like but they just ignore it, right?
- 17:29Michael Hartmann: Either like in both of those situations is bad.
- 17:33Joe Bockerstette: It is, yeah.
- 17:34Joe Bockerstette: So uh we know from experience about 70% of all problems relate to process deficiencies, right?
- 17:41Joe Bockerstette: And from a leadership perspective, it really comes down to two sort of ideas.
- 17:45Joe Bockerstette: One is we accept the way it is is the way it is, right?
- 17:50Joe Bockerstette: Like there's nothing I can do about it.
- 17:52Joe Bockerstette: It is what it is, and I'm a victim of the system, and there's nothing I can do uh about that system.
- 18:00Joe Bockerstette: And then secondarily, I'm overwhelmed by the system and don't know how to get started, right?
- 18:08Joe Bockerstette: We have some great examples.
- 18:10Joe Bockerstette: I had a product development system example, very large CPG company.
- 18:14Joe Bockerstette: We were on the front end of scoping and planning, and we were there a couple of days, and the the head of product development says to me, You've done more to solve our problems in two days than we've been able to do in two years, right?
- 18:28Joe Bockerstette: Because it didn't have the template, the model to attack the problem.
- 18:33Joe Bockerstette: Like you look at it, you throw your hands up and say, I don't know what to do and I don't know where to begin, right?
- 18:38Joe Bockerstette: Well, that's our business model is attacking that sort of complicated, overwhelming, intimidating, large workflow that we can't wrap our arms around and rustle to the ground.
- 18:49Joe Bockerstette: So that's you know, we've been doing that for over 30 years now.
- 18:53Michael Hartmann: Yeah.
- 18:53Michael Hartmann: Well, I think a lot of people get stuck in their can't they sort of the imagination of what should be possible.
- 19:00Michael Hartmann: They've lost that muscle a little bit.
- 19:03Joe Bockerstette: Right, right.
- 19:04Michael Hartmann: Yeah.
- 19:04Michael Hartmann: So one of the things that I've seen, I think probably people listening have seen too in market in marketing, is let's say you've got a process that you think is working smoothly, and then inevitably there's some sort of mistake, you know, a you know, bad launch, the email has mistakes in it.
- 19:21Michael Hartmann: Um, and the the reaction from the organization is to just put in more rules, more reviews, more approvals, like all these kinds of things that I think um I get the the the instinct to have that kind of reaction, but to me that's usually made things worse instead of better.
- 19:41Michael Hartmann: And sort of sort of be able to actually like is do you see the same thing and do you have anything open to try to avoid that?
- 19:48Joe Bockerstette: Yeah, so we we do see that and a couple of implications of that.
- 19:53Joe Bockerstette: Number one, it slows everything down.
- 19:55Joe Bockerstette: Number two, it introduces as many errors as it fixes.
- 20:00Joe Bockerstette: Number three, ultimately, folks go around the system.
- 20:04Joe Bockerstette: I can't tell you how many clients we start work with where the final approval sits on the executive VP's desk, but the project's already gone, right?
- 20:14Joe Bockerstette: Like the VP's waiting to approve something that executed a week ago because nobody waits around for it anyway, right?
- 20:21Joe Bockerstette: And so it just introduces more reasons for things to go wrong, basically, in the flow, right?
- 20:28Joe Bockerstette: See, you know, we when you're designing for high performance, right?
- 20:33Joe Bockerstette: It begins with that primary purpose that we talked about at the end of the stream.
- 20:37Joe Bockerstette: What are we trying to accomplish?
- 20:39Joe Bockerstette: What are the deliverables that will facilitate accomplishing that?
- 20:42Joe Bockerstette: Now let's start with those, right?
- 20:44Joe Bockerstette: What are the specs on those deliverables?
- 20:46Joe Bockerstette: How are we performing against those specs?
- 20:49Joe Bockerstette: How will we measure how we're performing?
- 20:51Joe Bockerstette: Most of the improvement comes at that stage.
- 20:55Joe Bockerstette: Who's my customer?
- 20:56Joe Bockerstette: What do they want?
- 20:57Joe Bockerstette: What am I providing?
- 20:58Joe Bockerstette: What do I need to do differently?
- 21:00Joe Bockerstette: And let's go fix those problems.
- 21:02Joe Bockerstette: That's always a great place to start.
- 21:04Joe Bockerstette: In a marketing system, you're generally talking about uh 20 or less processes, even in the very large ones.
- 21:11Joe Bockerstette: And we've worked for some of the largest uh in the world.
- 21:14Joe Bockerstette: You're talking 20 or less processes, 20 or less processes are producing, you know, well under 50 primary deliverables, maybe even 25.
- 21:24Joe Bockerstette: So the the point is you can wrap your arms around this and really focus on doing the important things well.
- 21:30Michael Hartmann: Would you say that number of deliverables?
- 21:32Michael Hartmann: You mean the types of deliverables, not no, I mean types.
- 21:36Joe Bockerstette: Yeah, a final report, a uh written uh blog, pages, yeah, a website page, right?
- 21:45Michael Hartmann: Okay, maybe multiple of those are the I just wanted to sort of yeah, okay.
- 21:50Joe Bockerstette: Right, but a type, yeah, that's fair, right?
- 21:52Michael Hartmann: Yeah, yeah.
- 21:52Michael Hartmann: Okay, that's that makes sense.
- 21:54Michael Hartmann: My dog agrees.
- 21:56Michael Hartmann: Um she's helping.
- 21:58Michael Hartmann: Um okay, so I'm curious, what um so one of the things that I because I've seen this before multiple times.
- 22:07Michael Hartmann: Maybe maybe walk us through them a little more in the detail about your the the approach for mapping.
- 22:12Michael Hartmann: And one of the one of the struggles I find is when you get this, whether it's an overreaction or I walk into a place where it's already got this like highly structured, lots of approval levels that you're saying point somebody's expected to do to approve but doesn't basically never does.
- 22:28Michael Hartmann: Like how do you get into things like defining the processes?
- 22:31Michael Hartmann: Steps or tasks that go into it?
- 22:33Michael Hartmann: Do you do anything like erasy?
- 22:35Michael Hartmann: We don't measure it.
- 22:37Michael Hartmann: Hold on a sec, how do you how do you do that?
- 22:39Michael Hartmann: And then what have you found surprises people most when you go through that with them?
- 22:44Joe Bockerstette: Yeah, so um when you let's just take a marketing group, let's say there are 10 processes, just to pick a smaller number, round number.
- 22:54Joe Bockerstette: We would produce what we call a process playbook for each of those 10, right?
- 23:00Joe Bockerstette: And we would identify a process owner and a process team to work with.
- 23:05Joe Bockerstette: Uh the process owner understands how the process operates today.
- 23:09Joe Bockerstette: The process team might be users, subject matter experts, whatever.
- 23:13Joe Bockerstette: Right?
- 23:14Joe Bockerstette: We will facilitate sessions.
- 23:17Joe Bockerstette: We generally work on uh remote at this point, Zoom or Teams.
- 23:22Joe Bockerstette: We'll facilitate sessions to uh map, document how the work is done today.
- 23:29Joe Bockerstette: We do it real time.
- 23:30Joe Bockerstette: We use Visio as the mapping tool.
- 23:32Joe Bockerstette: So just like this.
- 23:33Joe Bockerstette: Uh podcast, we would be mapping on the screen while we're facilitating the group, right?
- 23:40Joe Bockerstette: That takes about five hours over three sessions per process.
- 23:45Joe Bockerstette: So, and and we do this as a project.
- 23:48Joe Bockerstette: So 10 processes, we'd be putting in about 50 hours, getting the baselines built, right?
- 23:54Joe Bockerstette: We then take you to what we call a system alignment workshop where we bring all of those process owners together.
- 24:00Joe Bockerstette: This tends to be on site.
- 24:01Joe Bockerstette: We put all these flows up on posters and then we troubleshoot the disconnects, the misunderstandings, the uh duplications, the gaps, all of the issues around the larger flow.
- 24:16Joe Bockerstette: It starts with that target market, ends with that uh qualified lead and everything that's taking place in between.
- 24:24Joe Bockerstette: We then go into a series of analysis, right?
- 24:27Joe Bockerstette: We analyze the customer-supply relationship.
- 24:30Joe Bockerstette: Each of these processes has a customer.
- 24:32Joe Bockerstette: Who is that customer?
- 24:34Joe Bockerstette: What do they want?
- 24:35Joe Bockerstette: What are we providing?
- 24:36Joe Bockerstette: What do we need to do differently?
- 24:37Joe Bockerstette: What information is being used by that process?
- 24:41Joe Bockerstette: How does that process interact with technology, hardware, and software?
- 24:45Joe Bockerstette: What's the racy uh diagram?
- 24:47Joe Bockerstette: Who's responsible for what in that process?
- 24:50Joe Bockerstette: What are the red clouds?
- 24:51Joe Bockerstette: So we identify what we call red clouds when we map a process.
- 24:55Joe Bockerstette: Red clouds are the problems and opportunities getting in the way of what you're trying to accomplish, right?
- 25:01Joe Bockerstette: And uh the metrics, what metrics are we measuring or not measuring in that process?
- 25:06Joe Bockerstette: And so it's a very extensive analytical exercise once we've created and documented the process itself, ultimately yielding a process improvement plan per process of quick wins.
- 25:21Joe Bockerstette: Quick wins are red clouds that can be solved in 90 days without a budget request, right?
- 25:26Joe Bockerstette: The dumb low hanging fruit, right?
- 25:28Joe Bockerstette: So if you've got 10 processes, you're gonna have about 25 tasks per process, about 250 tasks.
- 25:34Joe Bockerstette: You're gonna have about 300 red clouds, about 150 of those are gonna be quick wins, right?
- 25:40Joe Bockerstette: So there's plenty to go work on right away.
- 25:43Joe Bockerstette: And then we do an overall system improvement plan that puts together a plan over the next year or two to improve the whole system with opportunities that are larger than just process level quick wins, right?
- 25:56Joe Bockerstette: And so, and we can do all that really well inside of a couple of months, like from the point you would start a first conversation to having an entire system fully mapped, implementation plans in place and starting to implement as well under 90 days.
- 26:13Michael Hartmann: Um I'm curious about like one of the things that I've seen that I've diagnosed is uh like unclear roles responsibilities, specifically around review and approval.
- 26:25Michael Hartmann: Specifically, you got it.
- 26:27Michael Hartmann: Right.
- 26:27Michael Hartmann: Yeah, and and then and then in particular, like having the same level of scrutiny um regardless of what the um whatever is being produced.
- 26:38Michael Hartmann: So when do you think about that?
- 26:40Michael Hartmann: Do you so and then with races, I've always struggled with getting a like some people trying to at such a high level that they are almost useless, and then you you know multiple people with the the same kind of role, racy role.
- 26:55Michael Hartmann: Oh good, all good points.
- 26:58Joe Bockerstette: Like what's the right level of detail and how do you how do you deal with the like this yeah uh so here's multiple levels of approval and yeah, so we do race the at the we do raise the at the task level, but let me uh let me broaden the question a little bit.
- 27:15Joe Bockerstette: One of the paradigm shifts for marketing that we often lay in place is marketing is a project management system, right?
- 27:26Joe Bockerstette: And it is a it is the management of campaigns or the management of client contracts, it's the access of a variety of content contributors and bits and pieces that contribute to that project or that campaign, but ultimately it's the overarching management of work through a flow of uh a requirement that gets fulfilled, right?
- 27:51Joe Bockerstette: And we're often putting in place uh review systems, milestones, right, uh uh stage gates, uh elements of uh commonality and uh logical review to sort of take out the unclarity of who's responsible for what when, right?
- 28:14Joe Bockerstette: I'm just to make it up.
- 28:15Joe Bockerstette: We may have a one-month stage, let's say it's a nine-month relationship, just to pick some sort of time frame.
- 28:22Joe Bockerstette: We may have monthly review cycles that include what deliverables are being reviewed by that month, who's in the meeting, if you will, who's responsible for approval and what's the criteria for approval, right?
- 28:39Joe Bockerstette: So that you formalize that in a way that is very clear who's doing what when based on what criteria, right?
- 28:47Joe Bockerstette: Uh as you mentioned, every time we walk into a marketing group, uh roles and responsibilities are unclear, without question.
- 28:55Joe Bockerstette: And largely because the work is not organized into project thinking or campaign thinking.
- 29:02Joe Bockerstette: It's sort of disjointed work all being uh sort of thrown out there to be picked up and moved along as uh available, if you will, not driven by calendars and driven by sequencing and driven by uh approvals and responsibilities.
- 29:19Michael Hartmann: I think you just you said something that really caught my attention there, because I I love the idea of being clear about who can approve versus who has input and there it's not.
- 29:28Joe Bockerstette: Precisely and what's the criteria, right?
- 29:31Michael Hartmann: What's the past what's the past fail, right?
- 29:33Michael Hartmann: I had not really, I mean, I probably intuitively thought about it, but like we asked what what constitutes something that can be approved or not?
- 29:40Michael Hartmann: Um and what's the timeline and what happens if that person like if there's somebody who's expected to review and approve and it's the time window, like what do we do?
- 29:48Michael Hartmann: Like those kinds of times I think need to be clearly stated.
- 29:51Michael Hartmann: Um and and I I I mean what I found is that two two things most commonly happen, right?
- 29:58Michael Hartmann: One it's really unclear.
- 29:59Michael Hartmann: So you got instead of a approver, you've got three or four people who all have veto power, right?
- 30:05Michael Hartmann: Right.
- 30:05Michael Hartmann: So things go through exactly just rounds, you don't know if they have conflicting feedback, and then you really screwed because it's right.
- 30:12Joe Bockerstette: And then it sits in somebody's inbox for two weeks because they didn't get to it, and you know, yeah.
- 30:18Michael Hartmann: And then um people get and then the other on the flip side is people get crushed for a mistake or something that is considered a mistake.
- 30:25Michael Hartmann: And some of it's some of it's objectively a mistake, put the wrong date for the webinar, right?
- 30:31Michael Hartmann: Time around time for work.
- 30:32Michael Hartmann: Some of it is subjective mistake.
- 30:35Joe Bockerstette: Interpretation.
- 30:36Michael Hartmann: Yeah, I didn't like the way that this looked or who went to and they get killed for it.
- 30:41Michael Hartmann: So the they get that reaction like, oh now we need even more review approval.
- 30:45Michael Hartmann: Right.
- 30:46Joe Bockerstette: See, the point is if you intentionally design these sort of big elements on the front end, it makes it easier to run the system, right?
- 30:54Joe Bockerstette: And if I know what deliverable specs are, if I know what go no go means, if I know who's approving it at what point, just to use that example, then I can operate the system in a standard repeatable way, right?
- 31:08Michael Hartmann: Yeah.
- 31:08Michael Hartmann: No, I I think I think that's great.
- 31:10Michael Hartmann: And it's that's a but I I'm a true I'm a huge believer that what you need to do is have a lot of that in place.
- 31:15Michael Hartmann: I the struggle I'm having with what you described is it sounds um that level of detail on that kind of stuff is to some degree sounds onerous, like it's almost a burden.
- 31:28Michael Hartmann: Um, whereas but but it could be that my perspective.
- 31:32Michael Hartmann: So the way I like to think about these, like I'm a big fan of having processes defined and things like that, right?
- 31:37Michael Hartmann: But I want them to be defined at a level that allows for this essentially more like guardrail, unless unless it has to be explicit, like you must do this, right?
- 31:46Michael Hartmann: Yeah, there's very few things where that's the case, right?
- 31:49Michael Hartmann: Right.
- 31:49Michael Hartmann: Um but statement guardrails and letting people interpret it and move things along.
- 31:54Michael Hartmann: Right.
- 31:54Joe Bockerstette: So you got it.
- 31:55Joe Bockerstette: So let me explain, right?
- 31:57Joe Bockerstette: So uh our process maps are at the task level, right?
- 32:02Joe Bockerstette: So it identifies the steps in the process, if you will.
- 32:05Joe Bockerstette: How that task gets accomplished is not defined unless you want it to be defined through a task instruction.
- 32:14Joe Bockerstette: So the opportunities, just take graphics, for instance, a sort of a creative area.
- 32:19Joe Bockerstette: There can be a task called design, right?
- 32:23Joe Bockerstette: And then your six graphic artists can design in their own sort of creative way, fulfilling that task.
- 32:31Joe Bockerstette: Now, there may be tasks where you want specific instructions uh defined, right?
- 32:37Joe Bockerstette: Like a lab test just to pick something that's different, right?
- 32:40Joe Bockerstette: So it's all available.
- 32:42Joe Bockerstette: It can be as flexible or as thorough as you want it to be.
- 32:47Joe Bockerstette: But what you definitely want is you want to understand the processes inside that system, what the primary deliverables are for each of those processes, and what steps are required in what sequence to make those deliverables happen.
- 33:01Michael Hartmann: I the other thing that you said that was interesting, you said it multiple times in our conversation already, is describing marketing as a project management function, which is interesting because so our audience being marketing ops folks are probably nodding their heads going, yeah, well, that's flipped you.
- 33:19Michael Hartmann: Um and in fact, if Mike was here, my co-host Mike Rizzo, he he has been advocating for a view of marketing ops specifics of you know the technology and execution of being almost like keep being treated like a product management function.
- 33:36Michael Hartmann: Yeah.
- 33:38Michael Hartmann: Does that make sense too?
- 33:40Joe Bockerstette: Yeah, yeah.
- 33:41Joe Bockerstette: It is the execution.
- 33:42Joe Bockerstette: I always use the term campaigns, you could as a marketing term, but you can call us is the execution of an intention, right?
- 33:49Joe Bockerstette: And there are a series of steps and deliverables to execute that intention, right?
- 33:55Joe Bockerstette: We've worked very, very large public company in marketing ops where they were executing email and phone campaigns, right?
- 34:04Joe Bockerstette: And every little digit was essential if you screw one thing up and the whole, you know, thousands of people get the wrong thing, right?
- 34:12Joe Bockerstette: And so it is the execution of projects, right, with specific requirements and very, very tight tolerances in that case.
- 34:23Joe Bockerstette: And you gotta have a scripted process flow and an understanding of the guardrails in order to make that successful.
- 34:32Michael Hartmann: Gotcha.
- 34:33Michael Hartmann: So you mentioned that term red clouds, and I like that interesting.
- 34:36Michael Hartmann: Yeah, it's it's very visual, right?
- 34:38Michael Hartmann: So it makes sense.
- 34:39Michael Hartmann: Right.
- 34:40Michael Hartmann: Um so if you think about the work you've done with marketing teams, if you think about it from an ops lens, ops and technology, um, what are some of the common things that you see in where opportunities are identified within that space that you would call red clouds?
- 35:00Joe Bockerstette: Uh yeah, so really across industry, across even functional, the red clouds tend to be pretty common, right?
- 35:09Joe Bockerstette: Undefined process would be number one.
- 35:12Joe Bockerstette: Uh process variation.
- 35:15Joe Bockerstette: Uh, most clients I work with have multiple departments or locations where different people do the same things different ways, right?
- 35:26Joe Bockerstette: Very, very common in the work we do.
- 35:29Joe Bockerstette: Undefined deliverables, that customer-supply relationship.
- 35:32Joe Bockerstette: Who's the customer?
- 35:33Joe Bockerstette: What do they want?
- 35:34Joe Bockerstette: What are we providing?
- 35:35Joe Bockerstette: Are we getting it right or not?
- 35:36Joe Bockerstette: Unmanaged data.
- 35:38Joe Bockerstette: It starts out inadequate on the front and just gets pushed through the whole system till it crashes at the back.
- 35:44Joe Bockerstette: Very, very common, right?
- 35:47Joe Bockerstette: Uh, missing uh performance uh metrics, right?
- 35:51Joe Bockerstette: We're not measuring our performance.
- 35:53Joe Bockerstette: Our org structure is out of sync with our workflow.
- 35:56Joe Bockerstette: We've got really goofy responsibilities.
- 35:59Joe Bockerstette: The implication of all this is you can't hold people accountable, right?
- 36:03Joe Bockerstette: If you don't have the foundational elements in place, then the idea that I'm gonna hold you accountable for your work is a little silly because so much of it's out of your control.
- 36:13Joe Bockerstette: What are you gonna do about it, right?
- 36:15Joe Bockerstette: Um let's see.
- 36:17Joe Bockerstette: Uh lack of clarity and roles and responsibilities, very, very common.
- 36:22Joe Bockerstette: It's where it comes with that misaligned org structure issue.
- 36:26Joe Bockerstette: Um you can find uh inadequate uh information system matchup, right?
- 36:34Joe Bockerstette: A system doesn't match to the real needs of that business, right?
- 36:38Joe Bockerstette: And so you've got a uh, you know, one of my favorite stories, we worked with a bank where over uh 50% of all their tasks were either Outlook, Word, or Excel, right?
- 36:50Joe Bockerstette: So what that tells you is they spend all their time working around their ERP system, right?
- 36:55Joe Bockerstette: Because it wasn't a good fit for what they were doing, right?
- 36:59Joe Bockerstette: So um you get this sort of uh automation can enable or hinder what you're trying to accomplish.
- 37:07Michael Hartmann: Right.
- 37:08Joe Bockerstette: I always find it hinders more than any well, it just makes it accelerates bad processes, right?
- 37:14Joe Bockerstette: It just it it makes it yeah, you know, a good process makes it easy to do the right thing, right?
- 37:20Joe Bockerstette: Uh a bad process makes it difficult to do the right thing, and we see far more of those than good ones.
- 37:27Michael Hartmann: Okay, so I might go back to my reaction to this as being feeling a little bit um overwhelming or um burdensome because I think a lot of the people who are listening to our our podcast are at smaller firms, right?
- 37:43Michael Hartmann: Even gross startups, things like that.
- 37:46Michael Hartmann: How and it couldn't bring you know forward miss maybe they bring in consultants for this, and how would you advise their what how would you suggest they start if they said oh yeah, we need to we need to be better about having clear roles of responsibilities and understanding our process.
- 38:01Michael Hartmann: So it was a yada yada yada.
- 38:02Michael Hartmann: So how how would you guide them to if you need to go do what's the first thing to do in the second thing?
- 38:08Joe Bockerstette: Yeah, so um I I would say this the first thing to do is, and we're talking about marketing, let's say specifically marketing, the first thing to do is let's identify the primary purpose of what we're trying to accomplish with our system, right?
- 38:26Joe Bockerstette: Whether it's brand awareness, whether it's lead generation, you know, marketing and sales often get sort of uh scrunched together today.
- 38:34Joe Bockerstette: So it can be um a sale, right?
- 38:38Joe Bockerstette: If you put marketing and sales together through an online strategy, for instance, it can all be uh put together.
- 38:45Joe Bockerstette: But the point is, what are we trying to accomplish?
- 38:48Joe Bockerstette: What deliverables are we producing inside this system today to accomplish it?
- 38:54Joe Bockerstette: What shape do we think they're in?
- 38:58Joe Bockerstette: Where are things going wrong?
- 39:00Joe Bockerstette: What processes would need to exist in order to do this well?
- 39:05Joe Bockerstette: And sort of where do we stand?
- 39:07Joe Bockerstette: What's our landscape relative to that intention?
- 39:11Joe Bockerstette: And then lastly, look at that organization structure.
- 39:14Joe Bockerstette: I see so many organizations where people are responsible for stuff because that person's a hero and we know we can throw more on them and they'll do a great job, and things get cobbled up, right?
- 39:26Joe Bockerstette: You want your organization structure to perfectly align with your workflow so that you can manage it well, right?
- 39:33Joe Bockerstette: If you don't have somebody responsible for uh, let me just pick an example, client data, which is something we find in bad shape almost everywhere we go.
- 39:45Joe Bockerstette: Well, if nobody is responsible for the client data setup, let's say it's being done in six different locations by six different people, what do you expect?
- 39:55Joe Bockerstette: It's gonna be bad.
- 39:57Joe Bockerstette: Right.
- 39:58Joe Bockerstette: And so you're aligning all of those elements into what do I intentionally want to accomplish and where do I stand today relative to that intention?
- 40:09Michael Hartmann: So um maybe this is so one of the things that I have done in leadership roles and I coach people on is because they're trying to understand the capacity of the team and who's got what you know, watching out for where like we've got a single point of failure, for example.
- 40:25Michael Hartmann: Right is like literally like it feels like this could have been a step towards what you're describing.
- 40:31Michael Hartmann: Like I'll make a list, like these are the types of tasks my team is responsible for.
- 40:35Michael Hartmann: And then here's yeah, here's the team across the top of you know, we'll make it to the matrix.
- 40:40Michael Hartmann: And like who's who's the primary person or primary couple of people who are secondary?
- 40:46Michael Hartmann: Uh, because it usually what it reveals is there's gaps, right?
- 40:50Michael Hartmann: Tasks were expected, and we don't have somebody currently who is the primary person for that or secondary at all.
- 40:57Michael Hartmann: And so it helps it helped me kind of go like, okay, where do we have gaps, right?
- 41:02Michael Hartmann: So if I it helped me fight for budget for headcount, for example, which is exactly or or reorganize.
- 41:08Michael Hartmann: Yeah, but more importantly, it was hey, like what are we not able to do today without you know, potentially burning people out because they're just getting crazy with something and um and then making sure that people could take time off, right?
- 41:22Michael Hartmann: Because there was somebody who could back them up, even if that was me.
- 41:25Michael Hartmann: Yeah.
- 41:25Michael Hartmann: So is that a step like a part of what you're talking about?
- 41:29Joe Bockerstette: It is, right?
- 41:30Joe Bockerstette: So you would call that a system skills matrix, right?
- 41:32Joe Bockerstette: And you would be matching up the available resources with the content of the work itself, right?
- 41:38Joe Bockerstette: Uh very, very common, uh, and typically run out of HR, right?
- 41:45Joe Bockerstette: But you know, it varies greatly.
- 41:49Michael Hartmann: I don't think they understand the domain well enough to be able to do that.
- 41:51Michael Hartmann: I wouldn't yeah.
- 41:53Michael Hartmann: I mean, I've worked so with some good HR partners, but I don't know that they would know it deeply.
- 41:59Joe Bockerstette: Yeah, but remember HR is responsible for more than, right?
- 42:03Joe Bockerstette: So they've got that same sort of challenge across the whole enterprise.
- 42:06Joe Bockerstette: But yes.
- 42:10Michael Hartmann: Yeah, I I mean it's not to dismiss their help.
- 42:14Michael Hartmann: Um I get it.
- 42:16Michael Hartmann: I wouldn't I wouldn't expect them to be to do that.
- 42:19Michael Hartmann: Like that to see that's like that's part of their job of being a leader is to anticipate that and do that.
- 42:25Michael Hartmann: Um interesting.
- 42:27Michael Hartmann: Okay.
- 42:28Michael Hartmann: Um this is maybe fairly tactical, but when you guys do the process mapping piece, uh is there a particular format to use?
- 42:43Michael Hartmann: Do you do you know you say Vizio, so flow diagrams use swim lane stuff?
- 42:48Michael Hartmann: Do you do we we do not?
- 42:50Joe Bockerstette: So we use a uh method we called Paragon.
- 42:54Joe Bockerstette: So Paragon is our name for what we do.
- 42:57Joe Bockerstette: Uh P E R I G O N, which is a 360-degree view of an object, right?
- 43:02Joe Bockerstette: We uh we use Vizio with a Paragon library of uh templates, tools, icons, stencils, like it's our own language.
- 43:14Joe Bockerstette: Our map is a vertical map, uh, very easy to train, very logical to follow, uh, and it stood the test of time for 30 something years now.
- 43:25Joe Bockerstette: It's amazing to me.
- 43:26Joe Bockerstette: It was invented by an electrical engineer who used schematic methodologies for workflow, right?
- 43:34Joe Bockerstette: So it's very, very sound.
- 43:36Joe Bockerstette: We're the only ones in the world that do it the way we do it.
- 43:40Joe Bockerstette: Uh and it's more detailed, more thorough, and more uh illustrative than other maps, much easier to follow.
- 43:51Joe Bockerstette: And then for the backside of the playbook, we use Excel because everybody can use Excel.
- 43:56Joe Bockerstette: And our our method is based on the idea.
- 44:01Joe Bockerstette: It's not that hard to figure out what's wrong.
- 44:02Joe Bockerstette: You just got to ask the people doing the work.
- 44:04Joe Bockerstette: Like there's plenty to work on when you ask somebody, why does just order entry not work?
- 44:09Joe Bockerstette: Yeah, exactly.
- 44:10Joe Bockerstette: Right?
- 44:10Joe Bockerstette: Like, why does why does order entry not work?
- 44:12Joe Bockerstette: Well, oh my God, I can't believe nobody's already, you know, and and it just starts uh spewing.
- 44:18Joe Bockerstette: And so we have no problem figuring out the cause and effect relationships between why things are going wrong and where, right?
- 44:26Joe Bockerstette: And so you're producing a playbook per process and tends to be 30 to 50 pages, although it's digital, uh, and uh it's uh easily updatable, right?
- 44:39Joe Bockerstette: It's it's also easily transferred.
- 44:41Joe Bockerstette: Like we'll train clients to do what we do.
- 44:44Joe Bockerstette: Uh and our goal in general is to start the early work, get the ball rolling, and turn it over to an internal client team to take it and run with it.
- 44:52Michael Hartmann: Got it.
- 44:53Michael Hartmann: All right.
- 44:53Michael Hartmann: Well, let me let me rent like one more question, then we'll wrap up.
- 44:56Michael Hartmann: So I'm curious.
- 44:57Michael Hartmann: So maybe tied to the people I talked about who are in like growth companies.
- 45:03Michael Hartmann: So part of this is going to be a challenge like going from where they are and then they need to scale over time.
- 45:09Joe Bockerstette: Yes.
- 45:09Michael Hartmann: How how what are what are signals they could be looking for when it's tough to rethink the system versus just sort of throw more bodies at it or power through it?
- 45:18Joe Bockerstette: Yeah, that is a great question.
- 45:20Joe Bockerstette: The majority of the work we do in all business systems is that, right?
- 45:24Joe Bockerstette: We are growing rapidly and we've got to do something.
- 45:27Joe Bockerstette: So a couple of signs would be we're fracturing today.
- 45:33Joe Bockerstette: Let's say we're on a Large growth path, and our people are stressed and overworked, and we're seeing some busts in the system, and we're really at our limit.
- 45:44Joe Bockerstette: And so I'm faced with I'm going to say doubling by next year just to pick a big number.
- 45:50Joe Bockerstette: And if I don't change anything, that means I've got to add 50 people or 100 people.
- 45:56Joe Bockerstette: And it doesn't make sense to me, right, that I've got to double my workforce to double my volume, just to again pick a number.
- 46:04Joe Bockerstette: There's got to be a way to scale that I can implement to prevent the need for me to, like, you know, I can't absorb 100 people next year just to pick that number, right?
- 46:17Joe Bockerstette: I've got to find a way to get the work done without that.
- 46:20Joe Bockerstette: And so that really triggers the idea we've got to look at process.
- 46:24Joe Bockerstette: And so we've got to understand our process, we've got to standardize our process, then we've got to automate our process in a way that allows us to super scale without adding a bunch of people.
- 46:37Michael Hartmann: Yeah.
- 46:38Michael Hartmann: That's it.
- 46:38Michael Hartmann: It reminds me of a project I did years ago at a big semiconductor company where I was asked to go figure out how can we how can we enable technical support to support more customers as revenue is growing at a certain pace without because historically it grown at the same pace and they wanted to capture more of the profit from that, right?
- 46:58Michael Hartmann: So they've like venture curve, if you will.
- 47:01Joe Bockerstette: Yeah, the one other point to add on that is if you just throw software on top of that without really understanding the system and the requirements and what your business model is, it just makes a mess.
- 47:13Joe Bockerstette: And it ends up being more of an inhibitor than an enabler, right?
- 47:17Joe Bockerstette: Because I don't put the right switches on, I don't make the right decisions about A, B, or C, and end up with something that uh really makes it difficult to do the right thing.
- 47:27Michael Hartmann: Yeah.
- 47:28Michael Hartmann: No, it's interesting.
- 47:29Michael Hartmann: It's kind of going back to my uh the roots of my early, early consulting career doing process.
- 47:33Michael Hartmann: It's a fun business.
- 47:35Michael Hartmann: Yeah, it's um, you know, to some degree, these like these are it feels like a little bit of fundamentals, but it's good to see that there's like a little more structure for it.
- 47:43Michael Hartmann: Yeah, Joe, been a been a pleasure talking to you.
- 47:46Michael Hartmann: If folks want to if they're interested in continuing the conversation or just want to learn more about what you're doing, what's the best way for them to do that?
- 47:54Joe Bockerstette: Yeah, so it's www.businessmapping.com and my email is Joe at businessmapping.com.
- 48:00Joe Bockerstette: Just feel free to reach out.
- 48:01Joe Bockerstette: It's been a pleasure.
- 48:02Michael Hartmann: All right, good.
- 48:03Michael Hartmann: Well, I appreciate it.
- 48:03Michael Hartmann: Again, Joe, thank you.
- 48:04Michael Hartmann: Thanks to our audience out there for continuing to support us.
- 48:08Michael Hartmann: We appreciate it.
- 48:09Michael Hartmann: If you have ideas for topics or guests or want to be a guest like Joe, please reach out and we'd be happy to get the ball rolling.
- 48:14Michael Hartmann: Till next time.
- 48:15Michael Hartmann: Bye, everybody.