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:

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