Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

What Is Agile Marketing

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

This ISN’T Agile Marketing

First, a couple of clarifications and myth-busting. Agile Marketing isn’t reactive marketing. Agile Marketing isn’t about how you react in a Marketing/PR crisis (ask United about those) or real-time opportunity (you can ask Oreo about those). I don’t mean that you can not/shouldn’t deal with those when you’re doing Agile Marketing, but it isn’t what Agile Marketing is about.

Agile Marketing also isn’t “We just get things done without any real process.” Being super-responsive and saying “yes we can” all the time isn’t Agile Marketing. (Especially if it means an unsustainable pace).

Finally, Agile Marketing also isn’t Scrum, Daily Scrums/Standups, Sprints, Scrum Masters, or Kanban Boards. It isn’t a methodology or even a framework.

What IS Agile Marketing? 

I like to think of Agile Marketing as an approach. Based on the same empiric and flow-oriented thinking and mindset behind Agile Development,  Agile Marketing manages for uncertainty through iterating, anticipating, and adaptation. Let’s start with why this sort of empiric approach is needed in marketing.

Why do marketers need Agile Marketing?

Here’s what we hear from marketers trying to optimize the impact they’re delivering for their organization:

  • Marketers struggle to deal with an onslaught of customer needs, partner demands, and requests from other parts of the organization. They need a flexible yet disciplined way to deal with this demand that is always outstripping their capacity. Balancing responsiveness with the ability to deliver on planned work is becoming harder and harder.
  • Marketers tell us they understand that they’re making a lot of leap-of-faith assumptions while their process is based on conventions, opinions, and upfront/static predictions. They want to create a culture of data-driven decision-making and validated learning, but that’s easier said than done with traditional marketing plans and schedules.
  • Marketers are frustrated with their lack of ability to “close the whole loop.” They have lots of dependencies on other marketing functions and non-marketing functions in and outside their organization. All these dependencies create delays, waste, and frustration.
  • Marketers are dealing with more and more technology. According to Scott Brinker’s latest Marketing Technology Supergraphic, there are now over 8000 marketing technology solutions. How do you select the right ones, manage the vendors and integrate them?
  • Marketers need to accelerate to match the pace of the Technology organization. As their technology/development organizations adopt more and more of the Lean/Agile/DevOps practices, marketers feel overwhelmed by the pace of delivery and change and look for ways to better align to a Lean/Agile technology/product organization.
  • As marketers, we constantly work in “hero mode” – we work long hours, lose our ability to be creative, and eventually burn out. The result is unhappy marketers AND stakeholders.

A lot of what marketers are facing is related to rising complexity and uncertainty in marketing work. Let’s explore that in more depth.

Dealing with uncertainty around WHAT marketing experience to deliver

The diagram above is called the Stacey Matrix (see a Sam Laing description back in 2013 or on my personal blog). It shows that traditional planned/defined approaches aren’t a good fit when facing the complexity that results from medium/high uncertainty. Specifically, the Stacey matrix maps two aspects – WHAT and HOW.

WHAT relates to questions around what our customer journey experience should look like. Well-understood and agreed on means that we have very high certainty around what experience would streamline our customer’s buying journey. Vague or not understood means we might think we know, but we’re not sure, or even that we don’t know what experience we’re looking for.

Dealing with uncertainty around HOW to deliver the marketing experience

HOW relates to questions around implementation. Here, a big part of the challenge is the growth of the marketing technology stack. As Molly Walsh asks, How the heck did we get here? Most marketing organizations are struggling to implement their marketing plays. The more technologies in your stack, the more moving parts, the more uncertainty around fitting the pieces together.

As you can see, once you have both WHAT and HOW uncertainty, you’re well into the complex space. In the complex space, planning upfront wields limited results as you can’t predict what would work in advance. You can plan your objectives/goals/investments, but even that would change as the landscape changes.

