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.



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

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