Martech enablement series: Part 6 — Building the car

Posted by

Welcome to Part 6 of: “A Nine Part Practical Guide to Martech Enablement.” This is a progressive guide, with each part building on the previous sections and focused on outlining a process to build a data-driven, technology-driven marketing organization within your company. Below is a list of the previous articles for your reference:

In the previous parts, we looked at how your martech team is a parallel to an automobile race team. So far, we’ve dug into how a race team constructs their team and then builds a strategy for winning their individual races and the overall race series. We’ve compared how these practices are similar to a successful approach to constructing and strategizing for a martech team, identifying this as the “martech enablement” process.

As we continue with this guide in the next two parts, we’ll discuss the “car” of the race team and how this corresponds to your marketing organization’s martech stack.

It would seem silly if I discussed martech stacks and didn’t mention the great work that Scott Brinker has done in helping us all understand the products available in the arena of martech. The “Martech Landscape” he has been producing since 2007 is clearly the de facto work that provides marketing organizations insight into the vast array of tools available to improve their marketing efforts. I can’t wait to see how the martech product landscape evolves. Brinker will surely be right there helping make sense of it all.

If we go all the way back to Part 1 of this guide, we discussed how ultimately martech enablement success boils down to insights and actions. What we understand (insights) about the race track we’re traveling on and how we respond (actions) will determine whether we win the race.

In this part, Part 6, as we discuss the car and technology, we’ll look at the systems of the car and your martech stack that enable you to take action. In Part 7 of this series, we will discuss the systems that support insights like dashboarding, KPI measurement, analytics and collaboration tools. Let’s get started.

Building the car

As this guide has been progressing, I’ve been asked several times about the order of the martech enablement process: “Why does that stack come last?” The answer is simple. As Stephen Covey’s book, “The 7 Habits of Highly Effective People,” says: “Begin with the end in mind.”

To understand the type of car a race team will need, you first must understand the kind of race you’re going to run. This is best determined by the team, which must be in place first. It would be silly to build an Indy car only to realize you’re racing a 100-day, all-terrain rally around the world. People, then strategy, then car and technology.

People -> Strategy -> Technology

This top-down approach (rather than letting the car/technology define the strategy and team) is, in my experience, the best way to approach martech enablement. I do realize that it is rare that marketing organizations are “greenfields” when it comes to martech stacks and products. You likely have many martech products currently in use.

“Getting better value” out of your existing investments might seem a logical goal for your martech enablement initiatives. Resist the urge to start there. This approach often results in misguided efforts that rarely hit the mark because they aren’t driven by your team objectives.

Instead, insist that your team objectives drive the need for modifications to your martech stack. This will ultimately result in getting better value out of your existing and future martech stack. In a later part of this guide, I’ll discuss how to enable your team and strategy to incrementally improve your existing stack to support your team objectives.

Safety first

When it comes to racing, it seems that a primary focus on speed and winning is all that’s needed. I think it’s appropriate to start off with a discussion about safety.

In racing, the well-being of the team is, without question, a paramount consideration. This isn’t just about the driver’s safety, either. It’s the safety of the pit crew and other team members. I don’t have to go into detail about the impact of a serious injury or death of a race team member. It’s severe.

Each racing team has its safety experts. Additionally, overarching race organizations such as Indy, Leman and NASCAR have their own race safety teams. The role of these personnel is to collaborate on safety equipment, technology, procedures and protocols.

So, too, is the case with safety in martech. Start with a mindset of safety first.

A few areas to focus on are:

  • internal governance — Systems, policies, procedures and protocols for how martech is managed in your organization.
  • regulatory compliance — Many industries have governmental regulation mandates.
  • legal compliance — All organizations have varying degrees of legal compliance requirements to follow as a risk mitigation strategy.
  • security — Protecting your organization from attacks and breaches.
  • disaster recovery — Preparation for unforeseen events that would interrupt business continuity.

A few words about the GDPR

Speaking of safety, there is a major regulatory compliance issue on the horizon. If you haven’t heard of the GDPR (General Data Protection Regulation), you will. This legislation passed in the EU goes into effect on May 25, 2018, with the intention of regulating how companies protect EU citizens’ data.

This will have a large impact on martech for companies that interact with people who reside within EU countries. It’s a serious piece of legislation that you should learn about. There are manygoodarticles on this site that will help you get familiar with GDPR and its impact.

The car

As has been the case across this guide, there are distinct parallels between the parts of a race team and your marketing organization. The car (structure) and technology (systems) that allow you to take action are no different.

When looking at a race car, the core systems can be broken down into three main categories:

  • Chassis — The frame, suspension and body
  • Powertrain — Engine and transmission
  • Control systems — Fuel, steering, braking

The chassis provides the foundation and structure for the car, with the powertrain providing propulsion and power. The control systems allow the driver to take action with the car, making it accelerate, turn/pivot and decelerate. A martech stack has a corresponding chassis, powertrain and control systems as well.

I think it’s important to state that I’m not going to exhaustively explain what each product type is and does. This article would become too long and unreadable. Much has been written about the value proposition of each of these systems.

What I will discuss is the strategy around using these products and how they interplay to create a cohesive and unified martech stack upon which to execute your martech strategy and achieve your team and organizational objectives. Let’s dig in and begin to see how these three systems come together to build a functional and flexible martech stack.

The chassis

As I mentioned, the chassis is the structure upon which the rest of the car is built. In the process of martech enablement, the chassis part of martech stacks is the products that are used to house and manage data. These products are the core of your martech stack and generally serve as the foundation all other martech technology is reliant on.

Below is a list of the types of products that fall into the “chassis” category in your martech stack. Buckle up, you are now entering the wide world of acronyms:

  • CRM — Custom Relationship Management
  • CDP — Customer Data Platform
  • ERP — Enterprise Resource Planning
  • DAM — Digital Asset Management
  • PIM — Product Information Management
  • DMP — Data Management Platform

The first question I expect to get asked is, “Why isn’t MAP (Marketing Automation Platform) or an e-commerce platform on this list?” While I agree that both these platforms house data, I prefer to categorize them in the Powertrain category as their primary roles in your martech stack are as automation and delivery tools. The fact that they store data is an incidental (albeit important) requirement, not their core intended use.

This brings up another topic: data strategy. This is what the chassis is all about.

[Read the full article on MarTech Today.]

Some opinions expressed in this article may be those of a guest author and not necessarily Marketing Land. Staff authors are listed here.

About The Author

Peter Ladka founded GeekHive in 1997 as a small startup, and today they’re a leading technology partner, focusing on strategic martech initiatives for some of the biggest brands and agencies in the world. As President, Peter focuses on strategic business management and developing strong partner and client relationships for the GeekHive brand. Peter remains deeply committed to the values on which GeekHive was founded; offer high-quality service to their clients and provide opportunities for meaningful growth for their employees.


Leave a Reply

Your email address will not be published. Required fields are marked *