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:

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