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:

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