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:

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