Agile Marketing – Anticipating Complexity/Uncertainty and Dealing with it using Iteration/Adaptation

Agile Marketing leverages Empiricism – Agile Marketers anticipate complexity/uncertainty and deal with it in a disciplined pragmatic, sustainable manner.

They work iteratively. Starting with a plan based on hypotheses. Quickly creating a small increment that aims to validate WHAT-related and HOW-related assumptions using a thin slice of the marketing campaign/play they’re working on.

Creating transparency by reviewing this increment with stakeholders and ideally testing it out in the real world.

Inspecting where they actually are based on this increment and adjust course accordingly.

Agile Marketers cherish Transparency, Inspection, and Adaptation – the pillars of Empiricism.

They and their leaders work to create a culture of trust, openness, courage, and respect required to enable empiricism.

Agile Marketing requires organizing your work and your teams differently

Agile Marketers work in Teams that cut across multiple marketing and other business functions enable customer-focused collaboration.

They replace the handoffs you might find in a relay race with the collaborative play you see in rugby (or basketball or soccer). These agile marketing teams are designed to be cohesive and autonomous.

They deliver increments of valuable marketing outcomes with minimal outside dependencies.

We call them A-Teams – A for autonomous, authorized, able, and aligned.

The Agile Marketing Manifesto

While several practitioners used Agile in Marketing more than 10 years ago, Agile Marketing was officially born in 2012 with the creation of the Agile Marketing Manifesto during the SprintZero event.

The Agile Marketing Manifesto emphasizes/values some new marketing approaches that are replacing some well-entrenched marketing conventions. This is actually aligned with what Marketing leaders such as Sergio Zyman have been advocating for. If you read Sergio’s “The End of Marketing As We Know It”  from back in 2000, you will find hints of Agile Marketing!

 

Validated Learning, Customer Discovery With Many Small Experiments, Leading to Adaptive and Iterative Campaigns

The Agile Marketing Manifesto introduces concepts such as validated learning (which is brought over from the Lean Startup approach) – replacing decisions made just based on opinions and conventions with a process of looking at each marketing play, identifying risks/assumptions, then for the risky plays going into a Build-Measure-Learn experimentation iterative loop where marketers try to validate as quickly as possible whether their thinking and assumptions are correct.

Upon validation, the play can be completed and scaled. In case of invalidation, the play can be tweaked/changed in a “Pivot” to continue to look for a winning play.

This is called “Fire bullets (and only) then fire cannonballs” in Jim Collins’s Great By Choice.

When there’s less risk, it still makes sense to deliver incrementally – you want to minimize the cost of delays between the time you decide to execute a marketing play/campaign and the time you’re able to go to the market. If you can deliver some minimal play/campaign that can already start to impact your customer journey/brand, you want to do that.

 

Agile Marketing Isn’t Easy To Digest.

This seemingly goes against marketing conventions like “nailing the perfect campaign and only then launching it with a big bang” and “protecting our brand by only releasing high-quality marketing content.”

Why seemingly? because, in spirit, the agile marketing approach is actually more aligned with the rationale behind these conventions.
Using adaptive iterative campaigns, leverage small experiments to make sure “we nailed it” and only then “launching with a big bang” still looks like a “big bang” to most of the market.

Also, you get the advantage of having a higher chance of success since it was validated in the real world, thereby protecting the brand by reducing the chance of spectacular failure upon the big bang launch. (e.g., Pepsi’s controversial ad or New Coke – both smartly pulled from the market pretty quickly after considerable sunk costs).

We HAVE to be able to adapt.

It might feel uncomfortable, but we must find a way to do it. The key to doing it well is to slice experiences in a way that you’re still delivering a great experience but only for a small slice of the market or some part of their needs but in a way that is representative of the wider audience/experience so that you can learn and improve your plans/designs based on it. (e.g., just in one city, just for one type of user of your product, just as an experiment in one airport, whatever).

