How to say no to low impact marketing work

1. Define low impact before judging requests

Low-impact marketing work consumes scarce capacity without a credible contribution to an agreed outcome, essential obligation or useful learning. It is not simply work with low immediate revenue. Accessibility, measurement maintenance and long-term brand development can matter even when their contribution is difficult to attribute.

Agree on three protected categories: essential maintenance, committed delivery and discretionary improvement. Rank discretionary work against other discretionary work rather than forcing everything into a short-term sales calculation.

Hypothetical example: a retailer receives requests to recolour an internal presentation, repair misleading delivery information and develop a seasonal buying guide. The delivery correction protects customers; the guide needs a strategic case; the presentation needs a reason beyond preference. Calling all three 'content updates' conceals the real decision.

• Name the outcome, obligation or uncertainty the work addresses.
• Identify who benefits and what changes for them.
• Ask what happens if the work waits a month.
• Separate weak evidence from evidence that the work has little value.

2. Require a decision brief, not a polished business case

Use one short intake format for requests, including those from senior stakeholders. Ask for the audience, problem, evidence, desired outcome, deadline reason and decision owner. The requester should explain the need; marketing should help estimate delivery effort.

Hypothetical example: 'We need a webinar next Friday' becomes 'Prospects repeatedly ask how migration works; sales needs a reusable explanation before renewal conversations.' That leaves room for a recorded demonstration or written checklist instead of a live event.

Avoid turning intake into a gatekeeping exercise. A customer-facing colleague may have valuable qualitative evidence without a dashboard. Record the observations and their limitations. Conversely, a precise deadline is not evidence of urgency unless something consequential happens on that date.

• Return incomplete requests with one specific question.
• Accept customer objections, support themes and sales feedback as evidence to investigate.
• Keep the requested format separate from the underlying problem.

3. Estimate the whole job and name the displaced work

Count briefing, production, review, legal or brand checks, publishing, tracking and maintenance. Include effort from other teams. A 'quick landing page' can occupy little writing time but require substantial design and approval work.

Hypothetical example: an agency estimates two hours to draft a bespoke client report, another hour to reconcile figures and two hours across review meetings. The relevant cost is five team-hours, not two. If the report repeats an existing dashboard, ask which decision needs the extra interpretation.

Make the opportunity cost explicit: 'Doing this now would move the onboarding email review to next week.' Avoid invented revenue losses. Where estimates are uncertain, provide a range and identify the dependency that could expand it.

• Include coordination and expected revision time.
• Check the bottleneck person's capacity, not only total team capacity.
• Name the deliverable that would move, shrink or stop.

4. Choose between decline, defer, reduce and test

A yes-or-no system creates unnecessary conflict. Decline work with no defensible purpose. Defer valuable work whose timing is wrong. Reduce scope when a smaller deliverable solves the problem. Test when uncertainty is material and a bounded trial can resolve it.

Hypothetical example: a hospitality team is asked to open another social channel. It could decline because no target audience case exists, defer until someone can maintain it, or test a limited content series with a defined review date. 'Post whenever possible' is not a test because it lacks a learning question and stopping rule.

Do not use testing to disguise a reluctant yes. Set a maximum effort budget, identify the evidence that would justify continuation and explain what a weak result would mean. Low distribution or tracking failure may make a test inconclusive rather than prove the idea ineffective.

5. Say no with a decision, an alternative and an owner

A useful refusal is specific and calm. Acknowledge the objective, explain the constraint, state the decision and offer an alternative only if it is genuinely worthwhile. Avoid vague phrases such as 'not strategic', which invite debate without explaining the tradeoff.

Hypothetical response: 'I understand the sales team needs stronger evidence for this tender. We cannot produce a new industry report by Thursday without delaying the agreed campaign launch. We can adapt the approved case study instead. If the report takes priority, the marketing lead needs to approve moving the launch.'

Keep escalation about choices rather than personalities. A senior sponsor can change priorities, but the displaced commitment should change visibly too. For agency work, distinguish an out-of-scope request from low-value work: a valuable request may still require a revised fee or delivery date.

6. Protect quality work that is easy to undervalue

Efficiency programmes fail when they remove safeguards because the benefit is less visible than production output. Maintain a minimum quality checklist for accuracy, accessibility, tracking and approvals, with ownership appropriate to the work.

Hypothetical example: a video team proposes removing caption review to publish faster. W3C guidance explains that captions convey relevant speech and non-speech audio. Automatically generated words alone may therefore be insufficient. Reduce unnecessary edit rounds before removing checks that help people understand the content.

Apply the same discipline to fashionable requests. Google says normal SEO practices apply to its AI search features, with no special markup requirement or guaranteed inclusion. That supports challenging an unsupported 'AI-only markup' project, not abandoning useful technical SEO or helpful content.

• Define non-negotiable checks before deadlines become urgent.
• Require a concrete rationale for extra approval layers.
• Do not equate difficult attribution with low value.

7. Retire recurring work without creating hidden risks

Recurring tasks deserve explicit renewal decisions. Audit standing reports, meetings, routine posts and duplicated checks. Ask who uses each output, which decision it supports and whether the same information exists elsewhere.

Hypothetical example: a services firm produces a weekly slide pack that duplicates its monthly review. Rather than deleting it overnight, ask recipients which decisions require weekly attention. Replace the pack with exception notes for a trial period, while preserving access to the underlying figures.

Record the task owner, trial pause, replacement, affected stakeholders and restart trigger. Check contractual and operational dependencies first. Silence after cancellation is not sufficient proof that nobody needed the output; actively ask users whether a decision or handoff suffered.

• Remove obsolete dashboard links and meeting invitations.
• Tell recipients where essential information now lives.
• Review the change after a normal operating cycle.

8. Measure reclaimed capacity, not rejection volume

Track team-hours spent on comparable work, request-to-decision time, delivery cycle time and rework. Pair speed measures with quality checks and the completion of priority work. Counting rejected requests rewards obstruction rather than better judgement.

Hypothetical calculation: retiring a report avoids four team-hours each week, but its replacement exception note takes one hour. Net capacity released is three hours weekly. Record one-off transition effort separately. Those hours are available capacity, not automatically payroll savings or additional revenue.

Compare periods cautiously. Campaign complexity, staffing, seasonality and approval availability can change results. Report 'cycle time fell during the new intake process', not 'the process caused the improvement' without stronger evidence.

Keep outcome definitions consistent. Google's documentation distinguishes GA4 key events from Google Ads conversions. Mixing them can make a prioritisation change appear better or worse simply because the reporting basis changed.

9. Keep decisions visible and reopen them deliberately

Maintain a decision log with the request, disposition, rationale, owner and reopening condition. Review parked requests when evidence or capacity changes, not merely because someone asks again. Give strategic experiments protected capacity so short-term certainty does not crowd out learning.

Its described workflow lets DailyRise rank opportunities using connected evidence; people accept, park or dismiss them. Accepted opportunities become prepared tasks in RiseProjects. RiseInsights compares predicted and measured impact, but period comparisons do not establish causation.

Connected evidence depends on permissions, source quality and provider access. TikTok Ads and LinkedIn approvals remain pending; planned integrations should not be treated as available. Explore the relevant products and /the-solution, but establish the decision rules first. Software cannot make an unsupported priority defensible.