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:

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