Being able to craft meaningful, high-quality experiences that are still smaller than the “full thing” is one of the agile marketer’s non-trivial yet important skills.

There’s a lot of applicable learning in this domain from what startups and enterprises see trying to adopt “Lean Startup” and “Minimum Viable Product” thinking. Still, it comes down to innovative, creative thinking by marketers to develop the right tactics that can help them test their strategies without risking the brand or diminishing the overall impact of the overall marketing campaign.

Customer Focused Collaboration

Agile Marketing brings together marketers and other players to collaborate on improving customer experiences. If you were ever a sole marketer for a company or part of a small startup/company marketing team, you know what this looks like. You can move much faster when you need to deliver the overall marketing impact on your team (or in your head). Most marketing organizations lose this advantage when they grow beyond the single team and specialize.

Agile Marketing requires Lean/Agile Leadership.

Agile Marketing tries to bring back this effectiveness, speed, fun, and focus of the small startup regardless of your organization’s size. We create autonomous agile marketing teams empowered to make local decisions aligned with achieving their goals while doing what’s right for the overall brand. This only works if we:

  • build the right competence by hiring the right people and encouraging them to master their domain, and giving them the space to learn and improve
  • create high clarity by sharing the business context, our vision, and constraints.

This autonomy and new structure don’t mean there’s no need for marketing managers/directors, of course. It does mean changes in their focus, e.g., on hiring and nurturing great marketers and providing a clear and meaningful mission/purpose.

Customer-focus teams can take many shapes.

Those customer-focused teams own aspects such as:

  • the whole customer journey for a certain brand/product/market (e.g., SMB)
  • Content Creation, Publication, Measurement
  • A key marketing challenge/opportunity is a stuck Middle of the Funnel (MOFU), ineffective Sales Enablement.
  • Account-Based Everything (ABX)
  • Planning and delivering the company’s Customer event or presence at a key industry event
  • Exploration of a new marketing approach such as “Social Selling,” and “Video.”
  • A key marketing KPI that is not performing well or is identified as a key objective for growth.

While we call it Agile Marketing, in many cases, these teams include and involve participants from other adjacent functions such as Inside Sales, Product Management, Customer Success.

From tasks to Customer-focused stories

Once the marketing organization work structure is oriented towards a customer-focus – Agile Marketers start managing their work in a customer-focused way. They use work items that reflect marketing value, such as “User Stories” or “Job Stories” rather than “to-do lists” or “tasks.” Thinking of work in this way and including the goal/impact expected of each work item as part of the “Story” helps marketers maintain a laser-focus on the customer impact they’re aiming for – day in and day out. This also makes it easier to communicate with business stakeholders about what marketing is focusing on and get their early feedback and guidance – which helps avoid the common situation where marketers talk in language that business/sales don’t care about and after delivering something there are still major gaps between what the business/sales expected and the marketing that was delivered.

Agile Marketers also use more disciplined and more customer-focused prioritization mechanisms that take into account considerations such as Cost of Delay, Time Criticality, Opportunities, and Risks addressed to consider what to focus on next and whether to interrupt ongoing work for an emerging opportunity.

Continuous Planning

While some marketers understand agile marketing to mean “no planning,” this is not the intent. The Agile Marketing Manifesto talks about “Responding To Change” over “Following The Plan.” Another way to look at it is “Flexible” or “Continuous” Planning vs. “Rigid Static Planning.”

Agile Marketers plan at multiple levels oriented both around timeboxes (day, week, quarter) or content (campaign, launch, play). Planning might happen on a cadence or just-in-time. But as a general rule, Agile Marketers plan just enough just in time.

Agile Marketers use specific techniques such as Kanban, Scrum, and sometimes a higher-level framework such as SAFe (Scaled Agile Framework) to plan their work.

Subscribe for Email Updates:

Categories:

Tags:

