Marketing work is never done. At any given moment, you probably have multiple omnichannel campaigns running alongside the daily grind of managing all the deliverables needed to launch new engagement or win-back campaigns. And then, to top it all off, the only thing everyone wants to talk about is the latest movie in theaters.
You literally cannot afford to have a process that takes two weeks to build an email, have it approved it, test it, then deploy. By the time you launch, everyone’s moved on to talking about the latest hyper-casual game. And suddenly your movie-themed campaign is rendered irrelevant.
How does one manage omnichannel marketing campaigns at this pace?
There are ways for growth and marketing teams to deal with the constant onslaught deadlines while coping with constantly changing customer needs. And one of the most potent methods available is Agile marketing.
Agile marketing is the use of data to continuously improve on your campaigns by deploying tests more quickly, evaluating results, and rapidly introducing the data-backed revisions.
This is an offshoot of Agile – a project management method that was primarily created for the development of software but which the larger business world adopted once it became obvious how effective it was in streamlining processes and delivering work.
Agile marketing is simply using the Agile philosophy within your marketing campaigns and tactics so that you create value for your users at every step, no matter how needs or tastes change.
To better understand it, we need to find out where it started.
Agile began in the early days of software development when multi-million-dollar programs would be shipped so late and so over budget that customers’ needs had changed by the time the software was released.
Thus, 17 developers gathered in 2001 and put their heads together to find a better way. They came up with the Agile Manifesto – a formal document outlining 12 principles for building software efficiently so that it could provide value to customers, ship on time, and meet the budget.01
The Agile Manifesto was not a prescriptive tutorial on how to deliver software. It merely listed guiding principles that helped workers prioritize tasks. They were, in effect, guidelines on how to be an effective, and customer-focused team.
In general, those guiding principles can be condensed into four pillars that all Agile methodologies share:
When you put the principles of the above idea into action, you have a frame upon which to hang your process and tools.
But why learn something new like Agile? And why subject your marketing/growth team to a radical change in the way you do things?
Because the benefits – to both customers and your own marketing team – are huge.
One thing to remember: since the Agile Manifesto wasn’t prescriptive, there has been an abundance of methodologies that popped up over the years to better codify the Manifesto’s principles into an actual process.
Thus you’ll hear about some of the more popular methodologies such as Scrum, Lean, or Kanban.
But there are also many others that are less mentioned outside of project management experts. Those other methods include: Crystal, Six Sigma, Feature Driven Development, Extreme Programming (XP), Dynamic Systems Development Method (DSDM), and more.
After all that information, what are the actual nuts-and-bolts of turning your growth team into an Agile team?
Well, it depends on the methodology you choose to follow.
For this article, we’ll assume you go with the Scrum method, arguably the most popular Agile process around. Here’s what you would need to have to kick things off:
First off, you need the right number of team members. The team should be large enough to be effective at implementing a complete marketing campaign from scratch. But it also needs to be small enough so that everyone is accountable to one another.
Ideally, this means anywhere from a minimum of three to a maximum of 10 people. If you have more than that, your meetings become unwieldy, and the work gets bogged down by too many cooks.
An Agile team will require people to take on some basic roles:
For Agile to work, it needs to be done in quick cycles, called “sprints.” A marketing sprint is typically a week or even two weeks long. Sprints are this length so they give the team enough time to get a sufficient amount of work done, but shouldn’t be long enough for projects to drag on needlessly.
During every sprint, deliverables are agreed upon before work commences. These are due by the end of the sprint and cannot be revised. All new requests for work will be tackled in the next sprint, using a defined intake process.
Part of the Agile experience is building a spirit of transparency among team members. This is done via the daily standup meeting, which should last 10-15 minutes only. The Scrum master ensures meetings stick to this limit.
The standup meeting is conducted without sitting down, so no one gets too comfy and starts talking lengthily. And each member gets two to three minutes maximum to go over:
The Scrum master then takes on the mentioned roadblocks and will work on clearing them so that work can continue.
To track what’s being done and what’s coming next, an Agile team will make use of a visual task board – either a physical or virtual Kanban board separated into columns such as (but not limited to): backlog, in process, on hold, and done.
Each task is on an individual card (or sticky note) and is moved through the columns as each phase of the work gets done.
The idea is to break down a large campaign into smaller, manageable chunks so you get it done incrementally.
Every sprint is bookended by two meetings that help the Agile process improve as it goes along.
The spring starts with a kickoff meeting where the Product Owner describes objectives and outlines what needs to be done. Team members then pick the tasks they want to focus on that fall under the sprint’s goals and assign themselves to those tasks.
At the end of the sprint is the retrospective meeting, where the scrum master goes over the data from the sprint to see what was done effectively, what test results were, what worked and what didn’t. It is also at this meeting that each team member shares the most important lessons learned from the sprint that just ended. Discussing and then documenting the process helps the team improve their work, their process, and their collaboration skills.
Consider this a primer on Agile marketing and not a comprehensive manual. There are many more levels to it than can be covered in a single post. Feel free to find them online.
The point of this entire process is not to change just for change’s sake. It’s to improve how you work as a team so you can answer customer needs better and faster. So keep these guidelines in mind:
A Complete Guide to User Engagement