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

Choosing your Agile Marketing Tool

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

This post is a continuation/refresh of an earlier post from Yuval’s personal blog 

Tools for Agile Marketing seem to be a hot topic in the various Agile Marketing communities. The Marketing Agility Podcast is talking to some tool vendors and people started to discuss it on the  Agile Marketing Facebook Group as well.

For co-located marketing teams the best approach would probably be to start without an electronic tool and just use a physical board/wall with sticky notes at least until they get the hang of it and learn what they really need. Many marketing teams are distributed and therefore don’t have this luxury. While moving to a co-located setup is definitely a recommended option it isn’t always realistic… So those teams do need to have some electronic tool to support their move to agile marketing.

There’s a variety of tools supporting agile work management. Most of them come from the development/IT world since this is where Agile is coming from. While many of the principles and practices of Agile Development map nicely to Agile Marketing when it comes to tools there’s actually a bigger difference in my experience. I find marketers are typically more visual and artsy than developers. They also have a different language. Many of the Agile Development tools speak the development-world language which confuses marketers.

I’ve seen many marketing departments being asked to use the tool their peers in IT/Development use – mainly to achieve economies of scale (standardize on one tool vendor, easier to support fewer tools, etc.). While this has merit, in many cases it becomes a significant impediment to the success of the Agile Marketing transformation. Tooling should work for the people rather than against them. I’m not saying don’t consider economies of scale and alignment but also consider whether the tool will actually work well in a marketing context. If you have concerns, start small and see. Suggest it as an experiment.

To help marketers make sure they are considering the right tools, here’s my view on what would be a great tool supporting Agile Marketing:

  • It would talk marketer’s language. Not force marketers to learn the language of development/IT.
  • It would be flexible. Marketers are not following Scrum to the letter. It should enable marketers to follow lean/agile principles without forcing the wrong practices.
  • It would be visual and beautiful because marketers appreciate those things. It wouldn’t bog down people with too many grids and lists and instead, use more “Boards”.
  • It would support dynamic teams not just fixed scrum teams. Because that happens in Marketing. (also in Development btw)
  • It would support a combination of Scrum, and Kanban without forcing you to choose one or the other.
  • It would allow different teams in the organization easily adapt their area in the tool to support their own process.
  • It would TEACH marketers how to think about lean/agile flow/behavior. As a complement to frontal training, the tool should proactively support changing marketing culture to support agility.
  • Marketers spend even more of their time doing “Keep the lights on” activities such as cleaning up leads, monitoring campaigns, running webinars, etc. A great tool would find an effective way not just to take that into account but also to help them manage those activities more effectively. Some of the Personal Kanban body of knowledge can help here.
  • Marketing Agility starts with individuals and can scale to hundreds of people. Not all tools need to support scale. But if the organizational agile tool can help the individual marketer become more agile it would help with the adoption of the tool and agile marketing in general.
  • Emphasize simplicity, ease of use, and streamlined flows. Otherwise, it won’t stick. Having a situation where you have special people working the tool because the actual marketers won’t touch it with a stick is unacceptable (a true story I heard in a recent meetup). It should take minutes to onboard a new team. It should take seconds for a marketer to add new work or move work along.
  • Integration into the other main tools of the 21st-century marketer. Integration into email is one key thing. SalesForce when we start to talk about Account Based Marketing? Marketo/Hubspot/etc.? Integration into collaboration tools such as Slack/Flowdock?
  • It should provide some actionable insights – e.g. these items have been in flight for quite a while, worth looking at them in your next daily stand-up. These items took a long time to cross the finish line – may be worth discussing them in a retrospective/five-whys session. These items ping-ponged a lot between states – worth looking at. There seems to be a lot of queueing up for the designer. mmmm. maybe you should look at that (and suggest some tips along the lines of the theory of constraints’ five focusing steps). Why is it important to marketers? actually, the more of those insights agile tools include the better it would be for everybody not just marketers. But since marketers are new to this agile thing, and many marketers aren’t necessarily process-oriented, this can help them along. (If they don’t have a lean/agile coach close by that is 😉

I hope this list helps you choose an effective agile marketing tool for your context. If you need further help in choosing an agile marketing tool, don’t hesitate to reach out. I’m available at yuval@agilesparks.com.

Subscribe for Email Updates:

Categories:

Tags:

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