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:

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