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:

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