Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

Agile Marketing Validation Board

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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:

Categories:

Tags:

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