What agile management in B2B marketing is
Agile management in B2B marketing starts with a question, not a tool. The most common signal that a marketing team needs to change how it works sounds roughly like this: we have forty tasks in Jira, a LinkedIn campaign, two webinars in production, and nobody can say which of these elements actually influenced anything in the sales pipeline. Marta, a marketing manager at a manufacturing company near a mid-sized city, called a team meeting and instead of discussing statuses, asked one question: which of these forty tasks brought us closer to a conversation with a decision-maker in the last month? It turned out that none of them did. She closed twenty-eight tasks, kept two threads going, and within two weeks the team learned more about market reaction than in the previous quarter. Agile management answers one question here: what are we doing in the next two weeks and how will we know it worked.
In B2B this question is harder than in e-commerce, because sales take months and the purchasing decision passes through several people. The result is that marketing gets feedback with a huge delay. If you wait for a deal to close to evaluate a campaign, you learn about the market six months after the market has changed. Agile management shortens the feedback loop to what can be measured in two weeks: traffic quality, the number of qualified conversations, the cost of reaching a decision-maker.
At Growth Group we work with companies across the region and beyond. We bring 16+ years of experience and PLN 160 million in profit generated for clients. The conclusions from these projects are fairly consistent: teams do not have a problem with ideas, they have a problem with the rhythm of decision-making.
Why the classic quarterly plan falls apart in B2B
A quarterly plan assumes that the assumptions from day one will still hold on day sixty. In B2B that is rarely true. It only takes the main competitor changing its pricing, a key client shifting budget to the next fiscal year, or the product department releasing a feature that changes audience segmentation.
Then there is the structure of the team itself. In B2B companies, marketing often numbers three to eight people, half of whom also work on sales or customer service. Such a team cannot sustain a plan that requires running six initiatives in parallel. Research on the effects of interactions between marketing variables shows that the impact of one action on the result depends on the level of another factor (for example, the effect of advertising on sales changes with price). This is exactly the mechanism that makes rigid plans fall apart at the first change in conditions.
The practical conclusion: a quarterly plan makes sense as a direction, not as a task list. Agile management does not eliminate strategy, it breaks it into shorter segments where assumptions can be verified. Strategy answers the question "where do we win", a sprint answers the question "what will we learn in two weeks".
| Quarterly plan | Two-week sprint | |
|---|---|---|
| Decision horizon | 3 months | 2 weeks |
| Number of active initiatives | 5-8 in parallel | 1-2 |
| Moment to verify assumptions | after the quarter | after two weeks |
| Reaction to market change | at the next plan | in the next sprint |
| The core problem | assumptions that drift apart | the risk of too narrow a test |
What a B2B marketing sprint looks like when it is not theater
Sprints in marketing have a bad reputation because teams often copy them from IT along with the whole ritual: a daily standup at 9:15, estimation in points, a retrospective with stickers. In a B2B marketing team this is usually overkill. A sensible marketing sprint has three elements.
1. One research question per sprint
Not "a trade show campaign", but "do operations directors at companies of 50-200 people respond to a video case study". Formulating the question forces you to choose one segment and one channel. If you test three segments and four formats in a single sprint, you will learn nothing about any of them.
2. A success measure set before the start
Set a threshold that you treat as a signal to continue. It can be the number of sales meetings with qualified accounts, the number of downloads of a piece of content by people in decision-making roles, or the cost of acquiring a contact with a decision-maker. What matters is that the threshold is written down before launch, not after.
3. A decision at the end: scale, change, close
Three options, no fourth. "We continue and see" is the most common way sprints turn into an eternal project without conclusions. If the data did not convince the team, close the thread and move on.
Agile marketing in its B2B form differs from the consumer version in one more respect: salespeople must take part in the feedback loop. If sales cannot see what marketing is testing in a given sprint, they will not give you feedback on lead quality. This is the most common reason why a B2B marketing strategy exists on paper but does not translate into conversations with clients.
Marketing backlog: what to include and what never to include
A backlog is a to-do list, but in B2B marketing its main function is to protect the team from distraction. Good marketing backlogs have three characteristics.
- Items are sprint-sized. If a task will not fit into two weeks, it needs to be broken down. "Website rebuild" sounds like a task, but in practice it is a project.
- Every item has an owner and an acceptance criterion. Without this you go back to talking about whether something is finished instead of talking about results.
- The list is short. Five to eight items per sprint is a realistic maximum for a team of 3-5 people that is also handling ongoing sales tasks.
What not to include: tasks that cannot be verified in a short cycle (for example "building the brand" as a separate item), and tasks that are a reaction to someone's whim rather than to data. In practice it is worth keeping two lists separate: a backlog of experiments and a queue of operational tasks. Mixing them means experiments always lose to urgent fixes.
The decision rhythm: three meetings that replace seven
Agile management is not about adding meetings, it is about consolidating them. In B2B marketing teams, three rhythms work well.
- Sprint planning (90 minutes, once every two weeks). Choosing one research question, setting a success measure, assigning tasks. No status presentations from the previous period, those go separately.
- Data review (45 minutes, once a week). Only numbers and conclusions. If the data does not change a decision, the meeting is not needed.
- Retrospective (60 minutes, once every two weeks). What sped up the work, what blocked it, what we change in the next sprint. Without judging people.
That is all. Daily standups in a B2B marketing team usually do not make sense, because the work is not as interdependent as in development. An asynchronous channel where everyone posts one sentence about their status is enough.
-
1
Planning
Choosing one research question, setting a success measure, assigning tasks. 90 minutes.
-
2
Execution
Two weeks of work on the chosen thread. A weekly data review after 45 minutes.
-
3
Reading the data
Comparing the result with the threshold set before the sprint started.
-
4
Decision
We scale, we change, or we close. No fourth option.
-
5
Retrospective
What sped up the work, what blocked it, what we change in the next sprint. 60 minutes.
When agile management does not make sense
Not every marketing problem is solved with sprints. If your company is just entering a new market and you do not yet know who the customer is, you first need research work, not iteration. Sprints assume you have at least a rough hypothesis to test.
Agile management also fails where there is a lack of competence to interpret data. If no one on the team can tell correlation from causation, fast iterations will produce fast wrong conclusions. In such situations, external support is often more sensible, for example interim marketing manager paid for the result, who introduces a work rhythm and at the same time safeguards the quality of conclusions.
Third case: the company has one client generating most of its revenue. Priorities are then imposed by definition, and sprint flexibility has no room to develop.
How to implement this without hiring a scrum master
Starting with a change in how we work does not require a new tool or a new person. It requires three decisions made in a single meeting.
Step 1: choose one question for the next two weeks
Write it on a single line. If it does not fit in one sentence, it is too broad.
Step 2: define what will count as evidence
A specific number, a specific data source, a specific read date. Without this, step three will not work.
Step 3: schedule the decision for the end of the sprint
Put a meeting in the calendar where the decision will be made: scale, change, or close. This is the only meeting that cannot be moved.
After two or three sprints, the team usually starts proposing hypotheses to test on its own. This is the moment when agile management stops being a process and becomes a way of thinking about marketing. That is when it is worth returning to the strategy and checking whether the direction still holds, because sprints without a strategy turn into a series of interesting experiments that do not add up to any result.
Sources
- Methods of Marketing Analytics, chapter 2.1 Regression (analysis of interactions between marketing variables)
- Friestad, M., Wright, P., The Persuasion Knowledge Model: How People Cope with Persuasion Attempts, Journal of Consumer Research, 1994
- Feick, L., Price, L., The Market Maven: A Diffuser of Marketplace Information, Journal of Marketing, 1987