Campaign operations workshop / 5 MIN READ
Price the consequences of a campaign change before saying yes
Make a change decision visible across scope, commitments and dependent work.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-06
A small-looking request can change approvals, supplier work and the audience promise. The team should assess the consequence before treating enthusiasm as authorization to proceed.
What you will leave with: A change request that shows the reason, affected work and approved decision.
Use this when
- Late additions repeatedly disrupt campaign delivery.
- Different stakeholders give suppliers conflicting instructions.
This does not authorize spending, contract changes or new data sharing; those require the organization’s proper approval.
State the change and the reason separately
Atlassian’s project-poster guidance treats project understanding as something that can evolve. A campaign should allow justified change while making the consequences explicit.
Describe the current agreed state and the proposed difference. Then explain why the change is needed: new evidence, an external requirement, a corrected error or a stakeholder preference. These reasons should not be treated as equivalent. A necessary correction may deserve immediate attention, while a discretionary addition can be weighed against existing commitments. Avoid framing every new idea as a tiny tweak before anyone has inspected it.
Trace the affected decisions and outputs
Ask which work, approvals, dependencies and external promises would change. A new audience can require different eligibility checks; an extra venue can change staffing; a new product claim can reopen technical review. Include work already completed that may need to be replaced.
Get the relevant owners to assess the impact rather than inventing an estimate from the requesting team’s perspective. Distinguish known costs from unresolved questions. Do not promise a delivery date while assuming suppliers will absorb additional work. If the change creates a safety, legal or privacy issue, pause the affected action and route it to the appropriate specialist.
Offer realistic options
Present the useful alternatives: accept with an adjusted scope or date, replace another item, defer the addition or decline it. Explain the consequence of each in plain language. A no-change option should also state any real risk of leaving the current plan intact.
Name who can authorize the choice and which separate approvals are needed. A project lead may coordinate a scope decision without having authority to commit new expenditure or amend terms. Keep the supplier instruction pending until approval is complete. Do not let a draft discussion become a de facto order because someone copied a vendor into the thread.
Update the authoritative plan and notify affected people
After the decision, revise the relevant scope, schedule, approval map and supplier instruction together. Record what was accepted, rejected or deferred and why. Make the changed version easy to identify so teams do not execute different plans.
Check that affected owners understand the practical implication, especially when work is stopped or a promise is narrowed. Close the request only when the decision has reached the people who must act on it. Preserve a lightweight record for later questions, but avoid a bureaucratic process for harmless edits that remain inside already-approved bounds.
Make the reasoning concrete.
A fictional campaign sponsor requests an additional regional event after invitations and supplier bookings are approved. The request is described as “just one more stop.”
Agree immediately
Opening: Ask the supplier to add the venue while impact is still unclear.
Hypothesis: The sponsor receives a quick positive response.
Risk: The team may create unapproved costs and an unsupported delivery commitment.
Assess the change
Opening: Check venue, staffing, eligibility, supplier terms and affected dates before deciding.
Hypothesis: The sponsor can choose among real options.
Risk: The added event may require replacing another activity or being deferred.
The team presents a scoped option with the necessary approvals and a deferred alternative. No supplier commitment is made until the authorized decision is recorded.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Difference
What changes from the currently agreed scope?
Reason
Is this a correction, requirement, new evidence or preference?
Impact
Which outputs, approvals, costs and promises are affected?
Options
What can be added, replaced, deferred or declined?
Execution
Who updates the plan and gives the authorized instruction?
Watch for the wrong conclusion.
- Calling a request small before assessing its dependencies.
- Letting a copied supplier interpret discussion as an order.
- Approving a change without updating the working plan.
Your next action
Write one pending change as current state, proposed difference and affected commitments before giving anyone a yes.
Sources & scope
The workflow, worksheets and hypothetical examples are original editorial analysis. Sources support only the identified principles. No measured business results or named human reviewer are claimed.
- Atlassian Team Playbook: Project Poster →Primary framework-publisher guidance · Supports: A project poster is updated as understanding changes; the intake and scope-control tools are original editorial analysis.