DevOps
ALM Tools
WIP
lean agile change management
ATDD
EOS®
predictability
Lean Budgeting
Scrum Values
Limiting Work in Progress
Covid19
Jira
The Agile Coach
Managing Risk on Agile Projects
Nexus vs SAFe
Slides
Self-organization
Agile Contracts Best Practices
Value Streams
Agile Project Management
Agile Games and Exercises
Kaizen Workshop
Amdocs
Agile Delivery
Change Management
RSA
Software Development
Lean Agile Basics
Operational Value Stream
Presentation
Agile Release Planning
Development Value Streams
Accelerate Value Delivery At Scale
Releases Using Lean
Keith Sawyer
Lean Agile Organization
Agile Exercises
A Kanban System for Software Engineering
agileisrael
Planning
Agile Israel Events
Lean and Agile Principles and Practices
Kanban 101
Agile Assembly Architecture
Risk Management in Kanban
Continuous Deployment
Professional Scrum Master
Agile Product Ownership
Artificial Intelligence
Implementation of Lean and Agile
Continuous Delivery
Agile Project
Achieve Business Agility
Agile India
Nexus
Process Improvement
Lean Risk Management
Manage Budget Creation
Professional Scrum with Kanban
Sprint Retrospectives
Sprint Iteration
Risk Management on Agile Projects
Program Increment
Managing Projects
Games and Exercises
Atlassian
chatgpt
Kanban Game
Acceptance Test-Driven Development
Nexus and SAFe
Nexus and Kanban
Agile in the Enterprise
Lean-Agile Budgeting
Webinar
Lean Startup
Continuous Planning
Agile Marketing
Lean Agile Management
IT Operations
Agile Games
Agile and DevOps Journey
Agile Techniques
Tips
Agile Community
Reading List
SPC
PI Objectives
QA
NIT
Team Flow
Introduction to ATDD
Lean-Agile Software Development
ScrumMaster Tales
Introduction to Test Driven Development
speed at scale
BDD
Scrum Master
Lean and Agile Techniques
Hybrid Work
Professional Scrum Product Owner
Rapid RTC
Release Train Engineer
Entrepreneurial Operating System®
Scrum With Kanban
ATDD vs. BDD
Agile Outsourcing
Applying Agile Methodology
Quality Assurance
AgileSparks
ART Success
System Team
Large Scale Scrum
RTE Role
Agile Release Management
SAFe DevOps
LeSS
AI Artificial Intelligence
Agile Development
Software Development Estimation
The Kanban Method
Elastic Leadership
Jira admin
Scrum and XP
Spotify
Agile
PI Planning
An Appreciative Retrospective
Kaizen
Iterative Incremental Development
Agile for Embedded Systems
Kanban Kickstart Example
Enterprise DevOps
Product Management
SAFe Release Planning
Lean Agile Leadership
Legacy Code
Agile Basics
Principles of Lean-Agile Leadership
POPM
Agile Mindset
Scrum.org
Continuous Improvement
Built-In Quality
ROI
Jira Plans
Risk-aware Product Development
Tools
Atlaassian
Certification
RTE
Daily Scrum
Portfolio for Jira
Lean Software Development
Sprint Planning
speed @ scale
LAB
System Integration Environments
User stories
Engineering Practices
Implementing SAFe
Scrum Primer
Advanced Roadmaps
Agile Testing Practices
Video
Kanban
Effective Agile Retrospectives
Scrum
Certified SAFe
ARTs
Scrum Guide
Continuous Integration
Product Ownership
Agility
Pomodoro Technique
Perfection Game
Story Slicing
What Is Kanban
Scaled Agile Framework
Agile Israel
Frameworks
Agile Risk Management
Legacy Enterprise
Scrum Master Role
Jira Cloud
SA
Lean Agile
AI
GanttBan
LPM
Systems Thinking
Code
Coaching Agile Teams
System Archetypes
Business Agility
Test Driven Development
Kanban Basics
Agile Product Development
Nexus Integration Team
TDD
Agile Program
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart