Agile Marketing Validation Board


Note: This post was originally published in Yuval Yeret’s personal blog

“Validated Learning Over Opinions and Conventions” is the first value in the Agile Marketing Manifesto. A couple of weeks ago I was helping form what we call a “Marketing Agile Release Train” – a group of Agile Marketing teams each focused on supporting the business activities of a key product/solution in a large portfolio. The way we do this is typically a combination of some Agile Marketing training followed up by actual high-level planning of their first quarter followed by a deep dive into their first iterations/sprints.

One of my personal peeves while teaching Agile Marketing is this whole validation/experimentation/learning thing. In other words the difference between increments and iterations. It’s not iterating if you’re not inspecting and possibly adapting along the way.

Let me emphasize – Just taking a big campaign and breaking it into small tasks and planning two weeks at a time while running demos to show what you’ve accomplished and daily standups to make sure progress is according to plan and solving emerging problems is just a glimpse of what Agile Marketing is really about.

This is why when we got to high-level planning I felt something was missing from how the teams were planning. They were working on an MVP BOM – A Minimally Viable Program Bill Of Materials describing the minimum aspects of the campaign/program they were focusing on. It was a good start to focus on smaller more minimal programs/campaigns and working incrementally, but I felt the iterative/learning message was missing from the discussion once we moved from theory to practice.

At that point, I recalled the “Lean Startup Validation Board”. I first learned about the Validation Board and practiced using it as a mentor in a “Lean Startup Machine” event back in Tel Aviv. It is a practical hands-on planning tool that focuses you on what you don’t know and need to learn.

In the classic Lean Startup context, it should help you in your search for a Product Market Fit. You start by identifying your hypothesis around who are your potential customers, what’s problem you think they have, and what solution might fit their needs. You then try to think what are your core assumptions that would need to be true in order for all your hypothesis to be true. You look for the riskiest assumption – the one you feel might be the first one to bring your house of cards down. Then you structure experiments/validated learning around that. If your experiment validates your assumption you move to the next assumption. If it invalidates it you need to pivot to another set of hypothesis and start the core assumptions validation process again.

Is this a good fit for an Agile Marketing context? While watching the teams plan their “MVP”s I was trying to think about that. My conclusion is that the core idea is very useful but needs a bit of tweaking.

The “Minimum” tweaking I would do is to change from “Solution Hypothesis” to “Marketing Solution Hypothesis”. When I say Marketing Solution I include things like channel or message. An example of a channel hypothesis might be – “we think that Snapchat can be a useful marketing channel for us”. A messaging hypothesis might be “During a snow storm people would really connect to messages regarding vacations in warm places”. 

Most of the teams we were working with this time around were focused on scaling/growing revenue which means that there’s already a Product Market Fit and they were trying to find new creative ways to leverage that fit by getting to more people in the identified market and optimizing the customer’s journey.

In general, I think we need to differentiate between the search for Product Market Fit which is mainly a Product Development activity (in which Marketing can be a supporting function in) and the search for the best way to streamline the customer’s journey – which is typically the role of Agile Marketing teams. These two activities might use similar tools and techniques but are quite differently focused. And in both cases, there’s the potential for a lot of uncertainty therefore stating your hypothesis and validating your core assumptions are key.

So if you’re serious about Agile Marketing, don’t just plan tasks. Plan experiments aimed at validating assumptions. Plan to learn. Plan to iterate.

Subscribe for Email Updates:



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