Flow Over Velocity: A Systemic Approach to Marketing Agility
Marketing isn’t failing at Agile. Agile is failing at marketing. The irony is that applying the frameworks without the principles means they don’t realize they’ve engineered the very friction they’re trying to eliminate. It is not uncommon for a marketing organization to adopt Scrum, install the ceremonies, measure velocity, and then quietly wonder why marketing still feels chaotic.
Having worked with dozens (probably a few hundred by now) Agile Marketing teams, I have noted a common denominator: Most ‘Agile Marketing Playbooks’ are focused primarily on the tactical application of agility. To flip that, my Marketing Agility Flow model includes tactical considerations, but it is decidedly systemic and focuses on clarity with alignment.
Because marketing is not software development, which is what Scrum was purpose-built for, marketing agility requires a demand-signal interpreter sitting between Product, Sales, and the market. It requires models and systems that absorb volatility by design. Without this model, if the system assumes stability, it will always punish the team for reality.
Marketing Agility Flow is my model that incorporates the best applicable ideas from the Toyota Production System, Lean, Kanban, and Scrum into a model meant for marketing.
Start With the Problem We’re Solving
Marketing is interrupt-driven. Some work is:
- Milestone-driven (launches, events, campaigns)
- Signal-driven (sales asks, competitor moves, exec requests)
- Flow-driven (always-on content, nurture, optimization)
Traditional Scrum assumes:
- Stable sprint commitment
- Protected sprint capacity
- Predictable velocity
But marketing has:
- Variable demand
- High cross-functional dependency
- External deadlines
- Political interruptions disguised as urgency
Problem-solving for the actual Marketing workflow:
- We do not optimize for sprint velocity.
- We optimize for the flow of value under variable demand.
2. System Design Principle: Separate the Work by Physics
Toyota didn’t try to treat every workflow the same; they separated predictable flow from variable flow, and so does my Marketing Agility Flow model.
A) Work is categorized before it is planned:
- Committed Delivery (Sprint Work)
- Campaign builds, product launches, milestone-based work.
- Interrupt Capacity (Expedite / Sales Support, etc.)
B) Continuous Flow (Kanban)
Each lane has:
- Defined entry criteria
- WIP limits
- Explicit policies
- Measurable flow metrics
C) Instead of pretending interrupts don’t exist, we design for them.
This is why we have three categories for work types that all marketing organizations have to account for. Here’s an example of a “Version 1” starting allocation for a marketing team new to Marketing Agility Flow:
- 60% Committed Sprint Work
- 25% Interrupt Buffer
- 15% Continuous Flow Optimization
If interrupts exceed 25%, something upstream is broken, and that becomes a leadership conversation, not a team failure. Over time, the team shapes the division of work along those three categories to become better at (never aiming for perfect or static percentages) allocating their time and focus.
Toyota principle: If the line stops frequently, fix the system and do not blame the worker.
3. Focus on Flow Intelligence
We replace velocity worship with flow intelligence because velocity is unstable in interrupt-driven environments like marketing. So, instead, we model measures in three ways:
A) For Committed Work
- Sprint Goal Achievement Rate
- Predictability Index (Committed vs Delivered)
- Dependency Aging
B) For Interrupts:
- Interrupt Volume by Source
- Time to Resolution
- Capacity Trade-Off Impact
C) For Continuous Flow
We represent the team’s work through Cycle Time, which includes:
- Throughput
- Blocker Aging
- Work-In-Progress (WIP) Breach Frequency
What Visually Matters: Burndown charts are optional, but flow diagrams are required. Velocity becomes a reference; flow stability becomes the signal.
4. Agile Influence: Make the Invisible Visible
Information radiators are how people have a shared understanding of the work categories, work assignments/owners, workflow, and throughput. This is where Kanban shows up the most in my hybrid model, utilizing a Kanban board (likely with swimlanes in addition to columns).
A) Visual Management:
- One unified board
- All lanes visible
- Interrupts tagged
- Blockers aging visualized in color (red, usually)
B) Adopt Andon Thinking (the “pull cord” to stop the line)
If interrupt volume spikes, the team metaphorically ‘pulls the Andon cord’:
- Escalate upstream
- Diagnose the root cause
- Redesign the intake
This means the team has a direct say in what, how, and why they work the way they do. They see the value of “Stop starting, start finishing.” Work In Progress (WIP) limits are sacred because they mean teams can focus without being diluted.
If WIP breaks: We do not add people; we reduce what we start.
5. Sprints are for Alignment, not Isolation
Sprint Planning includes the interrupt forecast review. The Inspect & Adapt ceremony allows for capacity rebalancing. The Look Ahead ceremony includes a “flow health” discussion. And Retrospectives include system diagnosis, not just team reflection.
Agile Principle: The point of any Agile ceremony is always system learning loops, not ritualized compliance.
6. Executive Insights and Decision-making
At the portfolio level, leadership reviews a simplified dashboard and a summary report:
- % Capacity consumed by interrupts
- Aging dependencies across teams
- Decision latency
- Milestone drift risk
If interrupts are systemic, we identify the cross-business (Sales, Product, etc.) alignment issue. If milestones slip, we can uncover the capacity modeling issue. If WIP explodes, it is always — always — elevated as a prioritization issue that Leadership must solve for in the systemic/structural/cultural pain points. This rarely points to a team maturity issue; it’s almost always a portfolio governance issue.
Executive Servant Leadership Principle: When we have visual, measurable, and anecdotally-supported proof of problematic patterns or anti-patterns, this diagnosis protects the team and elevates leadership accountability to serve the team.
Final Thoughts
I have done so many iterations of various methodologies that I refused to make yet another methodology myself. Instead, I created this model, which has a clear structure but built-in adaptability and flexibility without losing coherence.
I believe that clarity with alignment prevents volatility from becoming chaos. That’s why I have created the Marketing Agility Flow model, which I have licensed for non-commercial, personal usage for free using Creative Commons (CC BY-NC-SA 4.0). For commercial uses, contact me directly.
