I spent two productive days this week at Demand Gen Report’s B2B Content2Conversion Conference in New York. As some who spends more time creating content than pondering it, I appreciated the opportunity to put content generation in a more broader perspective.
Sessions at the conference were consistently excellent, which isn’t the case at every show. Here some of the key points that stuck with me:
- Take control of the conversation. Brent Adamson of the CEB presented the Challenger Sales and Marketing models, which have been around for a few years now but still impress me. The gist of the model is that marketers and sales people need to disrupt the normal purchase process by convincing buyers that they’re doing something wrong, it’s costing them money, and the seller’s product can fix it. Without that disruption, buyers will view competitive products as commodities. This notion of disruption is what separates the Challenger approach from conventional solution selling. It gives a strategic focus to your content planning, and readers of this blog know I’m a sucker for strategic focus.
- Measure wisely. Jim Lenskold of the Lenskold Group offered a detailed framework for ensuring that content marketing measurements tie to actual business objectives. The critical point is those objectives vary in different situations, so marketers need to be very purposeful in deciding which measure apply in each situation. In case you’re wondering, yes, that’s a lot of work. But this is one of those “eat your vegetables” situations where there’s not much value in taking shortcuts. I'm a big fan of other people eating their vegetables.
- Buying processes differ with market maturity. Matt Papertsian of SiriusDecisions refined the now-cliched notion of buyers taking control of the purchase process, pointing out that it really depends on how well they understand what they’re buying. Buyers are in control in an established market, where they can easily assess the alternatives. But when sellers are offering something new, they can – in fact, must – educate buyers about why they need what the seller is selling. This elevates the role of sales people and means they should be engaged earlier in the buying process. It also echoes the Challenger Sales process while suggesting that the Challenger approach will work better in some circumstances than others. Naturally, content should be adjusted to the type of buying process as well.
Other sessions offered practical advice and case histories on how to succeed with marketing content. They were all good, too, but I’m a big picture kind of person. I look forward to applying these concepts at Raab Associates over the coming year.
Incidentally, Demand Gen Report will be moving the conference from New York to Scottsdale, AZ for its next session, which will be February 16-19, 2015. Definitely worth the trip.
Showing posts with label marketing strategy. Show all posts
Showing posts with label marketing strategy. Show all posts
Thursday, May 08, 2014
Tuesday, April 15, 2014
Matching Marketing Technology to Business Strategy: A Starting Framework
As you may know, I’m working with Scott Brinker of Chief Martech blog fame and Third Door Media on the MarTech marketing technology conference set for August 19-20 in Boston.*
When Scott asked for content suggestions during the early stages of the conference planning, my reaction was that one thing everyone needs is a framework for relating marketing technology investments to larger business strategy. Scott was flatteringly enthusiastic and – I totally should have seen this coming – came back two weeks later with the suggestion that I present such a framework.
Bluff called.
Every consulting engagement I do starts with the relationship between business strategy and marketing technology.** But I've always defined it on a case-by-case basis. Until Scott asked, I never had a reason to create the framework for a generalized approach.
So, where to begin? The first thing to remember about strategies is that they’re about making choices: a strategy is a method for reaching a goal; knowing the method gives you a way to decide whether a particular choice is consistent with it. More concretely, “make money” is a goal; “make money by building high quality products for which customers will pay a premium” is a strategy. Even a strategy as simple as that one tells you a great deal about where to invest, what kinds of systems to build, what kinds of marketing to perform, whom to hire, and much else. I do this analysis for my clients so we can be sure to find marketing systems that are consistent with their business approach and resources.
But here’s the thing: just about every discussion of marketing technology starts off with the (true) fact that today's customers demand a highly personalized experience informed by detailed knowledge of their history. The implication is that every business needs to adapt a strategy of customer intimacy. But if everyone has the same business strategy, then shouldn’t everyone use the same technology strategy as well?
[crickets]
I think the answer is no, for two reasons. First, everyone doesn’t have the same business strategy. Second, even the same business strategy could result in different technology approaches.
• Business strategies still differ. It’s true that customers today expect every company to track their interactions and respond intelligently across all touchpoints.† But precisely because that expectation is universal, meeting it isn’t enough by itself to be a successful strategy. Remember, strategy is about choices and there’s no choice about whether to meet those expectations. It's HOW you meet those expectations that involves choices that are strategy-driven.
• Tech strategies can vary for the same business strategy. Let’s say your business strategy is to be a low cost provider. You still have to deliver a reasonable degree of customer intimacy, just as you still have to deliver a reasonable degree of product quality. In this case, the goal of your tech strategy is always the same: “to deliver customer intimacy at low cost”. But the method could be “through extensive automation”, “through low labor cost via outsourcing”, or “through limiting services provided”. Each would imply a different technical approach.
Okay, the notion of a strategy-to-technology framework seems to make sense. [cheers] So what would that framework actually look like?
It would start with strategic options. The classic big three are high quality, low cost, and high service (i.e., close customer relationships). Each implies different requirements for marketing, product design, production, customer support, and administration, which in turn drive technology, core competencies, and organization.††
Those requirements are the goals of the technology strategies. Methods to meet them are technology options, such as integrated suites, best of breed systems, and platforms-and-apps. These are modified by other parameters such as in-house vs. outsource, scope of channels, sophistication level, resources, and scale. Note that some of these are choices while others are constraints.
The really critical challenge in setting your technology strategy is understanding the implications of each option so you can pick the technology strategy that best meets the business strategy requirements. Once the technology strategy is chosen, the final step is mapping the choices to the different layers of the marketing technology architecture: Data, Decisions, and Deployment (I just made that up but we all adore alliteration). The resulting framework would indeed be specific enough to give useful guidance. [more cheers]
I’m guessing this sounds like gibberish to at least some of you. Fair enough. Here’s an example of the framework for an online retailer trying to compete with Amazon by offering customers even lower prices. As you read this chart from left to right, each column provides guidance to the column that follows it.
The recommended strategy in this example is to buy an integrated suite and outsource its operation, accepting limited flexibility in return for lowest possible cost. You might not feel that suites actually give the lowest cost, but that's okay. In fact, I recommended a suite specifically to make the point that the platform-and-app architecture seen as the future of marketing tech by many people (myself definitely included) isn’t always the right solution. Nor, alas, can a framework force you to make the best choice. What it can do is provide clarity about the options being chosen, so people can argue their case if they disagree, and then pull in the same direction once a decision is made.
So that’s what I’m thinking at the moment. It could well change by the time I reach Boston in August. Join us then and find out.
______________________________________________________________________________
* The conference will provide a much-needed vendor-agnostic forum for understanding marketing technologies and how organizations can use best them. If you’re reading this blog, you should attend. Click here for more info and early bird pricing.
** You do know I make my living by helping companies define their marketing technology requirements and select tools, right? Some people seem not to realize this.
† Well, maybe not every company. Some still don’t identify individual customers. But even former bastions of anonymity like consumer packaged goods manufacturers now increasingly connect to customers through targeted advertising, social media, and promotions. So we can modify the claim to state that customers expect this tracking when they know the data could be available. It doesn’t change the rest of this analysis.
†† This is all basic “strategy map” stuff based on work by Robert S. Kaplan and David P. Norton. Wikipedia tells me that strategy maps are obsolete but I still find them useful.
When Scott asked for content suggestions during the early stages of the conference planning, my reaction was that one thing everyone needs is a framework for relating marketing technology investments to larger business strategy. Scott was flatteringly enthusiastic and – I totally should have seen this coming – came back two weeks later with the suggestion that I present such a framework.
Bluff called.
Every consulting engagement I do starts with the relationship between business strategy and marketing technology.** But I've always defined it on a case-by-case basis. Until Scott asked, I never had a reason to create the framework for a generalized approach.
So, where to begin? The first thing to remember about strategies is that they’re about making choices: a strategy is a method for reaching a goal; knowing the method gives you a way to decide whether a particular choice is consistent with it. More concretely, “make money” is a goal; “make money by building high quality products for which customers will pay a premium” is a strategy. Even a strategy as simple as that one tells you a great deal about where to invest, what kinds of systems to build, what kinds of marketing to perform, whom to hire, and much else. I do this analysis for my clients so we can be sure to find marketing systems that are consistent with their business approach and resources.
But here’s the thing: just about every discussion of marketing technology starts off with the (true) fact that today's customers demand a highly personalized experience informed by detailed knowledge of their history. The implication is that every business needs to adapt a strategy of customer intimacy. But if everyone has the same business strategy, then shouldn’t everyone use the same technology strategy as well?
[crickets]
I think the answer is no, for two reasons. First, everyone doesn’t have the same business strategy. Second, even the same business strategy could result in different technology approaches.
• Business strategies still differ. It’s true that customers today expect every company to track their interactions and respond intelligently across all touchpoints.† But precisely because that expectation is universal, meeting it isn’t enough by itself to be a successful strategy. Remember, strategy is about choices and there’s no choice about whether to meet those expectations. It's HOW you meet those expectations that involves choices that are strategy-driven.
• Tech strategies can vary for the same business strategy. Let’s say your business strategy is to be a low cost provider. You still have to deliver a reasonable degree of customer intimacy, just as you still have to deliver a reasonable degree of product quality. In this case, the goal of your tech strategy is always the same: “to deliver customer intimacy at low cost”. But the method could be “through extensive automation”, “through low labor cost via outsourcing”, or “through limiting services provided”. Each would imply a different technical approach.
Okay, the notion of a strategy-to-technology framework seems to make sense. [cheers] So what would that framework actually look like?
It would start with strategic options. The classic big three are high quality, low cost, and high service (i.e., close customer relationships). Each implies different requirements for marketing, product design, production, customer support, and administration, which in turn drive technology, core competencies, and organization.††
Those requirements are the goals of the technology strategies. Methods to meet them are technology options, such as integrated suites, best of breed systems, and platforms-and-apps. These are modified by other parameters such as in-house vs. outsource, scope of channels, sophistication level, resources, and scale. Note that some of these are choices while others are constraints.
The really critical challenge in setting your technology strategy is understanding the implications of each option so you can pick the technology strategy that best meets the business strategy requirements. Once the technology strategy is chosen, the final step is mapping the choices to the different layers of the marketing technology architecture: Data, Decisions, and Deployment (I just made that up but we all adore alliteration). The resulting framework would indeed be specific enough to give useful guidance. [more cheers]
I’m guessing this sounds like gibberish to at least some of you. Fair enough. Here’s an example of the framework for an online retailer trying to compete with Amazon by offering customers even lower prices. As you read this chart from left to right, each column provides guidance to the column that follows it.
The recommended strategy in this example is to buy an integrated suite and outsource its operation, accepting limited flexibility in return for lowest possible cost. You might not feel that suites actually give the lowest cost, but that's okay. In fact, I recommended a suite specifically to make the point that the platform-and-app architecture seen as the future of marketing tech by many people (myself definitely included) isn’t always the right solution. Nor, alas, can a framework force you to make the best choice. What it can do is provide clarity about the options being chosen, so people can argue their case if they disagree, and then pull in the same direction once a decision is made.
So that’s what I’m thinking at the moment. It could well change by the time I reach Boston in August. Join us then and find out.
______________________________________________________________________________
* The conference will provide a much-needed vendor-agnostic forum for understanding marketing technologies and how organizations can use best them. If you’re reading this blog, you should attend. Click here for more info and early bird pricing.
** You do know I make my living by helping companies define their marketing technology requirements and select tools, right? Some people seem not to realize this.
† Well, maybe not every company. Some still don’t identify individual customers. But even former bastions of anonymity like consumer packaged goods manufacturers now increasingly connect to customers through targeted advertising, social media, and promotions. So we can modify the claim to state that customers expect this tracking when they know the data could be available. It doesn’t change the rest of this analysis.
†† This is all basic “strategy map” stuff based on work by Robert S. Kaplan and David P. Norton. Wikipedia tells me that strategy maps are obsolete but I still find them useful.
Subscribe to:
Posts (Atom)


