Module 4 — Campaigns and Experiments · Lesson 4.1
Planning a Campaign as a Project
One objective, an owner, a premortem, and a schedule that respects the planning fallacy
What you'll learn
- Write a campaign brief with one objective, an audience, a message and a measure
- Break a campaign into owned, dated tasks with explicit dependencies
- Run a premortem to surface risks while there is still time to act on them
- Correct a campaign schedule using past campaigns rather than optimism
Marketing teams talk about campaigns as creative ideas. Most of the work, and nearly all of the risk, is project management: dozens of small deliverables across writing, design, data, channels and sales follow-up, each of which can slip, and several of which only matter if another one is done first. Treating a campaign as a project is not bureaucracy. It is how a small team ships one campaign properly instead of three campaigns partially.
The brief: one objective
Every campaign starts with a one-page brief, and the brief has exactly one objective. Not 'awareness and leads and a better website'; one outcome, expressed as the number you will look at afterwards. The rest of the brief follows from it: the audience (by ICP segment and job, Lesson 1.4), the primary job of the work (brand or activation, Lesson 2.1), the single message pillar the campaign leans on, the offer if there is one, the channels, the budget in money and hours, the dates, and — written before anything is made — the measure and the threshold that will count as success.
The Content Marketing Institute's 2026 B2B trends research is a useful reminder of where results come from. Among the 61% of B2B marketers who reported their content strategy improved, 74% credited refining the strategy, against 51% who credited new technology. The brief is where strategy refinement happens at the scale of a single campaign.
Work breakdown, owners and dependencies
Break the campaign into deliverables, then into tasks small enough that each has one owner and a due date: copy for each asset, design, landing page, list build and verification, email or cadence setup, sales enablement, the launch itself, follow-up, and the measurement review. Make dependencies explicit — the landing page depends on final copy; the send depends on a verified list and a tested unsubscribe; sales follow-up depends on enablement. Most campaign slips are a dependency nobody wrote down.
Integration is part of the plan, not a nice-to-have. Binet and Field's IPA analysis found that brand and activation channels together outperformed either alone and that integration could double efficiency. In project terms that means the ad, the email, the landing page and the sales follow-up are one campaign with one message and one calendar, not four tasks run by four people who happen to share a topic.
The premortem
Gary Klein described the premortem in Harvard Business Review in 2007. Before the project starts, the team imagines it is the end of the campaign and it has failed, then team members generate every plausible reason why. Klein's argument is that projects fail at a high rate partly because people are reluctant to voice reservations during planning, and that making it safe — expected, even — for knowledgeable dissenters to speak up improves the odds of success.
A campaign premortem can be done in under an hour, and the risks it surfaces tend to be mundane: the list is smaller or dirtier than assumed, legal review of a claim takes longer than planned, the landing page breaks on mobile, sales is at a conference the week of launch, the offer is unclear. Each credible risk gets a mitigation task or an owner who watches for it. The premortem's value is not prediction; it is giving the quiet person who has seen this go wrong before a moment designed for saying so.
A schedule corrected for optimism
Roger Buehler, Dale Griffin and Michael Ross's 1994 study of the planning fallacy found that people's predictions of their own task completion times were too optimistic across a variety of tasks, that people focused on plan-based scenarios rather than relevant past experience when predicting, and that they attributed past failures to external, one-off causes. Notably, the optimistic bias was eliminated for participants instructed to connect relevant past experiences to their predictions, and observers predicting others' completion times were more pessimistic and used past experience more.
The practical fix follows directly. Schedule a campaign from how long your last few campaigns actually took, not from how long this one should take. Ask someone outside the campaign to sanity-check the dates. And put the launch date after the dependencies, not before them; a date announced to the company before the work is broken down is a date that will be met by cutting the follow-up, which is the part that produces results.
Build the campaign on the board
- 1
Write the brief into the project charter
Create a project for the campaign on /projects/tasks and put the brief — objective, audience, measure, threshold — in the project's charter, so the agent and every assignee see it.
- 2
Have the agent draft the work breakdown
From /ai-agent, ask the agent to propose tasks from the brief. Review them, set owners, due dates and dependencies, and delete what the campaign does not need. The proposal is a draft; the plan is yours.
- 3
On /planning, confirm the people who own the critical tasks have room in the sprints before launch. Compare the plan's duration with how long your last campaign actually took.
- 4
On /knowledge, record the premortem's risks and mitigations, and add mitigation tasks to the project.
Campaign execution
- On-time launch
- Whether the campaign launched on the date set after the work breakdown, with every gate task complete.
- Healthy signal: Yes, without cutting the follow-up tasks to make the date.
- Schedule overrun versus last campaign
- Actual duration divided by planned duration, compared with the same ratio on previous campaigns.
- Healthy signal: Closer to 1.0 each time — a sign the team is planning from history rather than hope.
- Objective hit
- Whether the one objective in the brief met the threshold written before launch.
- Healthy signal: Measured honestly either way; the record of hits and misses is what improves the next brief.
Key takeaways
- ·A campaign has one objective and a success threshold written before launch.
- ·Break it into owned tasks with explicit dependencies — and run brand and activation as one integrated plan.
- ·A premortem gives knowledgeable doubters a safe moment to name what will go wrong.
- ·Schedule from how long past campaigns took; the planning fallacy is reliable and correctable.
A campaign's brief names a measure. Whether a change actually moved that measure is a question for an experiment — and experiments are easy to run and easy to misread. That is the next lesson.
Sources
- 1.Performing a Project Premortem
Gary Klein · Harvard Business Review, September 2007 · 2007
Imagine the project has failed and generate reasons; making it safe for knowledgeable dissenters to speak up improves a project's chances.
- 2.Exploring the 'Planning Fallacy': Why People Underestimate Their Task Completion Times
Roger Buehler, Dale Griffin, Michael Ross · Journal of Personality and Social Psychology 67(3), 366–381 · 1994
Predictions of one's own completion times are too optimistic; the bias disappeared when people linked predictions to relevant past experience.
- 3.The Long and the Short of It: 10 key principles of success (presentation)
Les Binet and Peter Field · IPA · 2013
Brand plus activation outperforms either alone; integration can double efficiency.
- 4.9 Takeaways and Insights From the 2026 B2B Content and Marketing Trends Report
Robert Rose, Content Marketing Institute · contentmarketinginstitute.com (survey of 1,015 B2B marketers) · 2025
61% reported their content strategy improved; of those, 74% credited strategy refinement and 51% new technology.