Balancing Urgent Marketing Requests With Planned Work

A marketing plan can be sensible at the beginning of the week and difficult to follow by the end of it. Store needs, vendor requests and last-minute changes still arrive after the campaign calendar is agreed.

During my retail marketing work at BabySquare, annual and quarterly plans sat alongside short-notice manufacturer campaigns, store needs and timely opportunities. Online and in-store execution also had to move together. That experience made it clear to me that a usable plan needed room for incoming work.

The harder question is how to decide what deserves that room. If every request automatically interrupts the plan, the calendar stops representing a meaningful commitment. If the team protects the plan without examining new information, it can miss a customer problem that needs attention now.

I would approach this as a decision about consequences and capacity. The method below is a practical recommendation drawn from that experience, rather than a description of a formal system I implemented at BabySquare.

Classify urgency by what happens if the work waits

The word “urgent” is a useful signal to investigate. Ask what changes if the team does not act today.

A customer-facing error in an active offer is different from an additional asset someone would like to have. A fixed external deadline is different from a preferred completion date. Both may matter, but the team needs to understand the consequence before choosing the order of work.

For an incoming request, establish:

• what needs to change and who is affected;
• the actual deadline and what makes it fixed;
• the consequence of waiting;
• the minimum useful response;
• the effort, dependencies and review needed to deliver it.

Keep the request small enough to assess. “Update the campaign” could mean correcting one date or replacing the entire creative direction. Those are different commitments even when they arrive in the same message.

Separate a quick response from a delivery commitment

Acknowledge a request promptly when that helps the requester understand what will happen next. Acknowledgement does not need to imply that all the work has started or that a new deadline has been accepted.

Sometimes the immediate response is a clarification, a temporary correction or a smaller deliverable. The full change can then be considered against the existing plan.

For example, imagine a fictional retail campaign whose terms need correcting shortly before launch. The first action might be to confirm the accurate terms and correct the affected customer-facing material. A separate request to redesign every asset would need its own assessment. This is an illustrative situation, not a reported BabySquare incident.

That distinction allows a team to respond to the real consequence without accepting a larger scope by accident. State what is being handled now, what is still under review and who will decide the remaining work.

Make displaced work visible

An incoming request uses capacity already available to the team. If that capacity was committed elsewhere, accepting the request changes another promise.

Before starting material unplanned work, identify what will move. It could be a delivery date, a campaign component, another request or a less urgent improvement. Explain the tradeoff in concrete terms so that the person setting priorities can make an informed decision.

The May 2025 Kanban Guide, by John Coleman and Daniel Vacanti, calls for explicit workflow policies and control of work in progress. It describes starting work when capacity is available. Applying that principle to marketing, I would make an exception visible rather than quietly adding another active task. This application does not require claiming that the team operates a complete Kanban system.

A short intake sequence can help:

1. Clarify the consequence and minimum useful scope.
2. Identify the capacity and dependencies required.
3. Show the planned work affected by accepting the request.
4. Confirm the priority decision and communicate the revised commitment.

The sequence is useful only if someone has authority to choose. A board can display too much work accurately and still leave the underlying priority conflict unresolved.

Leave room for work you cannot specify in advance

Some incoming work is foreseeable even when the exact request is unknown. A retail team can expect operational questions, vendor changes and customer-facing corrections without knowing their content at the start of the month.

Avoid choosing a universal percentage of the week to reserve. Look at what actually arrives and how long it takes, including clarification, review and coordination. Use that record to decide how much planned work the team can reasonably commit to.

For a small team, this can begin with a simple review of completed requests and postponed commitments. A complex tracking tool is optional. What matters is whether the record changes the next planning decision.

Capacity also depends on who can perform the work. Time available from one person does not solve a dependency on someone else who must approve the offer or provide the correct information. Check those constraints before describing a request as easy to absorb.

Repeated exceptions deserve a planning decision

When the same kind of request keeps arriving, examine why. A recurring promotional requirement may belong in the campaign plan. Repeated clarification may point to an incomplete brief. A task that waits for the same person each time may need clearer ownership or an earlier review.

Keep this review focused on how the work operates. It should help the team see which requests can be anticipated and which genuinely require an exception. It does not need to become a judgment about whether a colleague was entitled to ask.

In my career experience, planned campaigns and operational work have often been connected. A useful marketing plan reflects that connection: it gives incoming needs a way to be assessed, makes the cost of changing direction visible and leaves the team with commitments it can explain.