Scaled Agile Marketing Flow with Kanban

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

In the previous article, I mapped out the essentials of applying SAFe™ (The Scaled Agile Framework) to a marketing context and ended with a cliffhanger. As you can guess from the title of this article, what I feel is missing from the list of essential SAFe elements is Flow and Kanban, which IS an important part of SAFe. In this article, I will focus on the key Flow/Kanban elements that are essential to succeeding with Agile Marketing at scale in my view. These elements don’t have to be implemented as part of SAFe by the way. Some organizations implement them on their own.

What do we mean when we say effective marketing flow

Sailing - by Aidan Morgan

Put the same paper boat in a rapid river and it will move much faster obviously.

Rapid River by Caroline Johnston

What we are trying to create in marketing is a river-like flow.

Marketing Development Value Stream Flow vs Customer Journey Flow

The flow of what? We’re mainly talking about the flow of marketing creation/development/operational work, not of actual leads. Actual leads/customers flow in your customer journey.

Effective flow in your customer journey IS important to work on and actually many agile marketing teams take on work aimed at improving this flow. Using flow diagrams and maybe even Kanban to manage your customer journey is not a bad idea, but not our focus here…

Flow at various levels

Work needs to flow at various levels in the organization. Obviously at the agile marketing team level but also at a higher/program level when looking at bigger plays/campaigns and making sure that those flow as well rather than get stuck in the swamp. And even at a higher level than that the marketing organization should visualize and manage the flow of their portfolio of initiatives and make sure they’re focusing on the right number of initiatives and delivering results on them rather than being stuck in the swamp of too many things and not enough focus.

Marketing Team Kanban
Marketing Program Kanban
Portfolio Kanban

These different kanbans create a hierarchical network of kanban systems where when initiatives from the portfolio kanban get to the implementation stage they get expanded into more tactical marketing plays that then start to flow in the program-level kanban system. When they get to their implementation stage they get expanded into marketing stories that are then managed in a team-level kanban system of one or more teams. As marketing work progresses the flow status can be visualized up the tree and as we decide we finished all marketing stories related to a play/campaign we can collapse back into the marketing play/campaign and continue to finalize its flow at the program-level kanban system. (and similarly all the way up to the initiative.

In all those kanban systems the key to effective fast-flowing work is first of all to visualize the flow and the obstacles to flow, then to attend to the flow on an ongoing basis as a key executive management practice, and to limit the amount of work in process (WIP). This is the essence of Kanban. Having discussions about flow and work-in-process limits at all levels of the marketing organization helps build the lean/agile muscle at all those levels.

Flow-based marketing prioritization using Cost of Delay and Weighted Shortest Job First

Fast flow and low work in process levels are only possible if you prioritize. If you stop starting everything as you’re used to and start focusing on finishing instead. Saying “I’m not starting this now” despite the fact that it is considered important is hard. Figuring out what to actually prioritize is not easier…

In a flow-oriented mode of execution prioritization isn’t something you do in your annual marketing planning. It is something you do continuously. Yes, the frequency of prioritization at the team/stories level is much higher than at the portfolio/initiatives level. But at all those levels we strive not to build a whole list of priorities to plan out a long horizon but rather figure out what are the top things to start now and defer the decision about what will come after that to the point that we will actually have the capacity to start the next thing.

Each time we start something we want it to be the marketing deliverable that will have the highest impact/cost on our operation if we don’t start it. This is called the “Cost of Delay” (CoD). What we try to do is to weigh the Cost of Delay vs the size of investment needed to come up with the best choice. This is sometimes called Weighted Shortest Job First (WSJF). SAFe is a very specific approach for comparing different initiatives/campaigns and deciding which ones to go for. Other practitioners like Joshua Arnold consider this too watered down and WSJF. I won’t go into the pros and cons of each. The basic point here is that whenever you consider starting something new you should consider whether it’s the right thing to start and whether it should really replace any of the things you’re currently working on. Getting to the higher maturity of really farming out the biggest opportunities out of your options is a very nice extra bonus.

Here in the picture, you can see a group of VPs and directors trying to figure out what to focus on at their program-level kanban system using a SAFe-style WSJF exercise.

Inviting change using Kanban

An interesting property of kanban systems is that they don’t require as much change to the organization as a full-fledged scaled agile framework such as SAFe. If considered on their own, creating a set of kanban systems for the marketing organization can be a good way to get the people in the organization to start to think in a Lean/Agile way, look at their flow, start to improve it, and over time adopt other lean/agile practices such as the essential elements of SAFe. I’ve seen this happen in a healthy way in several enterprise-scale organizations. It can be the right approach if people are hesitant to drive revolutionary change in the organization.

Invitation/Pull-based change

It fits into a higher-level topic of how to drive sustainable change in an organization. One of the key approaches I’ve been using in the last couple of years is Invitation/Pull-based change management. I also wrote a SAFe guidance article about invitation-based SAFe implementations. In essence, the point is that if you want sustainable change you need to let people in the organization pull it and make it their own. You need to look at the organization as a market where you need to “market/sell” your change ideas rather than force them. Having to market your change ideas is of course harder and slower than mandates. But it is typically much stickier and more successful in the long run.

Conclusion

In this article I talked about Kanban/Flow/Prioritization – keys to successful agility whether as part of SAFe or standalone, as well as the evolutionary/pull-based change management philosophies that Kanban inspired in the Lean/Agile world. Every marketer looking to apply agile at scale should be aware of both the importance of kanban systems as well as these change methods and figure out when to apply them.

Subscribe for Email Updates:

Categories:

Tags:

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