Salvaging a Mid-Size Campaign Business Case After Silent Disagreement
When a campaign business case has been politely approved but not believed, executives need a corrective playbook before the team starts execution. A short, light guide.
The case got approved. Now everyone is doing something different.
An approved business case that nobody believes is worse than a contested one. The contest is the conversation you needed to have.
The most expensive failure mode for a mid-size campaign business case is silent approval — the case is signed without objection, then each function quietly executes against its own private version of what the campaign should be. By week four, the team is producing assets that look like they belong to three different campaigns. The silent disagreement pattern has done its work invisibly.
The executive corrective at this point is short. It's not a re-approval cycle. It's a 30-minute conversation that surfaces what each function actually believes the case to be, in writing, where the discrepancies become impossible to ignore.
“We had a perfectly approved business case and three teams executing different campaigns. Once I made each team write their version of it on a whiteboard, the gaps were obvious in five minutes.”
- Day 1Convene the function leadsMarketing, sales, product marketing, customer success — anyone whose work touches the campaign. 30 minutes.
- Minutes 0–10Each lead writes their understanding of the caseThree lines: outcome, audience, success metric. Independent. No conferring.
- Minutes 10–20Read aloud, capture differencesThe PM reads each version. Differences are surfaced and named — not debated.
- Minutes 20–30Single re-statementThe executive picks one outcome, one audience, one metric. Function leads commit to executing against that statement. Written and circulated within 24 hours.
Output of the 30-minute correction
0 / 4- A single one-paragraph re-statement of the campaign's outcome, audience, and metric
- An explicit acknowledgement of which functions had been operating against a different version
- A circulation plan: the re-statement is sent within 24 hours and re-read in the next standup
- A two-week checkpoint to test whether execution has aligned with the re-statement
| Signal | Silent disagreement | Active disagreement |
|---|---|---|
| Sign-off speed | Suspiciously fast | Slow, with edits |
| Number of edits requested | Zero or cosmetic | Several, substantive |
| Mid-project escalations | Frequent, indirect ("not what I expected") | Rare — the disagreement was settled |
| Stakeholder presence at reviews | Drops over time | Stays consistent |
| Recovery cost | Re-scoping or re-doing the work | Negotiation time only |
The reason this corrective works at mid-size is that the function leads do not actually disagree on the campaign — they disagree on the case, because the case wasn't precise enough to bind them. Forcing each lead to articulate their version surfaces the imprecision. The executive's pick reduces it to one. It's not elegant, and it doesn't require a re-approval cycle. It does require the executive to spend 30 minutes on something that was supposed to have been settled at sign-off — which is the cost of the original silent disagreement, paid late.
For the prevention of the same pattern, see the twelve common mistakes article; for adjacent corrective work on different patterns, see the implementation single-point-of-failure version.