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:

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